MCP HubMCP Hub
SKILL·8FD648

seo-content-gap-audit

rampstackco
Actualizado 23 days ago
4 vistas
953
132
953
Ver en GitHub
Metamcpdesigndata

Acerca de

Esta habilidad audita las brechas y el deterioro del contenido SEO analizando datos de Ahrefs para identificar temas ausentes, páginas de contenido escaso y contenido desactualizado. Proporciona recomendaciones prácticas para crear, actualizar, fusionar o eliminar contenido con el fin de construir autoridad temática. Úsela al planificar una hoja de ruta de contenido, al renovar un catálogo estancado o al diagnosticar un tráfico orgánico estancado.

Instalación rápida

Claude Code

Recomendado
Principal
npx skills add rampstackco/claude-skills -a claude-code
Comando PluginAlternativo
/plugin add https://github.com/rampstackco/claude-skills
Git CloneAlternativo
git clone https://github.com/rampstackco/claude-skills.git ~/.claude/skills/seo-content-gap-audit

Copia y pega este comando en Claude Code para instalar esta habilidad

Documentación

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

  1. Charter the audit. Scope (whole site or section), goal, time window for performance data.
  2. Pull the inventory. Every URL, with publish date, primary topic, organic clicks, ranked keywords.
  3. Pull competitor coverage. Top pages and content clusters from each competitor.
  4. Classify each existing page. Healthy / thin / outdated / decaying / off-topic.
  5. Identify missing topics. Cross-reference competitor top pages and keyword gap output.
  6. Score each opportunity. See references/content-decision-matrix.md.
  7. Cluster. Group related missing topics into pillar concepts.
  8. Decide actions. Create / update / merge / redirect / prune for each opportunity.
  9. Sequence the roadmap. Quarter by quarter, with effort estimates and traffic forecasts.
  10. Hand off. Output feeds content-strategy, content-and-copy, and seo-onpage.

The action decision matrix

For each piece of existing content or proposed new content, decide one action.

SignalAction
Strong page, healthy traffic, current informationKeep. Defend with internal linking and refresh on schedule.
Page exists, ranking on page 2-3, content is thin vs SERPUpdate. Deepen, restructure, broaden.
Page exists, traffic declining, content is datedRefresh. Update facts, examples, year references, screenshots.
Page exists, low or zero traffic, low ranking, no improvement pathPrune or merge. Redirect to a stronger relative if one exists.
Multiple pages on overlapping topicsMerge into one canonical page. Redirect the others.
Topic missing entirely, competitor coverage strongCreate new page or pillar.
Topic missing, but competitors do not rank well eitherValidate intent before investing. Could be an opportunity or could be a dead end.
Page is off-topic for the propertyRedirect 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:

  1. Executive summary. Top 3 themes, content health verdict, recommended quarterly investment split.
  2. Content inventory snapshot. Counts by health classification.
  3. Missing topics. Prioritized list with cluster mapping and traffic forecast, or state the gap per the data-availability rule.
  4. Thin coverage. Pages to deepen, with recommendation for each.
  5. Outdated content. Pages to refresh, with refresh scope.
  6. Decaying content. Pages to diagnose and act on, with hypothesis for each.
  7. Cannibalization findings. Page pairs to merge.
  8. Action roadmap. Quarter by quarter, with effort and forecast.
  9. 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

Repositorio GitHub

rampstackco/claude-skills
Ruta: dist/codex/.agents/skills/seo-content-gap-audit
0
agent-skillsai-agentsanthropicclaudeclaude-aiclaude-code
FAQ

Preguntas frecuentes

¿Qué es el Skill seo-content-gap-audit?

seo-content-gap-audit es un Skill de Claude creado por rampstackco. Los Skills agrupan instrucciones y recursos que Claude carga cuando los necesita para realizar tareas relacionadas con seo-content-gap-audit sin indicaciones adicionales.

¿Cómo instalo seo-content-gap-audit?

Usa los comandos de instalación de esta página: añade seo-content-gap-audit a Claude Code como plugin o clona su repositorio en tu directorio de skills y reinicia Claude para cargarlo.

¿A qué categoría pertenece seo-content-gap-audit?

seo-content-gap-audit pertenece a la categoría Meta.

¿Se puede usar seo-content-gap-audit gratis?

Sí. seo-content-gap-audit aparece en AIMCP y se puede instalar gratis.

Habilidades relacionadas

content-collections
Meta

Esta habilidad proporciona una configuración probada en producción para Content Collections, una herramienta centrada en TypeScript que transforma archivos Markdown/MDX en colecciones de datos con tipado seguro mediante validación Zod. Úsala al construir blogs, sitios de documentación o aplicaciones Vite + React con mucho contenido para garantizar seguridad de tipos y validación automática de contenido. Abarca todo, desde la configuración del plugin de Vite y compilación MDX hasta la optimización de despliegue y validación de esquemas.

Ver habilidad
polymarket
Meta

Esta habilidad permite a los desarrolladores crear aplicaciones con la plataforma de mercados de predicción Polymarket, incluyendo la integración de API para operaciones y datos de mercado. También proporciona transmisión de datos en tiempo real a través de WebSocket para monitorear operaciones en vivo y actividad del mercado. Úsela para implementar estrategias de trading o crear herramientas que procesen actualizaciones de mercado en tiempo real.

Ver habilidad
creating-opencode-plugins
Meta

Esta habilidad ayuda a los desarrolladores a crear complementos de OpenCode que se conectan a más de 25 tipos de eventos, como comandos, archivos y operaciones LSP. Proporciona la estructura del complemento, las especificaciones de la API de eventos y los patrones de implementación para módulos en JavaScript/TypeScript. Úsala cuando necesites interceptar, monitorear o extender el ciclo de vida del asistente de IA de OpenCode con lógica personalizada basada en eventos.

Ver habilidad
sglang
Meta

SGLang es un framework de alto rendimiento para el servicio de LLM que se especializa en generación rápida y estructurada para JSON, expresiones regulares y flujos de trabajo de agentes utilizando su caché de prefijos RadixAttention. Ofrece una inferencia significativamente más rápida, especialmente para tareas con prefijos repetidos, lo que lo hace ideal para salidas complejas y estructuradas, y conversaciones multiturno. Elige SGLang sobre alternativas como vLLM cuando necesites decodificación restringida o estés construyendo aplicaciones con uso extensivo de prefijos compartidos.

Ver habilidad