
This is what you reach for when organic traffic starts bleeding out on existing pages. It walks you through a proper triage framework: is the topic dead, is there a duplicate eating your traffic, did search intent shift, or is it just stale facts and screenshots? The composite decay scoring system is genuinely helpful for prioritizing which fires to put out first, weighing traffic loss against position drops and competitive displacement. You get different refresh playbooks depending on content type, from blog posts to data roundups, with realistic time estimates. The consolidation and redirect logic is sound. If you're staring at a Search Console graph trending down and don't know whether to rewrite, merge, or kill the page, this gives you a decision tree that actually maps to reality.
$ npx -y skills add calm-north/seojuice-skills --skill recover-content --agent claude-codeInstalls into .claude/skills of the current project.
Diagnose and reverse traffic loss on existing pages using the decay triage framework: refresh, consolidate, redirect, or retire.
Gather this context (ask if not provided):
If the user doesn't know which pages are declining, suggest checking Google Search Console → Performance → Pages, sorted by click change over the last 6 months.
Content decay happens when a page gradually loses search traffic over time. Common signals:
Score each page across 5 weighted signals to prioritize action:
| Signal | Weight | How to Score (0-100) |
|---|---|---|
| Traffic decline | 30% | 0 = no decline, 50 = 20-40% drop, 100 = >60% drop |
| Position drops | 25% | 0 = stable, 50 = lost 3-5 positions, 100 = dropped off page 1 |
| CTR decline | 15% | 0 = stable, 50 = 20% decline, 100 = >40% decline |
| Content freshness | 15% | 0 = updated this quarter, 50 = 6-12 months stale, 100 = >2 years stale |
| Competitive displacement | 15% | 0 = no new competitors, 50 = new entrants on page 1, 100 = displaced from top 3 |
Composite Decay Score = (Traffic x 0.30) + (Position x 0.25) + (CTR x 0.15)
+ (Freshness x 0.15) + (Displacement x 0.15)
| Score | Stage | Response |
|---|---|---|
| 0-20 | Healthy | Continue monitoring |
| 21-40 | Early decay | Add to refresh queue (next month) |
| 41-60 | Active decay | Schedule refresh this week |
| 61-80 | Significant decay | Immediate refresh or rewrite decision |
| 81-100 | Terminal decay | Rewrite, redirect, or retire |
When multiple signals fire together, escalate:
| Signal Combination | Priority | Response Time |
|---|---|---|
| Traffic decline + Position drop | P1 Critical | Refresh within 48 hours |
| Traffic decline + CTR decline | P1 Critical | Rewrite title/meta immediately |
| Position drop + Competitor displacement | P2 High | Refresh within 1 week |
| CTR decline only | P3 Medium | Rewrite title and meta this week |
| Freshness indicators only | P3 Medium | Schedule refresh within 2 weeks |
For each decaying page, apply this decision tree:
Check what currently ranks for the target keyword. Has the SERP changed from:
Listicles → long-form guides?
Blog posts → product pages?
Text → video?
General → specific?
Yes, intent shifted → Rewrite. Rebuild the page to match current intent. Keep the URL.
No → proceed to Decision 4
Check for: stale statistics, outdated screenshots, deprecated tools/methods, old dates in the title, broken external links.
Different content types require different refresh approaches. Use the matching playbook:
For any content type, always complete:
When merging two pages:
Score each page for refresh priority:
| Factor | Weight |
|---|---|
| Current traffic value | 25% |
| Decay severity (composite score) | 20% |
| Competitive opportunity | 20% |
| Refresh difficulty (inverse — easier = higher) | 15% |
| Strategic importance (conversions, brand) | 10% |
| Backlink equity at risk | 10% |
Then rank pages:
| Page | Decay Score | Traffic Lost | Priority Score | Action | Effort |
|---|---|---|---|---|---|
| ... | 72 (significant) | 1,200/mo | 85 | Refresh | 3-4 hrs |
| ... | 45 (active) | 300/mo | 60 | Consolidate | 2 hrs |
Focus on pages that (a) had the most traffic, (b) drive conversions, and (c) are easiest to fix. A quick refresh on a high-traffic page beats a full rewrite on a low-traffic one.
When a page can't be saved, choose the right exit:
| Option | When to Use |
|---|---|
| 301 redirect | Content has backlinks or residual traffic — send equity to closest relevant page |
| Consolidate | Multiple weak pages on same topic — merge best content into one URL |
| Noindex | Internal utility page that shouldn't rank but serves users |
| Delete (410) | No value, no links, no traffic — clean removal |
Decay Summary
Triage Results
| Page | Traffic Lost | Diagnosis | Action | Effort |
|---|---|---|---|---|
| ... | ... | intent shift / outdated / cannibalization / irrelevant | refresh / consolidate / redirect / retire | low / medium / high |
Priority Actions
For each high-priority page:
Pro Tip: Use the free Keyword Density Analyzer to check whether a declining page is still optimized for its target keyword. SEOJuice MCP users can run
/seojuice:content-strategyto see active content decay alerts with severity ratings — thelist_content_decaytool pulls pages losing traffic automatically.
Sponsors