What Is Content Decay and How to Detect It

Content decay is the gradual, sustained loss of organic search visibility on a page that used to rank and earn traffic steadily. This guide explains what causes it, how to tell it apart from seasonality, algorithm updates and tracking problems, which Search Console signals show it early, and how to set up a monitoring routine that catches it while a refresh is still cheap. What to do once you have found a decaying page is covered in depth in the content refresh playbook.

Decay is rarely sudden. Typically impressions soften first, average position slips a few places, and clicks follow weeks or months later. By the time a traffic chart in a monthly report looks alarming, a good part of the loss has already happened. The teams that hold their organic traffic are usually not the ones publishing the most; they are the ones that notice early and maintain what already works.

What decay is, and what it is not

“Traffic went down” is too broad to act on. Before you call something decay, rule out the other four common causes of a decline. They look different in the data:

Real situations often mix these: a core update can speed up decay that was already under way, or a seasonal peak can hide it for a few months. The point of the table is to make you look before you rewrite. Teams that skip it end up rewriting healthy pages after an update, or ignoring real decay as “just seasonality”.

Decay is a lagging indicator of relevance. The goal is to spot weakening signals while you can still refresh, merge or reposition a page deliberately rather than in a hurry.

Why pages decay

Rankings are relative. A page that was the best answer to a query three years ago can be the fourth-best today without getting any worse, because the pages around it improved. Usually several of the causes below compound.

1. Freshness expectations

Google’s ranking systems guide describes “query deserves freshness” systems designed to show fresher content where searchers would expect it. That is obvious for “best project management tools”, and less obvious for topics where the advice quietly dated: remote-work tips written around a situation that no longer applies, or a comparison whose prices and features have changed. Nothing penalizes the old page; newer, more accurate results simply serve the searcher better.

2. Competitors raising the bar

When competing pages add original data, worked examples, better tables or clearer structure, a static page loses ground by comparison. You only see this by looking at the results page, not your rank alone. See competitor benchmarking.

3. Search intent shifting

The same query can come to mean something different. When the top results move from explanatory articles to product comparisons, tools or templates, an accurate essay still slides. The results page itself shows the shift: different page types and formats at the top. Catching it takes search intent analysis, not just position tracking.

4. Search features taking attention

A page can hold the same position and still get fewer clicks because more of the results page sits above it: AI Overviews, video and image blocks, People Also Ask. Google states that clicks and impressions from AI Overviews and AI Mode are included in Search Console’s Performance report under the “Web” search type, counted in the overall data rather than reported separately (see AI features and your website). So falling CTR at a stable position is the signal to watch, and a live look at the results page is the way to explain it.

Some changes are not decay at all. Google stopped showing FAQ rich results in Search from 7 May 2026, according to its documentation changelog, and How-to rich results were removed in 2023. If a page lost clicks when those features disappeared, no content edit will bring them back. See SERP feature targeting for the features that remain.

5. Ranking updates

Core updates and other ranking changes tend to show as step changes, not slopes. Google’s guidance on core updates says they are broad, do not target individual pages, and that pages which move down are not necessarily bad. The conditions that leave a page exposed to an update, though, often overlap with decay: thin coverage, out-of-date information, unclear expertise, a mismatch with intent. That overlap is why steady maintenance tends to pay off on both fronts.

6. Technical and structural erosion

A redesign drops a page from the navigation, a migration breaks internal links, a canonical tag starts pointing elsewhere, or a template change slows the page. The page itself never changed, but its support did. This is why decay checks must include crawl and indexing data, not only content.

7. Lost links

External pages that linked to you get rewritten or removed, and internal links from strong pages disappear in restructures. For competitive head terms where links carried the ranking, the position eventually follows.

8. Self-competition

As a library grows, newer pages start answering the same queries as older ones. Google tends to pick one, and the other slides, or both sit lower than one strong page would. See how to find and fix keyword cannibalization.

Early warning signals

The cheapest decay to fix is the decay you catch before the traffic chart moves. These signals come first. The thresholds are rules of thumb for pages with meaningful volume; tune them to your own site after a cycle or two.

Three practical notes. Monitor at the page level: a site-wide increase easily hides individual declines. Filter out branded queries, which hold up on their own and mask weakness; Search Console has a branded and non-branded filter for sites with enough impressions. And treat engagement as a hint about your own visitors, not about rankings. In GA4 an engaged session lasts longer than 10 seconds, has a key event, or has two or more page views; bounce rate is the share of sessions that were not.

How to detect decay systematically

One-off checks catch disasters. A routine catches the slow leaks. Build it on three sources: Search Console, crawl and indexing data, and the live results page.

Search Console as the backbone

Search Console is the only source of actual Google impressions and clicks. Everything else is an estimate. Use it like this:

• Year over year by page. Compare the last three months with the same three months last year to remove seasonality. The Performance report holds 16 months, so keep dated exports if you want longer history.
• Then the queries. For each flagged page, check whether every query is falling or only some. Long tail falling while the main query holds means lost breadth. The main query falling is more serious. Remember that rare queries are anonymized: they count in page totals but never appear as rows, so query rows will not add up to the page total.
• Device and country. A mobile-only decline points to a page experience problem rather than content. A single-country decline points to local competition or a different results layout.
• Trend lines, not snapshots. A page losing 5% a month for six months has lost about 26% of its traffic, and no single month looked alarming. Chart consecutive 28-day windows.
• Beyond 1,000 rows. The interface exports 1,000 rows. For a whole site, use the Search Analytics API or Looker Studio, which return up to 50,000 rows per day per site and search type.

Crawl and indexing checks

For every page you flag, answer the structural questions before you touch the copy:

• Does it still return 200, or did a release add a redirect or an error?
• Is it still in the sitemap, and does URL Inspection show it indexed with your chosen canonical?
• Did it lose internal links, for example from navigation or a hub page, in a redesign?
• Did a new page on your own site start ranking for its queries?
• Did the template get slower, or did outbound links break?

If a redesign removed the links a page used to get from a sidebar or hub, that loss may be the main driver, and no amount of rewriting will fix it. The internal linking guide covers how to restore it.

The live results page

For your most valuable pages, look at the results for the main query every quarter and note: the format of the top five (guide, list, tool, template, video, comparison), how recently they were updated, which search features appear, what they cover that you do not, and whether the brands at the top changed. Two or three saved snapshots in a row show the pattern behind a decline, which is what tells you whether to refresh, reformat or reposition.

dash.morrison.app/lumenpay.com/chat

Illustration

lumenpay.com/Decline check: expense template

What do you want to know about lumenpay.com?

Ask about your website content...

Search ConsoleSerpApi

Claude Sonnet 5.5

Telling decay from an update

When a decline lines up with a ranking update, Google’s core updates guidance suggests a specific routine: find the update’s start and end dates on the Search Status Dashboard, wait at least a full week after the rollout completes, then compare a week after with a week before, looking at which pages and queries moved most. For a small drop, Google advises no drastic action and warns against changing content that is already performing well. Recovery after real improvements can take several months, sometimes until the next core update.

Decay, by contrast, has no date to line up with. It starts with impressions, then position, then clicks, over weeks to months, and it usually affects pages one at a time or in small clusters by topic or template.

Worked example

A hypothetical template page, with illustrative numbers rather than client data:

The decay review, step by step

Run this monthly for your most important pages and quarterly for the rest. What changes with scale is how much you automate, not the steps.

1. Build the candidate list. Take pages with enough impressions to be meaningful (100 or more in the period is a common floor) and flag those that trip two or more signals from the table above.
2. Rule out the other causes with the diagnostic steps: tracking, seasonality, update dates, technical changes.
3. Tag the likely cause:freshness, competition, intent shift, search features, technical, lost links, or self-competition. The cause decides the fix, which is why “just rewrite it” is the wrong default.
4. Investigate the top candidates by hand. Read the page, search the main query, and compare. Is it still accurate? Do competitors cover subtopics you miss? Has the expected format changed? Are links and screenshots current? Does the title still describe the page? This judgment is the part that cannot be fully automated.
5. Assign an action, an owner and a date.Pages that need nothing get “reviewed, no action” with a reason, so nobody re-investigates them next cycle.

What to do with a decaying page

Match the action to the cause and the page’s value. This tree covers the common cases; the content refresh playbook covers how to prioritize a long list and run each refresh, and the consolidation guide covers merging and retiring.

• Refresh in placewhen structure and intent are sound but details aged: statistics, examples, screenshots, prices, missing subtopics. Change the visible “updated” date only when the content changed substantially: Google’s helpful content guidance lists changing dates to seem fresh, without substantial changes, as a sign of search-engine-first content.
• Consolidate when several pages split the same intent: keep the strongest URL, merge the best material, 301 the rest and update internal links to point straight at the survivor.
• Rewrite or reformat when intent shifted: the essay that now competes with comparison tables and templates.
• Reposition a strong page with good links toward a related query it can still win, when the original query has moved beyond it.
• Retire deliberately when the topic no longer matters to your business. Redirect only to a page that serves the same need, remove internal links, and record why.

Building a decay monitoring routine

Tier your pages

Not every decline deserves the same attention. A simple tiering, with rule-of-thumb triggers:

Before anyone edits a page, the alert should pass a short triage: no tracking change, no indexing or status change, not a seasonal dip. That order keeps false alarms from eating editorial time.

Owners and review dates

Give every important page an owner and a review interval that fits its type: a product comparison might need review every 90 days, an evergreen explainer once a year, a page about regulations whenever the rules change. Alerts go to the owner, not a shared inbox, where they pile up unread. See content decay detection.

Keep a change log

Log every refresh (date, what changed, who), every new competitor you notice, and every ranking update. Without it you keep asking the same question: did we change something, or did the results page change? The measurement guide covers how to report it.

Where Morrison fits

You can run everything above with Search Console exports and a spreadsheet, and many teams should start there. It gets hard at a few thousand pages, when exports are stale before anyone reads them. In Morrison, the URL grid shows each page’s HTTP status, page type and 90 days of Search Console clicks and impressions, so redirects and errors that look like decay surface on their own. Chat connects to Search Console for queries, URL inspection and sitemaps, and to SerpApi for live results and search features, so you can ask why a specific page is slipping. Chat can also list the pages that lost the most clicks straight from Search Console, and an automation can email that list every week, reading the previous run to say what changed. Automations run weekly or monthly on Starter, up to daily on Pro and up to hourly on Business. See content decay detection and outdated content finder.

Key takeaways

• Decay is specific: a gradual, sustained decline from compounding causes. Rule out tracking, seasonality, updates and technical breaks first.
• Leading signals exist: impressions, position drift, CTR at a stable position and query count move before clicks. Watch them page by page, without branded queries.
• Diagnose before you edit: the cause decides whether to refresh, consolidate, reformat, reposition or retire.
• Do not chase lost features: clicks lost when FAQ rich results ended are not decay.
• Routines beat audits: tiers, owners, a change log and a fixed review rhythm stop small losses compounding.