Intent taxonomy

How should a business map the questions people ask before they act?

Direct answer

An intent taxonomy maps real customer questions to the pages, ads, evidence and actions that should answer them, organized by what the asker is trying to do: research, compare, clarify, validate, or act. Product category is the wrong axis. It is a working map, not a branded framework: categories should be useful and changeable.

Last reviewed 2026-07-14Published 2026-07-14

The stages: research, compare, clarify, validate, act

The same words carry different jobs at different moments. Someone researching wants the landscape explained. Someone comparing wants honest fit criteria. Someone clarifying wants the process demystified. Someone validating wants proof it works for people like them. Someone acting wants the shortest path to a call, a booking, a quote. A usable taxonomy reads the stage as well as the topic, because the right answer differs by stage even when the topic is identical.

These five categories are working labels, not a branded framework. When a business’s questions split differently, the taxonomy should change.

Query fan-out

Answer systems expand one question into many. “Best CRM for a small law firm” fans out into pricing, migration, integrations, and reviews sub-queries before an answer is composed. Mapping question families is what keeps the taxonomy stable under fan-out: the family persists while phrasings multiply.

Topic versus intent

Topic buckets group content by what the business sells. Intent stages group it by what the asker is doing. The difference is operational: a topic map produces one page per service and stretches it across every stage; an intent map produces the pricing explanation, the comparison, the process page and the action page as distinct surfaces, each answerable, each measurable.

Mapping intent to pages, ads, proof and conversions

Each question family in the taxonomy carries four assignments: the page that answers it, the ad language that may address it, the proof it requires, and the conversion event that honestly reflects its stage. Research questions do not get contact-form conversions; they get answered, and the return visit gets measured. Action questions get the shortest credible path to the tracked call or form.

Example intent taxonomy mapping question families to stage, answer, proof and conversion
Question family	Stage	Answers with	Proof required	Conversion
Cost and pricing	research	Pricing-explanation page with real ranges	Transparent range or method	None at this stage
Comparison	compare	Honest comparison with fit criteria	Third-party references	None at this stage
Process clarification	clarify	Step-by-step process explanation	Practitioner credentials	Soft inquiry
Worthiness validation	validate	Evidence page: cases and outcomes	Attributed case evidence	None at this stage
Ready to act	act	Action page: schedule or call	Minimal; trust already formed	Tracked call or form

Download the full example taxonomy (CSV)

Failure patterns

Topic buckets where intent stages belong

Content maps to product categories while the customer's actual stage goes unread

Everything mapped to action intent

Research questions get sales pages; the visitor leaves and the remarketing budget chases them

The taxonomy as deliverable

A one-time spreadsheet nobody maintains, while pages and ads go on without a living map

Claims on this page

InterpretationModerate confidenceChecked 2026-07-14
Paid search and organic surface decisions increasingly draw on the same inputs: interpreted intent, page relevance and structured evidence.
Ad Rank has long used landing-page experience; answer surfaces now interpret the same pages for organic inclusion. Managing paid and organic separately duplicates the intent and evidence map both need.
Google Ads Help

Inspectstructure, entities, claims, sources, dates

Direct answer

An intent taxonomy maps real customer questions to the pages, ads, evidence and actions that should answer them, organized by what the asker is trying to do.

Page purpose

Define the method and provide a working example taxonomy with a downloadable artifact.

Entities

Digital Traction
Intent taxonomy
Query fan-out

Defined terms

Intent taxonomy
Query fan-out
Research intent
Validation intent

Relationships

Defines: the intent stages used across this site
Feeds: Relevance, Paid distribution, Content systems
Applied by: Hyphen, Local Traction

Dates and status

Published: 2026-07-14
Last material update: 2026-07-14
Last reviewed: 2026-07-14
Status: published

Available actions

Download the example taxonomy (CSV)
Discuss a search system (/engage)

Structured data

TechArticle · BreadcrumbList · Dataset

Change log

Claims

Interpretation · Moderate confidence · checked 2026-07-14
Paid search and organic surface decisions increasingly draw on the same inputs: interpreted intent, page relevance and structured evidence.

Structured-data preview

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://www.digitaltraction.co/#organization",
      "name": "Digital Traction",
      "legalName": "Digital Traction LLC",
      "url": "https://www.digitaltraction.co",
      "logo": "https://www.digitaltraction.co/brand/digital-traction-mark.svg",
      "description": "Digital Traction is an independent search-systems practice. It studies and builds how businesses are understood, surfaced, advertised and measured across paid search, organic discovery and emerging AI interfaces.",
      "founder": {
        "@id": "https://www.digitaltraction.co/about#person-sal-ferrara-loris"
      }
    },
    {
      "@type": "Person",
      "@id": "https://www.digitaltraction.co/about#person-sal-ferrara-loris",
      "name": "Sal Ferrara-Loris",
      "jobTitle": "Operator, Digital Traction",
      "description": "Sal Ferrara-Loris operates Digital Traction, an independent search-systems practice covering paid search, relevance architecture, measurement and answer-engine visibility.",
      "knowsAbout": [
        "Paid search",
        "Intent taxonomy",
        "Conversion measurement",
        "Offline conversion imports",
        "Answer-engine visibility",
        "Agent-ready websites"
      ],
      "worksFor": {
        "@id": "https://www.digitaltraction.co/#organization"
      }
    },
    {
      "@type": "BreadcrumbList",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Digital Traction",
          "item": "https://www.digitaltraction.co/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Systems",
          "item": "https://www.digitaltraction.co/systems"
        },
        {
          "@type": "ListItem",
          "position": 3,
          "name": "Intent taxonomy",
          "item": "https://www.digitaltraction.co/systems/intent-taxonomy"
        }
      ]
    },
    {
      "@type": "TechArticle",
      "@id": "https://www.digitaltraction.co/systems/intent-taxonomy#webpage",
      "mainEntityOfPage": "https://www.digitaltraction.co/systems/intent-taxonomy",
      "headline": "Intent taxonomy: mapping the questions people ask before they act",
      "description": "How to build an intent taxonomy: research, comparison, clarification, validation and action intent, query fan-out, and mapping question families to pages, ads, proof and conversions. Includes a downloadable example.",
      "datePublished": "2026-07-14",
      "dateModified": "2026-07-14",
      "author": {
        "@id": "https://www.digitaltraction.co/about#person-sal-ferrara-loris"
      },
      "publisher": {
        "@id": "https://www.digitaltraction.co/#organization"
      }
    }
  ]
}