Content decay is the gradual decline in a page’s organic search performance after it has already ranked — fewer impressions, a softer average position, clicks that fade out — and it shows up over weeks, not in a single bad day. Measuring it on your own site means pulling Search Console by date across a wide window, checking whether a drop held for more than a day or two, and ruling out reporting lag before calling anything a decline. Run that check against this site’s own 138-day window and the honest number is 910 impressions, 6 clicks, a 0.659% click-through rate, and 38 of 138 days — 27.5% — with zero impressions at all. That is the floor this piece measures against, not a cherry-picked good stretch.
I checked the live search results for “content decay SEO” before writing any of this. The term is used consistently to describe a slow fade in rankings, impressions, clicks, or engagement on a page that previously performed — never a sudden penalty. Documented causes include competitor pages overtaking a position, outdated information on the page itself, newer pages on the same site cannibalizing the same query, and shifting SERP features such as AI-generated overviews that cut clicks even while position holds steady. Every source treats detection the same way: a trend read over months from Search Console data, not a single day’s row. This piece runs that exact check against this site’s own numbers, including the ones that do not flatter it.
The method, step by step
Two pulls do the work. The first groups Search Console data by date across a wide window, which shows whether visibility exists on a given day and how that level moves over weeks. The second groups the same window by query, which shows which terms are producing the impressions and at what position. A by-date view can look stable while one query quietly disappears underneath it, and a by-query view cannot show the week-to-week movement that separates a real decline from a blip. Pulling both as raw data through a script, rather than reading a dashboard chart by eye, is the same discipline behind building an SEO dashboard from APIs, not screenshots: a number computed the same way twice is checkable, and a number eyeballed off a graph usually is not.
Once both pulls are in hand, the actual decay test is a short set of questions applied to anything that looks like it is dropping: has the lower level held for multiple weeks, or is it one bad week bouncing back the next? Does the drop show up across several related queries, or only one? Is there a plausible explanation — a competitor’s new page, a stale claim on this page, a cannibalizing post published since — or no corresponding event at all? A genuine decay shows a sustained lower level across weeks with no single-day recovery. A blip reverts within days. Treating a blip as decay means rewriting a page that did not need it; treating real decay as noise means leaving a fading page untouched while something else quietly takes its place in the results.
This site’s real numbers right now
The by-date pull covers June 1 through October 16, 2026 — 138 days, with the 17th requested but not yet returned, a one-day gap that is lag rather than a drop (more on that below). Across that window: 910 total impressions, 6 total clicks, a site-wide click-through rate of 0.659%. Thirty-eight of the 138 days — 27.5% of the window — show zero impressions at all, including an unbroken 22-day stretch from June 1 through June 22 before this site had any visibility whatsoever on the queries it was being measured against. That zero-impression rate, not a single strong day, is the baseline any decay claim on this site has to be measured against.
The clearest step change in this dataset sits in late August: impressions jumped from single digits to 41 on August 26 and held at an elevated level for six straight days — 42, 38, 42, 55, then 33 — before settling lower again. That multi-day persistence is what makes it a step change rather than a spike; a one-day jump that reverted immediately would have been noise, not signal. The most recent seven days in this pull, October 10 through 16, show 78 impressions and zero clicks (9, 7, 12, 11, 8, 13, 18) — visibility that is measurable but not converting. The last click anywhere in this window landed on September 17, which makes the stretch from September 17 to October 16 a 29-day run of impressions with no clicks at all, a pattern this site’s own impressions but no clicks: what the data actually shows argues should be read as a separate problem from visibility, not folded into it.
The by-query pull for the same general period is a 50-row alphabetical sample rather than a ranked list, so it is useful here only for coverage, not for ranking which terms matter most. Every row in that sample shows zero clicks, and the highest-impression row — a question about adding a canonical tag in a WordPress header — sits at 20 impressions and position 18.95. Most rows carry one to three impressions at positions in the 50s through 90s, individually too thin to call a trend in either direction. That is exactly the kind of single-query noise SEO KPIs worth reporting (and three to drop) argues should be left out of a report rather than included to make a dashboard look fuller — and it is a reminder that a decay check needs a wide date window before it needs a long query list.
Reading results honestly
Two specific sources of noise showed up in pulling this exact data, and naming them matters more than smoothing them over. The first is timing: the most recent day or two of any Search Console pull is provisional, because the data backfills and gets reclassified after the fact. The mechanism is covered directly in why Search Console data lags and how to handle it, and it is the reason this piece’s own pull, requested through October 17, only actually returns complete rows through October 16. Reading that single missing day as a sudden drop in visibility would be the wrong read; it is a processing gap, not decay, and decay only means anything measured over weeks, never off the newest row in a pull.
The second is a mismatch between data sources that is informative precisely because it does not line up. Checking this site’s GA4 engagement data over a comparable window, three days stand out sharply against a normal busy day of roughly 282 seconds average session duration: July 18 shows 3 sessions but a 1,198-second average duration, August 1 shows 2 sessions at 764 seconds, and August 7 shows a single session at 1,435 seconds — the most extreme of the three. Each pairs a tiny session count with an outsized duration, the usual signature of a bot or crawler session rather than a real reader. They are named here as likely artifacts, not cited as engagement, because folding them into a clean average would distort any baseline built from this window — the same noise-versus-signal discipline telling SEO signal from noise on a small site applies to Search Console data applies just as directly here.
None of this means the numbers are too noisy to use. It means the number worth reporting is a window-level aggregate, re-checked after a few more days of backfill, rather than a single day’s row read in isolation — and it means saying out loud which days look like artifacts instead of quietly averaging them into a tidier-looking total.
What would falsify the conclusion
This is a method meant to be re-run, not a one-time read of a dashboard. The pre-publish baseline above shows zero rows in this site’s 50-query sample containing the term “content decay” or any variant of it — a clean starting point to check against later. If, 60 days after this page publishes, it still shows zero Search Console impressions for any query containing its primary keyword terms, despite being confirmed as indexed, the method described here did not work for this specific page, and that result should be reported rather than quietly dropped.
Three checks are worth running before concluding the page itself is decaying:
- Confirm the page is indexed before reading a drop as decay. A page that was de-indexed or never fully crawled will show falling or zero numbers for reasons that have nothing to do with search performance fading.
- Re-pull the same date range a few days later rather than trusting the newest rows. As this piece’s own pull shows, the final day or two of any window is provisional until Search Console finishes backfilling it.
- Check whether the lower level held for multiple weeks or reverted on its own. This site’s own August step change moved in the other direction and held for six days; real decay should show the same multi-week persistence before it gets treated as a problem worth fixing.
Leave a Reply