Expertise·Marketing, SEO & Social·v1.3.1

Keyword Research

When the user wants to research keywords, find target keywords, or analyze search intent.

You say
Buy it · $49 Read it before you buy $49 Written by kostja94 · unverified publisher
Context cost
2.7k tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 10.7 kBtext throughout, nothing executable
Licence
MITpaid listing
Last change
v1.3.1
Servers it uses
Noneruns standalone

What it does

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.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Expertise

Domain judgement the base model does not have.

seokeywordssearch-intentcontent-strategy

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md10.7 kB · 196 lines
--- name: keyword-research description: 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. metadata: version: 1.3.1 ---
8# SEO Content: Keyword Research
9
10Guides keyword research for SEO: finding target keywords, assessing difficulty, understanding search intent, and building topical maps. ~95% of keywords get fewer than 10 searches/month; low-volume, high-intent terms often yield faster rankings and conversion.
11
12**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
13
14## Initial Assessment
15
16**Check for project context first:** If .claude/project-context.md or .cursor/project-context.md exists, read it for product, audience, and positioning.
17
18Identify:
191. **Product/service**: What you offer
202. **Audience**: Who searches for it
213. **Goals**: Traffic, conversions, brand
224. **Tool access**: Google Keyword Planner, Google Trends, or SEO tools
23
24## Discovery Methods
25
26### Base Discovery
27
28| Method | Purpose |
29|--------|---------|
30| **User perspective** | What pain points? What would they search? Customer language from product context |
31| **Tool expansion** | Related keywords, questions, suggestions; Google autocomplete, PAA, Related Searches |
32| **Competitor reverse** | Analyze competitor titles, H1, URL; identify topics they rank for; find gaps (#4–10 = opportunity) — see **competitor-research** |
33| **Google PAA** | People Also Ask and Related Searches; high-value signals from real user behavior |
34| **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 |
35
36### Google Autocomplete (Long-Tail Discovery)
37
38Google 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.
39
40**Alphabet method** (seed + space + letter):
41- Type seed keyword + space + each letter: keyword a, keyword b, ... keyword z
42- Record relevant suggestions; repeat with numbers 0-9
43- Example: SEO a -> "SEO audit," "SEO agency"; SEO b -> "SEO basics," "SEO best practices"
44
45**Position variants** (seed in different positions):
46- **Prefix**: a keyword, b keyword (discover what users add before)
47- **Suffix**: keyword a, keyword b (most common; alphabet method)
48- **Middle**: how to keyword a, best keyword for (question + modifier combos)
49
50**Question modifiers**:
51- how to keyword, what is keyword, why keyword, when to keyword, keyword vs
52- keyword for beginners, keyword for small business, keyword without
53
54**Why 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).
55
56### Incremental Discovery
57
58- **User feedback**: Support, community, reviews, NPS—high-frequency questions = unmet search demand
59- **Multi-platform search**: Reddit, Quora, X (Twitter), Hacker News—real questions and discussions
60
61## Search Intent
62
63| Intent | Content type | Example |
64|--------|--------------|---------|
65| **Informational** | Blog, guide, FAQ | "how to optimize sitemap" |
66| **Navigational** | Brand page | "alignify login" |
67| **Commercial** | Comparison, review | "SEO tools comparison" |
68| **Transactional** | Product, pricing | "best SEO tool pricing" |
69
70### Intent Identification
71
72**Modifier words** (often signal intent):
73
74| Intent | Modifiers |
75|--------|-----------|
76| Informational | "how," "what," "why," "guide," "tutorial" |
77| Commercial | "best," "compare," "vs," "review," "top" |
78| Transactional | "buy," "price," "cheap," "coupon," "free shipping" |
79| Local | Location names |
80
81**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.
82
83## Long-Tail Expansion
84
85- **Google Autocomplete**: Alphabet method, position variants, question modifiers; see above. Primary source for long-tail.
86- **Intent modifiers**: Core + "how," "best," "vs," "compare," "price"
87- **Question words**: "how to," "what is," "why," "when"
88- **Functional modifiers**: Core + "-er/-or" (e.g., "image optimizer" for tool-type queries); often higher conversion
89- **Clustering**: Group by SERP overlap (same top pages), semantic similarity, or intent.
90
91## Keyword Clustering & Topical Map
92
93| Method | Use |
94|--------|-----|
95| **SERP overlap** | Keywords with overlapping top-ranking pages → same cluster |
96| **Semantic** | Group by meaning, LSI, related concepts |
97| **Intent-based** | Group by intent; separate pages if intent differs within cluster |
98
99**Pillar–cluster** (map keywords to structure):
100- **Pillar** (Hub): Broad topic page; links to clusters
101- **Cluster** (Spoke): Focused subtopic; links back to pillar
102- Target long-tail first; then pillar. Interlink clusters within topic.
103- See **content-strategy** for full pillar-cluster planning and implementation.
104
105## Evaluate & Screen
106
107| Factor | Consider |
108|--------|----------|
109| **Search volume** | Monthly searches; ~100+/month typical floor; niche can relax |
110| **Keyword difficulty (KD)** | New sites target lower KD |
111| **CPC** | Higher CPC often = stronger commercial intent |
112| **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** |
113| **Screening order** | 1) Remove irrelevant 2) Filter very low volume 3) Assess achievability 4) Prioritize commercial/transactional |
114
115## Product Positioning Test (SEO Fit)
116
117Test if positioning is clear enough for search:
118
119- **XXX + Function words**: Generator, Creator, Maker, Builder, Changer, Shortener, Scraper, Converter, Downloader, Translator, Extender, Summarizer, Resizer, Remover, Extractor, Recorder, Rewriter, Solver, Calculator; or Platform, Tool, Software, App, Provider, Assistant, Copilot
120- **Input + to + Output**: e.g., "image to video," "text to speech"—clear input/output signals intent
121
122**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.
123
124## Principles
125
126- **Core rule**: Someone must search it—validate with tools; avoid inventing terms
127- **Functional keywords**: Tool-type (-er/-or) often convert better; users are closer to action
128- **Multi-language**: Re-research in target language; don't translate existing lists. See **translation** for translation workflow.
129
130## SEO–PPC Keyword Synergy
131
132Keyword research serves both SEO and Google Ads. Align both channels to avoid duplication, cannibalization, and wasted spend.
133
134| Data flow | Use |
135|-----------|-----|
136| **keyword-research → google-ads** | Keyword list, clusters, intent; support terms (login, forum, pricing) → negative keywords for PPC |
137| **google-ads → keyword-research** | PPC conversion rate, Search Terms report → SEO priority; high-converting PPC terms = worth ranking organically |
138| **keyword-research → landing-page** | Clusters → dedicated LP per intent; PAA questions → FAQ sections |
139| **GSC organic rank 4+** | If you rank well organically, consider reducing/pausing PPC on those terms to avoid cannibalization |
140
141**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.
142
143**Reference**: [Backlinko – SEO and PPC: 8 Smart Ways to Align](https://backlinko.com/seo-and-ppc)
144
145## Data Sources
146
147| Source | Use |
148|--------|-----|
149| **Ahrefs** | Keywords Explorer, Site Explorer |
150| **SEMrush** | Keyword Overview, Organic Research |
151| **GSC** | Search queries, impressions, clicks |
152| **GA** | Traffic by landing page |
153| **PostHog** | Feature/search usage |
154
155## Report Workflow
156
1571. **Parse** — Read Excel/CSV, infer keyword, volume, KD, intent, etc. from headers
1582. **Enrich** — Web search, visit competitor/product pages; read project-context.md if present
1593. **Build** — Structure data for report
1604. **Generate** — Output report in chosen format
161
162## Output Format
163
164- **Keyword list** with volume, KD, intent
165- **Keyword mapping** to pages/content
166- **Content gaps** (competitors rank, you don't)
167- **Priority** ranking for implementation
168- **Topical map** (cluster → pillar → page mapping)
169
170### Report Structure Reference
171
172| Section | Content |
173|---------|---------|
174| Executive Summary | Priorities (top 3) |
175| Keyword Overview | Total keywords, primary intent, avg KD, content gaps count |
176| Keyword List | Keyword, volume, KD, intent, priority, target page |
177| Keyword Mapping | Page/URL, target keywords, status |
178| Content Gaps | Keywords competitors rank for that you don't |
179| Action Plan | Priority, action, impact, effort |
180| Appendix | Search intent reference (Informational, Commercial, Transactional, Navigational) |
181
182## Related Skills
183
184- **seo-strategy**: SEO workflow, Product-Led SEO, audit approach; keyword research is Content phase
185- **google-ads**: Keywords inform Search targeting; PPC data feeds back into SEO priority
186- **paid-ads-strategy**: When to use paid vs organic; channel selection
187- **content-strategy**: Keywords inform content plan; topic clusters
188- **content-optimization**: Keyword placement, density vs stuffing, H2 keywords
189- **title-tag, meta-description**: Keywords in title, description
190- **heading-structure**: Keywords in H1, H2
191- **link-building**: Keywords inform link targets
192- **serp-features**: SERP features in keyword screening; PAA, Featured Snippet
193- **featured-snippet**: Snippet-worthy query targeting
194- **competitor-research**: Competitor keyword/topic analysis; reverse engineering
195- **faq-page-generator**: PAA questions to FAQ sections; question-based keyword to FAQ content
196
In the file
SKILL.md1,500 words
Files1
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈120
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
2,555
on trigger
The instruction body, read only when the skill fires.
1.3%
of a 200k window
Ten skills this size would take about 13% of the window before you open a file.
050k100k150k200k context window

2.7k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 10.7 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md10.7 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$49 once
Keyword Research · MIT · kostja94
one-time
Price$49 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery release of 1.x through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Version1.3.1
Publishedno release date on file
Price$49
Referencekostja94/keyword-research

Versions

v1.3.1 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v1.3.1
  • No earlier releases have been published to the marketplace.
Pinning

Put kostja94/keyword-research@1.3.1 in the install command to hold this exact version. Without the suffix you get whatever is current the day you install, and nothing moves under you afterwards.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

KO
kostja94

Publishes on mcprush.

0 servers listed3 skills listednot claimed
Profile
Publisher
Servers0