Should You Update Old Blog Posts or Write New Ones?

Why does old content stop bringing in traffic?

Old posts lose traffic for reasons that have nothing to do with quality. Competitors publish something newer. The advice inside goes stale. Search intent shifts. Google reshuffles the page. Nothing broke on your end, but the post quietly slides down, and most site owners never notice until the whole blog flattens.

This is the question we get most often from founders who have been publishing for a year or two. They did the work. They have forty posts. Traffic went up, then plateaued, then started drifting down. The instinct is to publish more. That instinct is usually wrong.

The honest answer is that a blog is not a pile of articles. It is a portfolio of assets, and assets need maintenance. Deciding what to fix and what to leave is a skill, and it is worth more than raw publishing volume.

What is content decay and how fast does it happen?

Content decay is the slow decline of a page's organic traffic and rankings over time. Ahrefs defines it exactly that way, and stresses that it happens over months or years rather than overnight. That slowness is the problem. A sudden drop gets attention. A gradual one gets ignored.

The scale of the wider problem is worth sitting with. Ahrefs studied roughly 14 billion pages in 2023 and found that 96.55% of them get zero traffic from Google, with another 1.94% getting between one and ten monthly visits. Most published content never gets read at all.

That statistic gets quoted as doom, but we read it differently. It means the bar is low and the competition is thinner than it looks. Most pages fail for boring reasons, including topics nobody searches for and pages nobody links to.

Decay also is not uniform. Posts about tools and platforms rot fastest, because the products change. Posts about principles age slowly. We plan maintenance around that difference rather than treating every post the same.

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

Update the old post when it already ranks somewhere and covers the same question you would write about anyway. Write a new post when the topic is genuinely different. The test is not age. The test is whether the existing page and the new idea are answering the same reader question.

HubSpot's own reporting on this is the clearest public data we know of. On its blog, HubSpot says it increased monthly organic search views of the old posts it optimized by an average of 106%, and more than doubled the monthly leads those posts generated. That is from updating, not publishing.

The same HubSpot article reports that 76% of its monthly blog views came from posts published before that month, and that 92% of its monthly blog leads came from those older posts. If most of your results come from the archive, most of your effort probably should too.

The trap is writing a second post that competes with your first. Two pages targeting one question split your links and confuse the search engine about which to rank. When we find that pattern, we merge the two into the stronger URL rather than keeping both alive.

Which old posts are worth updating first?

Start with pages that rank between positions five and twenty for a query with real demand. Those pages have already proven they can compete. A modest improvement can move them onto the visible part of page one, where almost all of the clicks are. Pages ranking at 80 need a rewrite, not an update.

Google Search Console is the tool for this, and it is free. Filter to the last three months, sort by impressions, and look for pages with high impressions and a low click-through rate. That gap means people see you and choose someone else, which is usually a title and intro problem rather than a content problem.

The second list is pages that used to perform and no longer do. Compare a recent three-month window against the same window a year earlier. The biggest losers are your decay list. We walk through this comparison in more depth in our guide on how we diagnose a traffic drop.

The third list is pages that are simply wrong now. A post recommending a tool that shut down, or a workflow that a platform removed, is worse than no post at all. Those get fixed first regardless of traffic, because they cost credibility.

What does a real content update actually involve?

A real update changes the substance of the page. That means new sections that answer questions the original missed, replaced statistics with current sources and years, removed advice that no longer applies, and a rewritten introduction that matches how people phrase the question today. Swapping a few words is not an update.

We start by reading the page as a stranger would and writing down every question it fails to answer. Those gaps become the new headings. This is more useful than tinkering with keyword density, because it is the questions that the answer engines and the readers both care about.

Then we check every number on the page. Any statistic without a named source and a year gets either sourced properly or deleted. Any statistic older than about three years gets replaced if a newer figure exists. This one habit does more for trust than any other edit we make.

Internal links are the last pass. An old post written before your newer, better articles existed has no links to them. Adding those links helps readers and spreads authority across the cluster, which is the practical mechanism behind building topical authority.

Does changing the publish date help your rankings?

Changing the date on its own does nothing good, and Google says so directly. Its guidance on creating helpful content lists "changing the date of pages to make them seem fresh when the content has not substantially changed" as a warning sign of search-engine-first thinking. Update the date when you update the content, not instead.

Google's same documentation goes further. It asks whether you are adding or removing lots of content mainly because you think making the site seem fresh will help rankings, and answers its own question in a parenthesis: no, it will not. That is unusually blunt for vendor documentation.

Our approach is to keep both dates visible. Show the original publish date and a separate "last updated" date, and only move the updated date when the substance actually changed. Readers can tell the difference, and so can anyone auditing your site later.

There is a practical reason beyond honesty. If you fake freshness across a whole archive, you lose your own signal. You can no longer tell which posts have genuinely been maintained, which makes your next round of maintenance guesswork.

How do updates affect AI search and citations?

Freshness appears to matter more to answer engines than to classic search. Ahrefs reports that URLs cited by AI assistants are on average 25.7% fresher than the URLs ranking in organic search. If that pattern holds, a maintained archive has a real advantage in AI answers.

The mechanism makes sense. Systems like ChatGPT, Perplexity, Claude, and Google AI Overviews are assembling an answer right now, and a page that contradicts current reality is a liability for them. Current numbers with named sources are easy to quote. Vague, undated claims are not.

This changes what an update is for. We are no longer only trying to move a ranking. We are trying to keep a page quotable, which means clear answers near the top of each section and statistics a model can attribute to somebody.

We would still not chase freshness for its own sake. A page that is accurate and three years old beats a page that was touched last week and says nothing. The goal is a page that is true today, and updating is just how you keep it that way.

When should you delete an old post instead?

Delete or merge a post when it has no traffic, no links, no strategic purpose, and no realistic path to any of those. Thin posts written years ago to hit a publishing quota are the usual candidates. Keeping them costs nothing in hosting and something in clarity.

Merging beats deleting in most cases. Take the useful parts of the weak post, fold them into the stronger one, then redirect the old URL to the new home. You keep whatever links the old page earned and you stop two pages from competing for the same query.

Be careful with pure deletion. Google's guidance warns against removing lots of older content mainly to seem fresh, and a page with no search traffic may still be the page a customer reads before they buy. Check referral traffic and assisted conversions before you cut anything.

When we do remove a page, it gets a permanent redirect to the closest relevant page, never to the homepage. A visitor who followed an old link wanted something specific, and dropping them on the homepage just makes them leave.

How often should you review your content?

Review the whole archive twice a year, and check your top twenty pages every quarter. Most sites do not need more than that. The point of a schedule is to catch decay while it is small, because a page that slipped from position four to position eight is far easier to recover than one that fell off entirely.

We keep it simple. A quarterly look at Search Console for the biggest movers, and a twice-yearly pass over everything to flag pages with stale numbers, dead tool references, or broken links. Screaming Frog handles the broken link sweep in minutes.

Set a ratio rather than a rule. If you publish four posts a month, updating one or two existing posts in the same month is a reasonable balance. Teams that publish constantly and never update end up with a large archive that mostly does nothing.

This is also the honest answer to the wider question of whether blogging still pays off, which we covered in our piece on whether you should still blog for SEO. Publishing alone stopped working a while ago. Publishing plus maintenance still works.

What should you do this month?

Open Google Search Console, sort your pages by impressions, and find the five with the most impressions and the worst click-through rate. Fix their titles and opening paragraphs first, because that is the cheapest change with the fastest feedback. Then pick one decaying post and rebuild it properly.

Resist the urge to update everything at once. A large batch of edits makes it impossible to learn what worked. Change a handful of pages, wait four to six weeks, and look at what moved. That feedback is what turns maintenance into a repeatable process instead of a chore.

The mindset shift matters more than the tactics. Treat every published post as something you own and maintain, not something you shipped and forgot. Sites that do this quietly pull ahead of sites that only chase new word counts. Working out what is missing in the first place is its own job, and we cover it in using AI to find content gaps. Deciding which old posts should be cut rather than saved is a separate question, and we work through it in our guide to content pruning.

If you want a second opinion on which posts are worth saving and which should be merged away, we are happy to look through it with you. Reach out at phoenix.studio and we will give you a straight answer about where your archive is actually leaking.