How to Update Old Blog Posts to Win Back Traffic

Quick answer

Start in Search Console: compare the last three months with the same period last year and list posts that lost clicks or rank just off page one. For each, decide to update, merge, redirect or leave it. Rewrite for today's search intent, add new facts and examples, fix links, then change the "Last updated" date only if the change is substantial.

Google's own checklist for helpful content includes a pointed question: "Are you changing the date of pages to make them seem fresh when the content has not substantially changed?" It's there because swapping a date on an old post and calling it updated is one of the most common shortcuts on the web.

A real refresh takes more work and pays back far more. Your older posts already have links, history and some trust with Google, so improving them is often faster than publishing something new. The trick is picking the right posts, deciding what each one needs and making changes a reader would notice. Here's how to do all three, in order.

Why old posts lose traffic

Old posts lose traffic for a handful of reasons, and most of them have nothing to do with a penalty. Knowing the cause tells you what kind of update the post needs.

  • Search intent has changed. A query that once returned how-to guides might now show product comparisons or videos. If your post no longer matches what ranks, it slips.
  • The facts are out of date. Old prices, discontinued tools, retired features and last year's statistics make a post less useful, and readers notice.
  • Newer pages are better. Competitors publish fresher, more detailed answers to the same question.
  • Your own posts compete with each other. Two or three similar posts on one topic divide attention, where one strong page would gather it.
  • AI Overviews answer simple questions directly. For short factual queries, fewer people need to click through. Our guide to getting cited in AI Overviews explains how to stay visible there.

Step 1: Find the posts worth updating in Search Console

Use Search Console's Performance report to find posts that lost clicks and posts ranking just off page one. These two groups usually offer the fastest wins, because they already rank for something.

Compare date ranges. Open the Performance report, set the date filter to compare the last three months with the same three months a year earlier, and switch to the Pages tab. Comparing the same months removes seasonal swings, which are large for businesses like HVAC, tax prep or landscaping.

Sort by click loss. Sort the pages by the difference in clicks. Posts with the biggest drops go to the top of your list, especially if their impressions held steady, since that suggests people still see them but click something else.

Find near-miss pages. Next, look at average position. Search Console defines it as "The average position of the topmost result from your site" for a query. Filter or sort to find posts averaging roughly position 8 to 20. These rank at the bottom of page one or on page two, where a strong update can make the biggest difference.

Check the queries. Click into each candidate page and switch to the Queries tab. Note whether the main queries match what the post was written for. Sometimes a post ranks for a different question than intended, and the update should lean into the search it's already winning. The searches it ranks for tell you what readers expect from it, and they often reveal questions the post doesn't answer yet.

By the end of this step you should have a short list, perhaps five to ten posts, ranked by how much traffic they've lost or could gain.

Decision tree for old blog posts
  1. 1Is it performing well?Leave it
  2. 2Does another post cover the same topic?Merge + 301
  3. 3Has a newer, better page replaced it?Redirect
  4. 4Does the topic still get searches?Update
  5. 5No searches, no links, no value?Delete

Ask each question in order and stop at the first “yes”.

Step 2: Update, merge, redirect or delete?

Each post on your list needs one of four decisions. The right choice depends on whether the topic still earns searches, whether another post covers the same ground and whether the page has links worth keeping.

DecisionWhen it fitsWhat to do
UpdateThe topic still gets searches and the post is the best page you have on itRewrite and expand it at the same URL
MergeTwo or more posts cover the same topic and compete with each otherCombine the best parts into one post, then redirect the others to it
RedirectA newer or better page now covers the topic fullySend the old URL to the better page with a permanent redirect
DeleteThe post gets no searches, has no links and offers readers nothing currentRemove it, and let it return a 404 or 410 status

For merges and redirects, use permanent redirects. Google's site move guide recommends "HTTP permanent redirects if possible, such as 301 and 308," and advises: "Keep the redirects for as long as possible, generally at least 1 year."

Before you merge or redirect, check that the posts truly target the same search. Say you have three posts: "How to choose a water heater," "Tank vs tankless water heaters" and "Best water heater for a family of four." If all three rank on page two for similar searches, merging them into one detailed guide, then redirecting the other two URLs to it, often produces a page that outranks all three. Two posts can look similar but answer different questions. Our guide to how to do keyword research explains how to check intent by looking at what ranks for each query.

Step 3: Rewrite for today's search intent

Search the post's main query and look at what ranks today, then reshape your post to match. If the top results are step-by-step guides and yours is an opinion piece, the format needs to change along with the facts.

Work through the post section by section:

  • Open with the answer. Readers and Google both want the point quickly. Put a direct answer in the first two sentences, then expand.
  • Add the questions people ask now. Check People Also Ask and the queries in Search Console. Each new question can become a heading with a short answer below it.
  • Cut what's no longer true. Remove outdated advice, retired tools and steps that no longer work. A shorter, accurate post beats a long one with stale sections.
  • Match the format that wins. Add a table, checklist or numbered steps if that's what top results use.

Read the post aloud after rewriting. If any paragraph would make a reader skim, shorten it. Updated posts that are easier to read keep visitors longer, and that's the experience Google's systems are built to reward.

Our content marketing strategy for small businesses explains how refreshed posts fit into a wider publishing plan.

Step 4: Add something new and true

Give the post something it didn't have before: fresh figures, first-hand examples, new screenshots or local detail. A refresh should leave the reader with more useful information than the old version, and every new fact should be easy to check.

Good additions include:

  • Updated statistics with a link to the source and the date it was published.
  • Examples from your own work, such as a recent job, a client question or a common mistake you've seen this year.
  • New screenshots of tools and interfaces that have changed since the post went live.
  • Local or industry detail that generic articles miss.

Keep a short note in the post, near the top or bottom, explaining what changed in the update, such as "Updated with 2026 prices and a new section on heat pump rebates." Readers who return to the post can see what's new.

Answer the questions in the order readers ask them. If most people searching want the cost first, put the cost section near the top, even if the original post saved it for the end.

If you use AI to help draft new sections, review every claim before publishing. Google's current guidance asks publishers to fact-check AI-generated content, and our guide to whether AI content is bad for SEO covers how to do that safely.

Refresh the parts around the content too: the title, meta description, internal links, outbound links and images. These small fixes help readers find, trust and move through the updated post.

  • Title and meta description: rewrite them to match the updated content and the main query. If the post covers a new year's data, say so.
  • Internal links from newer posts: link to the refreshed post from your recent, related articles, so readers and crawlers find it.
  • Internal links out: point the refreshed post to your newer service pages and guides.
  • Broken outbound links: replace dead links with current sources.
  • Images and alt text: replace outdated screenshots and write descriptive alt text for each image.

Check the URL too, but leave it alone if it works. Changing a URL means setting up a redirect and waiting for Google to process it, so only change it if the old one is misleading, such as a slug containing an old year.

If you do change it, update every internal link to point at the new URL directly, so visitors and crawlers don't pass through a redirect each time.

Our on-page SEO checklist covers each of these elements in more detail.

When to change the publish date (and when not to)

Change the date only when you've made substantial changes, and label it "Last updated" so readers know what happened. Swapping a date on an unchanged post is the exact pattern Google's helpful-content questions warn against.

Dates done right:

  • Google's warning: its helpful content guidance asks: "Are you changing the date of pages to make them seem fresh when the content has not substantially changed?"
  • Label it clearly: Google's byline date guide suggests labeling dates "with text like 'Publish' or 'Last updated'."
  • Keep dates matching: the same guide says the visible date and the structured data values (datePublished and dateModified) should match.
  • Small fixes don't need a new date: a corrected typo or one swapped link doesn't count as an update.

What about backdating, setting a post's date earlier than when it went live? It's a question people ask often, and there's no good SEO reason to do it. Keep the original publish date, add a "Last updated" date when you make real changes, and let both show.

Step 6: Ask Google to recrawl, then measure

After publishing the update, ask Google to recrawl the page with URL Inspection in Search Console, then give it time. Results usually take weeks, and an update doesn't guarantee a recovery.

Google's recrawl guide says "Crawling can take anywhere from a few days to a few weeks," and that "Requesting a crawl does not guarantee that inclusion in search results will happen instantly or even at all." There's also a quota on individual URL requests, so for many updated pages, submit an updated sitemap instead.

Wait four to eight weeks, then repeat the comparison from Step 1 for the updated posts. Look at clicks, impressions and average position against the period before the update. Keep a simple log of what you changed and when, so you can see which kinds of updates work best on your site.

A basic log needs five columns: the post URL, the date of the update, what you changed, the clicks and position before, and the clicks and position eight weeks later. After a few rounds, patterns appear, such as rewrites for intent moving posts more than new statistics, and you can focus on what works.

Google's Refresh Outdated Content tool is something else

Google's Refresh Outdated Content tool sounds like a content refresh helper, but it does a different job. It asks Google to update its search results when a page has changed or been removed, usually a page on someone else's site.

Google's help page for the tool explains that requests only work when the content has really changed or is no longer available. It's mainly used by people who spot outdated information about them on another site that has since been corrected or deleted. For your own site, the normal route is to update the page and request a recrawl, as in Step 6.

Do it yourself or hire help?

A quarterly refresh needs only Search Console and a few focused hours: pick five posts, decide what each needs, update them and check results eight weeks later. Hiring help makes sense when your blog has hundreds of posts, when traffic has dropped sharply or when you lack the time to research and rewrite properly.

A simple quarterly routine:

  1. Week 1: run the Search Console comparison and pick five posts.
  2. Week 2: decide update, merge, redirect or delete for each.
  3. Weeks 3 and 4: rewrite, add new information, fix links and request recrawls.
  4. Eight weeks later: compare results and log what worked.

Our content refresh services handle the full process, from picking posts to tracking results. To see how refresh work fits into a wider budget, read how much SEO costs in 2026.

Updating old blog posts FAQs

How often should you update old blog posts?

Review your key posts at least once a year, and check Search Console every quarter for posts losing clicks. Update sooner when facts, prices or tools change. Posts on fast-moving topics need more frequent updates than evergreen guides.

Can I change the date on an old blog post?

Yes, if you've made substantial changes. Show a "Last updated" label and keep the structured data date matching it. Google's helpful-content guidance warns against changing dates to make pages seem fresh when the content hasn't substantially changed.

Should I update an old post or write a new one?

Update the old post if it covers the same topic and search intent, since it keeps its links and history. Write a new post if the topic or intent has changed enough that the old one can't be reshaped to fit, then consider redirecting the old URL.

What is a content refresh in SEO?

A content refresh is a substantial update to an existing page: new facts, better answers, current examples, fixed links and an updated title. The goal is to make the page more useful than before, so it can regain or improve its search visibility.

How long does it take to see results after updating a post?

Google says recrawling can take a few days to a few weeks. Ranking changes often take longer. Wait four to eight weeks before comparing clicks and positions with the period before the update, and remember that results aren't guaranteed.

Sources

  1. Google Search Central, "Creating helpful, reliable, people-first content," updated October 5, 2026: https://developers.google.com/search/docs/fundamentals/creating-helpful-content
  2. Google Search Central, "Influence your byline dates in Google Search," updated December 10, 2025: https://developers.google.com/search/docs/appearance/publication-dates
  3. Google Search Central, "Ask Google to recrawl your URLs," updated December 10, 2025: https://developers.google.com/search/docs/crawling-indexing/ask-google-to-recrawl
  4. Google Search Central, "Site moves with URL changes," updated August 20, 2026: https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes
  5. Search Console Help, "Performance report (Search results)": https://support.google.com/webmasters/answer/7576553
  6. Search Console Help, "Refresh Outdated Content tool": https://support.google.com/webmasters/answer/7041154
← All posts

Appear now.

Send your site. Get a growth plan.

Your free growth review

  • Your biggest ranking blockers
  • Where AI search skips you
  • A quote with no long lock-in
Book a growth call