Refresh a decaying page
Improve a decaying page in place with a refresh Page Brief tied to its existing URL, so you keep the page's history instead of spawning a duplicate.
When a page starts losing ground, you refresh it in place. A refresh creates a Page Brief tied to the page's existing URL, so you improve the page you have instead of building a new one beside it. You keep the page's whole history: its rankings, its backlinks, its accumulated signal. That's the difference between fixing an asset and abandoning it.
The mechanics ride on the creation pipeline. A refresh brief is the third way a brief can start, alongside accepting an Opportunity and starting from scratch. What makes it a refresh is the tie to a live URL.
Why fix in place instead of starting over
A new page on a new URL throws away everything the old page earned. The old URL still has its rank, its links, and its track record with the engines that crawl it. Spin up a duplicate and you split that equity across two pages, then compete with yourself for the same query.
Decay is the reason this matters now rather than later. Content that sits untouched for more than about 30 days earns far fewer AI citations than fresh content, and a page that's slipping keeps slipping until someone tends it. A refresh in place lets you reverse the slide while holding onto the foundation the page already built.
The refresh steps
Spot the decaying page
Find the page that's slipping in your Page Portfolio. The signals to watch are a falling position, traffic eroding across its early-versus-late windows, and a Big Picture status that's moved toward Needs Work. The detail panel reads out what's happening and what to fix first.
Start a refresh brief on the live URL
Create a refresh Page Brief from the live page. It stays attached to the existing URL, so the work lands on the page that already has history rather than a fresh address. GrowthOS also routes overlapping Opportunities here, so a query that matches an existing page becomes a refresh instead of a duplicate.
Let an agent rework the content
With the brief set, an agent reworks the outline and the draft against the current search intent and what competitors now cover. The page may have been right a year ago and wrong today; this is where it catches up. You edit and direct in the editor, the same as any draft.
Review and republish
Review the reworked draft inside and outside the workspace, apply the feedback worth applying, and publish. Because the brief is tied to the live URL, publishing updates the existing page record. The page keeps its address and its history, now with better content on it.
After you republish
A refresh isn't done when it ships. The point was to reverse a decline, so confirm it did. Watch the page's performance windows for the lift and read the next progress snapshot for the change. Track impact covers how to tell whether the refresh worked.
Common questions
How is a refresh different from a new page? A new page gets a new URL and starts its history at zero. A refresh stays on the existing URL and builds on the rank and links the page already earned.
What if an Opportunity overlaps a page I already have? GrowthOS catches the overlap and routes it to a refresh of the existing page rather than spawning a duplicate, which keeps your Page Portfolio clean.
How often should I refresh a page? Let decay drive it. When a page's position and traffic start sliding, or its content has aged past relevance, that's the trigger. The portfolio surfaces the pages that need attention so you're not guessing.
Where to go next
Last updated at June 3, 2026
Optimize
Keep every page fresh, relevant, and converting. Optimization is the steady state of running a site, not a one-time project. The loop never stops.
Track whether it worked
Confirm a refresh paid off through the page's performance windows, the progress snapshot's what-changed view, and, as it rolls out, AI citations.