Content Decay: Find, Update and Recover Traffic from Declining Blog Posts
With a thousand-post library, our biggest traffic lever is not the next new post — it is the hundred old ones quietly sliding. Content decay work recovers monetizable pageviews without new URLs, which is exactly why it matters for publishers (see the AdSense–GA4 review loop this feeds). The method below is the one used on this site: duplicate-permalink cleanups, noindex fencing of dead silo pages, hub refreshes with dated last_modified_at bumps. No invented case figures anywhere — the spreadsheet columns show the shape, not our data.
1. What content decay is
Previously ranking pages losing clicks and impressions over months through staleness (old stats, dead links, retired tools), intent drift (the query now wants video, not text), fresher competitors, or your own newer posts cannibalizing the same queries. Distinct from penalties (sudden) and seasonality (calendar-shaped) — §5 separates them.
2. Why winners lose traffic
Rankings are rented against four depreciating assets: factual freshness (prices, screenshots, “2024” in titles), intent fit (SERP features change what the query wants), competitive pressure (someone published the better, newer version), and internal competition (your 996th post outranks your 3rd for the same query and splits the click). Diagnose which before touching anything — each has a different fix.
3. Find declining pages in Search Console
Pages report, date range 6 months, sort by clicks difference (compare mode) or export two periods and diff. Flag pages down >25% with previously meaningful volume; ignore low-volume noise (a 4→2 drop is variance, not decay). Record: URL, previous clicks, current clicks, primary query, and a first-guess cause. That table is the audit spreadsheet below.
4. Compare equivalent periods properly
Always year-over-year or season-over-season equivalents — never adjacent months for seasonal businesses. Festival, admissions, trekking and wedding queries all have calendars in Nepal; judging October against September manufactures false decay. Use 90-day minimum windows; 28-day blips are weather.
5. Seasonality vs genuine decay (the call)
| Signal | Seasonality | Decay |
|---|---|---|
| Shape | Calendar-repeating dip | Steady multi-month slide |
| Queries | Whole topic dips together | Page loses its core terms while siblings hold |
| Demand | Category demand visibly seasonal | Demand stable, your share falling |
| Fix | Schedule around it; refresh before the season | Refresh, consolidate, or retire now |
6. Find queries that lost impressions and clicks
Per flagged page, open the queries tab for the same periods: which queries lost impressions (visibility problem — intent drift, fresher rivals) versus lost CTR at stable impressions (packaging problem — stale title/meta, lost rich results). Impression loss means rewrite territory; CTR loss often means title/meta/date surgery only. Cheapest fixes first.
7. Audit staleness ruthlessly
Per page: dates in title and body, statistics with years attached, screenshots of changed UIs, dead external links, retired tools or prices, and advice your own newer posts contradict. Update last_modified_at only when substance changes — gaming dates without changes trains nobody and risks trust.
8. Realign search intent
Re-read the live SERP for the primary query: has the intent shifted (video pack, calculators, comparison tables, local pack where none existed)? Match the winning format with your own original version — a text wall where Google now answers with tools loses regardless of prose quality. Adjust headings to mirror the questions asked, not the outline you started with.
9. Refresh internal links and supporting resources
Point new related posts at the refreshed page (it is old enough to deserve authority, new enough to deserve traffic), fix its outbound dead links, and add it to the relevant hub list and related_links cluster. On this site, refreshed pillars get re-included in layout-level related blocks — one edit promotes across hundreds of pages. Orphaned refreshes recover slowly; linked refreshes recover fast.
10. Consolidate cannibals
When two of your URLs chase one query: pick the stronger (links, history, URL cleanliness), merge the best unique content into it, canonical or redirect the loser, and update internal links to the survivor. We found 43 duplicate-permalink pairs this way (regeneration artifacts) — consolidation beats letting twins split every signal indefinitely.
11. Redirect or retire honestly
Retire when: demand died (discontinued product category), the page cannot be made accurate without rewriting from zero, or traffic value never covered maintenance. Redirect to the closest surviving intent match — never bulk-redirect everything to the homepage (soft-404 behavior that teaches Google to ignore your redirects). Deleted pages leave the sitemap promptly.
12. Measure recovery without assuming it
Watch the page’s primary queries weekly for 4–8 weeks post-refresh: impressions recover first, CTR second, clicks last. Pre-commit the success criterion (e.g. “back to 80% of pre-decline clicks on core queries”) before editing — judging after the fact invents victories. Log what was changed per URL; unlogged refreshes cannot teach the next cycle.
Audit spreadsheet (copy this shape)
| URL | Previous clicks | Current clicks | Main query | Signal (season/decay) | Action |
|---|---|---|---|---|---|
| Article A | 1,000 | 600 | head term | decay (core-term impression loss) | Update + relink |
| Article B | 400 | 390 | stable term | noise | Monitor |
| Article C | 700 | 120 | tool term | decay (retired tool) | Rewrite or retire |
(Figures illustrative — the shape of the sheet, not any site’s data.) Add columns for owner, date refreshed, and 8-week check result as the process matures.
Related reading: AdSense–GA4 integration, Looker revenue dashboard, content calendar with refresh cadence, technical SEO, and hire a digital marketing expert.


