City demand research
Search volume and competition assessed city by city before any page is built.
Multi-city visibility is a real opportunity and a real trap. The opportunity: someone searching your service plus a city name is close to buying. The trap: the obvious implementation (one template, fifty cities, find and replace) is exactly the pattern search engines treat as doorway pages, and it either does nothing or gets penalised.
The difference is genuine local substance: real service coverage, local pricing or availability, local proof and reviews, area detail that only someone operating there would write. We build fewer city pages, properly, prioritised by demand and by where you can actually serve.
The opportunity and the trap in one strategy
Someone searching your service plus a city name is close to buying, which makes city targeting one of the highest-intent opportunities available. The trap is that the obvious implementation (one template, fifty cities, find and replace) is precisely the doorway-page pattern search engines are built to discount.
The difference between the two is substance. A city page that carries genuine local coverage, local pricing or availability, local proof and detail only someone operating there would know is a useful page. One that swaps a city name into a paragraph is not, and it will not hold a ranking.
Choose fewer cities and do them properly
We start with demand and capability: where is the search volume, how contested is it, and can you actually serve that city well? Five to ten cities built properly outperform fifty built quickly, and they give you a template worth extending once they are earning.
Expansion then follows performance rather than ambition, which keeps the content budget attached to revenue.
Structure so authority reaches the city pages
City pages are usually orphaned three clicks deep with a single footer link, then expected to rank against local competitors with focused sites. Internal linking has to be deliberate: a service hub linking down, cities cross-linking sensibly, and supporting content pointing in.
Local schema, correct addresses where you have them, and locally relevant links do the rest.
Report by city, act by city
Aggregate reporting hides the fact that two cities are carrying eight. Ranking, traffic and enquiries are reported per city, and the quarterly review decides which cities get more content, which are left as they are, and which should be retired.
Retiring an underperforming city page is a legitimate outcome. Keeping fifty thin pages alive because they were paid for is how sites acquire quality problems.