Recover Content

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.

skills.sh installs: 2.1K
GitHub stars: 21
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add calm-north/seojuice-skills --skill recover-content --agent claude-code

Installs into .claude/skills of the current project.

Files

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):

Which pages are losing traffic? Specific URLs or a general "the whole blog is declining."
How much traffic was lost? Percentage drop or absolute numbers.
Over what timeframe? Gradual decline over months vs sudden drop.
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.