SEO for new categories starts before people search the product name. Nobody types a term they do not know yet — so the job is to meet buyers where they already look: the problem, the alternatives, the workflow, the trigger. SEO cannot create that demand; it can help reveal and serve it.
Why new-category SEO is different
Classic SEO usually starts from a known category noun — “CRM,” “invoicing tool,” “email marketing” — with buyer intent already indexed against it. New-category SEO cannot start there. The category noun either does not exist in the buyer’s head yet, or it exists as a fuzzy shorthand for a workflow they solve today with something else. What is available instead:
- The buyer’s own words for the problem, gathered from real conversations.
- The alternatives they currently use — including spreadsheets, consultants, an existing category, or doing nothing.
- The workflow they are trying to complete.
- The comparison language they reach for when they are evaluating options.
- The trigger events that put the problem on their agenda in the first place.
- The frustrations that surface in support tickets and community threads.
- Jobs-to-be-done style framing: the outcome the buyer is trying to reach.
- The adjacent categories the buyer already knows how to search inside.
What SEO cannot do here is create demand where there is none. It can help a startup meet real demand more precisely, and it can help the market recognise a new category over time — but only in combination with real product substance, real positioning, and real customer conversations. April Dunford’s Obviously Awesome is a useful anchor for the positioning work that has to sit beneath the pages, and Geoffrey Moore’s Crossing the Chasm remains the entry-level reference for why direct product-name search rarely exists in the early market.
What people search before they know your product name
Practical query classes that come from listening rather than from a keyword tool. Read them as evidence patterns to explore, not as guaranteed traffic sources:
- Problem queries — the pain the buyer would type when it is fresh.
- “How to” queries — the workflow they are trying to complete.
- Alternative / tool queries — the names of tools they already know, often used to look for something better.
- Comparison queries — “X vs Y” or “alternatives to X,” where the honest answer sometimes includes the buyer’s own spreadsheet.
- Workflow queries — the step-by-step language people use when the problem is procedural.
- Symptom / friction queries — the way buyers describe what is going wrong before they know the cause.
- “Best way to” queries — decision-shaped searches with a strong implicit standard.
- Integration / use-case queries — the way buyers explore fit with the tools they already run.
- Category-adjacent queries — searches inside a familiar category that the new category partially replaces.
The new-category SEO framework
This is an author’s editorial framework — not an external standard. Eight elements, in the order I sequence them with founders before any page is written.
- Problem language — the specific pain, in the buyer’s own words.
- Alternatives — what the buyer would use today; named honestly.
- Use cases — the narrow, real situations the product is genuinely best for.
- Buyer triggers — the events that make the problem visible today.
- Category education — the careful introduction of the new frame, connected to what the buyer already knows.
- Comparison logic — how the alternatives fall short in the specific situations the product answers.
- Proof — the specific evidence a sceptical buyer would accept.
- Measurement — what will be read as directional signal, and what will be refused as vanity.
The table below is the one I use to sort the demand layers so the team can decide which page type earns its place first.
| Demand layer | What the buyer searches | Page type | Evidence needed | What to avoid |
|---|---|---|---|---|
| Problem | The pain in their own words | Problem-led page | Recurring language from discovery calls; observed frustrations | Naming the product too early; abstract pain descriptions |
| Alternative / competitor | The tool they already know; “X vs Y” | Honest comparison page | Buyer-verified criteria; recent competitor docs; win/loss patterns | Adjective bingo; pretending to be best for every buyer |
| Workflow / how-to | The step-by-step language of the job | Use-case / how-to page | Real workflows from customer conversations; screenshots | Doorway pages; identical templates with only the noun swapped |
| Category education | Category-adjacent language; concept explainers | Category education page | Careful definition; connection to known concepts; honest limits | Inventing jargon buyers will never type |
| Trigger / symptom | What is going wrong right now | Diagnostic or symptom page | Support-inbox patterns; sales-call opening lines | Fake urgency; symptom-shopping without a real answer |
| Direct name | The product name — once it exists | Product page | Named benefits, honest use cases, real proof | Treating this as the starting point in the early market |
Problem-led pages
Problem-led pages start where the buyer already is: with a specific pain, in language they use. The page names the situation, describes the current workaround honestly, and explains — qualitatively — the friction the workaround produces. The new approach is introduced only after the problem is fully in view. Practical shape:
- Open with the buyer’s exact phrasing of the pain, not the team’s internal shorthand.
- Describe the workaround they use today — spreadsheet, consultant, another tool, doing nothing — with fair characterisation, not caricature.
- Explain the friction qualitatively; do not invent time-saved or cost numbers. A qualitative honest description is more credible than a fabricated statistic.
- Introduce the new approach when the problem is legible — the connection is more persuasive than a leading hook.
- End with a calibrated next step: an explainer, a comparison, a demo, or a short call — matched to the buyer’s readiness.
Alternative and comparison pages
Comparison pages are one of the highest-leverage assets in new-category SEO because they meet buyers in exactly the shape they already think in. They also fail most often because teams are dishonest with them. The rules I press for:
- Name the real alternatives, including the honest ones — a spreadsheet, a consultant, a legacy tool, a manual workflow, and doing nothing.
- Use buyer-verified criteria — the axes the buyer cares about, not the axes the product happens to win.
- Be specific about when the alternative is still a better fit. A comparison page that admits when the answer is not the startup’s product earns more trust than one that pretends otherwise.
- Refuse fake competitor claims — outdated capability lists and imagined weaknesses age badly and undermine the entity as a whole.
- Date the page and set an editorial rhythm; comparison pages that stop updating stop being useful.
Category education pages
Category education is delicate. Done well, it introduces a useful frame the buyer can adopt. Done badly, it invents jargon nobody will type into a search bar. The discipline:
- Define the concept carefully, in plain language, before naming it.
- Connect it to concepts the buyer already understands — a new lens on a familiar problem is more useful than an abstract term standing alone.
- Show the situations in which the category is useful and the situations in which it is not. A category that fits everywhere is usually not a category at all.
- Build glossary or supporting pages only when they add real value — not to game topical coverage.
- Refuse to invent jargon. The tell is easy: if the category name reads like it was pieced together from three thought-leadership pieces, buyers will not adopt it.
The category-design decision that sits underneath these pages — whether to borrow, narrow, or create a category — is a strategic choice covered in its own article. New-category SEO is the surface work that follows that decision; the strategic choice comes first.
Use-case + ICP pages, measurement, and expansion
Use-case and ICP pages should be one page per real use case or ICP — not doorway pages generated from a template with the industry name swapped. Each page has to add unique context: the specific trigger, the workflow, the objections that come up for this buyer, the proof that will land, and a next step. A useful test is that a page cannot exist unless the team can name at least three buyers who fit it or three real conversations that produced it. The programmatic-SEO risks that appear when this discipline slips are covered in their own article and worth reading before scaling any template pattern.
Measurement in this environment has to stay honest. Google’s Search Console performance report help is the authoritative reference for what impressions and queries represent — read the docs before turning any single metric into a story. What is worth reading in the early stage:
- Query language in Search Console, when the search-side signal starts to appear — the buyer’s phrasing back to the team is the sharpest cheap signal available.
- Impressions as directional discovery, not proof of demand — buyers seeing the page is different from buyers wanting the product.
- Clicks as a weak signal unless paired with lead quality — high CTR to nowhere useful is not a win.
- Sales-call and demo questions — the first three questions in a demo tell the team whether the pages are landing.
- Objections that stop appearing — the strongest sign a page is doing its job.
- Branded vs. non-branded query changes over months — a slow but honest brand-side signal.
- Assisted sales conversations — how often reps quote a page or a framework back.
- Internal-site search when available — a direct window into the vocabulary buyers arrive with.
- Qualitative lead quality — the paragraphs prospects write are more informative than the count of submissions.
Google’s Search Essentials remains the entry-level checklist for eligibility — the technical baseline any of these pages must clear to be indexable at all. Expansion into a wider SEO cluster is a decision, not a schedule. The signals that suggest the moment is right: buyer language and objections have repeated for weeks, the ICP is clearer than a quarter ago, category explanation stabilises across pages, use cases are real, proof inventory has improved, the internal-linking path is coherent, and page quality can be maintained at the new cadence without cutting corners.
Common mistakes worth naming plainly: starting with product-name keywords nobody uses; inventing category jargon; chasing zero-volume keywords without buyer evidence; publishing glossary pages with no original value; treating impressions as demand; producing doorway pages; using AI to draft category definitions with no underlying insight; overbuilding a full cluster before any single page has taught the team something; and hiding the product until the page becomes abstract. If you want a calm audit of whether buyers already search the problem, alternatives, use cases and language your startup can credibly own, that is what my marketing audit and consulting engagement covers. Longer write-ups on positioning, SEO, and content strategy live in Insights, and the AI Lab contains practical templates worth using once the pattern is stable.
Frequently Asked Questions
Can SEO create demand for a new category on its own?
No. SEO can reveal, organise, and serve existing demand — problems, alternatives, workflows, triggers — and it can help a market gradually adopt a new frame when the product substance justifies it. It cannot invent buyers who do not exist. If the problem is not real, no cluster of pages rescues it.
Should we chase zero-volume keywords?
Only when there is genuine buyer evidence behind them — recurring language in discovery calls, support tickets, or community threads. A zero-volume keyword with real buyers behind it can become the page a small right-audience finds; a zero-volume keyword with no buyer evidence is a word the team invented, and it will earn nothing.
Is a comparison page against a bigger competitor a good idea?
Yes, if it is honest. Buyers already compare; the question is whether the team is willing to describe the comparison fairly and to name the situations where the bigger competitor is still a better fit. An honest comparison earns more trust than a slanted one — and it is more durable to updates.
How do we tell if a category education page is working?
By the language buyers use back to the team, the sharpness of the objections that arrive in sales calls, and the vocabulary that shows up in Search Console once the page has been indexed for a while. Treat these as directional, not as proof. A single “our category” article does not settle the category question.
When should we build the full SEO cluster?
When buyer language and objections have repeated for several weeks, the ICP has narrowed, category explanation is stable across pages, use cases are real, proof inventory has improved, and the team can maintain quality at the new cadence. Expanding earlier tends to lock in language the team has not earned yet.