MCP HubMCP Hub
SKILL·D27215

seo-competitor

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

정보

이 스킬은 사용자의 사이트와 경쟁사를 SERP 중복도, 콘텐츠 깊이, 백링크 프로필, 기술적 상태를 종합적으로 비교하여 경쟁사 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-competitor

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

문서

SEO Competitor Analysis

Compare a site to its competitors and find the gaps worth closing. Stack-agnostic. Tool-friendly but tool-optional.


When to use

  • Identifying which competitors to study
  • Finding content gaps (topics they cover, you do not)
  • Finding backlink gaps (sites linking to them, not you)
  • Understanding why a specific competitor outranks the user
  • Benchmarking authority, technical posture, and content depth

When NOT to use

  • Single-page optimization (use seo-onpage)
  • Initial keyword research with no competitors yet identified (use seo-keyword first to find them)
  • Auditing one's own existing content (use seo-content-audit)

Required inputs

  • The user's site
  • 3 to 5 named competitors (or the topic area, if competitors are not yet identified)
  • Access to a keyword tool, a backlink tool, and any crawler

If competitors are unknown, start by listing the top 10 ranking domains for the user's top 10 priority keywords. Pick the 3 to 5 that appear most often.

Where competitor traffic estimation is the input you need (relative scale, channel mix, audience overlap), Similarweb MCP is the strongest source. Pair with Ahrefs (for backlink and keyword overlap) and Semrush (for SERP feature presence and SEO-PR overlap). Each platform gives a different cut of the same competitive landscape; using them together produces sharper signal than any one alone.


The framework: 5 angles

Competitor analysis covers five angles. Run all five for a full picture, or pick two or three for a focused investigation.

1. SERP overlap

Where do you and the competitor compete head-to-head?

  • For each priority keyword, who ranks in the top 10?
  • For each top-10 ranking, what page type wins (article, product, comparison, video)?
  • Are there SERP features (featured snippet, AI overview, video, image pack) one party holds and the other does not?
  • Which queries do competitors rank for that the user does not? (the content gap)

2. Content depth

What does their winning content look like?

  • Word count and structure of their top-ranking pages
  • Information types they include (data tables, original research, video, calculators, downloadable assets)
  • Update frequency on key pages (last modified date, change history)
  • Internal linking patterns (do their winning pages link to commercial pages?)
  • Topical breadth (how many related topics do they cover?)

3. Backlink profile

Where does their authority come from?

  • Total referring domains
  • Domain rating (or equivalent authority metric)
  • Top 50 referring pages by traffic value
  • Backlink types (editorial, directory, partner, paid, spam)
  • Link velocity (gaining or losing referring domains over time)
  • Pages on their site attracting the most links (these are their "linkable assets")

4. Technical posture

How clean is their technical foundation?

  • Core Web Vitals (LCP, INP, CLS)
  • Mobile usability
  • Schema implementation (which types, on which page types)
  • Site architecture and internal linking density
  • Crawl efficiency (are they wasting crawl budget?)
  • HTTPS, security headers
  • llms.txt and AI search readiness

5. Brand and entity strength

How well-known are they outside organic search?

  • Branded search volume (how many people search their name?)
  • Entity recognition in knowledge graph (do they have a Wikipedia page, knowledge panel, structured data feeding entity status?)
  • Mention frequency in their topic area (PR coverage, podcast appearances, citations)
  • Social signals (followers, engagement, share rates)
  • Reviews and reputation

Workflow

  1. Confirm the competitors. Either named, or derive from SERP overlap on top 10 priority keywords.
  2. Pick the angles. Run all 5 for a full audit, or 2 to 3 for a focused dive.
  3. Pull the data. Keyword tool exports, backlink tool exports, manual SERP inspection, technical crawl.
  4. Score each angle. Where does the user lead? Where do they trail?
  5. Identify gaps. Specific content gaps, specific backlink gaps, specific technical gaps.
  6. Prioritize. Which gaps are highest leverage to close? (Big traffic potential, achievable effort, strategic fit.)
  7. Write the report. Use the template in references/competitive-audit-template.md.

Failure patterns

  • Picking the wrong competitors. A site that outranks you on one keyword but operates a different business is not a competitor. Pick by SERP overlap and audience overlap, not by who you think you compete with.
  • Treating "more content" as the takeaway. They are not winning because they have 500 articles. They are winning because of specific content + links + UX. Find the actual lever.
  • Copying their pages verbatim. Diminishing returns. Beat them by being more useful, not by paraphrasing them.
  • Ignoring brand strength. A weaker site with a stronger brand wins on branded queries you cannot touch with content alone.
  • Static analysis. Re-run the analysis at least annually. Competitor strategies shift.

Output format

Default output is a markdown report at competitive-analysis.md plus accompanying spreadsheets for the keyword and backlink data.

Structure:

  1. Executive summary (3 to 5 critical findings)
  2. Competitor profiles (one per competitor, brief)
  3. SERP overlap analysis
  4. Content gap analysis
  5. Backlink gap analysis
  6. Technical comparison
  7. Brand and entity comparison
  8. Prioritized gap-closing roadmap

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-competitor
0
agent-skillsai-agentsanthropicclaudeclaude-aiclaude-code
FAQ

자주 묻는 질문

seo-competitor Skill이란 무엇인가요?

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

seo-competitor은(는) 어떻게 설치하나요?

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

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

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

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

네. seo-competitor은(는) 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을 선택하십시오.

스킬 보기