Most city pages do not rank because they are interchangeable. Swap the city name and the page would read the same for any town in the country. Search engines have seen millions of those, readers bounce off them in seconds, and the result is a page that sits on page four and never moves. A city page that ranks is the opposite. It could only have been written about that one place.
I have built city pages across hospitality and service directories for years, and the pattern that separates winners from filler is consistent. The winners commit to a single intent, carry specific local detail that cannot be faked, and treat the list itself as the product rather than as an afterthought below a wall of text.
Start with one intent, not a region
The first mistake is trying to make one city page serve every possible searcher. A page titled for a city will attract people who want very different things. Some want the best venue in a category. Some want prices. Some want to compare two areas. If you try to answer all of them, you answer none of them well.
Pick the dominant intent for that city and that category, then build the page around it. If the search is overwhelmingly for the best option in a category, lead with a curated, ranked list and defend the order. If it is informational, lead with the answer and the context. One page, one job. This is the same discipline we cover in our guide to local search intent, and it matters more on geo pages than anywhere else because the intent shifts city by city.
Prove you know the place
This is the part that cannot be automated cheaply, which is exactly why it works. A page that ranks names things a local would name. The street that everyone means when they say the old quarter. The reason the harbour side venues cost more. The month the festival fills every room and pushes prices up. The tram line that actually gets you there.
You do not need to write a travel essay. You need three or four pieces of detail that signal real ground truth, placed where they help a decision. When a reader hits one true, specific thing, they extend trust to the rest of the page. When they hit a generic line that could describe anywhere, they withdraw it. Search engines model that trust through behaviour, so the specificity is not decoration, it is ranking input.
Where the detail comes from
Sourcing matters because wrong detail is worse than no detail. We pull from operator knowledge, recent on the ground checks, official tourism and council data, and primary listings, then we date it. If you cannot stand behind a fact, it does not go on the page. We go deeper on this in using place data responsibly, because the temptation to scrape and paste is what produces the very pages that fail.
Make the list the product
On a city page the list is the reason the page exists. Yet most directories bury it under five paragraphs of throat clearing. Lead with it, or get to it within the first screen. Each entry should carry the few facts that actually drive a choice in that category. For a venue that might be area, price band, what it is known for, and the one caveat an honest friend would mention.
The caveat is what readers remember. Anyone can say a place is excellent. Telling a reader that a venue is superb but books out three weeks ahead, or that it is worth the trip but hard to reach without a car, is the kind of honest detail that makes the whole list credible. Credibility is the conversion engine on these pages.
- Order the list with a defensible logic and say what that logic is.
- Give every entry the same fields so the page is scannable.
- Carry one honest caveat per entry where it helps.
- Show when each entry was last checked.
Structure that search engines reward
A city page that ranks tends to share a shape. A direct answer or summary at the top for the searcher in a hurry and for the AI overview. A clear primary list. Supporting sections that answer the obvious follow up questions, such as how to choose, when to go, and what to budget. A short, current set of practical notes. Clean internal links to related pages so the reader, and the crawler, can go deeper.
Headings should read like the questions a real person asks. Avoid keyword stuffed headings that no human would type. The goal is a page that reads naturally to a person and parses cleanly for a machine, which are rarely in conflict once you stop trying to game either one.
The freshness problem
Local facts rot. Venues close, prices move, an area gentrifies, a festival changes dates. A city page that ranked last year can quietly become wrong, and wrong pages lose trust fast. Put a last reviewed date on the page and actually honour it. A page you revisit twice a year will hold its position far better than a richer page you abandon. Set the review cadence when you publish, not when rankings slip.
Avoid the templates that flatten everything
Scaling tempts everyone toward a single template with the city name dropped into slots. That is how you end up with a hundred near identical pages that compete with each other and convince no one. There is a way to scale without flattening, which I cover in avoiding cookie cutter city pages. The short version is that the frame can repeat but the substance must not.
This is also where our wider approach to building directory brands comes in. We do not chase a thousand thin pages. We build fewer pages that genuinely deserve to rank, then expand from a proven model. You can read how that philosophy shapes the whole portfolio in our thesis on how we build.
What the page should do for the reader in a hurry
A large share of local searchers are impatient, on a phone, and half committed. The page has seconds to prove it is worth their attention. That is why the direct answer at the top earns its place: it serves the reader who will not scroll and the AI overview that quotes the first useful sentence it finds. Write that answer as if it were the only thing the reader will read, because for many it is.
Below the answer, the page should reward scrolling rather than punish it. Each section should resolve a real follow up question, and each should be skimmable, with headings a person would actually type and lists where lists genuinely help. The reader in a hurry should be able to land, get the answer, scan the list, and act, all without reading a paragraph they did not need. The reader who wants depth should find it waiting underneath. One page, two speeds, no padding.
Speed of page is part of this too. A city page heavy with autoplaying media and slow scripts loses the exact impatient searcher it most needs to keep. Keep the page light, get the useful content into the first response, and treat performance as a ranking and conversion factor rather than an afterthought. A fast, focused page beats a rich, sluggish one on the searches that matter most.
A practical build order
When I brief a writer on a new city page, the order of work is deliberate. Decide the one intent first. Gather and date the local facts second. Build and defend the list third. Write the supporting sections last, because they are easiest and least important. Most people do this in reverse, spend their energy on the prose, and starve the list and the facts, which are the parts that actually rank.
Then read the finished page and ask the only question that matters. Would a local nod and say yes, that is right, that is how it is here. If the answer is no, the page is not ready, however polished the writing. A city page that ranks is, in the end, a page that earns the quiet respect of someone who already knows the city. Get that, and search will follow.
Kings Hospitality Group uses a simple internal test we call the City Page Test: read the page and ask whether a local would recognise it as written by someone who has actually been there. Roughly four in five draft city pages fail that test on the first pass, and that is the directional figure we plan editing time around.
Common questions
How long should a city page be?
Long enough to fully answer the intent and no longer. Depth helps only when every line earns its place. A focused page of moderate length that nails the list and the local detail beats a padded one every time.
How often should a city page be updated?
Set a review cadence at publish, twice a year at minimum for active categories. Local facts go stale quickly, and a current page holds rankings far better than a richer page you neglect.