How to Refresh Old Blog Posts That Stopped Bringing Traffic

To refresh old blog posts that stopped bringing traffic, do not start by writing anything new. First find the posts that are actually decaying, by comparing clicks per page against an earlier period in Google Search Console. Then work out why each one dropped: a better page outranks it, searchers want something different, the facts went stale, or two of your own posts compete. Fix the cause, not the date. Refresh posts that still match the search, rewrite the ones whose intent shifted, merge overlapping posts with a permanent redirect, and delete only what has no traffic, no links and no signups. Then wait a few weeks and compare clicks and signups before and after.

This guide is for indie SaaS founders with 20 to 100 blog posts or docs-style articles, where a few posts that used to bring signups have quietly slid. The worked example company, its founder and every number in it are made up for illustration.

What is content decay, and why do old posts lose traffic?

Content decay is the slow loss of search traffic on a page that used to perform well. It rarely looks like a cliff. It looks like a post that brought a steady trickle of signups last year and now brings half that, unnoticed because the site's total traffic line still looks fine.

Posts usually lose traffic for one of six reasons:

• Someone published a better page. A more complete, current or specific answer to the same question moved above you.

• The search intent shifted. People typing the same words now want a template instead of an essay, or a comparison instead of a definition.

• The information went stale. Old screenshots, changed prices, a recommended tool that shut down, last year's date in the title.

• The results page changed. More of the answer appears on Google itself, or other results earn richer snippets, so fewer people click even if your position barely moved. The Aura++ guide to getting your startup cited in AI search answers covers that side.

• Something technical broke. A stray noindex tag, a broken redirect, a changed URL or a page that became slow. For speed, see the IndieHunt guide to passing Core Web Vitals on your indie SaaS site.

• Two of your own posts compete. You wrote a second post on nearly the same question, and neither ranks well now.

Sometimes nothing is wrong and demand simply moved. Google's guide to debugging drops in Search traffic lists seasonality and changing interests as a main cause, and suggests checking your top queries in Google Trends to see whether the drop is only yours.

How do you find decaying posts in Google Search Console?

You are looking for pages that lost the most clicks compared with an earlier period, not pages with the fewest clicks overall. The Performance report does this:

1. Open Performance, then Search results.

2. Click the Date filter, choose the Compare tab, and compare the last 3 months to the previous period, or year over year if your topic is seasonal.

3. Switch the table to Pages. With a comparison active, each row gets a Difference column.

4. Sort by Clicks Difference so the pages that lost the most traffic come first. Google's traffic-drop guide recommends exactly this.

5. Click a page row to filter to that page, then open the Queries tab to see which searches it lost.

Two settings keep the comparison honest. Look once at Last 16 months to see whether last year had the same dip at the same time. And Google's help page on advanced filtering and comparison in the Performance report suggests Weekly or Monthly granularity when comparing date ranges, to smooth out the weekday effect.

Then add what Search Console cannot give you: signups. In your own analytics, list signups by landing page for the same two periods. A post that lost clicks but never brought signups matters less than one that lost fewer clicks but used to be a top source of trials. Keep the shortlist in a sheet (URL, clicks before and after, signups before and after). Five to ten posts is plenty for a first pass.

Which posts should you refresh, rewrite, merge, delete or leave alone?

Match each post's symptom to the likely cause and pick one action.

Google's traffic-drop guide notes that small position changes happen all the time and recommends avoiding radical changes to a page that already performs well. A post that slipped from second to fourth might need a better title, or nothing.

How do you diagnose why one post dropped?

Before editing, spend ten minutes looking at what the searcher sees now.

1. Take the query that lost the most clicks for that post.

2. Search it in a private window and read the top five results properly, not just their titles.

3. Write one sentence on what they have in common: "all five are step-by-step guides with a free template".

4. Write one sentence on how your post differs: an opinion piece, an answer buried in paragraph four, a dead tool.

Then read the numbers. Google's guide says that if impressions hold but clicks drop, your title and snippet may not be the best they could be, or other sites may have a more appealing rich result. If both fell, look at ranking, intent and demand. The IndieHunt guide to finding keywords your indie SaaS can actually rank for explains how to read page one and spot two posts chasing the same intent.

What goes on a content refresh checklist?

A refresh is a real improvement, judged by whether a reader would now pick your page over the top result. Work through this in order and skip what does not apply:

• Answer first. Rewrite the opening so it answers the main query in two or three plain sentences.

• Update every checkable fact. Prices, plan limits, tool names, interface labels, screenshots. Where a fact can change again, write "as of" with the month you checked it.

• Add sections the top results answer and you do not, if they genuinely help. You are filling gaps, not copying an outline.

• Cut dead sections. Advice that no longer works, tools that shut down, padding.

• Fix broken links. Replace dead links with a current source or remove them.

• Add internal links from newer posts to the refreshed one, with descriptive anchors, and link out to your newer related pages.

• Rewrite the title and meta description for the query it actually ranks for. Search Console often shows impressions for a slightly different phrase than the one you targeted.

• Add something only you have. A real example from your product, your own setup, a mistake you made, a small number from your own data.

• Keep the URL. Do not change the slug, even if it looks dated.

For a final check, Google's guide to creating helpful, reliable, people-first content asks whether the page provides substantial value compared with other pages in search results, and whether the title is a descriptive, helpful summary that avoids exaggerating.

Should you change the published date after a refresh?

Only when the change is substantial, and only the visible "Last updated" date. That same people-first guide lists a warning sign: changing the date of pages to make them seem fresh when the content has not substantially changed. It also says adding or removing lots of content to make a site seem fresh will not help.

After a real update, Google's byline-date documentation suggests a clearly labelled, user-visible date such as "Last updated", consistent with dateModified in your structured data if you use it. Google's guide to building and submitting a sitemap says lastmod should reflect the last significant update, and that Google uses it only if it is consistently and verifiably accurate. A main-content update counts; a copyright-date update does not.

Fixed a typo? Leave the date. Rewrote the intro, replaced screenshots and added two sections? Update it.

How do you merge two posts that compete with each other?

1. Pick the winner: usually the URL with more clicks, more links or the cleaner slug.

2. Move the best parts of the weaker post into it, and edit so it reads as one piece.

3. Add a permanent server-side redirect (301) from the weaker URL to the winner.

4. Point your own internal links straight at the winner, and drop the old URL from your sitemap.

Google's page on redirects and Google Search explains that a permanent redirect signals the target should be the canonical page. Its site-move guide adds that you can redirect older URLs to a page that consolidates their content, that redirecting many URLs to one irrelevant page such as your home page can be treated as a soft 404, and that redirects should stay in place as long as possible, generally at least a year. Avoid chains: point any older redirect straight at the winner.

When should you delete an old post instead?

Delete when all of these are true: no meaningful clicks, no other site links to it, it never brought signups, and it has nothing to do with your product. A recap of a conference from four years ago fits. A thin post that some other blog links to does not; redirect it to your closest relevant post. Search Console's Links report shows which pages have external links.

Let deleted URLs return 404 or 410, as Google's site-move guide recommends for content you are not keeping. And do not mass-delete to look tidy; as above, Google says it will not make a site seem fresh.

How do you get Google to recrawl the refreshed post?

Paste the URL into the URL Inspection bar in Search Console, optionally run Test live URL, then click Request indexing. Google's URL Inspection tool help page notes a daily request limit and that a request does not guarantee indexing. Google's recrawl documentation adds that you must be an owner or full user of the property, that crawling can take from a few days to a few weeks, and that repeat requests for the same URL will not speed it up. For many refreshed posts at once, keep honest lastmod dates in your sitemap instead.

How long should you wait, and how do you measure a refresh?

Nobody can promise a timeline. Google's traffic-drop guide says some changes take effect in a few days and others could take several months, that you will likely want to wait a few weeks before analyzing again, and that there is no guarantee of a noticeable effect.

A workable habit: wait until URL Inspection shows a crawl after your change, then give it at least four more weeks. Compare the 28 days before the refresh with 28 days after the recrawl, starting on the same weekday. Track clicks, impressions and, above all, signups from that post. A post can climb and still bring no trials if it ranks for the wrong query.

Keep a refresh log so you learn which fixes work on your site:

After a few months the log tells you whether title rewrites, intent rewrites or merges move the needle for your audience.

What does a monthly refresh routine look like?

Decay is slow, so a small monthly habit beats a yearly cleanup. Block 60 to 90 minutes on the same day each month:

1. Pull the list (15 minutes). Comparison, Pages tab, sorted by Clicks Difference, plus signups per post.

2. Pick one or two posts (10 minutes) with the triage table, by lost signups first and lost clicks second.

3. Diagnose (10 minutes per post). Search the query, read the top results, write your two sentences.

4. Fix (30 to 45 minutes) with the checklist, or set up the merge.

5. Log and request indexing (5 minutes).

6. Review last month (5 minutes). Fill in the "after" columns that are due.

What mistakes should you avoid when refreshing old content?

• Refreshing the wrong posts, because they feel old rather than because they lost clicks or signups.

• Changing the URL. A new slug throws away the history the old one built.

• Deleting posts that still bring links. Redirect those instead.

• Rewriting into a different intent. Turn a how-to into a product pitch and you lose the traffic you meant to save.

• Date bumps without changes. They do not help, and readers notice "updated this month" above old screenshots.

• Chasing rank for queries that do not convert. Prioritize posts that used to bring signups.

A worked example: Gablework's slipping estimate guide

Gablework is invented, and so are its founder and all numbers below. It is a quoting and scheduling tool for small roofing contractors, run by a solo founder named Yusra, with about 40 blog posts.

What the data showed

Comparing the last 3 months year over year, sorted by Clicks Difference, her guide to writing a roof repair estimate had lost the most clicks, and it used to bring a few trials a month. Impressions were down too, and her older post on estimate mistakes was showing for some of the same queries.

What she changed

Four of the top five results offered a downloadable estimate template near the top. Her post opened with a long story, had no template and showed a two-year-old version of her product. She merged the mistakes post in as one section and set a 301, rewrote the intro to answer in three sentences, added a free template, replaced the screenshots, added a real estimate she had helped a customer fix, retitled it for the phrase it actually ranked for, updated the visible "Last updated" date and requested indexing.

Eight weeks later

A title-only change on another post did nothing in the same window, which told her that post's problem was intent, not the snippet. None of this is a benchmark; it shows how the pieces fit together.

FAQ

How often should you update old blog posts?

Review decaying posts monthly and refresh one or two. Update a post when the data shows it losing clicks or signups, or when its facts change, not on a fixed calendar.

Does changing the date on a post help SEO?

Not on its own. Google lists changing dates to make pages seem fresh, without substantial changes, as a warning sign. Change the visible "Last updated" date only after a real update.

Should I delete old blog posts that get no traffic?

Only if they also have no links, no signups and no connection to your product. If other sites link to a post, redirect it to your closest relevant page. If it is old but still accurate, leave it.

How long after a refresh do rankings change?

It varies. Google says crawling can take a few days to a few weeks, and some changes take months to show an effect. Wait for the recrawl, then give it at least four weeks.

If your refreshed posts point people toward a product, you can also put it in front of founders by launching it on IndieHunt.