You open Search Console on a Monday and look at a post that used to be your best performer. No crash, no penalty email. Just a line that has been sloping down for a year, like a tyre with a slow leak.
That slope has a name: content decay. And the usual reaction, publishing more new posts to make up the difference, is like buying a new tyre every month instead of patching the one you have. The patch has a name too: a content refresh.
The problem: pages age, the web doesn’t wait
A page that ranked well two years ago was the best answer someone could find two years ago. Since then, a few things have probably changed:
- The facts moved. Prices, tool features, policies and screenshots went out of date.
- Competitors published newer, more complete pages on the same question.
- What searchers want changed. A query that once wanted a long guide now wants a quick comparison, or the reverse.
- Google started answering part of the question on the results page itself, including in AI Overviews.
- Your own site grew, and newer posts may now compete with the old one for the same query.
None of these is a punishment. The page simply stopped being the best answer, and search noticed. A content refresh is the work of making it the best answer again.
Before → after: old page, old facts → slow slide becomes same URL, current facts, sharper answer → a fair second chance. No promise beyond that; a fair second chance is what you can control.
Step 1: find the decaying pages
You need the Search Console Performance report, which shows clicks, impressions, click-through rate and average position for your site in Google Search (Google’s help page).
- Open Performance → Search results.
- Set the date filter to compare the last three months with the same three months a year earlier, so seasonal swings cancel out.
- Switch to the Pages tab and sort by the change in clicks.
- Write down the pages that lost the most clicks in absolute terms. A page that went from 2,000 to 1,400 matters more than one that went from 20 to 5.
Then, for each page, look at why:
- Impressions steady, clicks down: you are still being shown but chosen less. Check the title and description, and look at what now sits above you on the results page.
- Impressions down, position down: others overtook you. Read the pages that now rank ahead.
- Queries changed: click into the page and look at its Queries tab. If the queries drifted, the intent drifted.
Note that Google counts clicks from AI Overviews and AI Mode in the same Performance report, under the “Web” search type, not in a separate one (Google).
Step 2: decide what each page needs
Not every decaying page deserves the same treatment. Four honest options:
| Situation | Action |
|---|---|
| Still the right topic, facts out of date | Refresh in place: same URL, updated content |
| Right topic, wrong format for today’s searchers | Rewrite the page around the current intent, keep the URL |
| Two of your pages answer the same question | Merge into the stronger one and 301-redirect the other |
| Topic no longer relevant to your business or readers | Leave it, or retire it with a redirect to the closest useful page |
One warning on that last row. Google’s own guidance lists “removing a lot of older content primarily because you believe it will help your search rankings” as a sign of search-engine-first content (Google Search Central). Retire pages because they no longer help readers, not as a ranking trick.
Step 3: refresh for real
A refresh is not a new date at the top. Google asks, in the same guidance, whether you are “changing the date of pages to make them seem fresh when the content has not substantially changed.” If the answer is yes, that is the wrong kind of refresh.
What a real refresh includes:
- Re-check every fact. Prices, features, steps, screenshots, policy quotes. Link the primary source. If something cannot be confirmed any more, say so or cut it.
- Re-read the current results. What do the pages now ranking cover that you do not? Add what genuinely helps; skip what is padding.
- Put the answer first. Searchers and AI summaries both reward a direct answer near the top. This is the same habit behind answer engine optimization: a page that states its point plainly is a page that can be quoted.
- Cut what no longer earns its place. Dated asides, dead links, sections about tools that no longer exist.
- Fix internal links. Link the refreshed page from newer related posts, and check it links out to your current pages, not retired ones.
- Update the title and description if the intent shifted, keeping the main keyword.
- Then change the “updated” date, because now it is true.
After publishing, you can ask Google to recrawl the URL with the URL Inspection tool in Search Console: inspect the URL, then click “Request indexing” on the inspection result (Search Console Help).
A worked example (hypothetical)
Say you have a post called “How to back up a WordPress site”, written a few years ago. Clicks are down by a third against last year; impressions are almost flat.
- Diagnosis: still shown, chosen less. The results page now shows newer guides above you, and two of the backup plugins you recommended have changed their free tiers.
- Decision: refresh in place. The topic is still right, the facts are not.
- Work: re-check each plugin on its own site, rewrite the opening as a three-line answer (what to back up, where to store it, how often), replace the outdated steps, add a short “how to test a restore” section the old post skipped, link it from your newer security posts.
- Then: update the date, request a recrawl, and compare the same date ranges again in eight to twelve weeks.
If it recovers, good. If it does not, you have still replaced a wrong page with a right one, which is the part you owe your readers either way.
Common mistakes
- Date-only refreshes. Covered above. Google names it; readers notice it too.
- Changing the URL. A refresh keeps the URL. If you must move it, 301-redirect the old one.
- Rewriting a page that was fine. If a drop is seasonal or site-wide, the page is not the problem. Compare year over year and check the whole site before blaming one post.
- Bulk AI rewrites with no checking. Running a hundred posts through a tool to “refresh” them can make them worse. AI help is fine; unchecked AI output at scale is the risk. If you are unsure where the line sits, read does Google penalize AI content.
- Refreshing once. Decay is continuous. Put the review on a calendar: quarterly for your top pages is a reasonable start.
Refresh or publish new?
My stance: refresh first, publish second. A page that already has history, links and a URL Google knows is usually a cheaper win than a brand-new post starting from zero. New posts are for questions you have not answered yet, not for questions you answered badly or a long time ago.
If you want the publishing side handled, Wayback Press Autopilot posts new articles on keywords people search with intent to visit, on a schedule, each checked before it goes live, with a Search Console report. No traffic promise; just the work and the numbers.
A slow leak never fixes itself. It just waits for a longer drive.