Diagnose and reverse traffic loss on existing pages using decay triage framework.
Works with
Composite decay scoring across five weighted signals (traffic decline, position drops, CTR decline, content freshness, competitive displacement) prioritizes which pages need action most urgently
Decision tree guides whether to refresh, consolidate, redirect, or retire each decaying page based on topic relevance, intent shifts, and content staleness
Refresh playbooks tailored to content type (blog posts,
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrecover-contentExecute the skills CLI command in your project's root directory to begin installation:
Fetches recover-content from calm-north/seojuice-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate recover-content. Access via /recover-content in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
5
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
5
stars
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.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
sickn33/antigravity-awesome-skills
aaron-he-zhu/seo-geo-claude-skills
aaaaqwq/claude-code-skills
hvpandya/stop-slop
JuliusBrussee/caveman
JuliusBrussee/caveman
I recommend recover-content for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
recover-content reduced setup friction for our internal harness; good balance of opinion and flexibility.
recover-content has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: recover-content is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for recover-content matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: recover-content is focused, and the summary matches what you get after install.
We added recover-content from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
recover-content fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in recover-content — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
recover-content fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 41