Content decay: find the pages losing traffic in time
How to spot pages slowly losing clicks in Search Console, tell decay from seasonality or a technical fault, and decide whether to refresh, merge or leave them.
A page that loses half its traffic overnight gets noticed. A page that loses a little every month for two years doesn’t. Content decay is this slow slide: a page that once brought clicks, bringing fewer each month, with nothing wrong on the page to explain it.
It’s easy to miss because nothing breaks and no alert fires. With several sites, it’s nearly invisible.
First, check it isn’t something else
Google’s guide on debugging traffic drops lists the usual causes. Rule these out before you touch a page:
| Cause | How to tell |
|---|---|
| Seasonality or changing interest | Set the date filter to the last 16 months. If it repeats yearly, it’s the calendar. Google Trends shows whether interest fell for everyone |
| A technical fault | Sudden, across many pages. Check Page indexing and Crawl stats |
| A site move or URL change | It starts on the day of the change |
| A manual action or a security issue | Listed in the reports of those names |
| An algorithm update | Often sudden, across a theme or the whole site |
Note Google’s distinction: a small drop, such as position 2 to 4, is normal and may recover without action, and it advises against radical changes to pages that already do well. Decay is different in that it keeps going, over months, in one direction.
A warning about comparing with last year
Google reported impressions inaccurately from 13 May 2025 until 27 April 2026 because of a logging error. Impressions, click-through rate and position were affected, not clicks. So for now, compare clicks year on year, not impressions. It’s a good habit anyway: clicks are what you’re trying to keep.
How to find decaying pages
In one property, in the Performance report:
- Open the date filter, choose Compare, then the last 3 months against the same period a year earlier. Google suggests this one for ruling out seasonality.
- Open the Pages tab, and sort by the difference in clicks.
- Keep pages that lost many clicks, not pages that lost a high percentage: a page going from 4 clicks to 1 is down 75% and doesn’t matter.
- Click a page, then its Queries tab, to see which queries went.
Then look at what happened to position against click-through rate:
- Position fell. Others overtook you, or your page aged. This is the classic decay.
- Position held, clicks fell. The results page changed around you: more features, or fewer clicks on that kind of query. Rewriting the page may not help.
- Impressions fell, position held. People search for this less. That’s demand, not you.
What to do with each page
| Page | What to do |
|---|---|
| Still the right answer, but out of date | Refresh it properly: new facts, new examples, what’s changed |
| Overtaken by better pages | Read what ranks now, and add what you’re missing, if you have something real to say |
| Overlaps with another of your pages | Merge them, and redirect the weaker one |
| Topic faded, little left to save | Leave it. Not every page needs saving |
| No longer true, and not worth keeping | Redirect it to the closest useful page, or let it return 404 |
Three warnings from Google’s own guidance:
- Don’t just change the date. It asks directly whether you’re changing the date of pages to make them seem fresh when the content hasn’t substantially changed.
- Don’t purge for its own sake. The same page warns against removing a lot of older content primarily because you believe it’ll help your rankings.
- Not every query wants fresh. Its freshness systems apply where newer content is expected, such as a film just released. A stable how-to may not need a new date, just to stay correct.
After a real update, request indexing for that page, note the date, and compare in a few weeks. A sitemap’s lastmod helps here, if it’s accurate.
A routine that works across sites
Decay is a slow problem, so a monthly check is plenty. For each site:
- Compare the last 28 days with the 28 days before, and with the same period a year earlier.
- List the ten pages with the largest loss of clicks.
- Throw out those explained by seasonality or by a fault you already know about.
- For the rest, pick a decision from the table above, and write it down.
Writing it down is what stops you revisiting the same page every month. It’s also the only way to learn whether your refreshes work.
Doing this for five sites takes an afternoon. For twenty, it won’t happen without help, and the API can do the first two steps: pull page by month and keep your own copy, since the reports stop at 16 months. Owlseen’s first version is meant to show what dropped and what rose for every site, on a daily copy of the figures. It isn’t released yet, so until then a spreadsheet per site is the honest answer.
Start with the limits of the source itself: what Search Console holds back.