Every content library decays. Rankings slip, information ages, better competitors publish. The teams that compound treat refreshing as a program with rules — not a panic response to a traffic dip. Here is the framework.
Detect decay before it becomes collapse
Set a quarterly review comparing every significant page’s clicks and average position against the prior period. Decay has a signature: position drift from 3 to 5 to 8 over months, often while the page looks "fine". Catching it at position 5 is a refresh; catching it at position 25 is a rebuild.
Prioritize by value at risk: pages with conversion history or link equity get attention first. A decaying post that never converted anyone may deserve consolidation instead of rescue.
Diagnose why before touching anything
Four distinct diseases produce the same falling line. Outdated information: facts, screenshots, prices, or years that scream neglect. Intent drift: the SERP changed shape — what wanted a guide now wants a tool or a comparison. Competitive displacement: someone simply published better coverage. Cannibalization: your own newer post is splitting the query.
Each has a different cure, and applying the wrong one wastes the effort. Read the current SERP for the target query before opening the editor: what Google rewards today is the spec you’re writing to.
Catching decay at position 5 is a refresh; catching it at position 25 is a rebuild.
Refresh, consolidate, or redirect — the decision rules
Refresh when the page still matches intent and holds equity: update facts and examples, close the coverage gaps competitors opened, strengthen E-E-A-T signals (author, evidence, dates), and improve internal links. Keep the URL; update the modified date honestly.
Consolidate when multiple weak pages split one intent: merge the best material into the strongest URL and 301 the rest. Redirect or prune when the topic is dead or was never yours to win — thin pages with no traffic, no links, and no strategic role dilute sitewide quality signals.
Execute refreshes like releases
Batch refreshes into a monthly cycle with briefs, owners, and deadlines — the same discipline as net-new content. A refresh brief lists what changed in the SERP, which sections to add or rewrite, which internal links to add, and what success looks like at 30 and 90 days.
Resist the temptation to change the things that were working: if the page ranks for forty long-tail variants, wholesale rewrites can vaporize them. Diff carefully; expand more than you replace.
Measure recovery and feed the learning back
Track position and clicks at 30/60/90 days post-refresh. Successful patterns — "adding comparison tables recovered every commercial-intent post" — become standing rules for the next batch. Failures redirect effort: a page that doesn’t respond to a competent refresh is usually fighting an intent shift or authority gap that editing can’t fix.
Mature programs typically find refresh work outperforms net-new publishing on ROI: the page already has age, links, and indexed history. It just needs to deserve its ranking again.
The useful takeaway
Review quarterly, diagnose the specific disease before treating, choose refresh/consolidate/prune by rule, execute in disciplined batches, and measure recovery. Old content with equity is the cheapest growth most sites are ignoring.
