Quick answer: to refresh an old blog post, first find posts that are losing clicks or ranking just off page one in Google Search Console. Then update outdated facts, add a direct answer near the top, cover the questions the page already gets impressions for, improve the title and description, add internal links, and change the "last updated" date only when the content has meaningfully changed. Finally, request reindexing and compare results after four to eight weeks.
Why refreshing beats publishing more
Publishing new posts is the default habit. But older pages already have history: they are indexed, may have links, and Google already understands roughly what they are about. Improving them often moves results faster than starting from zero.
Content also decays. Competitors publish better answers, tools change, statistics age, and searchers' expectations move. A post that ranked well two years ago can slide quietly until nobody reads it. AI assistants add a new reason: if your page states outdated prices or steps, an AI tool may repeat them, or prefer a fresher source.
Step 1: Find the posts worth refreshing
Open Google Search Console → Performance → Search results, choose Pages, and compare the last three months with the previous period or the same period last year. Look for three patterns:
| Pattern | What it means | Priority |
|---|---|---|
| Clicks and impressions falling | Content decay or a competitor overtook you | High |
| Many impressions, average position 5–20 | You almost rank: "striking distance" | High |
| High impressions, very low click-through rate | Title or description is not compelling, or the AI Overview answers it | Medium |
| No impressions at all after six months | Topic mismatch, thin content or indexing issue | Decide: improve, merge or remove |
Then click into a page and open the Queries tab. These are the searches Google already associates with the page, including ones you never targeted. They are your refresh brief.
Step 2: Decide what to do with each post
- Update when the topic is still relevant and the page is the right one for it.
- Merge when two or more posts compete for the same queries. Combine the best parts into one page and redirect the others to it with a 301.
- Remove or noindex when a post has no audience, no links and no business purpose, such as old company news. Redirect it if it has links.
Step 3: Make changes that matter
Fix what is wrong or outdated
Update statistics, screenshots, prices, laws, tool names and steps. Remove dead links. If something you recommended no longer works, say so.
Lead with the answer
Add a two to three sentence direct answer to the main question right under the title. It helps readers, featured snippets and AI summaries. See our AEO guide for the format.
Cover the queries you are already getting
For each relevant query in Search Console that the page does not answer well, add a short section or an FAQ entry. This is usually the change that moves striking-distance pages onto page one.
Add experience and evidence
Include your own examples, results, photos or opinions based on doing the work. Name the author and link to their profile. This is what separates your page from the many others written from the same top ten results, as explained in our E-E-A-T guide.
Improve the title and description
Make the title match the main query and promise something specific. Rewrite the meta description as a short pitch for the click.
Strengthen internal links
Link to the refreshed post from newer related posts and from the relevant service page, and link out from it to related cluster articles. Our guide to topic clusters explains the structure.
Check the technical basics
Compress heavy images, make sure the page passes Core Web Vitals on mobile, and confirm the structured data (Article, author, FAQ where visible) still matches the content.
Step 4: Update the date honestly
Show a "last updated" date and update dateModified in your structured data when you make a substantial change. Do not change dates for a typo fix or to look fresh. Google has said that changing dates without meaningful changes is not a helpful practice, and readers notice when "updated this month" pages contain old information.
Step 5: Tell search engines and measure
- Use URL Inspection → Request indexing in Search Console for important pages.
- Submit the URL through IndexNow (supported by Bing and others) or Bing Webmaster Tools, which also helps AI tools that rely on Bing's index.
- Note the date of the change, then compare clicks, impressions, position and key events four to eight weeks later. Our guide on how long SEO takes explains what to expect.
- If you track AI referrals as described in how to track AI search traffic in GA4, watch whether the refreshed page starts receiving them.
A refresh rhythm that works
| When | What |
|---|---|
| Monthly | Review Search Console for falling pages and striking-distance queries |
| Quarterly | Refresh the top five to ten opportunities |
| Yearly | Audit the whole blog: update, merge or remove |
| Whenever facts change | Update affected posts immediately |
Frequently asked questions
How often should I update blog posts?
Update when the content is outdated or underperforming, not on a fixed schedule. Fast-changing topics may need quarterly updates; evergreen guides may only need a yearly check.
Should I change the URL when I refresh a post?
No, unless the current URL is truly misleading. Keeping the URL keeps the page's history and links. If you must change it, use a 301 redirect.
Will refreshing old content hurt my rankings?
Rarely, if you keep what already works and add value. The risk comes from removing sections that ranked or changing the topic of the page. Check the queries before you cut anything.
Is it better to update or rewrite from scratch?
Usually update. Rewrite only when the page no longer matches what searchers want or the original is too weak to save.
Want a list of the posts on your site that could win back traffic fastest? Our SEO content and copywriting service can start with a refresh audit, and our technical SEO checklist covers the basics underneath.
