Install any skill in seconds. Free to start, no credit card required.
Get Started Free →When the user wants to research keywords, find target keywords, or analyze search intent. Also use when the user mentions "keyword research," "keyword tool," "target keywords," "search volume," "search intent," "keyword difficulty," "topical map," "keyword clustering," "People Also Ask," "Google autocomplete," "autocomplete keywords," or "alphabet method." For clusters, use content-strategy.
.claude/skills/mkurman-keyword-research/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-06 | ✗→✓ | ▲ Improved | 86% | 0% |
| case-08 | ✗→✓ | ▲ Improved | 67% | 0% |
| case-13 | ✗→✓ | ▲ Improved | 85% | 0% |
| case-17 | ✗→✓ | ▲ Improved | 95% | 0% |
| case-16 | ✓→✓ | = Same ✓ | 70% | 0% |
--|---------| | User perspective | What pain points? What would they search? Customer language from product context | | Tool expansion | Related keywords, questions, suggestions; Google autocomplete, PAA, Related Searches | | Competitor reverse | Analyze competitor titles, H1, URL; identify topics they rank for; find gaps (#4–10 = opportunity) — see competitor-research | | Google PAA | People Also Ask and Related Searches; high-value signals from real user behavior | | Extract from article | When auditing existing content: extract seed keywords from title, H1, H2s, meta keywords, first 100 words; then search "[primary keyword]" or "[primary keyword] related keywords" for opportunities; use "[primary keyword]" site:competitor.com if competitors known |
Google autocomplete reflects real user searches; suggestions only appear if queries have actual traffic. Free; often uncovers low-volume long-tail that keyword tools miss. ~70% of search traffic is long-tail; lower competition, higher conversion.
Alphabet method (seed + space + letter):
keyword a, keyword b, ... keyword zSEO a -> "SEO audit," "SEO agency"; SEO b -> "SEO basics," "SEO best practices"Position variants (seed in different positions):
a keyword, b keyword (discover what users add before)keyword a, keyword b (most common; alphabet method)how to keyword a, best keyword for (question + modifier combos)Question modifiers:
how to keyword, what is keyword, why keyword, when to keyword, keyword vskeyword for beginners, keyword for small business, keyword withoutWhy it works: Keyword tools filter low-volume terms; autocomplete only shows queries with real traffic. Use with PAA and Related Searches for full coverage. Categorize results by intent (informational, commercial, transactional).
| Intent | Content type | Example | |--------|--------------|---------| | Informational | Blog, guide, FAQ | "how to optimize sitemap" | | Navigational | Brand page | "alignify login" | | Commercial | Comparison, review | "SEO tools comparison" | | Transactional | Product, pricing | "best SEO tool pricing" |
Modifier words (often signal intent):
| Intent | Modifiers | |--------|-----------| | Informational | "how," "what," "why," "guide," "tutorial" | | Commercial | "best," "compare," "vs," "review," "top" | | Transactional | "buy," "price," "cheap," "coupon," "free shipping" | | Local | Location names |
SERP check: Search the term—knowledge cards/Wiki → informational; product lists/reviews → commercial; brand sites → navigational. Broader terms often show mixed SERP. See serp-features for feature types.
| Method | Use | |--------|-----| | SERP overlap | Keywords with overlapping top-ranking pages → same cluster | | Semantic | Group by meaning, LSI, related concepts | | Intent-based | Group by intent; separate pages if intent differs within cluster |
Pillar–cluster (map keywords to structure):
| Factor | Consider | |--------|----------| | Search volume | Monthly searches; ~100+/month typical floor; niche can relax | | Keyword difficulty (KD) | New sites target lower KD | | CPC | Higher CPC often = stronger commercial intent | | SERP features | Featured Snippet, PAA, zero-click; SERP features can satisfy intent without click—affects real traffic; see serp-features (Zero-Click section), featured-snippet | | Screening order | 1) Remove irrelevant 2) Filter very low volume 3) Assess achievability 4) Prioritize commercial/transactional |
Test if positioning is clear enough for search:
Agent/Copilot products: Pure native Agent hard to grow via SEO; users rarely search "agent." Release related features first (e.g., CRM, sales bot for sales agent) to build traffic, then funnel to Agent product.
Keyword research serves both SEO and Google Ads. Align both channels to avoid duplication, cannibalization, and wasted spend.
| Data flow | Use | |-----------|-----| | keyword-research → google-ads | Keyword list, clusters, intent; support terms (login, forum, pricing) → negative keywords for PPC | | google-ads → keyword-research | PPC conversion rate, Search Terms report → SEO priority; high-converting PPC terms = worth ranking organically | | keyword-research → landing-page | Clusters → dedicated LP per intent; PAA questions → FAQ sections | | GSC organic rank 4+ | If you rank well organically, consider reducing/pausing PPC on those terms to avoid cannibalization |
PPC data for SEO priority: SEO ROI ≈ (Organic clicks × PPC conversion rate × Customer value) − SEO cost. Use PPC conversion data to validate which keywords to pursue in organic.
Reference: Backlinko – SEO and PPC: 8 Smart Ways to Align
| Source | Use | |--------|-----| | Ahrefs | Keywords Explorer, Site Explorer | | SEMrush | Keyword Overview, Organic Research | | GSC | Search queries, impressions, clicks | | GA | Traffic by landing page | | PostHog | Feature/search usage |
project-context.md if present| Section | Content | |---------|---------| | Executive Summary | Priorities (top 3) | | Keyword Overview | Total keywords, primary intent, avg KD, content gaps count | | Keyword List | Keyword, volume, KD, intent, priority, target page | | Keyword Mapping | Page/URL, target keywords, status | | Content Gaps | Keywords competitors rank for that you don't | | Action Plan | Priority, action, impact, effort | | Appendix | Search intent reference (Informational, Commercial, Transactional, Navigational) |
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→fail | 36,490 | 27,494 | -25% | 1 | 1 | 0% | 6,232 | 7,062 | +13% | 0 | 0 | — |
case-16 | pass→pass | 14,098 | 8,800 | -38% | 1 | 1 | 0% | 2,096 | 3,558 | +70% | 0 | 0 | — |
case-02 | fail→fail | 23,151 | 25,762 | +11% | 1 | 1 | 0% | 3,830 | 6,420 | +68% | 0 | 0 | — |
case-03 | fail→fail | 21,657 | 21,601 | -0% | 1 | 1 | 0% | 3,611 | 5,591 | +55% | 0 | 0 | — |
case-04 | pass→pass | 14,907 | 10,940 | -27% | 1 | 1 | 0% | 2,442 | 4,183 | +71% | 0 | 0 | — |
case-05 | fail→fail | 18,415 | 22,145 | +20% | 1 | 1 | 0% | 2,772 | 4,690 | +69% | 0 | 0 | — |
case-06 | fail→pass | 14,483 | 12,170 | -16% | 1 | 1 | 0% | 2,140 | 3,984 | +86% | 0 | 0 | — |
case-07 | fail→fail | 14,657 | 14,089 | -4% | 1 | 1 | 0% | 2,277 | 4,413 | +94% | 0 | 0 | — |
case-08 | fail→pass | 13,798 | 10,570 | -23% | 1 | 1 | 0% | 2,442 | 4,074 | +67% | 0 | 0 | — |
case-09 | pass→pass | 13,210 | 15,273 | +16% | 1 | 1 | 0% | 1,894 | 4,495 | +137% | 0 | 0 | — |
case-10 | fail→fail | 15,112 | 15,378 | +2% | 1 | 1 | 0% | 2,337 | 4,687 | +101% | 0 | 0 | — |
case-11 | pass→pass | 15,695 | 15,439 | -2% | 1 | 1 | 0% | 2,613 | 4,869 | +86% | 0 | 0 | — |
case-12 | pass→pass | 12,508 | 11,395 | -9% | 1 | 1 | 0% | 1,901 | 3,824 | +101% | 0 | 0 | — |
case-13 | fail→pass | 12,514 | 8,717 | -30% | 1 | 1 | 0% | 1,883 | 3,489 | +85% | 0 | 0 | — |
case-14 | pass→pass | 11,190 | 7,538 | -33% | 1 | 1 | 0% | 1,681 | 3,389 | +102% | 0 | 0 | — |
case-15 | pass→pass | 11,990 | 13,532 | +13% | 1 | 1 | 0% | 1,868 | 4,390 | +135% | 0 | 0 | — |
case-17 | fail→pass | 19,394 | 21,839 | +13% | 1 | 1 | 0% | 2,743 | 5,347 | +95% | 0 | 0 | — |
case-18 | pass→pass | 13,123 | 14,840 | +13% | 1 | 1 | 0% | 2,138 | 4,747 | +122% | 0 | 0 | — |
case-19 | fail→fail | 16,216 | 10,307 | -36% | 1 | 1 | 0% | 2,486 | 3,914 | +57% | 0 | 0 | — |
case-20 | fail→fail | 2,512 | 5,368 | +114% | 1 | 1 | 0% | 416 | 3,088 | +642% | 0 | 0 | — |
case-21 | pass→pass | 14,348 | 10,319 | -28% | 1 | 1 | 0% | 2,269 | 3,720 | +64% | 0 | 0 | — |
case-22 | pass→pass | 30,847 | 26,232 | -15% | 1 | 1 | 0% | 5,264 | 6,773 | +29% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +18 percentage points is the difference between those two pass rates over the 22 comparable cases.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.