To update old blog posts for SEO, start with posts losing clicks or ranking just off the top positions in Search Console. Decide whether to refresh, merge, redirect or delete each one, then improve what matters: current facts, a closer match to search intent, fresh examples and internal links. Keep the URL, and change the date only after substantial updates.
A content refresh is usually faster than writing from scratch, because the page already exists, is indexed and has some history with Google. What doesn’t work is cosmetic freshening, such as a new date on unchanged content or a handful of swapped words.
This guide explains how to update old blog posts for SEO: how to diagnose a drop, how to find candidates, the choice between refreshing, merging and deleting, what a real update changes, the date question, and a checklist you can reuse every quarter.
Key takeaways
- Find refresh candidates by comparing the last three months with the previous period in Search Console and sorting pages by lost clicks.
- Prioritize posts with plenty of impressions and an average position between roughly 5 and 20; they’re visible but not yet earning clicks.
- Refresh posts people still search for, merge overlapping posts with a 301 redirect, and delete only pages with no value, traffic or links.
- Change the visible date and dateModified only after substantial changes; Google warns against making pages look fresh without real updates.
- Rule out indexing problems, seasonality and algorithm updates before rewriting a post that lost traffic.
What is content decay and what causes it?
Content decay is the gradual loss of search clicks on a page that used to perform well. The usual causes are newer and better competing pages, a change in what searchers want, facts that have gone out of date, and your own newer posts competing for the same query.
Before rewriting anything, rule out causes a rewrite won’t fix. Google’s guide to debugging traffic drops lists algorithm updates, technical issues, security and spam problems, seasonality and site moves as the main reasons traffic falls.
- Indexing: paste the URL into the inspection bar at the top of Search Console to confirm the page is indexed and not blocked by a stray
noindextag. If many pages dropped at once, run a full SEO audit with free tools first. - Seasonality: check the main query in Google Trends. If interest fell everywhere, your page may be fine.
- Small moves: a slip from position 2 to 4 can reverse on its own. Google advises against radical changes to a page that is already performing well.
- Clicks down, impressions steady: Google suggests your title and snippet may be less appealing than other results, so start there.
How do you find old blog posts to update for SEO?
Compare recent performance with an earlier period in Search Console, sort pages by lost clicks, and shortlist posts that still get impressions. Those pages already have Google’s attention; they need a better answer, not a new URL.
- Open the Performance report for search results, click the date filter, choose Compare, and set the last three months against the previous three, or against the same months last year for seasonal topics.
- Click + Add filter, choose Pages, then URLs containing and enter
/blog/so only posts appear. - Open the Pages tab. With a comparison active, the table adds a Difference column; sort by the clicks difference to put the biggest losers first.
- Switch the chart to weekly granularity. Google recommends weekly or monthly views for date comparisons because they remove day-of-the-week effects.
- Click a shortlisted page, then open the Queries tab to see which searches it lost, where it now ranks and its click-through rate.
Then add three more groups to the shortlist:
- Near misses: posts with plenty of impressions and an average position between roughly 5 and 20. A better answer can move them into positions that earn clicks.
- Low click-through rate: Search Console’s help suggests looking for queries with high impressions and low CTR as chances to improve the page title and description.
- Outdated posts: anything with old prices, screenshots, menu names, rules or year references, whatever its traffic. Wrong information damages trust even on quiet pages.
For a large blog, export the Pages table and score each post by clicks lost, impressions and inquiries it still brings in GA4. That spreadsheet is the core of a content audit, which our content marketing specialists can also run for you.
Should you refresh, merge, redirect or delete an old post?
Refresh posts on questions people still search for; merge posts that compete for the same query; redirect posts whose topic is covered better elsewhere; and delete only pages with no useful content, traffic or links. When in doubt, improving a page is safer than removing it.
| Situation | Action | How to do it |
|---|---|---|
| Topic still searched; post is outdated, thin or slipping | Refresh | Update it in place on the same URL using the checklist below |
| Two or more posts answer the same question and split the clicks | Merge | Combine the best parts on the stronger URL, then 301 redirect the others to it |
| Post is obsolete, but a newer page covers the topic better | Redirect | 301 redirect to the closest relevant page, not the home page |
| No search demand, no links, no inquiries and nothing useful to readers | Delete | Remove the page so it returns a 404 or 410 status, and remove internal links to it |
| Performing well, with a small recent dip | Leave it | Monitor for a few weeks before changing anything |
Google recommends a permanent server-side redirect, meaning a 301 or 308 status, when a page moves for good. Pruning in bulk to look fresh is a different matter: Google says adding or removing lots of content mainly to make a site seem fresh won’t help its rankings.
What does a real content refresh change?
A real refresh makes the page more useful to today’s searcher: current facts, a better match for intent, new first-hand examples, fuller answers to related questions and stronger internal links. Changing a few words and the date is not a refresh.
The content
- Search the main query again and compare your post with the current top results: format, angle and questions covered. If intent has shifted, say from definitions to comparisons, restructure the post.
- Replace outdated statistics, prices, screenshots, menu paths and product names, and link each fact to its source.
- Add what you’ve learned since publishing: new examples, recent customer questions, your own photos and mistakes to avoid.
- Rewrite the opening so the first paragraph answers the question directly, and cut sections that no longer help.
Links, snippet and technical details
- Rewrite the title and meta description if the page earns impressions but few clicks.
- Fix broken links, and link from the post to newer related posts and the matching service page.
- Add links to the refreshed post from newer articles on the same topic.
- Keep the same URL. If you must change the slug, 301 redirect the old one.
- Check the author bio, image alt text and Article structured data while you’re editing.
New sections follow the same rules as a new article; our SEO blog post writing guide covers answer-first structure, headings and links.
Should you change the published date when you update a post?
Change the visible “last updated” date only when you’ve made substantial changes, and keep the original publish date. Google’s people-first content guidance lists changing dates to make pages seem fresh, without substantial changes, as a warning sign.
- Label dates clearly: Google’s byline-date documentation recommends labels such as “Published” or “Last updated”, so “Published March 2024, last updated September 2026” is fine.
- Structured data: keep
datePublishedas the original date and setdateModifiedto the update date. Google asks that visible and structured dates match. - Sitemap:
lastmodshould reflect significant updates. Google uses it only when it’s consistently accurate, and treats changes to main content, structured data or links as significant, but not a new copyright year. - Small fixes: correcting a typo or swapping one link doesn’t justify a new date.
How do you get an updated post recrawled and measure the results?
Link to the updated post from relevant pages, confirm it’s in your sitemap with an accurate lastmod, and request indexing if it matters. Then compare an equal period before and after the update once a few weeks have passed.
- Request indexing: inspect the URL in Search Console and click Request indexing. There’s a daily limit, and asking repeatedly for the same URL won’t get it crawled faster.
- Mark the date: right-click the Performance chart and choose Add annotation on the day you republish, so the change is visible when you review the data.
- Compare fairly: after four to six weeks, filter to the page and compare equal periods before and after, using weekly granularity.
- Track the full picture: clicks, impressions, position and CTR in Search Console; key events in GA4; and appearances in AI Overviews and AI Mode in the Generative AI performance report.
- Decide next steps: if nothing improves after two or three months, revisit intent or consider merging the post into a stronger page.
Build refreshes into your publishing rhythm rather than treating them as a rescue job. Our guide to how often to publish new posts shows how to balance them against updates, and a quarterly review slot belongs in your content marketing plan.
What goes on a content refresh checklist?
This table condenses how to update old blog posts for SEO into ten steps. Use them in order for every post, so nothing important gets skipped.
| Step | What to do | Where |
|---|---|---|
| 1. Diagnose | Rule out indexing problems, seasonality and algorithm updates | URL Inspection, Google Trends |
| 2. Decide | Refresh, merge, redirect, delete or leave alone | Decision table above |
| 3. Re-check intent | Compare format, angle and questions with today’s top results | Google Search |
| 4. Update facts | Prices, statistics, screenshots, menu paths, rules and year references | The post |
| 5. Add value | New examples, photos and sections; cut what’s obsolete | The post |
| 6. Improve the snippet | Rewrite the title and meta description if CTR is low | CMS or SEO plugin |
| 7. Fix links | Repair broken links; add links to and from related pages | The post and related posts |
| 8. Dates | Update the visible date and dateModified only for substantial changes | CMS and structured data |
| 9. Recrawl | Confirm the sitemap lastmod and request indexing | Search Console |
| 10. Measure | Annotate the date; compare equal periods after a few weeks | Search Console and GA4 |
How TechZone can help
TechZone can run a content refresh for your blog from start to finish. We audit your posts using Search Console and GA4, sort them into refresh, merge, redirect and delete lists, and update the priority posts with current facts, better structure and internal links.
Redirects, structured data and dates are handled in the same pass, and we annotate each change so results are easy to review. Our digital marketing services cover a one-off refresh or a quarterly routine. Book a free 30-minute call to talk through your blog.
Frequently asked questions
How often should you update old blog posts?
There is no fixed schedule for updating old blog posts. A practical routine is a quarterly review in Search Console that flags posts with falling clicks, strong impressions but few clicks, or outdated facts. Posts on fast-changing topics, such as software, prices or regulations, need checking more often than evergreen guides. Update when the content needs it, not on a calendar.
Does updating old content improve SEO?
Updating old content can improve SEO when the update makes the page genuinely more useful, for example by correcting outdated facts, matching current search intent or answering questions the page missed. Cosmetic changes, such as a new date or a few swapped words, don’t make a page more useful, so they shouldn’t be expected to help. Results vary by topic and competition, so measure each refresh.
Should I change the URL when I update a blog post?
You should keep the same URL when you update a blog post, because the existing URL carries the page’s history, links and bookmarks. Removing a year from a slug is rarely worth the disruption. If a URL change is unavoidable, set up a permanent 301 redirect from the old URL to the new one and update internal links to point directly at the new address.
What is content pruning?
Content pruning is removing or consolidating low-value pages, such as outdated announcements, thin posts or near-duplicates, so a site’s remaining content is more useful. Pruned pages are either merged into a stronger page with a 301 redirect or deleted so they return a 404 or 410 status. Pruning should be based on each page’s value to readers, not done in bulk to make a site look fresh.
Can updating a blog post hurt its rankings?
Updating a blog post can hurt its rankings if the update removes sections searchers valued, shifts the page away from the queries it ranked for, changes the URL without a redirect, or rewrites a page that was only fluctuating normally. Reduce the risk by keeping the URL, checking the Queries tab before cutting anything, and making changes in one pass so their effect is measurable.
Sources and further reading
- Creating helpful, reliable, people-first content – Google Search Central
- Debugging drops in Google Search traffic – Google Search Central
- Performance report (Search results): Advanced filtering and comparison – Search Console Help
- Redirects and Google Search – Google Search Central
- Influence your byline dates in Google Search – Google Search Central
- Build and submit a sitemap – Google Search Central
