MCP HubMCP Hub
SKILL·B0FCE6

seo-keyword

rampstackco
更新日 23 days ago
4 閲覧
953
132
953
GitHubで表示
メタwordaidesign

について

このスキルは、検索用語の特定、意図の分類、コンテンツ計画のためのトピカルグループへのクラスタリングを通じて、包括的なキーワードリサーチを実行します。新規サイトの立ち上げ、コンテンツカレンダーの計画、トピカル戦略の構築時に、開発者が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-keyword

このコマンドをClaude Codeにコピー&ペーストしてスキルをインストールします

ドキュメント

Keyword Research

Find the queries worth ranking for, classify them by intent, cluster them into topics, and prioritize what to produce. Stack-agnostic. Tool-agnostic (works with any keyword tool).


When to use

  • Starting a new site or content section
  • Planning a content calendar
  • Looking for ranking opportunities on an existing site
  • Understanding search intent before writing
  • Building topic clusters for internal linking
  • Identifying content gaps vs competitors

When NOT to use

  • Optimizing a single page where the target query is already known (use seo-onpage)
  • Comparing your site to a competitor across many dimensions (use seo-competitor)
  • Auditing existing content for performance (use seo-content-audit)

Required inputs

  • The site or topic area
  • The target audience and what they need
  • A keyword tool (Ahrefs, Semrush, Moz, Google Keyword Planner, or similar) OR access to search console for an existing site
  • Optional: 3 to 5 known competitors to seed the research

If no tool is available, the skill still works using SERP inspection and search console data alone, but the volume estimates will be rough.


The framework: 4 stages

Stage 1: Discover

Cast a wide net. Sources:

  • Seed terms from the brief or the user's vocabulary
  • Competitor keywords (any keyword tool will export these)
  • Search console queries for an existing site (find the page-1 and page-2 queries)
  • Related searches and "People also ask" in actual SERPs
  • Customer language (support tickets, sales calls, reviews)
  • Forum and community language (Reddit, niche forums, Stack Overflow)

Goal: 200 to 500 candidate keywords for a typical content sprint. More if planning a year of content.

Stage 2: Classify by intent

Every keyword maps to one of four intents. Get this right or the rest is noise.

IntentSignalPage type that wins
Informational"how to," "what is," "why," "best way to"Article, guide, tutorial
Navigationalbrand or product name + modifierBrand homepage, product page
Commercial"best," "review," "vs," "comparison," "alternatives"Listicle, comparison, review
Transactional"buy," "price," "deal," "near me," "for sale"Product page, category page

A keyword tool's volume tells you the demand. The SERP tells you the intent. When in doubt, look at what's actually ranking. If page 1 is articles, the query is informational. If page 1 is product pages, it's transactional.

Hybrid intents exist. "Best running shoes" is commercial-investigational. "Best running shoes under $100" is the same intent narrowed by a budget filter. Treat hybrids as their dominant intent and note the modifier.

Stage 3: Cluster

Group keywords that should target the same page (or topic cluster).

Two clustering approaches:

Approach A: SERP overlap. If two keywords share at least 3 of the top 10 results, they target the same page. This is mechanical and reliable.

Approach B: Topical relevance. Group keywords by the underlying topic, not just word overlap. "How to start a podcast" and "podcast equipment for beginners" are the same topic, different facets.

Use both. A typical cluster has:

  • 1 primary keyword (highest volume, broadest intent)
  • 5 to 15 secondary keywords (variations and long-tails)
  • 1 page that targets them all

Stage 4: Prioritize

For each cluster, score on three dimensions:

Opportunity (1 to 5):

  • Volume (raw search demand)
  • Click potential (some queries answer themselves in the SERP, lowering CTR)
  • Conversion potential (does this query attract buyers or browsers?)

Difficulty (1 to 5):

  • Domain authority of top results
  • Backlink count of top results
  • Content depth and freshness of top results
  • Whether the SERP has features (featured snippets, AI overview, video carousel) that compete with organic

Strategic fit (1 to 5):

  • Does it serve our audience?
  • Does it support our positioning?
  • Does it link to commercial pages naturally?

Priority score = Opportunity + Strategic fit - Difficulty.

Rank the clusters. Top 20 percent get produced first.


Workflow

  1. Define the scope. What site, what topic area, what audience.
  2. Run discovery. Pull seeds, competitor exports, search console data, SERP inspections. Aim for 200 to 500 candidates.
  3. Deduplicate and clean. Remove obvious junk, brand misspellings, irrelevant terms.
  4. Classify by intent. Mark each keyword.
  5. Cluster. Group into topical clusters. Aim for 20 to 50 clusters.
  6. Score each cluster on opportunity, difficulty, and strategic fit.
  7. Prioritize. Rank by composite score. Identify the top 10 to 20 clusters to produce first.
  8. Output. Use the template in references/keyword-research-template.md.

Failure patterns

  • Chasing volume without intent. A 10,000-volume informational keyword does not drive purchases. Match query to commercial outcome.
  • Targeting impossibly competitive keywords. New sites cannot rank for "credit cards." Find the underserved long-tail variant.
  • Ignoring search console. Existing sites already rank for queries they did not target. These are the easiest wins.
  • Treating clusters as one-keyword-per-page. A page can target 10 to 30 related keywords. One-keyword-per-page leads to thin, cannibalized content.
  • Ignoring SERP features. A query with a featured snippet, AI overview, and a video carousel above the organic results may not be worth pursuing.
  • Static keyword research. Search demand shifts. Refresh the research at least annually for evergreen sites, quarterly for fast-moving topics.

Output format

Default output: a spreadsheet (CSV or sheet) with one row per keyword and one row per cluster, plus a markdown summary with the top 10 to 20 clusters detailed.

Recommended columns for the keyword sheet:

ColumnSource
KeywordDiscovery
VolumeTool
DifficultyTool
IntentManual classification
SERP featuresManual or tool
ClusterStage 3
Cluster role (primary/secondary)Stage 3
Opportunity scoreStage 4
Strategic fitStage 4
PriorityComposite
NotesFree text

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

よくある質問

seo-keyword Skillとは何ですか?

seo-keyword はrampstackco が作成した Claude Skillです。Skillは、Claudeが必要に応じて読み込む指示とリソースをまとめ、追加の指示なしで seo-keyword に関連するタスクを実行できるようにします。

seo-keyword をインストールするには?

このページのインストールコマンドを使用してください。seo-keyword をプラグインとして Claude Code に追加するか、リポジトリを skills ディレクトリにクローンし、Claudeを再起動してSkillを読み込みます。

seo-keyword はどのカテゴリに属しますか?

seo-keyword は メタ カテゴリに属します。

seo-keyword は無料で利用できますか?

はい。seo-keyword は AIMCP に掲載されており、無料でインストールできます。

関連スキル

content-collections
メタ

このスキルは、Content Collections(Markdown/MDXファイルを型安全なデータコレクションに変換するTypeScriptファーストのツール)の本番環境でテストされた設定を提供します。Zodバリデーションによる型安全性を実現し、ブログ、ドキュメントサイト、コンテンツ重視のVite + Reactアプリケーション構築時にご利用ください。Viteプラグインの設定、MDXコンパイルから、デプロイ最適化、スキーマバリデーションまで、すべてを網羅しています。

スキルを見る
polymarket
メタ

このスキルは、開発者がPolymarket予測市場プラットフォームを活用したアプリケーション構築を可能にします。API統合による取引や市場データの取得に加え、WebSocketを介したリアルタイムデータストリーミングにより、ライブ取引や市場活動を監視できます。取引戦略の実装や、ライブ市場更新を処理するツールの作成にご利用ください。

スキルを見る
creating-opencode-plugins
メタ

このスキルは、開発者がコマンド、ファイル、LSP操作など25種類以上のイベントタイプにフックするOpenCodeプラグインを作成することを支援します。JavaScript/TypeScriptモジュール向けに、プラグイン構造、イベントAPI仕様、および実装パターンを提供します。カスタムイベント駆動ロジックでOpenCode AIアシスタントのライフサイクルをインターセプト、監視、または拡張する必要がある場合にご利用ください。

スキルを見る
sglang
メタ

SGLangは、高性能なLLMサービングフレームワークであり、RadixAttentionプレフィックスキャッシュを活用したJSON、正規表現、エージェントワークフロー向けの高速で構造化された生成を特長とします。特にプレフィックスが繰り返されるタスクにおいて、大幅に高速な推論を実現し、複雑な構造化出力やマルチターン対話に最適です。制約付きデコードが必要な場合や、広範なプレフィックス共有を伴うアプリケーションを構築する場合は、vLLMなどの代替案ではなくSGLangを選択してください。

スキルを見る