Agentic-SEO-Skill MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

16 sub-skills: technical SEO, content quality, schema, performance, links, GEO/AEO, sitemap, hreflang, strategy
10 specialist agents (technical, content, performance, schema, sitemap, visual, GitHub, benchmarking, data, verification)
33 evidence-collector scripts (32 Python + 1 shell) for auditable findings
Runs on Antigravity (project-local), Claude Code (user-global), and Codex (user-global)
Enforces current Google signals: INP not FID, full E-E-A-T treatment

Live-Demo

In der Praxis

agentic-seo-skill.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "agentic-seo-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/Bhanunamikaze/Agentic-SEO-Skill",
        "~/.claude/skills/Agentic-SEO-Skill"
      ],
      "_inferred": true
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "agentic-seo-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/Bhanunamikaze/Agentic-SEO-Skill",
        "~/.claude/skills/Agentic-SEO-Skill"
      ],
      "_inferred": true
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "agentic-seo-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/Bhanunamikaze/Agentic-SEO-Skill",
        "~/.claude/skills/Agentic-SEO-Skill"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "agentic-seo-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/Bhanunamikaze/Agentic-SEO-Skill",
        "~/.claude/skills/Agentic-SEO-Skill"
      ],
      "_inferred": true
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "agentic-seo-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/Bhanunamikaze/Agentic-SEO-Skill",
        "~/.claude/skills/Agentic-SEO-Skill"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "agentic-seo-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/Bhanunamikaze/Agentic-SEO-Skill",
          "~/.claude/skills/Agentic-SEO-Skill"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add agentic-seo-skill -- git clone https://github.com/Bhanunamikaze/Agentic-SEO-Skill ~/.claude/skills/Agentic-SEO-Skill

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: Agentic-SEO-Skill

Run an evidence-backed SEO audit with confidence labels

👤 SEO analysts tired of 'trust me' recommendations ⏱ ~60 min intermediate

Wann einsetzen: You want findings you can defend to a skeptical engineering lead.

Ablauf

Trigger the full audit

Use agentic-seo-skill on https://site.com — full evidence-backed audit.✓ Kopiert

→ Scripts collect raw data (meta tags, schema, link graph, CWV); agents analyze
Review findings with proofs

Show the top 10 issues with their supporting evidence and confidence labels.✓ Kopiert

→ Each finding has a literal quote/data point behind it
Prioritized action plan

Order by impact × effort.✓ Kopiert

→ Ranked plan with numeric rationale

Ergebnis: An audit where every finding is citable.

Fallstricke

Low-confidence findings treated as high priority — Use the confidence labels — skip 'low' until high/medium are done

Kombinieren mit: firecrawl

Audit a GitHub-hosted docs site with the GitHub-analyst agent

👤 Dev-tool teams with docs on GitHub Pages ⏱ ~40 min intermediate

Wann einsetzen: Your docs live in a repo and you want a SEO audit tied to the repo structure.

Ablauf

Point the GitHub agent at the repo

agentic-seo-skill — audit github.com/acme/docs site. Output GITHUB-SEO-REPORT.md.✓ Kopiert

→ Report in the repo format with per-file recommendations
Open a PR with fixes

Turn the high-confidence findings into a PR.✓ Kopiert

→ PR with concrete diffs

Ergebnis: A SEO-improved docs site with a trackable PR.

Fallstricke

PR touches too many files at once — Split by finding type (meta vs content vs schema)

Kombinieren mit: github

Optimize pages for Perplexity / ChatGPT / AI Overviews citations

👤 Content teams losing clicks to AI summaries ⏱ ~30 min intermediate

Wann einsetzen: You want to be the cited source, not just another organic result.

Ablauf

Run the GEO/AEO sub-skill

agentic-seo-skill — GEO audit on https://site.com/post.✓ Kopiert

→ Findings tied to snippet-friendliness, entity clarity, citation signals
Apply and verify

Apply recommendations and re-verify.✓ Kopiert

→ Score deltas with evidence

Ergebnis: Pages restructured for AI-citation pickup.

Fallstricke

Over-optimization hurts human readability — The content-quality agent catches robotic-sounding edits

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

agentic-seo-skill + firecrawl

Firecrawl does the JS-rendered crawl; agentic-seo interprets

Crawl with firecrawl, pipe rendered HTML into agentic-seo-skill for analysis.✓ Kopiert

agentic-seo-skill + github

Open PRs directly from audit findings

For the high-confidence findings, open a PR in the repo.✓ Kopiert

agentic-seo-skill + claude-seo-skill

Use the /seo slash commands for fast runs, agentic-seo for evidence-backed depth

First do /seo audit for the quick view, then agentic-seo-skill for the deep defensible audit.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen
Technical SEO agent	URL	Baseline tech audit
Schema agent	URL	Structured data work
Performance agent	URL	CWV review
GitHub-analyst agent	repo URL	Audits on GitHub-hosted sites
Verification agent	prior findings	Before publishing audit

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: None for the skill
Tokens pro Aufruf: 10-30k for full audit — evidence collection uses scripts, not tokens, for the raw data
Kosten in €: Free — skill is local
Tipp: Utility scripts are Python — run them as preflight outside the LLM loop to save tokens.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: No credentials — scripts hit public URLs only

Datenabfluss: Only to the sites you audit

Utility scripts run on your machine — review before running on sensitive internal URLs.

Fehlerbehebung

Häufige Fehler und Lösungen

Utility scripts fail to run

Check Python version and required packages; install dependencies from the skill's requirements file.

Prüfen: python --version

Confidence labels all 'low'

Scripts couldn't collect enough raw evidence — check network access and JS rendering.

GitHub-analyst can't access repo

Set a PAT for private repos; public repos should work unauthenticated.

Alternativen

Agentic-SEO-Skill vs. andere

Alternative	Wann stattdessen	Kompromiss
claude-seo-skill	You want slash-command UX and enterprise reporting	Claude-only; no multi-agent evidence framework
seo-geo-claude-skill	You want a phase-based lighter library	Less evidence-first methodology

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen