superseo-skills MCP — ユースケース, インストール & ライブデモ

なぜ使うのか

主な機能

11 discrete SEO skills, each with its own methodology
Claude Code marketplace install: /plugin marketplace add inhouseseo/superseo-skills
Covers the full SEO lifecycle: audit → plan → write → link
E-E-A-T audit based on current Google quality guidelines
Anti-AI-slop writing standards baked into write-content

ライブデモ

実際の動作

superseo-skill.replay ▶ 準備完了

0/0

インストール

クライアントを選択

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

{
  "mcpServers": {
    "superseo-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/inhouseseo/superseo-skills",
        "~/.claude/skills/superseo-skills"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config を開く。保存後、アプリを再起動。

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

{
  "mcpServers": {
    "superseo-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/inhouseseo/superseo-skills",
        "~/.claude/skills/superseo-skills"
      ],
      "_inferred": true
    }
  }
}

Cursor は Claude Desktop と同じ mcpServers スキーマを使用。プロジェクト設定はグローバルより優先。

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "superseo-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/inhouseseo/superseo-skills",
        "~/.claude/skills/superseo-skills"
      ],
      "_inferred": true
    }
  }
}

Cline サイドバーの MCP Servers アイコンをクリックし、"Edit Configuration" を選択。

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "superseo-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/inhouseseo/superseo-skills",
        "~/.claude/skills/superseo-skills"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop と同じ形式。Windsurf を再起動して反映。

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "superseo-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/inhouseseo/superseo-skills",
        "~/.claude/skills/superseo-skills"
      ]
    }
  ]
}

Continue はマップではなくサーバーオブジェクトの配列を使用。

~/.config/zed/settings.json

{
  "context_servers": {
    "superseo-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/inhouseseo/superseo-skills",
          "~/.claude/skills/superseo-skills"
        ]
      }
    }
  }
}

context_servers に追加。保存時に Zed がホットリロード。

claude mcp add superseo-skill -- git clone https://github.com/inhouseseo/superseo-skills ~/.claude/skills/superseo-skills

ワンライナー。claude mcp list で確認、claude mcp remove で削除。

ユースケース

実用的な使い方： superseo-skills

Audit a ranking page and ship the fixes in one session

👤 In-house SEOs and content leads ⏱ ~45 min intermediate

使うタイミング： A page used to rank, the traffic dropped, and you want a diagnosis with a concrete fix list.

前提条件

Install via marketplace — /plugin marketplace add inhouseseo/superseo-skills then /plugin install superseo@superseo-skills

フロー

Run page-audit

Run page-audit on https://example.com/blog/post. Include competitor comparison against the top 3 results.✓ コピーしました

→ Scored findings across 7 dimensions, specific fixes
Follow with semantic-gap-analysis

Now run semantic-gap-analysis vs the top 3 — what entities and subtopics am I missing?✓ コピーしました

→ Concrete list of missing coverage
Rewrite

Apply improve-content with the findings from the audit and gap analysis. Match the current brand voice.✓ コピーしました

→ New draft ready to replace the post

結果： A rewritten page that closes the gap to competitors.

注意点

Running write-content on a topic with weak search intent match — Run keyword-deep-dive first to confirm intent before writing

組み合わせ： firecrawl · brave-search

Plan a topic cluster around a seed keyword

👤 Content strategists ⏱ ~60 min intermediate

使うタイミング： You're starting a new content area and want a defensible hub-and-spoke plan.

フロー

Seed with topic-cluster-planning

Use topic-cluster-planning — seed topic: 'container orchestration'. Design a hub + 12 spokes with search volume estimates.✓ コピーしました

→ Tree with hub article + 12 supporting articles
Brief each spoke

Run content-brief for spoke #3. Audience: backend engineers.✓ コピーしました

→ Writer-ready brief with SERP gaps

結果： A content calendar with briefs you can hand to writers.

Win a featured snippet for a high-intent query

👤 SEO specialists targeting position 0 ⏱ ~15 min beginner

使うタイミング： You're ranking on page 1 but not in the snippet.

フロー

Run featured-snippet-optimizer

The query is 'what is retrieval-augmented generation'. My page ranks #4. Rewrite the answer block to win the snippet.✓ コピーしました

→ Tight answer paragraph + optional list/table format

結果： A rewrite ready to ship to the page.

Score a page's E-E-A-T and draft the fixes

👤 YMYL publishers, affiliate sites ⏱ ~30 min intermediate

使うタイミング： After a core update hit you and you suspect trust signals.

フロー

Run eeat-audit

Run eeat-audit on https://example.com/health/article — I want scores per dimension and concrete fixes.✓ コピーしました

→ Experience/Expertise/Authority/Trust scored with action items

結果： Actionable list of author-bio, citation, and edit-history changes.

組み合わせ

他のMCPと組み合わせて10倍の力を

superseo-skill + firecrawl

page-audit pulls live competitor content via Firecrawl for a real SERP gap diff

Use firecrawl to fetch the top 3 SERP results for my target query, then feed them to semantic-gap-analysis.✓ コピーしました

superseo-skill + brave-search

Get SERP data without paid API credits

Use brave-search to pull SERP for 'container orchestration', then topic-cluster-planning.✓ コピーしました

ツール

このMCPが提供する機能

ツール	入力	呼び出すタイミング
page-audit	url, competitor_urls?	Diagnose any single URL
content-brief	target keyword, audience	Before writing a new page
write-content	brief	After brief is approved
improve-content	existing url, issues	Updating an existing page
keyword-deep-dive	keyword	Single-keyword strategy
semantic-gap-analysis	your url, competitor urls	Gap vs top-3
eeat-audit	url	YMYL / trust work
topic-cluster-planning	seed topic	New content area
featured-snippet-optimizer	query, current url	Going after position 0
linkbuilding	domain profile	Off-page planning
expert-interview	topic, expert profile	Injecting first-party expertise

コストと制限

運用コスト

APIクォータ: None for the skill; any paired tools (Firecrawl, Brave) bring their own quotas
呼び出しあたりのトークン: 5–20k per skill invocation depending on size
金額: Free — skill is prompts + methodology
ヒント: Don't pair write-content with an expensive model unless you're shipping the output — use a cheaper model for drafts

セキュリティ

権限、シークレット、影響範囲

認証情報の保管： None — pure prompts

データ送信先： None from the skill itself

トラブルシューティング

よくあるエラーと対処法

page-audit returns generic advice

Supply the competitor URLs explicitly and the primary keyword — vagueness in, vagueness out

Marketplace install fails

Fall back to manual: clone the repo and copy skill folders into ~/.claude/skills/

確認： ls ~/.claude/skills/

代替案

superseo-skills 他との比較

代替案	代わりに使う場面	トレードオフ
ultimate-seo-geo	You also need AI search (GEO) coverage and schema automation	Bigger surface, more to learn

その他

リソース

📖 GitHub の公式 README を読む

🐙 オープンな issue を見る

🔍 400以上のMCPサーバーとSkillsを見る