Claude Marketplaces
SkillsMCP serversMarketplacesDigestTools
Submit

This week in Claude

Every Monday: Claude Code, Agent SDK, MCP, and the Anthropic platform moves worth your time.

Skills by category
Frontend DevelopmentBackend & APIsTesting & QASecurityDevOps & CI/CDGit & Pull RequestsDocumentationCode Review & QualityAI & Agent BuildingSkill Development
MCP servers by category
Sales & MarketingWeb & Browser AutomationDatabasesAI & LLM ToolsCloud & InfrastructureCommunication & MessagingDeveloper ToolsDesign & CreativeDocuments & KnowledgeSearch & Web Crawling
Marketplaces by category
AI Agents & OrchestrationLLM IntegrationDevelopment ToolsFrontend & UIBackend & APIsDatabasesTesting & Code QualityDevOps & CloudSecurity & ComplianceGit & Version Control
Claude Marketplaces

An independent directory of skills, plugins and MCP servers for Claude Code. Not affiliated with Anthropic.

Browse

  • Skills
  • MCP servers
  • Marketplaces
  • Weekly digest
  • Skill index
  • MCP index
  • Marketplace index

Site

  • About
  • Tools
  • Submit
  • Feedback
  • Privacy
  • llms.txt
  • Plugins reference

Maker

  • Snug
  • Agent Caffeine
  • knobs
  • Wax
  • Vectoys
  • mertduzgun.com
Crafted at
Skills/Debugging
calm-north avatar

Recover Content

calm-north/seojuice-skills

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.

installs
2.1K
GitHub stars
21
last updated
Aug 21, 2026
View on GitHubSave

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

  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:

SignalWeightHow to Score (0-100)
Traffic decline30%0 = no decline, 50 = 20-40% drop, 100 = >60% drop
Position drops25%0 = stable, 50 = lost 3-5 positions, 100 = dropped off page 1
CTR decline15%0 = stable, 50 = 20% decline, 100 = >40% decline
Content freshness15%0 = updated this quarter, 50 = 6-12 months stale, 100 = >2 years stale
Competitive displacement15%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)
ScoreStageResponse
0-20HealthyContinue monitoring
21-40Early decayAdd to refresh queue (next month)
41-60Active decaySchedule refresh this week
61-80Significant decayImmediate refresh or rewrite decision
81-100Terminal decayRewrite, redirect, or retire

Alert Priority Matrix

When multiple signals fire together, escalate:

Signal CombinationPriorityResponse Time
Traffic decline + Position dropP1 CriticalRefresh within 48 hours
Traffic decline + CTR declineP1 CriticalRewrite title/meta immediately
Position drop + Competitor displacementP2 HighRefresh within 1 week
CTR decline onlyP3 MediumRewrite title and meta this week
Freshness indicators onlyP3 MediumSchedule 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?

  • Yes → Consolidate. 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 shifted → Rewrite. 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, outdated → Refresh. Update facts, screenshots, examples, and dates. Add new sections covering recent developments.
  • No → Investigate 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:

FactorWeight
Current traffic value25%
Decay severity (composite score)20%
Competitive opportunity20%
Refresh difficulty (inverse — easier = higher)15%
Strategic importance (conversions, brand)10%
Backlink equity at risk10%

Then rank pages:

PageDecay ScoreTraffic LostPriority ScoreActionEffort
...72 (significant)1,200/mo85Refresh3-4 hrs
...45 (active)300/mo60Consolidate2 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:

OptionWhen to Use
301 redirectContent has backlinks or residual traffic — send equity to closest relevant page
ConsolidateMultiple weak pages on same topic — merge best content into one URL
NoindexInternal 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

PageTraffic LostDiagnosisActionEffort
......intent shift / outdated / cannibalization / irrelevantrefresh / consolidate / redirect / retirelow / 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.

SKILL.md on GitHub

Sponsors

SnugThe clipboard manager you and your agent can use, safelyAgent CaffeineClose your lid, come back to finished workWaxBlock anything with supervision, without erasing your iPhoneOpen StepsSponsoredFree and open-source skills that make AI coding agents easier to understand, verify, and control.

Details

Repository
github.com/calm-north/seojuice-skills
Categories
Debugging, Marketing & SEO

More from calm-north/seojuice-skills

All 14
  • Fix Linking2K
  • Target Serp2K
  • Find Keywords7K
  • Optimize For Ai6.6K
  • Build Links6.5K
  • Brief6.4K
  • Audit6.4K
  • Rank Local2.5K
  • Audit Speed2.4K
  • Diagnose Seo2.1K
  • Migrate Site2.1K
  • Beat Competitors2.1K
  • Build Clusters2.1K

Recommended

More Debugging
1anthropics avatarbuild-zoom-virtual-agentanthropics/knowledge-work-pluginsReference skill for Zoom Virtual Agent. Use after routing to a virtual-agent workflow when implementing web embeds, Android or iOS wrapper integrations, knowled2.1Kinstalls
2anthropics avatarbuild-zoom-contact-center-appanthropics/knowledge-work-pluginsReference skill for Zoom Contact Center. Use after routing to a contact-center workflow when implementing app, web, or native integrations; engagement context a2.1Kinstalls
3anthropics avatarzoom-oauthanthropics/knowledge-work-pluginsReference skill for Zoom authentication. Use after routing to an auth workflow when choosing app credentials, grant types, scopes, token refresh behavior, or de2.1Kinstalls
4jwynia avatargodot-best-practicesjwynia/agent-skillsGuide AI agents through Godot 4.x GDScript coding best practices including scene organization, signals, resources, state machines, and performance optimization.2.1Kinstalls
5k-dense-ai avatarpolarsk-dense-ai/scientific-agent-skillsHigh-performance DataFrame library for Python ETL, analytics, and pandas migration. Use for expression-based data manipulation with lazy query optimization, par2Kinstalls
6aliyun avataralibabacloud-sls-queryaliyun/alibabacloud-aiops-skillsAlibaba Cloud SLS (Simple Log Service) log query & analysis skill. Use this skill to help users write, explain, optimize, execute, or troubleshoot SLS index sea2Kinstalls