How to Find Content Decay in Google Search Console

To find content decay in Google Search Console, open Performance, switch to the Pages tab, set the date range to the last 6 months, and turn on Compare with the previous 6 months. Sort by the click difference column. Any page with a meaningful negative delta and stable impressions is decaying. That single comparison takes about two minutes and is the highest-value report most content teams never run.

What content decay looks like inside Search Console

Decay is a slope, not a cliff. A page does not fall off the first page in a week; it drifts from position 3 to 5 to 9 across two or three quarters while nobody is looking, and by the time someone notices the traffic line on the dashboard, twelve months of compounding loss is already booked. Search Console shows the slope clearly if you ask it the right question.

Three patterns account for nearly all of it, and they call for different fixes.

Read the pattern before you assign the work. Teams routinely spend a week rewriting a page whose only problem was a title that no longer promised what the SERP now rewards.

The step-by-step sweep

1. Open Performance, then the Pages tab. Queries are for diagnosis later; you are looking for URLs first.
2. Set the date range to the last 6 months and enable Compare. Pick the previous 6 months, not the previous year. Six versus six is long enough to smooth out seasonality and short enough to catch decay while it is still recoverable.
3. Sort by click difference, ascending. The worst decliners rise to the top. This list, not your publishing calendar, is your work queue.
4. Export it. Search Console's interface is fine for looking and terrible for thinking. Get the table into a sheet.
5. Filter out the noise. Drop pages with fewer than roughly 50 clicks in the earlier period. A page that fell from 6 clicks to 2 is not decay, it is weather.
6. Diagnose each survivor at query level. Click into the URL, switch to the Queries tab, and keep the comparison on. Now you can see which of the three patterns above you are dealing with, because you can watch position and CTR per query rather than in aggregate.
7. Add a business column by hand. Search Console does not know which pages make money. A blog post that lost 400 informational clicks may matter less than a comparison page that lost 60 clicks from buyers. Sort by revenue at stake, not by traffic at stake, whenever you can.

Run this monthly. It takes twenty minutes and it is the difference between finding decay at position 7 (recoverable in weeks) and finding it at position 24 (a rewrite).

Decay versus a cliff: do not confuse them

If the chart shows a step down on one specific date rather than a slope, stop. That is not decay and refreshing content will not fix it. A single-date drop is almost always an algorithmic update, a technical fault, or a tracking change. Rule out the boring causes first: a botched migration, a noindex tag shipped by accident, a canonical pointing somewhere strange, a robots.txt rule that went out with a release, or a stretch where the server was quietly unreachable while crawlers came knocking. Any of those can erase months of rankings in a way no amount of subtopic coverage will restore.

Our full diagnostic tree, in order of likelihood, is in why did my organic traffic drop. Come back to this article once you have confirmed the shape is a slope.

What Search Console cannot tell you

Search Console is a mirror. It shows what happened to your pages, and nothing at all about why the pages above you are winning. It has no idea that seven of the ten results now open with a comparison table, that four of them added a pricing section last spring, or that the entity every ranking page names was not in the vocabulary when you published. That is the gap between knowing a page is decaying and knowing what to do about it.

Closing that second gap is a comparison job: your page against the pages currently outranking it, section by section, entity by entity, question by question. Done by hand it costs 2 to 4 hours per page, which is why most libraries get audited once and then never again. It is exactly what a content gap analysis tool automates, and what our content decay checker runs across an entire sitemap so the queue sorts itself by recoverable traffic.

Turning the list into fixed pages

A decay list is not a deliverable. The deliverable is a page that ranks again. Once you have the ranked list of decliners, work each page in this order: re-check the intent against the live SERP, fix the title and meta if the CTR pattern implicated them, add the sections the ranking pages cover and you skip, restructure so the direct answer sits in the first 40 words, repair internal links from your newer posts, and update anything that dates the page. The full 12-point version is our refresh checklist, and the strategic case for doing this before publishing anything new is in historical optimization.

Keep the URL. The history on that slug is the asset you are protecting; a new URL starts from zero and throws away the very thing that makes a refresh faster than a rewrite. Update in place, show a visible revision date, and measure again in the next monthly sweep.

Frequently asked questions

How do I find declining pages in Google Search Console?

Open Performance, go to the Pages tab, set the range to the last 6 months, enable Compare with the previous 6 months, and sort by click difference ascending. Pages with a large negative click delta and flat impressions are your decliners. Export the table and drop anything under roughly 50 clicks in the earlier period.

How do you know if content is decaying rather than just fluctuating?

Decay is directional across two or more quarters, not noisy week to week. Look for average position drifting steadily downward while impressions hold, and confirm it at query level rather than in aggregate. A one-week dip that recovers is fluctuation. A slope that survives a six-versus-six month comparison is decay.

How often should I check for content decay?

Monthly for the sweep, quarterly for the deep audit. Monthly is frequent enough to catch a page while it is still at position 6 or 7, where a refresh usually recovers it in weeks. Waiting for the annual audit means catching pages at position 20, where recovery costs a rewrite.

Can Google Search Console tell me why a page is decaying?

Only partly. It shows the symptom (position, clicks, impressions, CTR) and never the cause, because it has no view of what the pages outranking you now cover. Diagnosing the cause requires diffing your page against the current top results for its keyword, which is a comparison Search Console cannot make.