Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Refresh old blog posts or write new ones? How to decide

Updated · 7 min read

Short answer Ask one question: does the new version answer the same question for the same searcher? If yes, update the old post at the same address, even if you rewrite every word; it keeps its links and history. If the question is different, write a new post. If only the address is wrong, move it with a 301 redirect.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

The rule: same question, same address

The page address (URL) belongs to a question, not to a draft. If the searcher's question hasn't changed, the answer lives at the old address, however much of the text you replace. A new post is for a new question.

Your situationDo this
Same question, facts are out of date (prices, rules, photos)Update the old post at the same address
Same question, but the post is so weak you'd start from scratchRewrite it completely, still at the same address
A different question on a nearby topicWrite a new post; link the two to each other
Same question, but the address is wrong (a year in it, an old service name)Publish at a better address; 301-redirect the old one to it
Two old posts already answer the same questionMerge them into the stronger one; redirect the other
Something new happened (a new law, a new rebate) that people search by nameNew post on the news; add a line and a link to your evergreen guide

Google's own advice for old content is to fix it where it is:

"Check in on previously published content and update it as needed, or even delete it if it's not relevant anymore." (Google Search Central: SEO Starter Guide)

How to find which old posts are slipping, and when to delete instead, is in content decay: update, merge or delete. This page is only the fork in the road: same address or new one.

How do I know if it's the same question?

Look at what people already type to reach the old post. In Google Search Console, open Performance, filter to the old post's page, and open the Queries tab. Google's own troubleshooting steps say to check every tab to see whether a change hit "specific queries, URLs, countries, devices, or search appearances" (Google Search Central).

  • The searches you want to win already show up for the old post. Same question. Update it.
  • They don't, and the person searching wants a different answer. New question. Write a new post.

A quick test without tools: would one customer be happy landing on either page? "How to unclog a drain" and "drain cleaning cost" are different people with different needs. "Furnace rebates 2025" and "furnace rebates 2026" are the same person a year apart.

New to Search Console? See the reports to read.

Why updating the same address usually wins

It keeps what the page has earned. Links from other sites, bookmarks and Google's history with the page all point at the old address. A new address starts with none of that unless you redirect.

Moving has a waiting cost. A 301 redirect (a permanent "this page moved" signal) carries the credit over; Google says "301 and other permanent redirects don't cause a loss in PageRank" (Google Search Central: Site moves). But it isn't instant:

"for medium-sized websites, it can take a few weeks or more for Google to gradually start showing the new URLs instead of the old ones" (Google Search Central: Site moves)

Two posts on one question compete with each other. Google shows only one of near-identical pages:

"Some of these may be very similar to each other. In such cases, our systems show only the most relevant results to avoid unhelpful duplication." (Google Search Central: ranking systems)

That's the real cost of a second post on the same question: you split your own visitors and links, and Google picks which one to show. SEO people call this keyword cannibalization; see keyword research for a local business.

It isn't a penalty, though. Google says so directly:

"Having duplicate content on your site is not a violation of our spam policies, but it can be a bad user experience and search engines might waste crawling resources on URLs that you don't even care about." (Google Search Central: SEO Starter Guide)

Does refreshing a blog post help SEO?

Only when the content really changes. Google favors fresh content only for searches where people expect recent information, like a just-released movie or a recent event:

"We have various "query deserves freshness" systems designed to show fresher content for queries where it would be expected." (Google Search Central: ranking systems)

A new date on an unchanged post does nothing good. Google lists it as a warning sign:

"Are you changing the date of pages to make them seem fresh when the content has not substantially changed?" (Google Search Central: helpful content)

When you do update, show it. Google suggests labels "with text like "Publish" or "Last updated"" and estimates "when a page was published or significantly updated" from several signals (Google Search Central: byline dates).

Two common claims with no Google rule behind them:

  • "Update every post once a year." Google sets no schedule. Update when the facts, prices or customer questions change. A how-to that is still right can wait.
  • "Updating causes a temporary traffic dip." Google describes no such effect for an update at the same address. The weeks-long wait applies when the address changes.

If you do move a post to a new address

  1. Publish the new post, then 301-redirect the old address straight to it, in one hop.
  2. Keep the redirect: Google says "generally at least 1 year" (Google Search Central: Site moves).
  3. Change your own menus and in-post links to the new address. Google's checklist: "Change the internal links on the new site from the old URLs to the new URLs" (same page).
  4. Redirect to the page that answers the same question, not your home page. Google warns that sending old URLs to an unrelated page, such as the home page, "might be treated as a soft 404 error" (same page).
  5. Pick an address with no year or date in it, like `/furnace-rebates/`, so next year's update needs no move at all.

Redirect or canonical tag? A canonical tag is a line in the page code that names the preferred version of duplicate pages. If the old post covers the same thing, a redirect is cleaner: Google says to use redirects "when you want to get rid of existing duplicate pages" (Google Search Central: canonical URLs). If your new post truly answers a different question, the two aren't duplicates and need neither.

Example

Illustrative cases with invented numbers.

A Calgary HVAC company (Canadian dollars)

Its post lives at `/2024-furnace-rebates/` and still gets visits. The 2026 rebates changed (say, C$1,000 became C$500). Same question, wrong address: it publishes `/furnace-rebates/` with 2026 figures, 301-redirects the 2024 address to it, and next year just updates the same page.

A bookkeeper (US dollars)

"How to pay quarterly estimated taxes" ranks well but shows last year's due dates. She updates the dates and the example payment (say, $1,200 a quarter), adds a "Last updated" line, and keeps the address. No new post.

A dog groomer

She has "How often to groom a poodle" and wants to rank for "poodle grooming price". Search Console shows no price searches reaching the old post. Different question: she writes a new post and links each to the other.

FAQ

Should I change the URL when I update a blog post?

No, unless the address itself is wrong, such as a year or a service you no longer offer. Then use a 301 redirect from the old address to the new one and keep it at least a year.

If I rewrite a post from scratch, is it a new post?

Not for Google. If it answers the same question, publish the rewrite at the same address so it keeps its links and history.

Should I delete the old post after publishing a new one?

If both answer the same question, redirect the old one to the new one rather than deleting it. If they answer different questions, keep both and link them.

Can I republish an old post with today's date?

Only if you changed it substantially. Google's guidance treats a new date on unchanged content as a sign of writing for search engines.

How do I know the update worked?

In Search Console, compare the page's clicks and queries for a few weeks before and after the change. Give Google time to recrawl it.

Different for you?

Keep learning

NextContent decay causes: why pages lose traffic over timeWhy an old page that used to bring visitors slowly loses Google traffic: competitors, stale facts, changed search intent, AI answers, and how to tell which.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Google Search Central: SEO Starter Guide
  2. Google Search Central: A guide to Google Search ranking systems
  3. Google Search Central: Creating helpful, reliable, people-first content
  4. Google Search Central: Influence your byline dates in Google Search
  5. Google Search Central: Site moves with URL changes
  6. Google Search Central: How to specify a canonical URL
  7. Google Search Central: Debugging drops in Google Search traffic