Search intent is the purpose behind a search: what someone wants to understand, find, compare, or do. Two queries can mention the same product while needing very different answers.
For example, “what is a standing desk?” asks for an introduction. “How to assemble this standing desk” calls for instructions for the relevant model. Repeating “standing desk” throughout a general essay won’t turn it into an assembly guide.
This article explains page planning, rather than recommending a product or providing assembly instructions. Use it alongside our beginner keyword research workflow.
One topic, several different tasks
| Query | Likely task | Useful content |
|---|---|---|
| What is a standing desk? | Understand the category | A definition, examples, and limitations |
| Manual vs. electric standing desk | Compare options | Differences under clear conditions |
| How to assemble a standing desk | Complete a task | Model-appropriate steps and checks |
| Buy a compact adjustable desk | Find a suitable purchase | Relevant products and buying conditions |
| A particular brand’s support site | Find a specific destination | A trustworthy official entry point |
These are hypotheses about intent, not certainty about every person using those words. Short queries often leave room for several interpretations.
Google’s explanation of ranking results discusses understanding query meaning and context. You don’t submit an “intent label” to Google and receive a ranking in return.
Four labels that help organize your thinking
Content planners often use informational, navigational, commercial investigation, and transactional as shorthand.
Informational queries seek understanding or instructions. Navigational queries seek a particular destination. Commercial investigation involves comparing possibilities. Transactional queries focus on taking an action such as purchasing or booking.
Treat these as practical planning categories, rather than a published Google scoring formula. A query can combine tasks: “desk showroom near me” may involve browsing options and locating a store.
The more useful question is: what should someone be able to do after landing on this page?
How to investigate intent
Read the modifiers
Words such as “how,” “why,” “vs.,” “buy,” “manual,” and “support” provide clues. Constraints such as a model number or available space tell you which details might matter.
“Desk assembly” and “replacement screws for model X” don’t necessarily need the same evidence. Notice the difference before deciding how to answer.
Inspect current result types
Look at a selection of results. Are they how-to guides, category pages, comparisons, official documents, or discussions? Read enough to understand the task they serve.
Don’t copy the top page’s outline as a substitute for judgment. Results vary by location and time. Record the context of your observation, and keep looking for a useful contribution you can make.
Write a reader outcome
For a comparison, an outcome might be: “The reader can identify the dimensions and features they need to verify before choosing.” For a tutorial: “The reader can complete one defined task and recognize when it is finished.”
If the outcome includes unrelated jobs, narrow the page or separate the tasks.
Let the task determine the structure
An explanation can open with a definition and develop examples. A procedure needs prerequisites, ordered steps, and completion checks. A comparison needs clearly defined alternatives and criteria. A page helping someone find an official service should make the destination easy to identify.
These are editorial decisions. No heading pattern guarantees rankings.
Consider an article titled “How to Choose a Desk for a Small Room” that spends most of its length on furniture history. The problem isn’t simply a lack of keyword mentions. It hasn’t supplied the information needed to make a choice.
A better outline could identify the available space, list measurements to confirm, compare candidates under those constraints, and flag details still missing. Without actual testing, it should avoid claiming tested product performance.
Should related queries share a page?
Different wording for the same task often belongs together. A genuinely different task may justify a separate page with a useful link between them.
After publication, compare real queries with the pages receiving visibility. Do readers appear to be looking for an answer your page doesn’t provide? Does the title create the wrong expectation?
If the page hasn’t been indexed, investigate that first using our Google indexing checklist. Intent helps you choose the answer; technical accessibility helps make the answer discoverable. Neither replaces the other.