Content refresh
Maps every existing blog against the visibility queries. Refresh candidates flagged. Write button fires the rewrite pipeline, preserving URL and authority.
Executive summary
Three short paragraphs explaining the feature and value.
Content refresh maps every existing blog from the Brand sitemap Blogs tab against the workspace visibility queries. Where a query is relevant to a blog but the blog is not currently surfacing for it, the row is flagged as a refresh candidate. The marketer sees exactly which existing content is leaking visibility and could be reclaimed.
Write per row fires the rewrite pipeline against that specific blog. The pipeline preserves the URL (so any backlinks, social shares, and search rankings stay intact), preserves the publish date and author, and updates the body content to incorporate the missing query, brand voice, ICP context, and competitor coverage gap. URL stays, authority stays, content gets sharper.
Content refresh is the highest leverage content move most brands have available. Writing a new blog costs new authority, new backlinks, new time for search engines to discover. Refreshing an existing blog uses the authority already earned, the backlinks already pointing at it, and an URL already indexed. Same effort, materially better return on investment.
Key highlights
Five capability points teams should know about quickly.
- Maps existing blogs against visibility queries
- Refresh candidates flagged automatically per row
- Write button fires rewrite pipeline per blog
- URL, authority, and metadata preserved across rewrites
- Highest leverage content move most brands have
Top FAQs
Five common questions answered for fast practical clarity.
How does the refresh candidate detection work?
For every blog in the Brand sitemap Blogs tab, the system asks: which visibility queries should this blog plausibly surface for, and does it currently? Blogs that should surface but do not get flagged. The judgement combines semantic relevance, current SERP and AI search position, and the blog's own keyword targeting derived from its current content.
What does the rewrite pipeline actually preserve?
URL, publish date, author byline, primary keyword targeting, internal links into and out of the blog, and any custom metadata fields like custom OG image. What changes is the body content, the meta description, the first paragraph, and any structural additions like FAQ schema or summary blocks needed to win the missing query. Surgical rather than wholesale.
Can I review the rewrite before publishing?
Yes. Every rewrite lands in a draft state on the Versioned scans surface. The marketer reviews the new version against the live one side by side, edits anything that needs human touch, and clicks publish to push the change. Drafts can sit indefinitely; nothing goes live without explicit human approval at the publish step.
How many refreshes can run in parallel?
Up to ten at a time per workspace, depending on plan tier. Each refresh takes two to three minutes from click to draft. For larger refresh sprints, the system queues additional requests and processes them as slots free up. Progress is visible in the workspace activity log so marketers can see the queue and current state.
What happens to old versions?
Every refresh creates a new version visible in the Versioned scans surface. Old versions remain accessible. Users can roll back to any prior version if a rewrite did not land well, view any version, or delete versions no longer needed. The default active version is the most recent published one, but any version can be reactivated.