SKILL·B0FCE6

seo-keyword

rampstackco
更新于 5 days ago
2 次查看
910
126
910
在 GitHub 上查看
元wordaidesign

关于

This skill performs comprehensive keyword research by identifying search terms, classifying their intent, and clustering them into topical groups for content planning. It helps developers prioritize SEO opportunities when starting new sites, planning content calendars, or building topical strategies. The skill is stack-agnostic and works with any keyword data source.

快速安装

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 是一个 Claude Skill,作者为 rampstackco。Skill 将 Claude 按需加载的说明和资源打包,让 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 是一个 TypeScript 优先的构建工具,可将本地 Markdown/MDX 文件转换为类型安全的数据集合。它专为构建博客、文档站和内容密集型 Vite+React 应用而设计,提供基于 Zod 的自动模式验证。该工具涵盖从 Vite 插件配置、MDX 编译到生产环境部署的完整工作流。

查看技能
polymarket
元

这个Claude Skill为开发者提供完整的Polymarket预测市场开发支持,涵盖API调用、交易执行和市场数据分析。关键特性包括实时WebSocket数据流,可监控实时交易、订单和市场动态。开发者可用它构建预测市场应用、实施交易策略并集成实时市场预测功能。

查看技能
creating-opencode-plugins
元

该Skill帮助开发者创建OpenCode插件,用于接入命令、文件、LSP等25+种事件。它提供了插件结构、事件API规范和JavaScript/TypeScript实现模式,适合需要拦截操作、扩展功能或自定义事件处理的场景。开发者可通过它快速构建响应式模块来增强OpenCode AI助手的能力。

查看技能
sglang
元

SGLang是一个专为LLM设计的高性能推理框架,特别适用于需要结构化输出的场景。它通过RadixAttention前缀缓存技术,在处理JSON、正则表达式、工具调用等具有重复前缀的复杂工作流时,能实现极速生成。如果你正在构建智能体或多轮对话系统,并追求远超vLLM的推理性能,SGLang是理想选择。

查看技能