Keyword research is demand research expressed through search language. Search volume can help size an opportunity, but it does not tell you whether the query fits your audience, whether the intent is clear, whether your site can answer it credibly, or whether a new page would add anything to existing results.
Decision snapshot
| Decision | Practical approach | Watch for |
|---|---|---|
| Begin with problems | List audience tasks, decisions, risks, and failure states before opening a tool. | Tool-first research tends to produce disconnected phrases. |
| Inspect intent manually | Read current results and note what users appear to expect. | Similar wording can hide informational, commercial, local, or navigational needs. |
| Map one primary page | Consolidate close variants that share an answer and outcome. | A separate page for every phrase creates duplication and internal competition. |
Define the audience and subject boundary
Write who the site serves, their knowledge level, situations, goals, constraints, and the subjects where the publisher has evidence or expertise.
Build seed topics from real language
Use sales and support questions, site search, community discussions, product workflows, regulations, competitor gaps, Search Console data, and stakeholder interviews.
Expand and classify
Collect modifiers for how, cost, versus, best, checklist, problem, location, tool, example, and stage. Classify intent, funnel stage, sensitivity, freshness need, and likely content type.
Evaluate the result page and fit
Review page formats, authority patterns, recentness, local or product features, unanswered subquestions, and whether your proposed page can provide stronger evidence or usability.
Create a prioritized topic map
Group terms by shared intent, select a hub and supporting pages, assign one canonical URL, define internal links, score value and feasibility, and record assumptions rather than inventing exact demand.
Action checklist
- Topic begins with a real audience task or decision
- Search intent and expected content format were manually reviewed
- Close variants are consolidated into one useful page
- Opportunity score includes business fit, expertise, difficulty, and reader value
- Sensitive claims have an evidence and review plan
- Page has a distinct role in a hub and natural internal-link destinations
Working worksheet
Record these fields in the same working document so the decision can be reviewed and handed off:
- Audience, situation, and problem
- Query family, modifiers, intent, and expected format
- Observed results and unmet reader need
- Proposed page, unique value, evidence, and hub
- Priority, confidence, owner, and review trigger
Common failure patterns
- Treating a third-party volume estimate as precise demand
- Choosing high-volume phrases outside the site purpose or expertise
- Publishing several pages that answer the same intent with slightly different wording
Connect this work
Research should inform structure without causing keyword stuffing. Read turn the topic map into a focused page.
A topic map becomes useful through navigation and context. Read design hub and supporting relationships.
Search Console can refine assumptions with actual visibility data. Read use first-party query evidence after publishing.