Agent skill · Security

seo-content-gap-audit

Audit content gaps and decay using Ahrefs MCP data: missing topics, thin coverage, outdated content, and decaying pages. Use this skill when planning a content roadmap, refreshing a stale catalog, building topical authority, or identifying which existing pages need update versus replacement. Triggers on content gap, content audit, content refresh, content roadmap, decaying content, content decay, topical authority, what topics should we cover, where is competitor content stronger. Also triggers when organic traffic is flat despite consistent publishing.

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

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

Facts
Files in the skill folder: 2
SKILL.md size: 8 KB
Bundled scripts: none
Path: skills/seo-content-gap-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

# SEO Content Gap Audit Find content gaps and decay using Ahrefs MCP data. Stack-agnostic. Produces a roadmap of create, update, merge, and prune actions across the existing content catalog and identified topic gaps. --- ## When to use - Planning the next quarter or half of content investment - Refreshing a stale or underperforming content catalog - Building topical authority in a target space - Identifying decaying pages before they tank traffic - Audit prep before a major site redesign or migration - Diagnosing why content investment is not driving organic growth ## When NOT to use - Pure keyword research (use `seo-keyword`) - Competitor keyword gap (use `seo-keyword-gap-audit`) - Single-page optimization (use `seo-onpage`) - Pure prune-and-redirect decisions (use `seo-content-audit`) - New site planning with no existing content (use `content-strategy`) --- ## Required inputs - Target property and content scope - Competitor set (3-5 properties with comparable content depth) - Target topics or pillars (if defined) - Existing content inventory with URLs, primary topics, publish dates - Performance data (organic clicks per page, ranked keywords per page) - Confirmation Ahrefs MCP is

What's inside
Steps it walks through
  1. When to use
  2. When NOT to use
  3. Required inputs
  4. The framework: 4 categories of content opportunity
  5. Category 1: Missing topics
  6. Category 2: Thin coverage
  7. Category 3: Outdated content
  8. Category 4: Decaying content
  9. Workflow
  10. The action decision matrix
  11. Failure patterns
  12. Output format
  13. Reference files
Ships with 1 file
  • references/content-decision-matrix.md
More from claude-skills
All skills →
About this skill
What does the seo-content-gap-audit skill do?

Audit content gaps and decay using Ahrefs MCP data: missing topics, thin coverage, outdated content, and decaying pages. Use this skill when planning a content roadmap, refreshing a stale catalog, building topical authority, or identifying which existing pages need update versus replacement. Triggers on content gap, content audit, content refresh, content roadmap, decaying content, content decay, topical authority, what topics should we cover, where is competitor content stronger. Also triggers when organic traffic is flat despite consistent publishing.

How do I install it?

Run `npx skills add rampstackco/claude-skills --skill seo-content-gap-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