MCP HubMCP Hub
SKILL·8FD648

seo-content-gap-audit

rampstackco
업데이트됨 23 days ago
4 조회
953
132
953
GitHub에서 보기
메타mcpdesigndata

정보

이 스킬은 Ahrefs 데이터를 분석하여 SEO 콘텐츠 격차와 노후화를 감사합니다. 누락된 주제, 내용이 부실한 페이지, 오래된 콘텐츠를 식별하고, 주제 권위를 구축하기 위해 콘텐츠를 생성, 업데이트, 병합 또는 정리하는 실행 가능한 권장 사항을 제공합니다. 콘텐츠 로드맵을 계획하거나, 부진한 카탈로그를 활성화하거나, 정체된 자연 유입 트래픽을 진단할 때 사용하세요.

빠른 설치

Claude Code

추천
기본
npx skills add rampstackco/claude-skills -a claude-code
플러그인 명령대체
/plugin add https://github.com/rampstackco/claude-skills
Git 클론대체
git clone https://github.com/rampstackco/claude-skills.git ~/.claude/skills/seo-content-gap-audit

Claude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요

문서

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

GitHub 저장소

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

자주 묻는 질문

seo-content-gap-audit Skill이란 무엇인가요?

seo-content-gap-audit은(는) rampstackco이(가) 만든 Claude Skill입니다. Skill은 Claude가 필요할 때 불러오는 지침과 리소스를 묶어 추가 프롬프트 없이 seo-content-gap-audit 관련 작업을 수행할 수 있게 합니다.

seo-content-gap-audit은(는) 어떻게 설치하나요?

이 페이지의 설치 명령을 사용하세요. seo-content-gap-audit을(를) Claude Code 플러그인으로 추가하거나 저장소를 skills 디렉터리에 복제한 다음 Claude를 다시 시작해 Skill을 불러옵니다.

seo-content-gap-audit은(는) 어떤 카테고리에 속하나요?

seo-content-gap-audit은(는) 메타 카테고리에 속합니다.

seo-content-gap-audit은(는) 무료로 사용할 수 있나요?

네. seo-content-gap-audit은(는) AIMCP에 등록되어 있으며 무료로 설치할 수 있습니다.

연관 스킬

content-collections
메타

이 스킬은 콘텐츠 콜렉션(Content Collections)을 위한 프로덕션 검증된 설정을 제공합니다. 콘텐츠 콜렉션은 Markdown/MDX 파일을 Zod 검증이 포함된 타입 안전한 데이터 콜렉션으로 변환해주는 TypeScript 최우선 도구입니다. 블로그, 문서 사이트 또는 콘텐츠 중심의 Vite + React 애플리케이션을 구축할 때 타입 안전성과 자동 콘텐츠 검증을 보장하기 위해 사용하세요. Vite 플러그인 구성과 MDX 컴파일부터 배포 최적화 및 스키마 검증에 이르기까지 모든 것을 다룹니다.

스킬 보기
polymarket
메타

이 스킬은 개발자들이 Polymarket 예측 시장 플랫폼을 활용한 애플리케이션을 구축할 수 있도록 지원하며, 거래 및 시장 데이터를 위한 API 통합 기능을 포함합니다. 또한 WebSocket을 통한 실시간 데이터 스트리밍을 제공하여 실시간 거래와 시장 활동을 모니터링할 수 있습니다. 이를 통해 거래 전략을 구현하거나 실시간 시장 업데이트를 처리하는 도구를 생성하는 데 활용할 수 있습니다.

스킬 보기
creating-opencode-plugins
메타

이 스킬은 개발자들이 명령어, 파일, LSP 작업 등 25개 이상의 이벤트 유형에 연결되는 OpenCode 플러그인을 만들 수 있도록 돕습니다. JavaScript/TypeScript 모듈을 위한 플러그인 구조, 이벤트 API 명세, 구현 패턴을 제공합니다. OpenCode AI 어시스턴트의 라이프사이클을 사용자 정의 이벤트 기반 로직으로 가로채거나, 모니터링하거나, 확장해야 할 때 사용하세요.

스킬 보기
sglang
메타

SGLang은 RadixAttention 프리픽스 캐싱을 활용하여 JSON, 정규식, 에이전트 워크플로우를 위한 고속 구조화 생성에 특화된 고성능 LLM 서빙 프레임워크입니다. 특히 반복되는 프리픽스가 있는 작업에서 상당히 빠른 추론 속도를 제공하여 복잡한 구조화 출력 및 다중 턴 대화에 이상적입니다. 제약 디코딩이 필요하거나 광범위한 프리픽스 공유가 있는 애플리케이션을 구축할 때는 vLLM과 같은 대안보다 SGLang을 선택하십시오.

스킬 보기