Skip to main content

Content Writing

How Often Should You Update Old Blog Posts?

There is no single right interval. Review posts on a tiered schedule set by how fast the topic changes and how much the post matters, and update when something has changed.

Content Writing Square Team Editorial Team 5 min read

There is no single right interval. Review fast-changing and commercially important posts every three to six months, stable evergreen posts once a year, and update a post whenever something in it has actually changed: a fact, a price, your service, or what the search results now expect. A review is cheap; an update should only happen when it will make the post better.

Updating is now a mainstream habit rather than a specialist tactic. Orbit Media's long-running blogger survey reports that the share of bloggers updating older articles peaked at 73%. The question is less whether to do it than how to spend limited time on the posts where it pays.

Why a Single Schedule Does Not Work

A guide to writing a good meta description may stay accurate for years. A post comparing software prices can be wrong within months. Putting both on the same twelve-month cycle wastes time on the first and leaves the second misleading readers for most of the year.

The interval should be set by two things: how quickly the topic goes out of date (volatility) and how much the post matters to the business (traffic and commercial value). Combine them and you get tiers.

A Tiered Review Schedule

TierWhat belongs hereReview everyTypical update
1. Volatile and commercialPricing, comparisons, tool roundups, regulations, anything with a year in the title, posts that send leads3 monthsFacts, prices, screenshots, CTAs
2. Important evergreenYour top 20% of posts by clicks, and posts linked from service pages6 monthsNew sections from Search Console queries, links, examples
3. Stable evergreenHow-tos and explainers on slow-moving topics12 monthsAccuracy check, internal links
4. Low-value archiveOld news, event write-ups, posts with no traffic and no business roleAt the annual auditUsually merge, leave or remove rather than update

Tag each post with its tier in your content inventory and put the next review date beside it. Most blogs end up with a small Tier 1, a modest Tier 2 and a long Tier 3, which keeps the monthly workload predictable. If you do not have an inventory yet, a blog content audit produces one.

If You Have Never Updated Anything

Do not try to put the whole archive on a schedule in one go. Start with the twenty posts that matter most and work outwards:

  1. Export the last twelve months from Search Console's Pages tab, filtered to your blog, and sort by clicks. The top twenty go into Tier 2 by default.
  2. Scan the full list of titles for years, prices, tool names and regulations. Those posts go into Tier 1 whatever their traffic.
  3. Add any post linked from a service page or used by your sales team. Prospects read those at the moment they are deciding.
  4. Everything else goes into Tier 3 with a review date spread across the next twelve months, so the work arrives evenly rather than all in one month.

That first pass usually takes an afternoon and leaves you with a calendar instead of a guilty backlog.

Signals That a Post Needs Updating Now

The schedule catches slow drift. These triggers override it:

  • Outdated detail: a fact, statistic, price, product name, screenshot or regulation has changed. Fix immediately on commercial posts.
  • Falling performance: clicks or impressions down noticeably against the same period last year. Search Console's date comparison shows this in minutes; the steps are in how to use Search Console to improve blog content.
  • Business change: you renamed a service, dropped a product, changed your pricing model or moved into a new market.
  • Stronger competition: the pages above you now cover questions yours does not.
  • New linking options: you have published newer posts the old one should link to, or that should link to it.
  • Near-miss queries: Search Console shows impressions for relevant queries at positions 8 to 20 that the post does not directly answer.

What Counts as an Update

Not every edit is an update worth announcing. A useful distinction:

ChangeExampleChange the 'Last updated' date?
MaintenanceFixing a typo, replacing a broken link, swapping a screenshot of the same thingNo
Substantial updateReplacing outdated facts, adding sections, rewriting the introduction, new examplesYes
RewriteMost of the text replaced, same URL and intentYes

Changing the date without changing the content is the classic shortcut, and Google calls it out by name. Its guidance on helpful content asks: are you changing the date of pages to make them seem fresh when the content has not substantially changed? Treat the date as a promise to the reader that something is new.

When you do update, Google's documentation on byline dates recommends a visible, labelled date (for example "Last updated") that matches the dateModified value in your structured data. Keep the original publish date as well; readers like to know a post has a history.

One Review, Start to Finish

Take a hypothetical Tier 1 post, "How much does a bookkeeper cost for a small business", published eighteen months ago. The three-month review finds that two of the hourly rates quoted have changed, Search Console shows new impressions for "bookkeeper vs accountant cost" at position 12, and the call to action still points to a service page that has since been renamed. That is a substantial update: new figures with sources, a short section comparing the two roles, a corrected link, and a new "Last updated" date. A similar review three months later might find nothing has changed, in which case the only edit is the next review date.

How Much Time to Give Updates

The return can be substantial. HubSpot reported that its historical optimisation project more than doubled the monthly leads generated by the old posts it optimised, and lifted their organic views by an average of 106%. That was one large blog with a deep archive, so treat it as a sign of what is possible, not a forecast.

A practical rule of thumb for capacity:

  • Under 30 posts: mostly publish new posts. Fix errors as you find them and review everything once a year.
  • 30 to 150 posts: roughly one update for every two or three new posts, drawn from Tier 1 and Tier 2.
  • 150+ posts or a falling traffic line: run an audit first, then let the refresh queue set the ratio for a few months, even if new publishing slows.

A Monthly Routine That Takes About Two Hours

  1. Open the inventory and filter for posts whose review date falls this month.
  2. Check each one: still accurate? Still the right CTA? Any new near-miss queries?
  3. Mark each as "no change", "maintenance" (do it now) or "substantial update" (schedule it).
  4. Run a Search Console comparison against last year to catch any decaying posts outside the schedule.
  5. Set the next review date on every post you touched.

The substantial updates then go through a proper process; how to refresh outdated blog content covers diagnosis, rewriting and measuring the result.

If the review list grows faster than your team can clear it, our blog management service is one way to hand it over, with an in-house team and no lock-in on standard plans.

Questions

Questions about this article

Still unsure about something? Talk to a specialist — no script, no sales pitch.

It can, when the update makes the post more accurate or more useful than the results it competes with. HubSpot reported large gains from optimising old posts on its own blog. What does not help is a cosmetic change: Google's guidance specifically questions changing dates to make pages seem fresh when the content has not substantially changed.

Keep the original publish date and add a visible 'Last updated' date when the change is substantial, with matching dateModified in the structured data. Google's documentation on byline dates recommends labelled, visible dates that agree with the structured data. For a typo fix or a swapped link, leave the dates alone.

Base it on capacity and on the size of your refresh queue, not on a fixed ratio. A common working split for an established blog is roughly one update for every two or three new posts, rising if an audit shows many decaying pages. A new blog with fewer than thirty posts should mostly publish new material.

The usual triggers are a fall in clicks or impressions compared with the same period last year, facts or prices that have changed, a change in what you sell, competing pages that now answer the question more thoroughly, and new posts on your own site that it should link to. Search Console's date comparison shows the first trigger in minutes.

Update if the existing URL targets the same intent and has any visibility or links, because you keep what it has earned. Write a new post when the intent has genuinely changed, for example a 2022 tool comparison that is now about different tools, or when the update would turn the post into something with a different purpose.

Ready when you are

Ready to work with the pros?

Get a free proposal in 24 hours — scope, timeline and fixed price. No obligation, no lock-in contract.

Trusted by 13,000+ businesses · 30M+ words published · 50+ industries