← Journal

Guides

How to update old blog posts without losing rankings

By Thomas Lovas Lokoy · Published 16 October 2026 · 7 min read

A green vintage typewriter
Photo: An old typewriter by Ivan Tsoma · CC0

Updating old blog posts is one of the most useful things you can do for a blog that has been running for a while, and one of the easiest to get wrong. A careless update can change a URL, strip out the section people were actually finding, or put a fresh date on a page that has not really changed. This guide sets out what Google's documentation says about updates, dates and redirects, and a step-by-step routine for improving an old post while keeping what already works.

One honest caveat first: nobody can promise that an update will hold or improve a ranking. Rankings depend on what else is published and on what searchers want, and both change. What you can do is avoid the mistakes that reliably cause damage, and make changes that leave the page more useful than it was.

Why update old blog posts at all

Google's SEO starter guide includes this in its description of useful content: "Check in on previously published content and update it as needed, or even delete it if it's not relevant anymore." That sentence covers the three outcomes of any review: update, leave alone, or remove.

Posts go stale in predictable ways. Prices, product names, screenshots and instructions date quickly. Links to other sites break. Your own understanding improves, so a post written early on may now be the weakest explanation you have of a subject. And readers notice: a how-to that refers to a menu that no longer exists sends people away.

What not to do: the fake refresh

Google's helpful content page lists questions that indicate content made for search engines first. One of them is aimed squarely at superficial updates:

"Are you changing the date of pages to make them seem fresh when the content has not substantially changed?"

The same list asks whether you are "adding a lot of new content or removing a lot of older content primarily because you believe it will help" your rankings, and answers its own question with "(No, it won't)". Two practices follow:

  1. Do not change the published or updated date unless the content has substantially changed. Fixing a typo or swapping a picture is not an update worth announcing.
  2. Do not pad a post to make it look new. Adding three generic paragraphs makes the post longer and worse. The page also asks whether you are writing to a particular word count, and says Google has no preferred one.

Decide first: update, merge, or remove

Before you edit anything, put each post you are reviewing into one of four groups.

  • Leave alone. Still accurate, still useful. Check its links and move on.
  • Update. The subject is still relevant but parts are out of date, thin or unclear.
  • Merge. Two or more posts answer the same question. The SEO starter guide's advice for duplicate pages is to set up a redirect "from non-preferred URLs to a URL that best represents that information". Combine the best material into one post and redirect the others to it.
  • Remove. The subject no longer applies to anyone. If there is a closely related page a reader would want instead, redirect to it; if not, let the page go.

Use the Performance report in Google Search Console to inform the decision. It shows clicks, impressions, click-through rate and average position, and you can group the data by page or by query. For a post you plan to update, note the queries it already receives impressions for. Those are the questions people expect the page to answer, and your update should not remove the parts that answer them.

How to update an old blog post, step by step

1. Record the starting point

Before changing a word, save a copy of the current post and write down its URL, its title, its main headings, and its main queries and clicks from the Performance report over a recent period. Without a baseline you will not know whether the update helped.

2. Keep the URL

The single most important rule for updating old blog posts is to leave the address alone. A changed URL is a new page as far as everyone else's links and bookmarks are concerned. If you genuinely must change it, for instance because the old slug is misleading, use a permanent server-side redirect from the old address to the new one. Google's redirects documentation recommends a permanent server-side redirect "whenever possible", and says to use permanent redirects "when you're sure that the redirect won't be reverted". Then update your own internal links to point at the new URL directly.

3. Re-read it as the reader it now serves

Search for the post's main query and look at what the results page shows today. Then read your post as someone arriving from that search. Ask the question from Google's helpful content page: "After reading your content, will someone leave feeling they've learned enough about a topic to help achieve their goal?" Note every point where the answer is no.

4. Fix accuracy before style

Work in this order:

  1. Facts, figures, prices, names and dates that are now wrong.
  2. Instructions that no longer match the product or process.
  3. Broken outbound links, replaced with a current primary source or removed.
  4. Missing parts that a reader now needs.
  5. Clarity, structure and style.

Every new figure needs a source you have actually opened. The routine in the guide on fact-checking an AI-written article works just as well for a human-written post that has aged.

5. Keep what already works

The sections that answer the queries you recorded in step 1 are the ones bringing readers in. Improve them, but do not delete them or bury them under new material. Keep the title and main headings close to the original unless they are actually misleading; a title rewritten purely for novelty can change what the page appears to be about.

6. Check the internal links both ways

Add links from the updated post to anything newer on your blog that a reader would want next, and make sure older posts that should point at this one do so. Google's link best practices page sets the minimum: "Every page you care about should have a link from at least one other page on your site." The guide to internal linking for blogs has a full routine.

7. Handle the date honestly

If the update is substantial, show it. Google's byline date documentation recommends that you "Add a user-visible date to the page and feature it prominently", label dates with text such as "Last updated", and specify dates in structured data using the datePublished and dateModified fields. It also asks you to "Make your dates and times consistent", so the visible date and the structured date should match, and says not to specify future dates.

If the change was minor, leave the date as it was.

8. Update the sitemap date only for significant changes

Google's sitemap documentation says the lastmod value should reflect the last significant update to the page. It describes changes to the main content, the structured data or the links on the page as generally significant, and a change to the copyright date as not. It adds that Google uses the value only when it is consistently and verifiably accurate. Most blogging platforms set this automatically on every save; if yours does, minor edits will move it too, which is worth knowing even if you cannot change it.

9. Wait, then compare

The starter guide is clear that results are not immediate: "Every change you make will take some time to be reflected on Google's end." It says some changes take effect in hours and others take several months, and suggests waiting a few weeks before assessing the effect. Compare the same Performance report figures you recorded in step 1 over a comparable period afterwards.

Updating posts that were drafted with AI

If an old post was drafted with an AI writing tool, the update is a good moment to check it properly: claims without sources, figures that cannot be traced, and passages that read as generic. Google's position on AI-assisted content is about quality and purpose rather than method; the guide to AI-generated content and Google Search quotes what its documentation actually says.

A review schedule that stays manageable

You do not need to review every post every year. A workable pattern:

  1. Quarterly: the posts that get the most clicks, because they matter most to readers.
  2. Twice a year: posts with dated details, such as prices, tools and step-by-step instructions.
  3. Yearly: everything else, in a quick leave-alone, update, merge or remove pass.

Keep a simple log with each post's URL, the date you reviewed it, what you changed and whether the date was updated. When you next review it, the log tells you what has already been done and stops the same post being "refreshed" twice with nothing new in it.

Sources