recover-content

calm-north/seojuice-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/calm-north/seojuice-skills --skill recover-content
0 commentsdiscussion
summary

Diagnose and reverse traffic loss on existing pages using decay triage framework.

  • 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,
skill.md

Recover Content

Diagnose and reverse traffic loss on existing pages using the decay triage framework: refresh, consolidate, redirect, or retire.

Before You Start

Gather this context (ask if not provided):

  1. Which pages are losing traffic? Specific URLs or a general "the whole blog is declining."
  2. How much traffic was lost? Percentage drop or absolute numbers.
  3. Over what timeframe? Gradual decline over months vs sudden drop.
  4. Any recent changes? Site redesign, CMS migration, content edits, algorithm update timing.

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.

Identifying Decay

Content decay happens when a page gradually loses search traffic over time. Common signals:

  • Clicks declining month-over-month for 3+ months
  • Position slipping from page 1 to page 2+
  • Impressions stable but CTR dropping (competitors have better titles/snippets)
  • Impressions declining (Google no longer considers the page relevant)

Composite Decay Score

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

Alert Priority Matrix

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

The Decay Triage Framework

For each decaying page, apply this decision tree:

Decision 1: Is the topic still relevant?

  • Yes → proceed to Decision 2
  • No (product discontinued, event passed, technology obsolete) → Retire. 301 redirect to the closest relevant page or parent category.

Decision 2: Is there another page on the site targeting the same topic?

  • YesConsolidate. Merge the best content from both pages into one. 301 redirect the weaker page.
  • No → proceed to Decision 3

Decision 3: Has the search intent shifted?

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 shiftedRewrite. Rebuild the page to match current intent. Keep the URL.

  • No → proceed to Decision 4

Decision 4: Is the content simply outdated?

Check for: stale statistics, outdated screenshots, deprecated tools/methods, old dates in the title, broken external links.

  • Yes, outdatedRefresh. Update facts, screenshots, examples, and dates. Add new sections covering recent developments.
  • NoInvestigate deeper. The issue may be technical (lost backlinks, slower page speed, mobile issues) or competitive (stronger pages now outrank).

Refresh Playbooks by Content Type

Different content types require different refresh approaches. Use the matching playbook:

Blog Post / Article (3-4 hours)

  1. Update title with current year or fresh hook (10 min)
  2. Rewrite introduction with a new angle (20 min)
  3. Update all statistics with current sources (30-60 min)
  4. Add 1-2 new sections covering gaps competitors address (60-90 min)
  5. Update screenshots and images (30 min)
  6. Add or refresh FAQ section with current PAA questions (20 min)
  7. Refresh internal links to recent related content (15 min)
  8. Update meta description (5 min)
  9. Add or update schema markup — dateModified at minimum (10 min)
  10. Republish with updated date and re-submit to Search Console (5 min)

Statistics / Data Roundup (4-5 hours)

  1. Verify every statistic — remove any without a current source
  2. Replace outdated stats with current data (within 2 years)
  3. Add new statistics from recent studies
  4. Update all source links — replace broken citations
  5. Update year references in title and body
  6. Add a data visualization if none exists
  7. Update meta description and title

How-To Guide (3-3.5 hours)

  1. Verify all steps still work as written
  2. Update screenshots for any changed interfaces
  3. Add new alternative methods if any have emerged
  4. Update tool recommendations (remove deprecated, add current)
  5. Add a troubleshooting section for common failure points
  6. Update FAQ with recent questions
  7. Test all external links

Refresh Checklist (General)

For any content type, always complete:

  • Update all statistics and data points to current year
  • Replace outdated examples and screenshots
  • Add new sections covering developments since last update
  • Remove or update broken external links
  • Improve the title and meta description (check competitor titles for CTR ideas)
  • Add internal links from recent, related content
  • Expand thin sections that competitors cover better
  • Add original insights, data, or expert quotes (E-E-A-T signals)
  • Update the published/modified date
  • Re-submit to Google Search Console for re-indexing

Consolidation Checklist

When merging two pages:

  • Identify the stronger URL (more backlinks, better position, older)
  • Move the best content from the weaker page into the stronger one
  • Set up a 301 redirect from the weaker URL to the stronger one
  • Update all internal links that pointed to the weaker URL
  • Check for backlinks to the weaker URL — the redirect will pass authority

Prioritization

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.

Content Retirement Options

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

Output Format

Content Recovery Plan: [domain]

Decay Summary

  • Pages analyzed: [count]
  • Pages needing action: [count]
  • Estimated traffic recoverable: [sum of lost traffic]

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:

  • What specifically needs to change
  • Which sections to update, expand, or remove
  • Estimated impact if recovered

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-strategy to see active content decay alerts with severity ratings — the list_content_decay tool pulls pages losing traffic automatically.

how to use recover-content

How to use recover-content on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add recover-content
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/calm-north/seojuice-skills --skill recover-content

The skills CLI fetches recover-content from GitHub repository calm-north/seojuice-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/recover-content

Reload or restart Cursor to activate recover-content. Access the skill through slash commands (e.g., /recover-content) or your agent's skill management interface.

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ 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.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.541 reviews
  • Benjamin Tandon· Dec 24, 2024

    I recommend recover-content for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Luis Iyer· Dec 8, 2024

    recover-content reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Pratham Ware· Dec 4, 2024

    recover-content has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Kwame Reddy· Dec 4, 2024

    Keeps context tight: recover-content is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Michael Torres· Nov 27, 2024

    Registry listing for recover-content matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Yash Thakker· Nov 23, 2024

    Solid pick for teams standardizing on skills: recover-content is focused, and the summary matches what you get after install.

  • Evelyn Bansal· Nov 23, 2024

    We added recover-content from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Aisha Ghosh· Nov 15, 2024

    recover-content fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Isabella Khanna· Nov 11, 2024

    Useful defaults in recover-content — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Michael Reddy· Oct 18, 2024

    recover-content fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 41

1 / 5