seo-competitor
Über
Diese Fähigkeit führt eine umfassende wettbewerbsorientierte SEO-Analyse durch, indem sie die Website eines Nutzers mit festgelegten Wettbewerbern in den Bereichen SERP-Überschneidung, Inhaltsqualität, Backlink-Profile und technische Faktoren vergleicht. Sie wird für Aufgaben wie die Identifizierung von Content-Lücken, die Erkennung von Backlink-Möglichkeiten und das Verständnis von Ranking-Unterschieden ausgelöst. Entwickler sollten sie nutzen, um eine Website zu benchmarken und umsetzbare Erkenntnisse zu gewinnen, um Wettbewerber zu übertreffen.
Schnellinstallation
Claude Code
Empfohlennpx 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-competitorKopieren Sie diesen Befehl und fügen Sie ihn in Claude Code ein, um diese Fähigkeit zu installieren
Dokumentation
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-keywordfirst 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
- Confirm the competitors. Either named, or derive from SERP overlap on top 10 priority keywords.
- Pick the angles. Run all 5 for a full audit, or 2 to 3 for a focused dive.
- Pull the data. Keyword tool exports, backlink tool exports, manual SERP inspection, technical crawl.
- Score each angle. Where does the user lead? Where do they trail?
- Identify gaps. Specific content gaps, specific backlink gaps, specific technical gaps.
- Prioritize. Which gaps are highest leverage to close? (Big traffic potential, achievable effort, strategic fit.)
- 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:
- Executive summary (3 to 5 critical findings)
- Competitor profiles (one per competitor, brief)
- SERP overlap analysis
- Content gap analysis
- Backlink gap analysis
- Technical comparison
- Brand and entity comparison
- Prioritized gap-closing roadmap
Reference files
references/competitive-audit-template.md- Fillable competitive audit template.references/content-gap-method.md- Detailed methodology for finding content gaps with example.
GitHub Repository
Verwandte Skills
seo-onpage
AndereDiese Fähigkeit führt umfassende On-Page-SEO-Audits und Optimierungen für einzelne Webseiten durch. Sie analysiert und verbessert acht Schlüsseldimensionen, darunter Title-Tags, Meta-Beschreibungen, Überschriften, Inhalte, Links, Bilder, URLs und Schema-Markup. Nutzen Sie sie, wann immer Sie eine einzelne Seite auditieren, optimieren oder SEO-freundliche Inhalte schreiben müssen, um die Suchleistung zu verbessern.
seo-technical
AndereDiese Fähigkeit führt einen umfassenden technischen SEO-Audit durch und analysiert Crawlbarkeit, Indexierbarkeit, Seitenarchitektur, Page Experience und strukturierte Daten. Sie wird durch spezifische Begriffe wie Sitemaps, Core Web Vitals oder Weiterleitungen ausgelöst und aktiviert sich auch bei Problemen wie Trafficrückgängen oder Indexierungsfehlern. Nutzen Sie sie, um eine breite Palette von suchmaschinenrelevanten Problemen auf der gesamten Website zu diagnostizieren und zu beheben.
seo-keyword
AndereDiese Fähigkeit führt umfassende SEO-Keyword-Recherchen durch, analysiert die Suchintention und gruppiert Keywords thematisch für die Content-Planung. Sie hilft dabei, Ranking-Chancen zu identifizieren und Keywords anhand von Metriken wie Schwierigkeitsgrad und Suchvolumen zu priorisieren. Entwickler können sie nutzen, um Content-Strategien zu erstellen, Themen zu strukturieren und Content-Lücken für neue oder bestehende Websites zu schließen.
seo-content-audit
AndereDiese Fähigkeit überprüft die Inhaltsbibliothek einer Website, um systematisch jedes Element anhand eines Keep/Update/Merge/Redirect/Delete-Rahmens zu bewerten und zu kategorisieren. Sie wird für SEO-Aufgaben wie die Behebung von Inhaltsverfall, die Lösung von Keyword-Kannibalisierung, das Ausdünnen von Seiten oder die Behandlung von siteweiten Traffic-Einbrüchen ausgelöst. Entwickler sollten sie nutzen, um Inhalte zu inventarisieren, die Leistung zu bewerten und umsetzbare Inhaltsmanagement-Entscheidungen zu generieren.
