Content refresh · 11 Nov 2026 · 7 min read
How to update old blog posts for SEO
Old posts can keep earning visits if they stay accurate and useful. This guide shows how to choose which posts to update, what to change and what to leave alone.
The short answer
Yes, update old blog posts that still matter to your business but have gone out of date, thin or hard to use. Choose them with Search Console data and your own judgement, keep the web address, fix facts and gaps, and change the visible date only when the post is substantially different. Then compare results after a few weeks.
Should you update old blog posts?
You should update old blog posts that still serve a purpose, and leave the rest alone or retire them. A post with a wrong fact, a dead link or an answer that no longer matches the question lets the reader down first and your search visibility second. The same post, corrected, is often cheaper to improve than a new one is to write.
Freshness is not a goal in itself. Google's ranking systems guide describes systems that show newer content for queries where freshness would be expected, such as news or a recent event. For many questions an accurate page stays useful for years. So ask whether the post is still correct and still answers the question, whatever its age.
How to choose which posts to refresh
Start with data, then apply judgement. A spreadsheet with one row per post is enough. Record the address, topic, publish date, last edit date and what Search Console shows for the post: impressions, clicks and the queries it appears for.
| What you see | What it usually suggests | Likely action |
|---|---|---|
| Impressions hold but clicks fall | The post still appears, but its title or opening is less attractive than rival results | Rework the title and the first lines |
| The post appears for queries it barely covers | Readers want something the post only touches on | Add a section, or write a companion post |
| The post appears, but low in the results | It is relevant but weaker than the pages above it | Compare with those pages and fill real gaps |
| Out-of-date tools, rules or screenshots | An accuracy problem, whatever the traffic | Correct the facts first |
| Other sites link to the post | The post is an asset | Protect the address and edit with care |
| No impressions at all | The post is not found, or nobody wants it | Check indexing and intent, then merge or retire |
Add posts that matter to the business even when their traffic is small. A post your sales team sends to prospects, or one that answers a question customers ask every week, earns its place on the list.
Keep, refresh, merge or retire
Every post on the list ends in one of four outcomes. Name the outcome before you open the editor.
| Outcome | When it fits | What happens to the address |
|---|---|---|
| Keep | Accurate, read, and nothing important missing | Unchanged. Note a review date |
| Refresh | Right topic, but parts are old or thin | Edit in place and keep the address |
| Merge | Several weak posts answer the same question | Fold the best parts into one post and redirect the others to it with a permanent redirect |
| Retire | The topic no longer matters and nothing links to the post | Remove it so the address returns a not found status, or redirect to the closest useful page if one exists |
Merging and retiring change addresses, so treat them as a small site move. The website redesign SEO checklist sets out the redirect and checking steps, and the same logic applies here on a smaller scale.
What to change when you refresh a post
Fix accuracy before anything else. Then look at how well the post answers the question.
- Facts: names, steps, screenshots, product versions and rules. Where a rule differs by country or changes often, say so and point to the official source.
- The opening: answer the main question in the first lines, then explain.
- Gaps: compare with the pages that currently rank for the same question and note questions yours leaves out. Add what is missing in your own words.
- Examples and screenshots: replace any that no longer match what readers see.
- Links: repair broken ones, and add links to newer posts of yours that help the reader.
- Headings: check that each describes its section, and cut sections that no longer help.
- Title and description: change them only if they are wrong or weak. A title that earns clicks should be left alone.
If the post aims to supply a short direct answer, the guide to how pages get featured snippets explains the idea. A clear answer near the top is a sensible thing to check either way.
What to leave alone
Keep the web address unless it is actively wrong. An address that has earned links and visits carries history, and changing it creates redirect work and risk for little gain. Keep the parts readers already use, such as a table people copy or a section that other sites quote.
Links from other sites point at the address you have now. The backlinks guide explains why they are worth protecting. Guest articles you wrote for other sites may link to the post as well. The guest posting guide covers those, and they are another reason to edit in place.
Do not rewrite a working post to change its tone, and do not add paragraphs only to make it longer. Completeness is a reason to update. Length alone is not.
Should you change the date?
Change the visible date only when the post is substantially different. Google's helpful content guidance lists changing the date of a page to make it look fresh, when the content has not substantially changed, as a practice to avoid. Its guidance on dates adds that a page changed significantly can reasonably show a newer date, and that the date you show should match.
A simple way to stay honest is to show two dates: Published, with the original date, and Updated, with the date of the last substantial change. When the change matters to a reader, such as a corrected step or a new rule, add a short note saying what changed. A typo fix or a replaced link does not justify a new date.
Google says its systems look at several factors to estimate when a page was published or significantly updated, so the date on the page is not the only signal. If you add dates in structured data, check the current documentation for the exact properties and rules.
A refresh workflow, step by step
- Record the starting point: the address, title, date and a recent period of Search Console figures, plus the main queries.
- Copy the live text into a document so you can compare before and after.
- Check every fact and link from top to bottom, and fix them.
- Read the post as the person who searches for it. Does the opening answer them?
- Compare with the current results for the main question and note real gaps.
- Edit in place and keep the address.
- Update the visible date only if the change is substantial, and add an update note if it helps the reader.
- Check the page on a phone and on a desktop, then publish.
- Add links to the refreshed post from newer posts that relate to it.
- Write down the date and set a review reminder.
How to tell whether a refresh worked
Wait a few weeks, then compare the same measures against a comparable period. The Search Console performance report for the page shows impressions, clicks and queries. Look for movement in the queries you aimed at, as well as in total clicks.
Seasonality can hide or exaggerate a change, so compare with the same time of year where you can. Change one thing at a time on important posts, or you will not know which edit mattered.
Some posts will not recover. Interest in a topic can fade, or a different kind of page may now suit the search better. Record what you learned and move on to the next post. If you are unsure how AI answer features change what a good post looks like, the SEO vs AEO vs GEO guide sets out what is known and what is not.
Refresh mistakes to avoid
- Changing the date without changing the content.
- Rewriting a post that was working and losing the parts readers valued.
- Changing the address without redirects, which breaks old links.
- Squeezing extra keywords into the update.
- Publishing a near copy as a new post and leaving the old one live, so two pages answer the same question.
- Refreshing every post at once, which leaves no way to see what helped.
If you would like help choosing and checking posts, the search engine optimisation service page describes the SEO work Liftup Technologies does.
Related guides
- SEO services
- Website redesign seo checklist
- Backlinks explained what they are and why they matter
- Content marketing vs seo vs digital marketing
Questions and answers
Should I update old blog posts?
Yes, if the post still matters to your business but is out of date, thin or hard to use. Fix wrong facts and dead links first, then fill real gaps. Posts about topics nobody needs any more can be merged into a better page or retired.
How do I choose which posts to refresh?
List your posts with their Search Console impressions, clicks and queries. Pick posts that still appear in results but are losing clicks, posts with out-of-date facts, and posts that matter to your sales conversations. Protect any post that other sites link to.
Should I change the date when I update a post?
Only when the post is substantially different. Google advises against changing a date to make a page look fresh when the content has not really changed. Showing both a Published date and an Updated date is a fair way to be clear.
How often should I refresh a blog post?
There is no schedule that suits every post. Posts on topics that change often, such as tools, rules or processes, need checking more often than posts on stable topics. Set a review reminder when you publish.
Will updating an old post improve its ranking?
It can, but nobody can promise it. A refresh helps when it makes the post more accurate, more complete or a better match for what searchers want. If the page was already the right answer, results may barely change.
Is it better to update an old post or write a new one?
Update the post when the topic is the same and its address already has links and visits. Write a new post when the question is different. Publishing a near copy of an old post leaves two pages competing for one question.
Tell us what you are building.
A short call, a written plan and a fixed quote. No obligation.