Content Decay: Spotting and Fixing Pages That Are Slipping

What content decay looks like

Decay is not a one-week dip. It is a sustained decline in visibility for a page that previously earned stable organic traffic. Impressions fall, average position worsens, or clicks drop while the query set shrinks. The page may still be indexed. It is simply less often chosen as a useful result.

Decay happens because competitors improve, facts age, SERP formats change, intent shifts, or your own newer URLs steal the same queries. Treating every decline as a random algorithm mood hides those concrete causes. Your job is to diagnose which cause applies, then pick a fix that matches.

How to spot decay without false alarms

Start in Search Console with pages that had meaningful traffic, not zero-impression URLs. Compare a recent 28-day or 90-day window against the same period last year when seasonality matters. Sort by largest absolute click or impression losses. Exclude URLs hit by known sitewide issues like outages or temporary noindex mistakes.

• Filter to URLs with a prior baseline of clicks or impressions
• Flag declines that persist across multiple weeks
• Check brand vs non-brand query mix for the URL
• Note whether lost queries still appear on other pages you own
• Open the live SERP for the top lost queries before rewriting

Seasonality fools people. Tax topics, holiday guides, and academic calendars swing every year. Compare year-over-year before you declare decay. Tracking changes also fool people: a new Search Console property filter or a migrated URL can look like collapse when the page simply moved.

Diagnose the cause before you rewrite

Three questions save rewriting time. Did the SERP format change? Did a stronger page appear? Did your content become incomplete or inaccurate? Open the current top results for the queries you lost. If winners now use comparison tables and your page is a soft overview, the fix is structural. If winners updated 2026 examples and yours still cites older defaults, the fix is factual refresh.

Cannibalization deserves a special check. If Page A decays while Page B rises on the same queries, a rewrite of Page A can worsen the conflict. Fix ownership first. Keyword cannibalization detection should sit inside every decay audit.

Fix path one: refresh the URL

Refreshing is the default when the URL still matches intent and retains some equity. Update facts, improve headings to match current questions, strengthen weak sections competitors now cover, and clarify the introduction so the page answers faster. Keep the URL stable when the topic is the same. Changing slugs resets signals you may still need.

1. List parity gaps against the current top three results
2. Update or replace outdated sections first
3. Improve examples, screenshots, and definitions users rely on
4. Tighten title and meta description to match the refreshed promise
5. Re-check internal links from your hub pages after the update

A refresh is a project with a brief, not a casual paragraph tweak. How to refresh old content instead of writing new covers the fuller workflow. Many decayed pages recover faster from a serious refresh than a brand-new URL ever climbs.

Fix path two: consolidate overlapping pages

When two or more URLs share intent, pick a winner. Merge the best sections into that winner, redirect losers, and update links. Consolidation looks aggressive, yet it often restores visibility by ending self-competition. Keep a short changelog so stakeholders understand why URLs disappeared.

Choose the winner based on historical performance, backlink profile, index health, and URL clarity. Do not automatically keep the newest draft. Do not automatically keep the oldest either. Evidence beats nostalgia.

Publishing a third overlapping article is the most expensive way to avoid deciding which URL owns the query.

Fix path three: prune or retarget

Some pages should not be saved. If demand disappeared, if the page never earned meaningful traffic, or if maintaining accuracy is impossible, prune. Redirect to a relevant parent when a clear successor exists. Retarget only when a different intent is still valuable and the URL can honestly serve it without confusing users.

Pruning improves crawl focus and reduces library noise. It is part of healthy maintenance, not an admission of failure. Teams that never prune eventually drown editors in pages nobody reads and nobody wants to update. An content audit and refresh process usually ranks URLs into refresh, consolidate, keep, and prune buckets for that reason.

Build a decay review cadence

Waiting for traffic emergencies is a poor system. Schedule a monthly or quarterly decay review for URLs above a traffic threshold. Keep a simple sheet: URL, baseline clicks, current clicks, suspected cause, owner, next action, due date. Close the loop after fixes by checking whether impressions stabilize or recover over the next 4 to 8 weeks.

• Protect high-traffic URLs with earlier review thresholds
• Batch similar refreshes by topic so research is reused
• Document SERP notes with dates for each major fix
• Alert writers when a cluster hub is decaying so spokes are checked too
• Resist publishing replacements until consolidation is ruled out

What recovery usually looks like

After a solid refresh, some pages regain impressions within weeks. Others need longer if competition moved far ahead. Consolidation can show faster query cleanup once redirects settle. If nothing moves after a real fix and clean indexing, revisit whether the topic is still worth the investment.

Decay is normal in a living search environment. Ignoring it is optional. The teams that keep organic performance steady treat slipping pages as a maintenance queue with clear owners, not as a mystery to discuss every quarter without action.