정보
이 스킬은 검색어를 식별하고 의도를 분류하며 주제별 그룹으로 클러스터링하여 콘텐츠 기획을 위한 포괄적인 키워드 연구를 수행합니다. 신규 사이트 시작, 콘텐츠 캘린더 계획 또는 주제 전략 수립 시 개발자가 SEO 기회를 우선순위화할 수 있도록 지원합니다. 이 스킬은 스택에 종속되지 않으며 모든 키워드 데이터 소스와 호환됩니다.
빠른 설치
Claude Code
추천npx skills add rampstackco/claude-skills -a claude-code/plugin add https://github.com/rampstackco/claude-skillsgit clone https://github.com/rampstackco/claude-skills.git ~/.claude/skills/seo-keywordClaude 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.
| Intent | Signal | Page type that wins |
|---|---|---|
| Informational | "how to," "what is," "why," "best way to" | Article, guide, tutorial |
| Navigational | brand or product name + modifier | Brand 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
- Define the scope. What site, what topic area, what audience.
- Run discovery. Pull seeds, competitor exports, search console data, SERP inspections. Aim for 200 to 500 candidates.
- Deduplicate and clean. Remove obvious junk, brand misspellings, irrelevant terms.
- Classify by intent. Mark each keyword.
- Cluster. Group into topical clusters. Aim for 20 to 50 clusters.
- Score each cluster on opportunity, difficulty, and strategic fit.
- Prioritize. Rank by composite score. Identify the top 10 to 20 clusters to produce first.
- 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:
| Column | Source |
|---|---|
| Keyword | Discovery |
| Volume | Tool |
| Difficulty | Tool |
| Intent | Manual classification |
| SERP features | Manual or tool |
| Cluster | Stage 3 |
| Cluster role (primary/secondary) | Stage 3 |
| Opportunity score | Stage 4 |
| Strategic fit | Stage 4 |
| Priority | Composite |
| Notes | Free 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
references/keyword-research-template.md- Spreadsheet column definitions and a markdown summary template.references/intent-classification-guide.md- Detailed examples of each of the four intent categories.
GitHub 저장소
자주 묻는 질문
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)을 위한 프로덕션 검증된 설정을 제공합니다. 콘텐츠 콜렉션은 Markdown/MDX 파일을 Zod 검증이 포함된 타입 안전한 데이터 콜렉션으로 변환해주는 TypeScript 최우선 도구입니다. 블로그, 문서 사이트 또는 콘텐츠 중심의 Vite + React 애플리케이션을 구축할 때 타입 안전성과 자동 콘텐츠 검증을 보장하기 위해 사용하세요. Vite 플러그인 구성과 MDX 컴파일부터 배포 최적화 및 스키마 검증에 이르기까지 모든 것을 다룹니다.
이 스킬은 개발자들이 Polymarket 예측 시장 플랫폼을 활용한 애플리케이션을 구축할 수 있도록 지원하며, 거래 및 시장 데이터를 위한 API 통합 기능을 포함합니다. 또한 WebSocket을 통한 실시간 데이터 스트리밍을 제공하여 실시간 거래와 시장 활동을 모니터링할 수 있습니다. 이를 통해 거래 전략을 구현하거나 실시간 시장 업데이트를 처리하는 도구를 생성하는 데 활용할 수 있습니다.
이 스킬은 개발자들이 명령어, 파일, LSP 작업 등 25개 이상의 이벤트 유형에 연결되는 OpenCode 플러그인을 만들 수 있도록 돕습니다. JavaScript/TypeScript 모듈을 위한 플러그인 구조, 이벤트 API 명세, 구현 패턴을 제공합니다. OpenCode AI 어시스턴트의 라이프사이클을 사용자 정의 이벤트 기반 로직으로 가로채거나, 모니터링하거나, 확장해야 할 때 사용하세요.
SGLang은 RadixAttention 프리픽스 캐싱을 활용하여 JSON, 정규식, 에이전트 워크플로우를 위한 고속 구조화 생성에 특화된 고성능 LLM 서빙 프레임워크입니다. 특히 반복되는 프리픽스가 있는 작업에서 상당히 빠른 추론 속도를 제공하여 복잡한 구조화 출력 및 다중 턴 대화에 이상적입니다. 제약 디코딩이 필요하거나 광범위한 프리픽스 공유가 있는 애플리케이션을 구축할 때는 vLLM과 같은 대안보다 SGLang을 선택하십시오.
