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.
63
75%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/seo-content-gap-audit/SKILL.mdFind 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.
seo-keyword)seo-keyword-gap-audit)seo-onpage)seo-content-audit)content-strategy)Every content opportunity falls into one of four categories. Different categories need different actions.
Content gap analysis is sharper with multiple data sources. Ahrefs surfaces keyword and topic gaps (the primary backend below). Similarweb surfaces traffic-driving page-level gaps (which of a competitor's pages earn meaningful traffic, not just rankings). Semrush surfaces SERP-feature gaps (where competitors win answer boxes, knowledge panels, People Also Ask placements). The three platforms often disagree on individual data points; that disagreement is itself a useful signal.
Topics with traffic potential where the property has no relevant page at all. Competitors often rank in the top 10. The fix: create new content.
Pulled from:
Topics where the property has a page but it is too shallow, narrow, or single-keyword to compete with topical hubs. Competitor pages cover the topic across multiple subtopics. The fix: deepen the existing page or expand into a topic cluster.
Pulled from:
Pages that ranked well historically but have lost ground due to staleness. Information is dated, examples are old, the SERP intent has shifted. The fix: refresh with current information and re-promote.
Pulled from:
Pages that have lost traffic for reasons not obviously about staleness: SERP feature changes, competitor publishing, intent shifts, internal linking dilution. The fix: diagnose why, then refresh, merge, or redirect.
Pulled from:
references/content-decision-matrix.md.content-strategy, content-and-copy, and seo-onpage.For each piece of existing content or proposed new content, decide one action.
| Signal | Action |
|---|---|
| Strong page, healthy traffic, current information | Keep. Defend with internal linking and refresh on schedule. |
| Page exists, ranking on page 2-3, content is thin vs SERP | Update. Deepen, restructure, broaden. |
| Page exists, traffic declining, content is dated | Refresh. Update facts, examples, year references, screenshots. |
| Page exists, low or zero traffic, low ranking, no improvement path | Prune or merge. Redirect to a stronger relative if one exists. |
| Multiple pages on overlapping topics | Merge into one canonical page. Redirect the others. |
| Topic missing entirely, competitor coverage strong | Create new page or pillar. |
| Topic missing, but competitors do not rank well either | Validate intent before investing. Could be an opportunity or could be a dead end. |
| Page is off-topic for the property | Redirect to most relevant page or remove from sitemap. |
A content gap audit document with:
Length: 8-15 pages plus an attached inventory spreadsheet.
references/content-decision-matrix.md - Detailed decision tree for classifying pages and choosing the create/update/merge/prune action, with worked examples.8e70d03
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.