ryze-ai-adgent/open-seo-mcp-skills

competitor-gap

Find keywords a competitor ranks for that the user's site doesn't — the content gap, prioritized by volume and winnability.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/ryze-ai-adgent/open-seo-mcp-skills --skill competitor-gap

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

Competitor Gap

Requires

The free Ryze MCP connector (https://connector.get-ryze.ai/mcp). Claude Code: claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp. claude.ai / Desktop / Cursor: add it as a custom connector with the same URL. Setup: https://www.get-ryze.ai/how-to-connect-claude-to-google-meta-ads-mcp

Their rankings are estimates (DataForSEO), yours are real (GSC). Diff them.

Workflow

  1. Competitor's keywords. Via the workspace's DataForSEO tools — Labs ranked_keywords for the competitor domain (request shape: native__get_provider_docs, provider dataforseo). Pull top ~500 by volume. If DataForSEO isn't exposed in this workspace, check for connected ahrefs/semrush providers and use their organic-keywords endpoint instead; if none, stop and say which connection is missing.
  2. Competitor overview. Labs domain_rank_overview — their estimated organic traffic and keyword count, for context.
  3. Your keywords. google_search_console__runRawSearchAnalytics, dimension ["query"], last 90 days, high rowLimit — the full set of queries the user's site gets impressions for.
  4. Diff into three buckets:
  • Gap — competitor ranks top 20, you have zero impressions → new content needed
  • Behind — you both rank but they're ≥ 5 spots ahead → improve existing page
  • Ahead — you outrank them (report briefly; it's the moat)
  1. Prioritize the Gap and Behind buckets by volume × relevance to the user's product. Drop branded competitor terms unless the user wants comparison pages — then list them separately as "vs / alternative" page candidates.

Output

Verdict (how big the gap is, in keywords and estimated traffic), then: Gap table (keyword, their position, volume, suggested page), Behind table (keyword, their pos, your pos, your page, fix), and a top-10 action list. Note explicitly which numbers are estimates (theirs) vs real (yours).

Verwandte Aufgaben

aus demselben Repository

Weitere Skills

Alle Skills
ryze-ai-adgent
Community

ai-visibility

Measure real AI-engine visibility — traffic from ChatGPT, Perplexity, Claude, Gemini and which pages they cite — from actual GA4 referral data, not prompt sampling. Use when asked "AI visibility", "GEO/AEO check", "do LLMs cite us", "traffic from ChatGPT", or "how do we show up in AI search".

Installationen
0
GitHub Stars
7257
Aktualisiert
23. Okt.
ryze-ai-adgent
Community

backlink-check

Backlink profile for any domain — referring domains, authority, anchors, new/lost links, and a side-by-side vs a competitor. Use when asked "check my backlinks", "backlink profile of X", "who links to them", or "link gap vs competitor".

Installationen
0
GitHub Stars
7257
Aktualisiert
23. Okt.
ryze-ai-adgent
Community

content-brief

SERP-driven content brief for a target keyword — what ranks, what to cover, headings, questions, internal links from your own data. Use when asked for a "content brief", "outline to rank for X", "what should this article cover", or before writing any SEO page.

Installationen
0
GitHub Stars
7257
Aktualisiert
23. Okt.
ryze-ai-adgent
Community

keyword-research

Keyword research from a seed topic — ideas, real Google volume/CPC, intent, difficulty, clustered into a plan. Use when asked to "find keywords", "keyword research for X", "what should I rank for", or "build a keyword plan".

Installationen
0
GitHub Stars
7257
Aktualisiert
23. Okt.