Content Decay: How to Find and Fix Slipping Pages in Search Console
A step-by-step way to spot content decay in Google Search Console, tell real decay from seasonality, and decide whether to update, merge, or leave a slipping page.
Most blogs do not die in one day. They fade.
A post that brought in steady clicks last spring now brings in half. Nobody notices, because nobody looks. New posts get the attention. Old ones quietly slip.
That slow loss has a name: content decay.
The good news is that you do not need a special tool to find it. Google Search Console already has the data. You need a repeatable way to read it, and a rule for what to do with each page you find.
What is content decay?
Content decay is a steady drop in search clicks or impressions on a page that used to perform, usually because the page has gone stale, competitors published something better, or the search results changed around it.
It is different from a sudden crash. A crash across the whole site in one week points to a technical problem or a Google update. Decay is page by page, and slow.
Step 1: Find the pages that are slipping
In Search Console:
- Open Performance, then Search results.
- Click the Date filter, choose the Compare tab, and pick "Compare last 28 days to previous period". Two 28-day windows side by side cancel out weekday swings.
- Turn on Total clicks, Total impressions, Average CTR, and Average position.
- Open the Pages tab below the chart. Each row now shows both periods and the difference.
- Sort by the clicks difference so the biggest losses are on top.
Ignore pages with only a handful of clicks in both periods. At that size, a drop of three clicks is noise, not a trend.
For seasonal topics, also run "Compare last 3 months year over year". A gift guide that drops in January is not decaying. It is January.
Step 2: Work out why it slipped
Click a slipping page. Search Console filters the whole report to that URL. Now look at which numbers moved together.
| What you see | Likely cause | What to check |
|---|---|---|
| Position dropped, impressions dropped | Other pages now rank above yours | Search the main query yourself. What do the pages above you cover that yours does not? |
| Position steady, impressions dropped | Fewer people search for it | Year-over-year comparison and Google Trends. This is demand, not your page. |
| Impressions steady, CTR and clicks dropped | Your result gets fewer clicks | Look at the results page: an AI Overview, new features, or a title that no longer matches what people want. |
| Two of your URLs take turns on the same query | Your own pages compete | Queries tab, filtered by query. If two URLs share it, consider merging them. |
| One group of queries disappeared | Part of the page went stale | Old prices, versions, years in the title, or steps that changed. |
The Queries tab is where the cause usually shows up. A page rarely loses everything at once. It loses one cluster of queries, and that cluster tells you which section went stale.
Step 3: Decide what to do with each page
Every slipping page gets one of four decisions.
Update it when the topic still matters and you can see what is wrong: outdated facts, a missing section the pages above you cover, or a title that no longer fits the query.
Merge it when two of your pages split the same query. Combine the best of both into the stronger URL and 301-redirect the weaker one to it.
Leave it when the drop is seasonal or the topic itself is cooling off. Rewriting a page will not create demand that is not there.
Retire it when the page no longer serves anyone: a dead product, an event that is over. Redirect it to the closest useful page, or remove it.
Do
- Fix the specific thing that went wrong: facts, missing section, title
- Keep the URL and keep what still works
- Request indexing in URL Inspection after a real update
- Write down the date you changed it, then compare the next 28 days
Don't
- Change the date at the top and call it updated
- Rewrite the whole post when only one section is stale
- Change the URL during an update
- Chase every small dip on low-traffic pages
Step 4: Update the page the right way
A good update changes what a reader would actually notice.
- Facts first. Prices, version numbers, screenshots, steps, and any year in the title.
- Fill the gap. If the pages now above you answer a question yours skips, add a section that answers it better.
- Match the query. If the queries you still get are different from the ones you wrote for, rewrite the title and description to match what people search now.
- Tighten. Remove sections nobody needs. A shorter, correct page beats a long, stale one.
Then open URL Inspection, paste the URL, and click Request indexing. This asks Google to recrawl it sooner. It does not promise anything about rankings.
Last, note the date. Four weeks later, compare the page's numbers before and after the change. That is the only way to learn which kinds of updates work on your site.
How often should you check?
A small blog with a few dozen posts can do this once a month in about half an hour.
Once you have hundreds of pages, a monthly check turns into a backlog. That is when a weekly routine, or a tool that does the first pass for you, starts to pay off.
If your blog lives in a Git repo
This is the loop NichePressa runs every week for Git-based blogs.
The weekly review compares your pages' last 28 days of Search Console data with the 28 days before, leaving out the newest days that are not final yet. When a published page loses impressions or clicks, the review proposes a specific update and names the sections it would change.
On manual review, you read the proposal and apply it yourself. On scheduled autopilot with Search Console connected, small, confident updates are applied on Wednesdays, at most one per site a week, as a normal commit you can revert.
Checking whether an update worked is still on you. Compare the page's next 28 days, the same way as in Step 4.
Frequently asked questions
What is content decay in SEO?
Content decay is a gradual drop in organic clicks or impressions on a page that used to perform well. It usually happens because the page went out of date, competing pages got better, or the search results page changed.
How do I tell content decay from a seasonal dip?
Compare the same period a year earlier. In Search Console, use "Compare last 3 months year over year". If the page dropped the same way last year, it is seasonal. If last year was steady and this year is falling, it is more likely decay.
How often should I update old blog posts?
Update a post when there is a reason: its numbers are slipping, its facts changed, or the queries it gets no longer match what it says. A fixed schedule for updating everything wastes time on pages that are fine.
Should I change the publish date when I update a post?
Show an updated date only when you changed something a reader would notice. Changing the date without changing the page tells readers nothing new.
Does updating old content help SEO?
It can, when the update fixes the reason the page slipped, such as stale facts, a missing section, or a title that no longer matches the query. It is not guaranteed, which is why you should compare the numbers before and after each update.
Related: how to build an editorial voice AI can follow and NichePressa vs AI blog writers.
NichePressa writes new posts and proposes updates for slipping ones, in your voice, as commits to your repo. Create two articles free.
