seo-content-gap-audit
À propos
Cette compétence audite les lacunes et la dégradation du contenu SEO en analysant les données Ahrefs pour identifier les sujets manquants, les pages peu fournies et le contenu obsolète. Elle fournit des recommandations actionnables pour créer, mettre à jour, fusionner ou élaguer le contenu afin de renforcer l'autorité thématique. Utilisez-la lors de la planification d'une feuille de route de contenu, du rafraîchissement d'un catalogue vieillissant ou du diagnostic d'un trafic organique stagnant.
Installation rapide
Claude Code
Recommandénpx skills add rampstackco/claude-skills -a claude-code/plugin add https://github.com/rampstackco/claude-skillsgit clone https://github.com/rampstackco/claude-skills.git ~/.claude/skills/seo-content-gap-auditCopiez et collez cette commande dans Claude Code pour installer cette compétence
Documentation
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 connected
The framework: 4 categories of content opportunity
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.
Category 1: Missing topics
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:
- Ahrefs Content Explorer (top performing content in target topics)
- Competitor top pages (Ahrefs Site Explorer)
- Keyword gap audit output (clustered into topics)
Category 2: Thin coverage
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 ranking on page 2-3 for target keywords
- Pages with low organic click share relative to ranked keyword volume
- Pages where competitors have longer or broader equivalents
Category 3: Outdated content
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 with declining organic clicks over the last 6-12 months
- Pages with publish dates over 18 months old
- Pages with ranked keywords slipping in position
Category 4: Decaying content
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:
- Pages with sharp recent traffic drops
- Pages where SERP composition has shifted (more video, more featured snippets, AI overviews)
- Pages that compete with newer pages on the same site (cannibalization)
Workflow
- Charter the audit. Scope (whole site or section), goal, time window for performance data.
- Pull the inventory. Every URL, with publish date, primary topic, organic clicks, ranked keywords.
- Pull competitor coverage. Top pages and content clusters from each competitor.
- Classify each existing page. Healthy / thin / outdated / decaying / off-topic.
- Identify missing topics. Cross-reference competitor top pages and keyword gap output.
- Score each opportunity. See
references/content-decision-matrix.md. - Cluster. Group related missing topics into pillar concepts.
- Decide actions. Create / update / merge / redirect / prune for each opportunity.
- Sequence the roadmap. Quarter by quarter, with effort estimates and traffic forecasts.
- Hand off. Output feeds
content-strategy,content-and-copy, andseo-onpage.
The action decision matrix
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. |
Failure patterns
- All-create, no-update bias. Teams default to creating new content. Updates and merges often outperform new pieces by a wide margin and at lower cost.
- Treating publish date as currency. A 5-year-old page can outrank a 1-month-old page if it is better. Stop deleting old content reflexively.
- Cannibalization blind spots. Two pages on overlapping topics dilute each other. Audit for it explicitly.
- No effort estimates. A roadmap without effort sizes cannot be sequenced realistically.
- No traffic forecast. A roadmap without forecasted impact loses funding fights. Forecast even with wide confidence bands.
- Refreshing without re-promotion. A refreshed page needs a re-crawl signal: update sitemap, internal links, distribution.
- Ignoring intent shift. Some keywords have shifted from informational to transactional or to AI-answer-dominated. Recognize when the SERP is no longer addressable by the existing format.
- Confusing decay with seasonality. A 30% click drop in summer for a back-to-school topic is not decay. Compare year-over-year, not month-over-month.
- Auditing in isolation from the keyword gap. The two audits feed each other. Run them adjacent.
Output format
A content gap audit document with:
- Executive summary. Top 3 themes, content health verdict, recommended quarterly investment split.
- Content inventory snapshot. Counts by health classification.
- Missing topics. Prioritized list with cluster mapping and traffic forecast, or state the gap per the data-availability rule.
- Thin coverage. Pages to deepen, with recommendation for each.
- Outdated content. Pages to refresh, with refresh scope.
- Decaying content. Pages to diagnose and act on, with hypothesis for each.
- Cannibalization findings. Page pairs to merge.
- Action roadmap. Quarter by quarter, with effort and forecast.
- Methodology. Data sources, classification criteria, caveats.
Length: 8-15 pages plus an attached inventory spreadsheet.
If required data is unavailable
This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.
Reference files
references/content-decision-matrix.md- Detailed decision tree for classifying pages and choosing the create/update/merge/prune action, with worked examples.
Dépôt GitHub
Questions fréquentes
Qu’est-ce que le Skill seo-content-gap-audit ?
seo-content-gap-audit est un Skill Claude créé par rampstackco. Un Skill regroupe des instructions et des ressources que Claude charge à la demande pour effectuer des tâches liées à seo-content-gap-audit sans consigne supplémentaire.
Comment installer seo-content-gap-audit ?
Utilisez les commandes d’installation de cette page : ajoutez seo-content-gap-audit à Claude Code comme plugin ou clonez son dépôt dans votre dossier skills, puis redémarrez Claude pour charger le Skill.
À quelle catégorie appartient seo-content-gap-audit ?
seo-content-gap-audit appartient à la catégorie Méta.
seo-content-gap-audit est-il gratuit ?
Oui. seo-content-gap-audit est référencé sur AIMCP et son installation est gratuite.
Compétences associées
Cette compétence propose une configuration éprouvée en production pour Content Collections, un outil axé sur TypeScript qui transforme des fichiers Markdown/MDX en collections de données typées de manière sûre avec une validation Zod. Utilisez-la lors de la création de blogs, de sites de documentation ou d'applications Vite + React riches en contenu pour garantir la sécurité de typage et la validation automatique du contenu. Elle couvre tout, de la configuration du plugin Vite et de la compilation MDX à l'optimisation des déploiements et la validation des schémas.
Cette compétence permet aux développeurs de créer des applications avec la plateforme de marchés prédictifs Polymarket, incluant l'intégration d'API pour le trading et les données de marché. Elle fournit également une diffusion de données en temps réel via WebSocket pour surveiller les transactions en direct et l'activité du marché. Utilisez-la pour mettre en œuvre des stratégies de trading ou pour créer des outils traitant les mises à jour de marché en direct.
Cette compétence aide les développeurs à créer des plugins OpenCode qui s'interconnectent avec plus de 25 types d'événements tels que les commandes, les fichiers et les opérations LSP. Elle fournit la structure du plugin, les spécifications de l'API événementielle et les modèles d'implémentation pour les modules JavaScript/TypeScript. Utilisez-la lorsque vous avez besoin d'intercepter, de surveiller ou d'étendre le cycle de vie de l'assistant IA OpenCode avec une logique personnalisée pilotée par les événements.
SGLang est un framework de service LLM haute performance spécialisé dans la génération rapide et structurée pour les workflows JSON, regex et agentiques grâce à son cache de préfixe RadixAttention. Il offre une inférence nettement plus rapide, particulièrement pour les tâches avec des préfixes répétés, ce qui le rend idéal pour les sorties complexes et structurées ainsi que les conversations multi-tours. Choisissez SGLang plutôt que des alternatives comme vLLM lorsque vous avez besoin d'un décodage contraint ou que vous construisez des applications avec un partage étendu de préfixes.
