Content Decay: Decide Which Pages to Refresh, Merge, or Leave Alone

Content decay is a maintenance question, not an expiry date#

Content decay describes a sustained decline in an existing page’s usefulness or search performance. The page may contain outdated instructions, miss a changed customer question or face better competing resources. It may also be losing traffic because demand fell, which is a different problem from the content itself becoming worse.

Do not assume every older article is decaying. A clear explanation of a stable concept can remain useful for years. Conversely, a new article can become inaccurate quickly if it describes a changing interface or policy. The maintenance decision should follow the task and evidence, not a rule that everything needs a new date.

For a sharp site-wide loss, start with the traffic-drop diagnostic. This guide is for examining individual resources and related page groups after obvious access or reporting failures have been considered.

Build a shortlist from meaningful losses#

Compare complete periods in Search Console and group equivalent seasonal windows where possible. Look for changes in clicks, impressions, queries and positions, then connect those observations with the page’s business role. A resource with fewer visits but the same useful enquiries may deserve a different priority from one losing both.

Keep absolute numbers visible. A 50% decline from a very small base can look more important than a modest percentage loss on a valuable entry page. Group exported queries with the SEO Regex Builder and Tester to inspect query mix as well: the page may have lost irrelevant impressions while preserving the searches it was built to answer.

Review the current result pages and customer task. Are people now looking for a calculator, a comparison, a current procedure or a local service? A longer article will not solve a format mismatch just because it contains more related phrases.

Choose between keeping, refreshing and merging#

Keep the page when it remains accurate, useful and distinct and the evidence does not justify a change. Add it to a review schedule if the topic is likely to change. Leaving a healthy resource alone is an active decision.

Refresh when the same page still serves the right task but its answer has gaps or obsolete material. Replace inaccurate steps, improve examples, repair broken references and make the next decision clearer. Retain useful sections instead of rewriting every sentence to make the page look newly written.

Consider merging when two or more pages genuinely answer the same task and compete for the same role. Identify the strongest relevant destination, carry over unique useful information and plan appropriate redirects and internal-link updates. Similar keywords alone are not enough; separate user needs can justify separate pages.

Treat consolidation as a small migration#

Before merging, record which sections and queries belong to each source page and which links point to them. Preserve the material a reader still needs. The destination should be a better answer to the original task, not simply the page with the largest traffic estimate.

If an old URL is permanently replaced, use the appropriate permanent redirect to the relevant final destination. Update internal links and the sitemap. Test that the destination is accessible, indexable as intended and not part of a redirect chain. Google’s migration guidance is useful here because consolidation changes the routes people and crawlers follow.

Where no suitable replacement exists, assess whether the resource should remain as a clearly dated archive or return a proper removal response. Do not manufacture relevance just to avoid a missing-page status.

TECHNOB EDITORIAL TAKEAWAY

Refresh the answer when the answer is the problem. Preserve the URL when it still has a useful job.

Measure the change without claiming an instant recovery#

Record what changed, why and when. Compare the same query and page group after enough time for discovery and reassessment. Consider demand, result-page changes and competing updates alongside your own work. The before-and-after movement alone cannot establish causation.

Build maintenance into the SEO plan so it competes fairly with new content. Assign review triggers based on the topic: changed product behavior, obsolete screenshots, broken references, repeated customer questions or a sustained performance loss.

Ahrefs’ competitor guide covers a broad update, consolidation and pruning workflow. The framework here emphasizes a narrower decision: the minimum useful change for the specific resource. That keeps maintenance from becoming a requirement to republish everything on a calendar.