Use Search Console to find posts losing clicks, work out why each one is declining, then fix that specific cause: update facts and products, deepen the content, answer the question clearly near the top and repair internal links. Only change the published date when the content has genuinely changed. A refresh that targets the real cause usually beats rewriting everything.
I recently ran a refresh programme for 29 declining posts on condoms.uk, and another for 20 education pages on Kwiat’s site. This post is the process I used, including the parts that are easy to get wrong.
Why refresh instead of writing something new
Refreshing an existing post keeps the rankings, links and history it has already earned, so improvements can show sooner than a new page starting from nothing. It also avoids two pages competing for the same searches. A new post makes more sense when the subject or intent has genuinely changed.
An old post that used to earn clicks already has things a new post doesn’t: a URL Google knows, links from other sites and internal links from your own. When it starts losing visibility, fixing it usually builds on that. Publishing a new post on the same subject risks splitting signals between two similar pages.
Step 1: find the posts worth refreshing
Compare the last three to six months with the same period a year earlier in Search Console’s Performance report, on the Pages tab, and sort by lost clicks. The posts that lost the most clicks, and still have meaningful impressions, are usually the best candidates.
- Open Performance in Search Console and switch to the Pages tab.
- Compare the last three to six months with the same months last year, to avoid seasonal noise.
- Sort by click difference to see the biggest losses.
- Filter to your blog or guides section.
- Shortlist posts that still have plenty of impressions. They’re still visible, so there’s something to win back.
- Note posts that matter commercially, such as those linking to your best-selling products or services.
On condoms.uk, that process identified 29 blog posts losing clicks. On Kwiat, it found 20 education pages losing impressions.
Step 2: work out why each post is declining
Posts lose traffic for different reasons: AI Overviews answering the question, competitors publishing better content, outdated information, broken links, falling positions or changing demand. Diagnose each post before rewriting anything, because the right fix depends entirely on the cause, and one site’s declining posts often have several different causes.
| Cause | How to spot it | What to fix |
|---|---|---|
| AI Overviews answering the question | Position holds but clicks fall; an AI Overview answers the search fully | Add what a summary can’t: detail, examples, tools, next steps |
| Competitors improved their content | Position fell; top results now cover more | Compare and cover what’s missing, without copying |
| Outdated information | Old prices, products, figures or advice | Update facts and check every source |
| Discontinued products | Links to products no longer sold | Replace with current products, checking each link is live |
| Broken internal links | Links to removed or redirected pages | Point links straight to live pages |
| Thin content | Much shorter or shallower than the results above it | Deepen where the reader genuinely needs more |
| Falling demand | Impressions down across all results for the topic | Refresh lightly, or leave it |
On condoms.uk, the declines had a mix of causes: AI Overviews answering simple questions, outdated product information, thinner content than competitors and broken internal links. Kwiat’s education pages were losing mainly to AI Overviews and competitors improving their content. Treating every post the same would have missed most of that.
Step 3: refresh the post properly
Keep what already works, including the URL, the parts that rank and any strong sections. Then rewrite and expand the rest, add a short, direct answer near the top, update facts and products, fix internal links and add a genuinely useful FAQ where it helps readers.
- Keep the URL. Changing it throws away the history you’re trying to build on.
- Keep the best of the original. Sections that already rank or earn links shouldn’t be rewritten for the sake of it.
- Answer the main question near the top, in a sentence or two, so readers and AI systems get the point straight away.
- Add first-hand detail. Real examples, photos, measurements and experience are what a summary or competitor can’t copy.
- Update facts, figures and sources, and replace anything you can’t verify.
- Check every product link is live before publishing, especially on sites where products are discontinued regularly.
- Fix internal links, and link to the refreshed post from newer relevant pages.
- Don’t pad. Google’s guidance on helpful content says it doesn’t have a preferred word count.
On condoms.uk, each refresh kept the best of the original, rewrote and expanded the rest, added a short answer passage near the top, fixed internal links and checked every product link was live before publishing. The condoms.uk case study covers the programme.
Step 4: handle dates honestly
Update the visible date only when you’ve substantially changed the content, and label it clearly as updated. Google’s guidance specifically asks whether sites change dates to make pages seem fresh when the content hasn’t substantially changed, so a date change on its own isn’t a refresh.
Google’s helpful content guidance includes this as a warning sign: “Are you changing the date of pages to make them seem fresh when the content has not substantially changed?” Its guidance on byline dates explains that Google estimates when a page was published or significantly updated using several factors, and recommends a visible, clearly labelled date on the page.
In practice:
- Substantial rewrite: show “Updated [date]”, and keep the original published date if your template supports both.
- Small correction: fix it without changing the date, or note the correction if it matters to readers.
- Keep dates consistent between the visible page and any structured data.
Step 5: measure the result
Record each refreshed post’s clicks, impressions and position before publishing, then compare the same measures over the following weeks and months against the same period the year before. Give Google time to recrawl, and judge the programme as a whole rather than one post at a time.
- Log the refresh date for every post in a spreadsheet.
- Request indexing in Search Console’s URL Inspection tool for priority posts.
- Check after four weeks, then again at three months.
- Compare against last year for the same weeks, not just before and after.
- Look for patterns across the programme. If refreshes aimed at one cause worked better than others, adjust the approach.
On condoms.uk, refreshed guides were among the strongest performers. Comparing six months with the six before, the sizing guide earned 68% more clicks and “does lube expire” earned a third more, from a position it already held.
What I learned
The biggest improvement to my refresh process was diagnosing each post before touching it. When I started treating “losing traffic” as a symptom rather than a single problem, a lot of refreshes became smaller and more targeted: a product update here, broken links there, a clearer answer at the top.
The second lesson was checking every product link before publishing. On a site where stock changes often, a refreshed post that sends readers to a discontinued product undoes much of the work.
If you’d like a refresh programme run for your site, content refresh covers diagnosis, rewriting and measurement.
FAQ
How often should I update old blog posts?
There’s no fixed schedule. Review your content with Search Console every few months, and refresh posts when they lose clicks, when information becomes outdated or when better content appears in search results. Evergreen posts on subjects that change quickly need checking more often than posts on stable topics.
Should I change the date when I update a blog post?
Only if you’ve substantially changed the content, and label it clearly as updated. Google’s helpful content guidance specifically warns against changing dates to make pages seem fresh when the content hasn’t substantially changed. For small corrections, fix the post without changing the date.
Should I delete old blog posts that get no traffic?
Not automatically. Check whether a post has links from other sites, supports other pages or answers a question customers still ask. Posts that are outdated, thin and unused can be improved, merged into a stronger post with a redirect, or removed. Deleting content just to look fresh won’t help rankings.
How long does it take to see results from refreshing content?
Once Google recrawls a refreshed post, changes can show in Search Console within a few weeks, though some take several months. Requesting indexing for priority posts can help Google find the changes sooner. Compare results against the same period last year to allow for seasonal changes in demand.
More on content:
If you’ve got posts losing traffic, get in touch or ask for a free assessment.
Sources
- Creating helpful, reliable, people-first content, Google Search Central, accessed 15 September 2026. Supports: no preferred word count, changing dates to seem fresh.
- Influence your byline dates in Google Search, Google Search Central, accessed 15 September 2026. Supports: how Google estimates published and updated dates, visible labelled dates.
- condoms.uk, content refresh programme and Search Console data, 2026. Supports: 29 declining posts, their causes and the refresh process.
- Kwiat, Search Console data and education page rewrites, 2026. Supports: 20 education pages losing impressions and the causes.