Help us improve
Share bugs, ideas, or general feedback.
From rampstack-skills
Audit site content to decide whether to keep, update, merge, redirect, or delete each page. Automatically activated for content audit, cannibalization, pruning, and traffic decline investigations.
npx claudepluginhub rampstackco/claude-skills --plugin rampstack-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/rampstack-skills:seo-content-auditThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
Audits content gaps and decay using Ahrefs MCP data: missing topics, thin coverage, outdated content, decaying pages. Produces a create/update/merge/prune roadmap for content catalogs.
Identifies outdated dates, statistics, examples, trends, and links in content; suggests prioritized refresh plans, update checklists, and SEO freshness signal tactics for older pages.
Performs full SEO audits using Google Search Console, PageSpeed Insights, and technical crawl to diagnose traffic drops, find content gaps, and produce actionable 30-day plans.
Share bugs, ideas, or general feedback.
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.
seo-onpage)seo-keyword)seo-competitor)seo-technical)For every content piece, the audit produces one of five decisions.
The page performs well, has clear intent, and needs no changes.
Signals:
The page has potential but is underperforming due to fixable issues.
Signals:
Two or more pages target overlapping queries and should consolidate.
Signals:
The page has no future but has assets (links, equity) worth preserving.
Signals:
The page has no future and no assets worth preserving.
Signals:
Note: In most cases, return 410 (gone) for intentionally deleted content. 410 is processed faster than 404 and signals the deletion was deliberate.
Pull these for every URL before deciding:
| Metric | Source | Threshold for "low" |
|---|---|---|
| Sessions (last 90 days) | Analytics | <10/month |
| Organic traffic (last 90 days) | Search console or analytics | <5/month |
| Average position for top query | Search console | >30 |
| Impressions (last 90 days) | Search console | <100/month |
| Click-through rate | Search console | <1% (when impressions exist) |
| Referring domains | Backlink tool | 0 |
| Engagement (avg time on page) | Analytics | <30 seconds |
| Last meaningful update | Manual / git | >24 months |
| Word count | Crawler | <300 (for articles) |
| Internal links in | Crawler | 0 |
A page can survive low scores on a few metrics. A page that fails on most is a delete or redirect candidate.
A simplified decision tree:
Has traffic? ─── Yes ──── Recent decay? ─── Yes ── UPDATE
│ │
│ └── No ─── KEEP
│
└── No ──── Has backlinks? ─── Yes ── Has relevant target? ─── Yes ── REDIRECT
│ │
│ └── No ─── UPDATE (rebuild)
│
└── No ──── Cannibalizing another page? ─── Yes ── MERGE
│
└── No ─── DELETE (410)
For overlapping pages, "merge" usually wins over "delete" because it preserves both link equity and any topical authority.
Default output: a spreadsheet with one row per URL, plus a summary markdown report.
Spreadsheet columns:
Summary report:
references/audit-template.md - Spreadsheet column definitions and report template.references/cannibalization-resolution.md - Detailed methodology for resolving cannibalization clusters.