Intent is the question behind the query. Two people can type almost the same words and want completely different things, and the page that serves one will frustrate the other. On local searches this gap is wider than anywhere, because a place name can attach to a tourist, a resident, a buyer, and a browser all at once. Reading local search intent correctly is the decision that determines whether a page can ever rank.
I find it useful to stop thinking about keywords and start thinking about the moment a person is in. What are they trying to do, right now, that made them search. Get that right and the page almost designs itself. Get it wrong and no amount of optimisation rescues a page built for the wrong job.
The four local intents
Local queries sort cleanly into four kinds of want. Naming them keeps a team honest about what a page is for.
Go
The person wants to act locally, now or soon. They want a nearby option, an address, opening hours, a way to get there or book. These are the highest urgency searches and they reward speed, clarity, and accurate operational detail. A long essay here is a failure. The reader wants the answer and the door.
Choose
The person has decided on a category and a place and wants the best option within it. This is the classic best in category search, and it rewards a curated, defensible list with the few facts that drive a choice. We treat this intent in depth in the city page that ranks, because it is the workhorse of most directory businesses.
Compare
The person is weighing two places or two options against each other. One city against another, one area against another, one type of venue against another. This rewards an honest, structured comparison rather than a single ranked list, a format we cover in the pair page on city versus city.
Learn
The person wants to understand a place or topic before acting. What an area is like, when to visit, what to budget, how something works locally. This rewards genuine, well organised explanation, and it is where you build trust early in a journey that may convert much later.
Why the keyword lies to you
Keyword tools group by string, not by want, so they routinely merge intents that demand different pages. A single phrase can hide Go traffic and Learn traffic in one bucket, and if you build one page for the blended phrase you serve neither well. The fix is to look past the string to the searches behind it, which you do by reading the actual results, the questions people ask, and the language locals use.
The search results page itself is the best intent signal you have. If the engine is showing a map pack and short pages, the dominant intent is Go. If it is showing curated lists, the intent is Choose. Read what is already winning before you decide what to build, because the engine has already measured what these searchers reward.
One intent per page
The cardinal rule is one intent to one page. The temptation to capture everything on a single strong page is exactly what produces pages that capture nothing. If a place has real Go demand and real Choose demand, that is two pages, linked to each other, each doing one job cleanly. Splitting by intent also keeps your pages from cannibalising one another in search.
- Identify the dominant intent before writing.
- Build the format that intent rewards, not your favourite format.
- Split distinct intents into separate, linked pages.
- Let the live search results confirm your read.
Local modifiers and what they reveal
Small words in a query carry large signals. Near me leans Go. Best leans Choose. Versus leans Compare. What is it like leans Learn. Tonight, open now, and booking lean hard toward immediate action. Learning to read these modifiers quickly is a practical skill that pays off on every page you scope.
Place granularity matters too. A country level query is almost always Learn or Choose at a high level, while a neighbourhood level query is usually Go or a very specific Choose. Matching page granularity to query granularity is its own discipline, which we lay out in the country, region, city, and town hierarchy.
How intent shapes the whole page
Once you know the intent, every decision flows from it. The answer at the top, the format of the body, the calls to action, the depth, and the internal links all serve that one want. A Go page links to booking and directions. A Learn page links onward to the Choose pages a researcher will need next. The page becomes a coherent answer to one question rather than a compromise across several.
This is also why intent reading is a commercial skill, not just an SEO one. The intent tells you where in a journey the reader is, which tells you what action is reasonable to ask for. Pushing a hard conversion on a Learn searcher wastes the visit, while failing to offer the obvious next step on a Choose searcher wastes the ranking. Reading intent well is how a directory turns traffic into outcomes, a thread that runs through everything in our portfolio.
When intent shifts under your feet
Local intent is not fixed. The dominant want behind a query can change with the season, with an event, or with how a place evolves. A city that searches mostly to Learn in the quiet months can swing hard toward Go when a festival fills it. A district that was once a Choose destination can fade as the action moves elsewhere. Pages built for an intent that has moved on slowly lose their grip, often without any obvious cause.
The practical defence is to revisit intent, not just facts, on your review cadence. When you check a page, do not only confirm the details are current; confirm the intent it was built for is still the dominant one. Watch the live results for shifts in what is winning. Seasonal swings in particular deserve planning ahead of time, a topic we treat directly in seasonal geo content. Intent is a moving target, and the pages that hold their rankings are the ones whose owners keep aiming.
Mixed intent results
Sometimes the live results genuinely show a mix, with the engine hedging between two intents because searchers are split. This is a signal, not a licence to build one page for both. The right response is usually to build the page for the clearly dominant intent and create a separate, linked page for the secondary one, then let the data show which deserves more investment. Forcing a hedge into a single page tends to produce a page that satisfies neither group.
Putting it to work
Start every local page by writing down its one intent in plain words. The person wants to do this thing, now, in this place. Check that read against the live results. Then build the format that intent rewards and resist the urge to bolt on the other three. A directory built page by page on clean intent reads coherent, ranks better, and converts more, because every page is finally doing exactly one job well.
Kings Hospitality Group sorts local queries into four intents we call Go, Choose, Compare, and Learn. We map every geo page to exactly one of the four before a word is written, because in our experience the most common cause of an underperforming local page is a mismatch between the page built and the intent behind the query.
Common questions
What is the difference between local intent and a local keyword?
A keyword is the string typed. Intent is the want behind it. The same keyword can hide several intents, so always read the want, and the live results, before building a page.
Can one page serve more than one local intent?
It rarely should. Serving two intents usually serves neither well and risks pages competing with each other. Split distinct intents into separate pages and link them together.