One page, one job — decided before the brief gets written.

Page intent analysis assigns each surviving URL exactly one primary intent — transactional, informational, comparison, or in-person — before semantic planning begins. A page built to serve two intents at once usually serves neither well, because the structure, language and calls to action each intent needs pull in different directions.

Four intent classes

Intent classes and the query modifiers that signal each one
IntentWhat the visitor wants to doTypical query modifiers
TransactionalBook, hire or request a quote nownear me, emergency, quote, book, cost
ComparisonDecide between two options before committingvs, best, compare, alternatives
InformationalUnderstand a problem or processhow, why, what is, guide
In-person / localConfirm a business can attend their specific location[service] [city], service area, coverage

Why one page can't carry two intents well

A transactional page needs a booking action above everything else. A comparison page needs symmetric treatment of every option under evaluation. Written together, the booking action competes for attention with the comparison table, and neither reader — the one ready to book, the one still deciding — gets what they came for quickly.

Intent gets assigned before the brief exists

Semantic content briefs inherit their structure from the intent decided here. Getting the intent wrong doesn't produce a bad brief — it produces a correct brief for the wrong kind of page, which is harder to catch during a content review than a structural mismatch at the planning stage.

See what a brief inherits from intent.

A worked comparison

An emergency plumbing page and a standard drain-service page share a business and a rough topic, but not an intent. The emergency page needs a phone number above the fold and almost nothing else competing for attention. The standard page can afford a fuller service description, pricing context and proof, because the visitor isn't deciding in the next ninety seconds.

Secondary intent, kept in its place

A transactional page can carry a small informational section — a short explanation that supports the booking decision — without becoming an informational page. The reverse doesn't hold as cleanly: an informational guide with heavy transactional language reads as thin sales copy dressed as an answer, which is exactly the pattern search engines and readers both discount.

Assign the right intent before a word gets written.

Four intent classes, one per page, decided ahead of the brief — not guessed at during a content review.

Build My Website Content