Are pages that used to bring in steady search traffic slowly losing clicks? Then you probably don’t need more new content. You need a content refresh SEO process. Find the pages that are decaying and work out why. Then improve, merge, redirect or leave each one based on evidence, not habit.
In this guide I walk through that process from start to finish. I cover how to spot decline in Search Console and GA4, and how to choose the right action for each page. I also cover what a real refresh includes, how to handle URLs and dates honestly, and how to tell if the work paid off.
Why Good Pages Lose Traffic
Content decay (a slow loss of traffic over time) rarely has a single cause. Before you touch a page, it helps to know which of these is most likely behind the drop. Each one points to a different fix.
- The facts went stale. Prices, tool names, screenshots, laws and product features change. A page that was accurate two years ago can now be quietly wrong.
- Search intent shifted. People searching the same phrase may now want a comparison, a checklist or a quick definition instead of a long explainer.
- Competitors improved. Your page didn’t get worse, but others got better, more specific or easier to use.
- The results page changed. AI Overviews, videos, forums and other features can push classic results further down. So clicks fall even when rankings hold.
- Freshness matters for the query. Google says it has “query deserves freshness” systems. They show newer content for searches where people expect it. For those topics, an old page starts at a disadvantage.
- You compete with yourself. Two or three of your own pages target the same topic, and none of them is clearly the best answer.
- Something technical broke. A redirect, canonical tag, noindex or template change can look like decay when it’s really an error.
I always rule out the technical causes first. There’s no point rewriting an article that dropped because a migration pointed its canonical tag at the wrong URL.
Step 1: Find Decaying Pages in Search Console
Search Console’s Performance report is the best place to start. It shows clicks, impressions, average position and click-through rate for each page. It holds up to 16 months of data. That’s enough to compare the same periods across two years.
- Open Performance and choose Search results.
- Click the date filter, pick the Compare tab and choose two equal periods. I like the last three months against the same three months a year earlier. It cancels out seasonal swings.
- Switch to the Pages tab and turn on all four metrics.
- Sort by the clicks difference to see which pages lost the most traffic in real numbers.
- Export the table so you can add notes and decisions for each URL.
Then read the pattern for each page, not just the size of the drop:
- Impressions steady, clicks down: you still rank, but fewer people click. Look at the results page itself, and at your title and snippet.
- Impressions and position both down: Google now ranks you lower. This usually points to stale content, a weaker answer or stronger competitors.
- Sudden drop on one date: check for a site change or a Google update around that date. Our breakdown of the May 2026 core update and what to check covers how to tell an update hit from a site problem.
- Slow slide over many months: classic content decay. In my experience, this is usually the best candidate for a refresh.
Next, click into one declining page. Open the Queries tab with the same comparison. This shows which searches you lost. Often a page keeps its main keyword but loses dozens of longer questions. Newer, more specific pages now answer them better.
Keep in mind that clicks from AI features in Google Search, such as AI Overviews, are counted within the normal web search data. A falling click-through rate on a page with healthy impressions is often a sign that the answer now shows above the blue links.
Step 2: Confirm the Business Impact in GA4
Search Console tells you about search visibility. GA4 tells you if the decline really matters to the business.
- Go to Reports, then Engagement, then Landing page.
- Add a comparison or filter so you only see sessions where the session default channel group is Organic Search.
- Compare the same two date ranges you used in Search Console.
- Look at sessions, engagement rate and key events for each declining URL.
Take a page that lost 40% of its traffic but never drove a sign-up, enquiry or sale. It’s a lower priority than a page that lost 15% and used to bring in leads. If you want a view of this you can reuse, a free SEO dashboard in Looker Studio can put both data sources side by side. Then you don’t rebuild the comparison every quarter.
After these two steps, you should have a short list. For each URL, note the clicks lost, the queries lost, the business value and your best guess at the cause.
Step 3: Decide Whether to Refresh, Merge, Redirect or Leave It
Not every declining page deserves a rewrite. Some are better combined, some should go, and some are fine as they are. My guide to auditing a site for unhelpful content covers how I decide which pages to cut.
| Situation | Action | What to do |
|---|---|---|
| Topic still matters, page still matches intent, but it’s dated or thin | Refresh | Keep the URL and improve the content in place. |
| Two or more of your pages cover the same topic and split the traffic | Merge | Combine the best parts into the strongest URL and redirect the others to it. |
| Topic is obsolete, but a closely related page now covers it | Redirect | Send a permanent redirect to the most relevant replacement. |
| Topic is obsolete and nothing on the site replaces it | Remove | Let the URL return a 404 or 410 rather than redirecting it to an unrelated page. |
| Drop is seasonal, small, or explained by a results-page change you can’t influence | Leave | Note it, and check again next quarter. |
A few practical rules I use make these calls easier:
- Merge when the pages answer the same question. If a reader would be happy landing on either one, they belong together.
- Redirect only to a true equivalent. Pointing a retired page at your homepage doesn’t help the reader. It also doesn’t carry the old page’s relevance over.
- Leave pages that still convert. A page with lower traffic but steady enquiries may only need a light fact check.
- Check links before removing. If a page has earned links from other sites, a redirect to a relevant replacement is usually better than letting it 404.
Step 4: What a Real Content Refresh Includes
A real refresh makes the page more useful to the person searching today. Swapping a few words, adding the current year to the title or moving paragraphs around doesn’t count. Work through the page in this order.
Re-Check the Search Intent
Search your main query and read the current first page of results. Note the format that wins most: guides, lists, comparison pages, tools or product pages. Say the results now favour a quick checklist, and your page is a 3,000-word essay. Then the fix is restructuring, not adding more words.
Update Facts, Figures and Screenshots
Go through the page line by line. Check every claim that can date: prices, feature names, menu paths, rules, statistics and screenshots. Replace anything outdated. Remove statistics you can no longer trace to a reliable source. Don’t keep them just for decoration.
Answer the Questions People Ask Now
Use the queries you found in Search Console. Add the People Also Ask box and related searches for your main keyword. Together they give you the questions readers have today. Then:
- Add a short section for each relevant question your page doesn’t yet answer.
- Cut sections that answer questions nobody asks anymore.
- Move the most important answer closer to the top.
For example, an old guide to setting up a newsletter might have been written around one email tool. Today, readers may also ask how to stay out of spam folders and what sender authentication is. They may ask how to measure open rates now that they’re less reliable. Those are new sections, not new pages.
Structure the Page so AI Answers Can Use It
AI Overviews and AI assistants pull short passages that make sense on their own. Pages that are easy to quote tend to share a few traits:
- A direct answer in the first sentence or two under each heading.
- Headings that match how people word the question.
- Numbered steps for processes, and short lists for options.
- Clear definitions and specific details such as numbers, names and conditions.
Our guide on writing content AI assistants can quote goes deeper on passage structure. These changes help human readers too, which is the point.
Add Fresh Examples and First-Hand Detail
Replace general or dated examples with current ones that show the advice in action. If you have real experience with the topic, add it: what you tested, what went wrong, what you’d do differently. That kind of detail is hard for competitors to copy. It also fits what Google describes as helpful, people-first content. This is the part of a refresh I think most people skip.
Rework the Title, Snippet and Internal Links
- Rewrite the title tag and meta description if the page’s focus has changed, or if click-through rate fell while impressions held.
- Link from the refreshed page to newer related articles you’ve published since it went live.
- Link to the refreshed page from relevant newer pages, using descriptive anchor text.
- Fix or remove broken outbound links.
Old pages often have too few internal links. They were written before the rest of the topic cluster existed. Our guide to building topic clusters with internal links shows how to fit a refreshed page back into its cluster.
Don’t Fake Freshness: What Google Says About Changing Dates
It’s tempting to change the date on a page and call it updated. Google speaks to this directly. Its guidance on creating helpful, reliable, people-first content lists questions to ask yourself. One is whether you’re “changing the date of pages to make them seem fresh when the content has not substantially changed.”
The same guidance warns against adding or removing large amounts of content mainly because you think it will help rankings. Its answer is that it won’t. The message is clear: update pages because readers need better information, not to send a signal.
Google also says its systems look at several factors to estimate when a page was published or greatly updated. It doesn’t trust a single date. And readers who spot old content under a new date lose trust quickly.
Here is the house rule I follow:
- Substantial update (new sections, corrected facts, reworked advice): change the “last updated” date.
- Minor edit (typo, broken link, small wording change): leave the date alone.
- Complete rewrite on the same topic: keep the original publish date and show an updated date, unless it’s truly a new piece.
Handling URLs and Dates When You Refresh
Keep the URL Whenever You Can
The existing URL has history: links from other sites, internal links and bookmarks. Refreshing in place keeps all of that. Only change the URL when the old one is truly misleading. For example, it might contain a year or a product name that no longer fits. If you do change it, set up a permanent server-side redirect from the old URL to the new one. Then update your internal links to point at the new address.
When you merge pages, the same applies. Keep the URL with the strongest history. Move the useful content into it, and redirect the others.
Set datePublished and dateModified Correctly
If you use Article or BlogPosting structured data, two properties matter here:
datePublished: when the page first went live. This doesn’t change on a refresh.dateModified: when the page was last meaningfully updated. This changes on a substantial refresh.
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "How to Choose a Business Email Provider",
"datePublished": "2023-03-14T09:00:00+00:00",
"dateModified": "2026-06-12T14:30:00+01:00"
}
Google’s documentation on influencing byline dates in Google Search gives a few rules. Keep visible dates and structured data consistent. Label them clearly with words like “Published” and “Last updated”. Include a time zone where you can, and avoid future dates. Keep other dates on the page to a minimum so they don’t confuse its systems. If your CMS bumps dateModified on every save, switch that off or make it a manual choice. I see this setting cause fake freshness by accident quite often.
Keep Your Sitemap Honest
Update the lastmod value in your XML sitemap when a page changes in a big way. Google has said it uses lastmod when it’s consistently and verifiably accurate. A sitemap that marks every page as changed every day teaches Google to ignore the field.
Step 5: Publish, Request a Recrawl and Promote It
- Publish the refreshed page. Check it displays correctly on mobile and desktop.
- If you changed the structured data, test it with the Rich Results Test.
- In Search Console, inspect the URL and use Request indexing so Google crawls it again sooner.
- Add a dated note to your tracking sheet with what changed and why.
- Share it where it’s relevant: your newsletter, social channels or sales team, if the update is truly useful to them.
Measuring Your Content Refresh SEO Results
Give a refreshed page time before you judge it. Recrawling, reprocessing and ranking changes can take from days to several weeks. It depends on how often Google visits the page and how competitive the query is. I do a first check around four weeks after publishing, and a fuller review at eight to twelve weeks.
Use the same tools you used to find the decline:
- Search Console: compare an equal period after the refresh with the period just before it. If the topic is seasonal, compare with the same period last year too. Track clicks, impressions, average position and the number of queries the page appears for.
- GA4: check organic sessions, engagement rate and key events on the landing page over the same periods.
- Your notes: match changes against what you did. If new sections brought in new queries, the approach is working and worth repeating on similar pages.
Measure merged and redirected pages as a group. Add up the clicks of all the old URLs before the change. Compare that total with the surviving URL afterwards. Judging the destination page alone will make a merge look better than it was. Judging the removed pages will make it look like a loss.
If a refresh doesn’t move the numbers after three months, go back to the diagnosis. The cause may have been intent, competition or a results-page change, not the content itself.
Conclusion
A good content refresh SEO process starts with evidence, not guesswork. Use Search Console and GA4 to find pages that are losing traffic that matters. Decide if each one should be refreshed, merged, redirected or left alone. Then make changes that truly improve the answer. Keep your URL, update dates only when the content has substantially changed, and measure the result over weeks, not days.
To start your content refresh SEO work, run the date comparison in Search Console today. Pick the three pages with the biggest drop in valuable traffic. Before you rewrite anything, check each one against our guide to what Google means by helpful content in 2026, so your refresh fixes the real problem.



