How to Detect Content Decay Using Google Search Console

The blog post that quietly stops working

A tutorial performs well for nine months. It brings people from Google, answers common questions and occasionally turns a reader into a customer. Then visits begin to fall. Nobody notices because the newest posts are getting attention.

This is a typical reason to investigate content decay: a gradual or persistent loss of search visibility or clicks for existing content. The term is useful, but it is not an official status that Google assigns to a page.

Not every decline is decay. A seasonal article will have quiet months. A page can lose impressions because fewer people search for the topic. A URL might decline because another page from your own site starts ranking for the same query. You need evidence before deciding that the text is obsolete.

Google Search Console is a good place to begin because it shows the page’s clicks, impressions, CTR and query-level performance over time.

Start with a definition you can reproduce

There is no universal content-decay threshold. A reasonable rule is to flag pages that lose clicks across three consecutive comparable windows and have enough traffic to make the change meaningful.

For example, take three complete 28-day periods and compare them. A page with 600, then 470, then 320 clicks deserves attention. A page with four, then three, then two clicks may simply have tiny sample sizes.

Also compare impressions. If clicks fell but impressions remained stable, you may be looking at a CTR or query-mix change. If both declined, investigate demand, ranking and search coverage.

Keep the definition explicit in your spreadsheet or report. If you change thresholds every week, it becomes difficult to know whether you are finding new problems or merely changing the rules.

Find candidate pages in Search Console

Open the Performance report and choose a sufficiently long period, such as three months. Switch to the Pages view. Export page-level performance over comparable windows, or use the Search Analytics API to request page and date dimensions.

For a larger site, filter to blog and documentation URLs first. Otherwise you may mix seasonal product pages, login pages and articles that serve very different purposes.

A simple report includes URL, clicks and impressions for each window, overall trend, largest changed query, page category and a business-value flag. Do not calculate a site-wide “decay rate” from raw page percentages without accounting for size.

Google’s Search Analytics API allows date and page breakdowns, with its documented row limits and aggregation rules.

A worked example: which page deserves attention?

Consider a hypothetical SaaS blog with the following history:

The API setup guide is a strong candidate. The annual trends article could be following an expected yearly demand pattern. The OAuth explainer has a mild decline that may be normal. The old announcement may no longer deserve investment.

Without context, a report might label all four as decay. A better workflow asks which losses are sustained, unexpected and worth fixing.

Check query-level evidence before editing

Select a losing page and compare its leading queries across periods. Did the same queries lose position and impressions? Did the page stop appearing for a cluster of questions? Did Google begin showing a different URL from your own domain?

Query-level changes tell you what kind of investigation makes sense. If the original article described a setup process from two software versions ago, a loss on installation queries is plausible evidence that the content needs review.

If impressions for a seasonal query fell while positions stayed similar, a content rewrite may do very little. Search demand may simply be lower.

Remember that Search Console does not show every query. Some are anonymized, and API results have data limitations. Avoid claiming the visible query rows account for 100% of the change unless the data actually supports that statement.

Separate decay from technical failures

Before rewriting, check whether the page still serves the intended URL and responds correctly. A noindex directive, bad redirect, canonical mismatch or broken rendering can look like a content problem in a traffic chart.

Review the page’s current HTML and URL Inspection signals where appropriate. Google’s URL Inspection API reports indexed-version information; it is not a live test.

Also investigate site-wide changes. If dozens of unrelated pages began declining on the same day, a shared technical issue, reporting change or broad search-environment shift may be more likely than simultaneous content decay.

The organic traffic drop checklist covers these broader checks.

Decide what actually needs updating

A good refresh is not “add 500 words and change the year.” Ask what the reader expects today that the page fails to provide.

For a software guide, test the commands and update UI screenshots, authentication steps and errors. For a comparison, verify features and explain trade-offs. For a conceptual article, improve examples and answer missing questions. For a product page, clarify use cases and current capabilities.

Do not automatically change the URL, remove valuable sections or rewrite a page’s entire structure. Preserve useful material that still answers the intent. If the old page has strong internal or external links, a careless migration can create unnecessary SEO risk.

When the original topic is no longer relevant, you may decide not to refresh it. Some content has a natural lifespan. Updating a defunct product announcement just to chase old impressions may not be a good investment.

What to do about competing pages on your own site

Sometimes the old article loses clicks while a newer, more relevant guide gains them. That is not necessarily bad for the business. The site may now serve the intent better through another URL.

Check whether the same queries appear across the two pages and whether total site-level clicks for those queries increased, decreased or stayed stable.

If both pages serve distinct intents, keep them separate and improve internal links. If they truly duplicate each other, consider a carefully planned consolidation—but not until you understand traffic, intent and backlink implications.

Our keyword cannibalization guide explains how to make that distinction.

Use an AI agent to detect trends, not invent causes

An assistant with authorized Search Console access can collect the same time windows for many pages and flag those with sustained declines.

A useful prompt is:

For the selected Search Console property, analyze blog and documentation URLs across three consecutive complete 28-day windows. Find pages with declining clicks in both transitions, at least 100 clicks in the first window, and meaningful overall losses. Return URL, clicks and impressions for each window, top changed queries and potential business importance. Label seasonality and technical causes as hypotheses. Do not rewrite content.

Adjust thresholds to your site’s size. If a report exposes only the current and previous period, request additional windows rather than claiming that two points prove a long-term trend.

GSC Magic documents report_content_decay for pages losing clicks across three consecutive windows. See its tool reference. The ready-made report is a shortlist generator; the decision to refresh still needs review.

Measure the result of a refresh

Record the publication or update date, what changed and which query intent you tried to satisfy. Recheck search performance after a suitable period, accounting for the time Google needs to recrawl and process content.

Measure the intended outcome. Did relevant queries regain impressions? Did qualified clicks improve? Did the page produce more useful visits or conversions when GA4 data is available?

Avoid comparing a holiday peak before the refresh with an ordinary month afterward. You may need a year-over-year comparison or a control group of similar, unchanged pages.

Even after careful work, a page may not recover. That does not necessarily mean the refresh was wrong; demand and competition can change. Use the result to improve future decisions.

Frequently asked questions

Is content decay a Google penalty?

No. “Content decay” is an analytical label for performance decline. It does not imply a penalty or manual action.

How many months should I compare?

Three complete monthly-style windows are a useful starting point. For seasonal topics, a longer history and year-over-year comparisons may be necessary.

Should I change the publication date when refreshing an article?

Only represent dates accurately. A meaningful update can justify showing an updated date, but changing a timestamp alone does not make outdated information useful.

Will adding more keywords fix decay?

Not by itself. Focus on matching current search intent, accuracy and useful detail rather than stuffing phrases into headings.

Can I automate content decay detection?

Yes. API queries or a reporting connector can identify candidate pages. A human should still investigate whether the decline is genuine and whether an update is worthwhile.

Keep the process small enough to act on

Start with the five highest-value pages that meet your decay rule. Investigate their queries, verify technical health and write an update brief for only the ones with a genuine content gap.

That process is manageable for a small team and much more likely to improve the site than publishing dozens of superficial refreshes. You can explore GSC Magic’s content decay report or use our SEO prompts to build a custom analysis.