Agent skill · Security

seo-content-audit

Audit existing content across a site to decide what to keep, update, merge, redirect, or delete. Use this skill whenever the user wants to audit existing content, fix content decay, resolve keyword cannibalization, prune underperforming pages, prioritize content updates, or apply a keep/update/merge/redirect/delete framework to a content library. Triggers on content audit, content decay, content refresh, cannibalization, keyword cannibalization, prune content, delete pages, redirect old pages, content inventory, what to keep, what to update, content scorecard, evergreen refresh. Also triggers

RampStack477★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add rampstackco/claude-skills --skill seo-content-audit --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 8 KB
Bundled scripts: none
Path: skills/seo-content-audit/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Content Audit Inventory existing content, score it, and decide for each piece: keep, update, merge, redirect, or delete. Stack-agnostic. Works on blogs, marketing sites, knowledge bases, and product content. --- ## When to use - Inheriting a content library you did not create - Diagnosing site-wide traffic decline - Resolving cannibalization (two pages competing for the same query) - Pre-migration cleanup - Annual or semi-annual content health check - Pruning before a redesign or replatform ## When NOT to use - Optimizing a single page (use `seo-onpage`) - Planning new content (use `seo-keyword`) - Comparing your content to competitors (use `seo-competitor`) - Site-level technical issues (use `seo-technical`) --- ## Required inputs - The site URL and access to crawl it (or a complete URL list) - Search console access (or a 12-month export) - Analytics access (sessions, conversions, engagement) - A backlink tool (to identify pages with referring domains worth preserving) --- ## The framework: 5 actions For every content piece, the audit produces one of five decisions. ### 1. Keep The page performs well, has clear intent, and needs no changes. **Signals:** - Top 10 ranking for its

What's inside
Steps it walks through
  1. When to use
  2. When NOT to use
  3. Required inputs
  4. The framework: 5 actions
  5. 1. Keep
  6. 2. Update
  7. 3. Merge
  8. 4. Redirect
  9. 5. Delete (and let return 404 or 410)
  10. Scoring inputs
  11. Decision matrix
  12. Workflow
  13. Failure patterns
  14. Output format
Ships with 2 files
  • references/audit-template.md
  • references/cannibalization-resolution.md
More from claude-skills
All skills →
About this skill
What does the seo-content-audit skill do?

Audit existing content across a site to decide what to keep, update, merge, redirect, or delete. Use this skill whenever the user wants to audit existing content, fix content decay, resolve keyword cannibalization, prune underperforming pages, prioritize content updates, or apply a keep/update/merge/redirect/delete framework to a content library. Triggers on content audit, content decay, content refresh, cannibalization, keyword cannibalization, prune content, delete pages, redirect old pages, content inventory, what to keep, what to update, content scorecard, evergreen refresh. Also triggers

How do I install it?

Run `npx skills add rampstackco/claude-skills --skill seo-content-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going