How Often to Refresh Old Content (By Type)
A content refresh cadence tells you which old posts to update, how often, and what to actually change so the update is real and not cosmetic.
A content refresh cadence is a repeating schedule for checking published posts against current facts, current rankings and current competitor pages, then updating the ones that need it. It matters because most sites lose more ranking value to pages quietly going stale than they gain from publishing new ones.
This is one recurring task inside a wider SEO content strategy — the calendar has to leave room for maintenance, not just new posts.
On this page
What counts as a refresh, versus a rewrite?
A refresh updates what has gone stale in an otherwise sound page: numbers that changed, a tool that got renamed, a competitor that entered the market, a section that is thinner than what now ranks above it. The structure, the core argument and most of the original text stay. A rewrite starts over because the original approach no longer works — wrong intent, wrong format, or built around a product that no longer exists.
Most posts need a refresh, not a rewrite. Reach for a rewrite only when the page's fundamental angle is the problem, not its details — refreshing a page built on the wrong premise just produces an updated version of something that was never going to rank.
There is a third option worth naming separately: consolidation. Two or three old posts that all answer near-identical questions, published before anyone noticed the overlap, are usually better merged into one stronger page with the weaker ones redirected than refreshed individually. Refreshing three competing posts just produces three slightly-better competing posts, still splitting the same ranking signal three ways.
Deciding between the three options comes down to one question: is the page's core premise still right? If yes, refresh it. If the premise was wrong from the start, rewrite it. If the premise is right but duplicated elsewhere on the site, consolidate it.
How do you decide which posts to refresh first?
By where the fastest recoverable value sits, not by publish date. Two groups matter most: pages whose organic traffic has dropped meaningfully over the last six to twelve months, and pages sitting on page two of search results with real impressions but few clicks. Both are already close — a page two ranking usually needs less than a rewrite to cross onto page one, and a page that used to rank and dropped has a known baseline to recover toward.
Pull twelve months of Search Console data
Sort by the largest year-over-year drop in clicks for pages that once earned real traffic.
Add page-two rankings
Filter for average position eleven through twenty with meaningful impressions — these are near misses, not failures.
Check the current top three results for each
What do they cover that your page does not? That gap is the refresh brief.
Rank the list by effort versus expected lift
A ten-minute fact update on a near-miss page usually beats a half-day rewrite of a page that never ranked.
What does a good refresh actually change?
Something real, in one of four places: facts that changed, a gap the current top results cover and yours does not, structure that has aged (a wall of text where competitors now use tables and steps), and internal links that point at pages which no longer exist or no longer matter. A refresh that only touches the publish date without changing any of these is not a refresh — it is a claim the sitemap's lastmod field is built to represent honestly, and search engines use that field to decide how often to recrawl a page [3]. Backdating that claim without a real change is a small dishonesty that tends to compound: once one page's date is faked, there is no way for a reader, or an editor auditing the site later, to trust any of the other dates either.
Sourced claims deserve the same scrutiny on a refresh as they did on the original draft. A statistic that was accurate two years ago and is quietly wrong today is worse than no statistic at all, because it reads as current and confident while being false. Re-verifying every source URL and every number during a refresh is tedious and exactly the step that gets skipped under a deadline — which is also exactly why it is the step that most separates a refresh done well from one done for appearances.
| Real refresh | Cosmetic refresh |
|---|---|
| Updates numbers, examples or sources that are out of date | Changes the publish date and nothing else |
| Adds a section covering a gap competitors now cover | Reorders existing paragraphs with no new information |
| Fixes internal links pointing at pages that no longer exist | Leaves dead links because the page still 'looks' fine |
| Re-checks every cited source is still live and still says what it did | Assumes old sources are still accurate |
How often should the cadence run, by content type?
Not on one fixed schedule for the whole site. Fast-moving topics — tool comparisons, pricing pages, anything naming a specific product version — deserve a check every three to six months, because the facts underneath them change on that rhythm. Evergreen how-to and definitional posts hold up longer and can run on a nine-to-twelve-month cycle. Anything inside an active topic cluster should be checked whenever a sibling spoke publishes, since a new spoke often makes an existing one's coverage look thin by comparison.
Treat the cadence as a standing calendar slot, not a reaction to a traffic drop you happened to notice. A fixed monthly or quarterly block — even a small one — catches decline before it shows up as an alarming graph, and it is far cheaper than the full recovery project a page needs after two years of neglect.
A simple starting split for a small team: reserve one refresh for every three or four new posts on the calendar. That ratio keeps maintenance from being squeezed out entirely by the more visible work of shipping something new, without stalling growth for a site that still has real gaps to fill. As the published library grows past a hundred or so pages, the ratio should shift further toward maintenance, because the number of pages that can quietly go stale grows faster than the number of genuinely new topics left to cover.
Who should do the refresh, and who signs off?
The same discipline a new post follows: a named author makes the changes, and a different named person reviews them before the update ships. This matters more for a refresh than people assume, because author pages and E-E-A-T depend on the byline meaning something — a page silently edited by someone who never reviewed the original, with no record of who checked the new claims, is weaker evidence of expertise than one nobody touched at all.
A refresh calendar is the least exciting line item in a content plan and usually the highest-return one. Nobody gets excited pitching 'we updated twelve old posts this month,' but that work recovers traffic faster than almost anything we do.
How do you know whether a refresh actually worked?
Watch the specific page's clicks and average position for at least eight weeks before judging it. Search engines take time to recrawl and reassess a changed page, and a shorter window mostly measures noise. Compare against the page's own trailing baseline, not against a competitor or an unrelated post — the question is whether this page recovered, not whether it beat someone else's number.
If a refreshed page has not moved after two full recrawl cycles, treat that as new information rather than a wasted effort: either the page needs the rewrite you decided against, or the real problem was never on the page — check whether internal links to it still exist and whether something upstream, like a lost backlink, explains the drop instead.
Keep a simple log of what changed and when, even a one-line note per refresh. Six months later, when someone asks why a page's traffic moved, "refreshed the pricing section and added a comparison table on March 3rd" is the difference between a real answer and a guess. That log is also what turns a one-off refresh into an actual cadence — a repeatable habit the team can point to, rather than something that only happens when a page's decline becomes impossible to ignore.
Questions people also ask
How do I decide which posts to refresh first?
Sort by traffic that has dropped over the last six to twelve months, then by pages sitting on page two of search results with real impressions. Both groups are close to recovering traffic with a fraction of the effort a new post takes.
Does changing the publish date count as a refresh?
No, and doing it without a real content change is a trust problem, not a shortcut. Update the date only when the body actually changed — new information, corrected claims, or a meaningfully expanded answer.
Can a refresh hurt a page that was already ranking fine?
Rarely, if the change is additive — new information, fixed errors, better structure. It can hurt if a refresh strips out the specific passages that were earning citations or rankings in the first place, which is why the original should be reviewed before anything is cut.
How long does a refresh usually take compared to a new post?
Well under half the time in most cases, because the research, structure and internal links already exist. Most refreshes are a few hours: updated facts, a new section for a gap, corrected links, and a re-read for anything that has quietly gone stale.
Sources
- How to Do a Content Audit (Step-by-Step Process) — Ahrefs (checked 22 September 2026)
- How to Do a Content Audit — Moz (checked 22 September 2026)
- Build and submit a sitemap — Google Search Central (checked 22 September 2026)
Get your existing content audited before you write anything new
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Ibrahem HelalCo-founder
Leads strategy and delivery.
Works on: SEO, GEO
Reviewed before publishing by Jeremy Zava, Co-founder.
- Topic Clusters: The Pillar and Spoke ModelA topic cluster is one deep pillar page plus several narrower spoke posts that all link to it and to each other. Here is how to build one properly.
- Google's AI Content Policy, ExplainedGoogle does not ban AI-written content. It bans content, AI or not, produced at scale mainly to manipulate rankings. Here is the actual line.
- Author Pages and E-E-A-T: What to BuildA real author page with credentials, a bio and a body of published work is one of the cheapest E-E-A-T signals a site can add. Here is what belongs on it.
- SEO content strategy: the 2026 guideHow to plan, write, review, refresh and measure content that ranks in Google and gets cited by AI assistants, without tripping the spam policies.