Search Console workflow

How to find content decay in Google Search Console

Content decay is slow and silent. Pages that ranked well a year ago lose impressions month by month without triggering a single alert. Here's how to find them in Search Console — and what to do once you have.

Content decay doesn't announce itself. There's no ranking drop notification, no penalty email, no single bad day you can point to. Instead, a page that once brought in 150 clicks a month quietly slides to 90, then 60, then 30 — over the course of a year — while you're busy building new things.

By the time you notice, the decline has been happening for months. The fix is still usually straightforward. The cost is the time you spent not knowing.

What content decay actually looks like in Search Console

In Search Console's Performance report, content decay shows up as one of three patterns:

  • Impressions falling, position stable. Google still ranks you where it did, but fewer people are searching for the query. The topic has cooled, or a competitor has taken the featured snippet and is absorbing most of the impression volume.
  • Position falling, impressions stable. The search volume is there, but you're sliding down the results page. Newer, fresher, or more comprehensive pages have pushed yours down.
  • CTR falling while impressions hold. You're appearing in search but fewer people click. Your title or description no longer matches what the searcher wants to find — usually because their intent has shifted, or a competing snippet is answering the question before they reach your result.

All three patterns produce the same outcome: fewer clicks, less traffic, lower revenue. But the fix for each is different, which is why identifying the pattern matters before you start rewriting.

How to find decaying pages in Search Console

Search Console doesn't have a "content decay" report. You have to build the picture yourself by comparing date ranges.

Step 1: Set a comparison date range

Open the Performance report. Click the date filter and choose "Compare." Set the comparison to the same 90-day period one year ago. This gives you a long enough window to see gradual decline rather than seasonal variation.

Step 2: Switch to the Pages tab

With the comparison active, click the Pages tab. Sort by clicks. Look for pages where clicks this period are significantly lower than the same period last year — particularly pages that used to be in your top 10 by traffic.

Step 3: Check the pattern for each declining page

Click into a declining page. Look at whether impressions, position, or CTR moved. This tells you the cause:

  • Impressions down, position stable → the topic is declining in search volume or a featured snippet is absorbing demand
  • Position down, impressions stable → your content is being outranked; it needs to be more comprehensive, more current, or better structured
  • CTR down, impressions stable → your title or description no longer matches search intent; rewrite the metadata

Step 4: Decide whether to refresh or retire

Not all decaying pages are worth saving. If the search volume itself is gone (because the topic changed, or it was always thin), the right answer is to consolidate the page into something broader or remove it and redirect. If the volume is there but your content has aged, a focused refresh — updating facts, restructuring for current intent, rewriting the title — is usually enough.

The problem with doing this manually every month

The Search Console workflow above works. The problem is that it takes 20–30 minutes per site, requires you to remember to do it, and leaves no record of what you found or what you changed. If you manage more than one site, it doesn't scale.

The pages that matter most for content decay detection are the ones that used to drive traffic — pages buried in the middle of your Search Console performance list, not the obvious current winners. These are easy to miss in a manual review.

What a structured content decay workflow looks like

The most reliable content decay workflow I've found keeps three things together:

  1. A consistent date comparison — same window, same frequency, so you see the trend rather than a snapshot
  2. A decision record — which pages you reviewed, which pattern you identified, what you decided to do
  3. A change log with outcome tracking — when you refreshed a page, what you changed, and whether clicks recovered in the following 4 weeks

Without the third step, you're optimising blind. You might refresh 10 pages and have no idea which refreshes actually recovered traffic and which ones did nothing.

Content decay vs. algorithm updates

One thing to separate out: content decay is a gradual trend. A ranking drop that happens over 2–4 days is almost always a core algorithm update, not content decay. Core updates move positions quickly and often affect many pages at once. Content decay affects individual pages over months.

If you see a sudden drop across many pages on the same date, look up whether a Google core update ran on or around that date before assuming content quality is the issue. Chasing content decay on pages that dropped due to an algorithm update leads you to change things that aren't the cause.

How often to run a decay review

Monthly is the right cadence for most small sites. Quarterly if your site is large or if content changes slowly. The key is consistency — a comparison run on the same schedule surfaces the trend. An irregular check produces a snapshot you can't act on confidently.

The pages most worth reviewing monthly are the ones that have historically driven your most qualified traffic — not the posts that went briefly viral, but the ones that reliably brought in buyers, subscribers, or leads over a 12-month window.