Content Refresh: How to Relaunch Old Blog Posts That Stopped Bringing In Customers

Pages drift out of first place long before anyone notices

Content decay is the slow slide of a page that once earned steady search traffic. It rarely has one cause. The prices in the post went stale. A competitor published a better answer. The results page grew an AI Overview and a video carousel above the old blue links. The question itself changed, and searchers now ask it in different words. Or the site added newer posts that quietly took the internal links the old page used to get.

The fix is cheaper than the problem. An old URL usually still has what a new post lacks: an indexing history, links from other sites, a place in your navigation. Relaunching it keeps those assets and replaces what aged. That is why the content marketing system ends with a refresh station, and why an afternoon spent here often returns more than a week spent writing something new. Topics that resist aging are covered in evergreen content; this guide handles the ones that aged anyway.

A new post starts from zero. An old one starts from everything it already earned.

Twenty minutes in Search Console to build the decay list

Google publishes a procedure for diagnosing traffic drops in its guide to debugging Search traffic drops, and most of it doubles as a decay finder. You need the Performance report and nothing paid. If you have never opened it, our Google Search Console guide covers setup first.

1. 1

   Open the long view

   In Performance, choose the Date filter and pick Last 16 months. A seasonal business sees its own calendar here, which keeps you from relaunching a pool post in November because pools are quiet in November.

2. 2

   Compare two windows

   Use Compare to set the last three months against the previous period. For seasonal topics, set a custom comparison against the same months a year ago instead, so you compare summer with summer.

3. 3

   Sort the Pages table by loss

   Switch the table to Pages and sort by Clicks Difference, as Google's guide suggests. The pages that lost the most clicks rise to the top. Copy the first twenty into a spreadsheet.

4. 4

   Open each page's queries

   Click a URL to filter by it, then switch to the Queries tab. Note which searches lost clicks, whether impressions fell with them, and whether average position slipped.

5. 5

   Mark the money pages

   Tag each URL by what it supports: a service, a product, nothing in particular. A post that feeds your best service outranks a bigger loser that sells nothing.

Read the symptom before you pick the cure

The numbers in Search Console describe the pattern of the loss, and each pattern points at a different repair. Rewriting a page whose real problem is a sister page stealing its clicks wastes the rewrite. Spend two minutes per URL matching it to a row below.

Google's guide adds a caution worth keeping on the desk: small shifts in position are normal, and it advises against radical changes to a page that is already performing well. A page that slid from position three to four has not decayed. It has wobbled.

Rewrite, merge or retire: a decision for every URL on the list

Every page on the decay list gets one verdict. Most get the first two. The third is rarer than content cleanup advice suggests, because a deleted page loses whatever it earned, while a merged one passes it along.

Before you retire anything, check whether other sites link to it, in Search Console's Links report or a backlink tool from our SEO tools roundup. A page with real links pointing at it deserves a redirect to its closest living relative, not a quiet death.

What a rewrite changes, and what it leaves exactly where it was

A relaunch is not a coat of paint. The reader has to learn something the old version did not tell them, or the work changed nothing that matters. Pull the original brief if one exists; the content briefs guide explains why it is worth keeping. Then work through the page in this order.

• Current facts first. Prices, codes, product models, timelines and rules, each checked against your own records or the issuing office. Wrong facts are the reason most old pages deserve to lose.
• The answer at the top. If the old version opened with a history lesson, move the answer into the first two sentences, the way SEO content recommends for any page.
• The questions searchers ask now. The Queries tab from step four shows phrasings the page never addressed. Give the real ones a section or a sentence.
• Proof only you have. A recent job, a fresh photo, a price range from this year's invoices. That is the material no competitor can copy.
• Cuts. Sections about discontinued services, outdated advice and the padding written to hit a word count. Shorter is often the relaunch.
• Links in both directions. Point the page at the service it supports, and point two or three newer posts back at it. Internal linking is how a refreshed page gets noticed again.

Leave the URL alone. Changing the address of a page that still ranks forces Google to process a redirect for no gain. Keep the same topic, too: a page about water heater repair that becomes a page about tankless installation is a new page wearing an old address, and it should be published as one.

Merging pages and deleting them without throwing away their links

A merge ends with redirects. Pick the strongest URL, the one with the most clicks, links or the cleanest address, and move the useful paragraphs from the weaker posts into it. Then send each retired URL to the merged page with a permanent redirect. Google's redirect documentation lists 301 and 308 as permanent server-side redirects, and the server rules for each platform are in our redirects guide.

The home page shortcut has a specific cost. Google's site move guidance warns against redirecting many old URLs to one irrelevant destination such as the home page, says that can be treated as a soft 404, and advises keeping redirects generally at least a year. When a page has no sensible destination, let it return an error. Google's status code documentation says all 4xx errors except 429 are treated the same, so a 404 and a 410 both remove an indexed URL. Broken links left behind are the job of 404 cleanup.

Republishing honestly: the date has to describe the edit

The temptation is obvious. Change the date, call the post new, collect the freshness. Google anticipated it. Among the self-assessment questions in its guide to creating helpful content, it asks whether you are changing the date of pages to make them seem fresh when the content has not substantially changed. Readers notice too, the first time a post dated this month quotes last year's price.

So the rule is plain: a substantive rewrite earns a new "Last updated" date; a typo fix does not. Google's publication date guidance asks for a visible, labeled date ("Published" or "Last updated"), a matching datePublished or dateModified value in structured data, and no future dates. Keep the original publish date and add the update date beside it. Your sitemap's lastmod should move with the same edit, because Google's sitemap documentation says it uses that value only when it is consistently and verifiably accurate, and a new copyright year does not count as a significant change.

The relaunch week, and the scorecard eight weeks later

A refreshed page deserves the attention a new one gets. Publish the update, then run URL Inspection in Search Console and click Request indexing. Google's URL Inspection help says there is a daily limit on requests and that a request does not guarantee indexing, so save it for the pages that matter and let the sitemap handle the rest.

Then treat it like a launch. Send it to the email segment it serves, hand it to the staff who answer that question, and give it the first week our content distribution guide describes. Log the relaunch date in the spreadsheet.

Judge it later than feels comfortable. Google's debugging guide suggests waiting a few weeks before analyzing again. Compare clicks, position and, above all, calls and forms that started on the page against the same window before the edit, and against the same weeks last year if the topic is seasonal. Pages that recover stay on the quarterly list. Pages that do not get one more look, then a merge.

A quarterly habit, or a team that keeps the list moving

For a site with a few dozen posts, the decay list is a quarterly afternoon: twenty minutes of Search Console, an hour per refresh, a little longer per rewrite. It belongs on the same calendar as broken links, plugin updates and the rest of SEO maintenance. Sites with hundreds of aging posts usually need the merge decisions made in one pass first, which is where a topic cluster plan earns its keep.

If the list keeps growing faster than the afternoons, DataCram's content marketing service runs the relaunch: we pull the decay list, interview you for the facts that changed, rewrite or merge, set the redirects and report on the calls each page brings back. On sites we build, Athena CMS helps between rounds: Ariadne suggests internal links, Atlas flags thin structure and Argus watches the site, each drafting for your approval. For a free first look, the website audit checks speed, SEO, mobile, security and content and emails a report with fixes.