2026 Guide
12 min read
Most business blogs have the same pattern: a handful of posts that once brought steady traffic, now slowly fading, and a long tail of older articles that never did much at all. Writing more new posts is the usual reaction. Often the faster win is improving what you already have, as long as the update genuinely makes the page better and isn’t just a new date at the top.
To update an old blog post so it can rank again: find posts losing traffic in Search Console, check what searchers want now, correct outdated facts, fill the gaps competing pages cover better, add original examples, improve the title and structure, and fix internal links. Only change the “last updated” date when the content has substantially changed; Google specifically warns against changing dates to make pages look fresh. Then request recrawling and track results over the following weeks.
This guide covers how to find which posts are worth updating, why posts lose rankings, how to decide whether to update, merge, redirect or leave a post, a step-by-step update process, how to handle dates correctly, and how to measure whether the update worked.
Why Updating Old Posts Works (and When It Doesn’t)
An existing post already has things a new one doesn’t: it’s indexed, it may have links pointing to it, and Google already has some sense of what it’s about. Improving it builds on that rather than starting from zero.
What doesn’t work is updating for the sake of looking fresh. Google’s guide to creating helpful, reliable, people-first content lists these as warning signs of search-engine-first content:
- Changing the date of pages to make them seem fresh when the content hasn’t substantially changed
- Adding a lot of new content or removing a lot of older content mainly because you believe it will make your site seem “fresh.” Google’s answer: “No, it won’t.”
Why Blog Posts Lose Rankings Over Time
There’s rarely a single cause, and Google doesn’t report one per page. These are the common reasons worth checking:
| Cause | What It Looks Like | Likely Fix |
|---|---|---|
| Outdated information | Old prices, screenshots, tools, statistics or years in the title | Correct and re-source every time-sensitive fact |
| Search intent shifted | The pages now ranking are a different type from yours | Restructure the page to the format searchers now want |
| Better competing pages | Others answer more questions, with clearer examples | Fill real gaps and add original insight |
| Overlap with your own posts | Two of your pages swap positions for the same query | Merge them and redirect the weaker one |
| Weak internal linking | Few or no other pages on your site link to it | Link to it from relevant newer posts and service pages |
| Technical issues | Page not indexed, slow, broken on mobile, or redirecting | Check the page in Search Console’s URL Inspection tool first |
If traffic fell sharply across many pages at the same time, the cause is more likely site-wide (a technical problem, a site change, or a broad Google update) than any single post. Investigate that before rewriting content.
How to Find Which Posts to Update First
Google Search Console’s Performance report is the best free starting point. Look for posts in these groups:
- Declining posts: compare the last three months with the same period a year earlier and sort by the largest drop in clicks.
- Almost-there posts: pages with plenty of impressions but an average position just off the first page. These often need the least work for a visible gain.
- Low click-through posts: high impressions, few clicks. The title or snippet may not match what searchers expect.
- Business-critical posts: articles that lead to your services or bring in enquiries, even if their traffic is modest.
Prioritize posts that matter to your business and have a realistic chance of improving. A post that never ranked for anything may need a new target rather than an update.
Update, Merge, Redirect or Leave It?
| Situation | Best Action |
|---|---|
| Topic still relevant, content dated or thin | Update on the same URL |
| Two or more posts cover the same question | Merge into the strongest page, then 301-redirect the others to it |
| Post is obsolete but a newer page covers the topic | Redirect to the replacement page |
| Post is accurate and performing well | Leave it, beyond checking facts and links occasionally |
| Post has no value for readers and no relevant replacement | Consider removing it, after checking it has no useful traffic or links |
Google’s documentation on redirects lists consolidating duplicate URLs and replacing removed pages as standard uses for permanent (301) redirects, and says Google treats the redirect target as the canonical URL. Only use a permanent redirect when you’re sure you won’t reverse it.
A Step-by-Step Process for Updating a Blog Post
Keep the old title, meta description and text so you can compare results or roll back.
In Search Console, filter the Performance report by the page. These queries show what Google already associates with it.
Search the main query and compare the page types now ranking with yours. If the format has changed, the structure needs to change too.
Prices, statistics, screenshots, tool names, laws, years. Re-source every figure from a current primary source and remove anything you can’t verify.
Use “People also ask,” your Search Console queries and customer questions. Add sections only for genuine questions, not to make the post longer.
A recent example from your work, new photos, your own results, or an expert’s view. This is what lifts an update above a rewrite.
Remove filler intros, repeated points and sections that answer questions nobody asks any more.
Make them match what the page now delivers. Keep the URL the same unless there’s a strong reason to change it.
Replace broken links, link to newer relevant posts from this page, and add links to this page from newer posts and service pages.
Change “last updated” only after a substantial update, then use Search Console’s URL Inspection tool to request indexing.
How to Handle Dates on Updated Posts
Google’s documentation on byline dates gives clear rules:
- Show a visible date and label it clearly, such as “Published” or “Last updated.”
- Use structured data with
datePublishedanddateModifiedon Article or BlogPosting markup. - Keep visible and structured dates consistent with each other.
- Avoid future dates, and don’t use dates of events in the content as the page date.
Combine that with Google’s helpful content warning: change the “last updated” date only when the content has substantially changed. Fixing a typo or swapping one link doesn’t count.
Not a real update
Changing “2025” to “2026” in the title, adding two sentences, and moving the date forward.
A real update
Replacing old pricing with current figures and sources, adding a section answering a question customers now ask, swapping outdated screenshots, and merging in a weaker overlapping post.
How to Tell if the Update Worked
Google’s documentation on asking Google to recrawl says crawling can take anywhere from a few days to a few weeks, and requesting it repeatedly won’t speed it up. So give it time before judging.
Then compare, in Search Console, the weeks after the page was recrawled with a matching period before the update:
- Clicks and impressions for the page
- Average position for its main queries
- New queries the page starts appearing for
- Enquiries or conversions from the page, in your analytics
Keep a simple log of what you changed and when. Seasonal demand and Google updates also move traffic, so a change in numbers isn’t automatically caused by your update. For a wider view of what to track, see our guide to digital marketing KPIs.
How Often Should You Update Blog Posts?
There’s no fixed schedule. Update when the content needs it: facts go out of date, the topic changes, readers ask new questions, or performance drops. Posts about prices, tools, laws or “this year” topics need checking more often than evergreen explainers.
A practical approach is to add a review date to each important post in your content calendar, and check your top posts in Search Console every few months.
Common Mistakes When Updating Old Content
- Changing the date without changing the content, which Google specifically warns against
- Changing the URL unnecessarily, and losing the page’s history if no redirect is set up
- Making the post longer instead of better, adding padding rather than answers
- Deleting posts in bulk to look “fresh”, which Google says doesn’t help
- Ignoring overlapping posts that compete with each other for the same query
- Rewriting a page that ranks well without a clear reason, and risking what already works
- Judging results after a few days, before Google has recrawled the page
- Not recording changes, so you can’t tell later what helped
Have Old Posts That Used to Perform?
Serpistan audits your existing content, shows which posts are worth updating, merging or retiring, and helps you improve the ones that matter to your business.
Frequently Asked Questions
Does updating old content improve SEO?
It can, when the update makes the page more accurate and more useful for what people are searching now. Cosmetic changes and new dates alone don’t help, according to Google.
Should I change the URL when I update a post?
Usually not. Keeping the same URL keeps the page’s existing links and history. If you must change it, set up a permanent 301 redirect from the old URL to the new one.
Should I republish an updated post as new?
No need. Keep the original publish date and add a “last updated” date. Republishing at a new URL splits the page’s history across two addresses.
How long after an update will rankings change?
Google says crawling can take a few days to a few weeks, and ranking changes can take longer. Compare several weeks of data before and after, and expect some variation either way.
Is it better to update an old post or write a new one?
If the old post targets the same question, update it. Write a new post when the question is genuinely different. Two posts answering the same thing usually compete with each other.
Should I delete old blog posts that get no traffic?
Not automatically. First check whether they could be improved, merged into a stronger post, or redirected to a relevant page. Remove a post only when it has no value for readers and nothing better to point to.
Can I use AI to update old posts?
AI can help spot gaps or tighten writing, but Google says all AI-generated content should be manually fact-checked before publishing. Updated facts especially need checking against current sources.
Sources / References
- Google Search Central, “Creating helpful, reliable, people-first content”
- Google Search Central, “Influencing your byline dates in Google Search”
- Google Search Central, “Ask Google to recrawl your URLs”
- Google Search Central, “Redirects and Google Search”
- Google Search Central, “Google Search’s guidance on using generative AI content on your website”