How to Update Old Blog Posts for SEO: A Refresh Checklist

This guide shows you how to update old blog posts for SEO with a refresh checklist I use on client blogs, plus clear rules on dates, URLs and redirects so an update helps instead of hurting.

Does updating old content help SEO?

Yes, updating old content helps SEO when the update makes the page more accurate and more useful than it was. A refresh does not earn rankings by itself. What helps is that the improved page better matches what searchers need today.

Google’s guide to helpful, people-first content makes the distinction clear. It asks whether content provides substantial value compared with other pages in results, and it lists “changing the date of pages to make them seem fresh when the content has not substantially changed” as a warning sign. So the work is in the content, not the timestamp.

Updates also matter for queries where freshness is expected. Google’s ranking systems include freshness systems that show newer content for searches where it is expected, such as prices, software versions or yearly rules. For evergreen topics, accuracy and depth matter more than recency.

Which old posts should you update first?

Update posts that already have impressions but weak clicks or positions first, because Google already sees them as relevant and small improvements can move them. Use the Performance report in Search Console, filtered by page, over the last 3 to 6 months.

After the Search Console data, add a business filter. A post that brings enquiries or supports a service page deserves attention before a post that gets visits from people who will never buy. On most client blogs I review, roughly a handful of posts drive most of the useful traffic, and refreshing those gives far more return than touching every post equally.

Keep a simple spreadsheet: URL, main query, impressions, clicks, position, last updated, and planned action. It stops you refreshing the same post twice and gives you a record to compare results against a few weeks after each update.

What should a blog post refresh checklist include?

A refresh checklist should cover accuracy, intent, depth, structure, links and metadata, in that order. Here is the 14 point list I work through for each post.

1. Search the main keyword and note what the current top five results cover.
2. Confirm the intent has not changed, for example from a guide to a list or a tool.
3. Correct every outdated fact, price, screenshot, version number and year.
4. Check every external link still works and still says what you claim.
5. Rewrite the first paragraph so it answers the question directly.
6. Add sections for subtopics the top results cover and your post misses.
7. Add one thing the others lack: a table, a worked example or your own data.
8. Remove sections that no longer help, such as old news or dead tools.
9. Turn headings into the questions people search today.
10. Add internal links to newer related pages, and from them back to this post.
11. Update the title and meta description if click rate is low.
12. Update image alt text and replace images that no longer match.
13. Update the “last updated” date only if the changes are substantial, and note what changed.
14. Request indexing with URL Inspection in Search Console after publishing.

For steps 11 and 12, my SERP snippet preview tool shows how a new title and description will look before you change them.

Work through the list in order. It is tempting to start with the title because it is quick, but a new title on an unchanged, outdated post only raises expectations the page cannot meet. Fix the substance first, then make the snippet sell it.

Should I change the date when updating a blog post?

Change the date only when you have made a meaningful update, and label it clearly as “Last updated” rather than replacing the original publish date. Changing dates without real edits is a pattern Google’s own guidance calls out as a warning sign.

Google’s guide to byline dates in search results recommends showing a clearly labelled date, and if you use structured data, setting datePublished and dateModified on the Article or BlogPosting markup. It asks that the visible date and the structured data match, and that dates reflect when the page was actually published or updated. A simple rule I follow: if a returning reader would notice the change, update the date. If you only fixed a typo, leave it.

Should I change the URL of an old blog post?

Usually no. Keep the existing URL because it already has links, history and indexing, and changing it adds risk for little gain. Google’s Starter Guide says keywords in the URL path have hardly any effect beyond breadcrumbs, so rewriting a URL just to add a keyword is rarely worth it.

There are good reasons to change a URL: it contains a year that is now misleading, it is a messy ID string, or you are merging two posts. When you do, use a permanent server-side redirect from the old URL to the new one. Google’s guide to redirects explains that 301 and 308 redirects signal a permanent move and that the target should be treated as canonical. Then update internal links to point at the new URL directly. If Search Console later shows the old address under “Page with redirect”, that is expected, as I explain in my guide to the page with redirect status.

What does a real blog post refresh look like?

If you have dozens of posts to review, my on-page SEO service includes content refreshes, and the free SEO audit checklist helps you spot technical issues at the same time.

Frequently asked questions