In Britain the unit of local search is the town, not the county
Britain packs a great many named towns and boroughs into a small area, and people search using the name of theirs. A business covering several of them is not competing in one local market but in a handful of adjacent ones, and needs a structure that reflects that rather than a page listing place names.
Ask somebody in Greater Manchester where they live and they will not say Greater Manchester. They will say Stockport, or Sale, or Chorlton. That is also how they search. The county and the region are administrative units, while the town and the borough are identities, and the difference matters because a business covering a dozen of them has a dozen small markets rather than one large one.
The usual answer to covering several towns is a paragraph with place names in it, or a set of near-identical pages where only the town name changes. The first does not read as being about anywhere. The second reads as exactly what it is, and search engines lost patience with it long ago. Meanwhile the business genuinely does work differently in different places: different travel time, different response window, different typical jobs, different competitors. None of that is written anywhere on the site. The information that would make a real page sits in the diary, and nobody has been asked for it.
When this work makes sense
Questions worth asking any supplier
Ask what would go on a town page besides the town's name, because if the answer is nothing, the page should not exist.
Ask how the coverage area was decided, because a radius drawn on a map and the places you would genuinely drive to on a wet Tuesday are different things.
Ask whether the plan separates towns you serve well from towns you merely reach, because spreading effort evenly across both is how the strong ones stay average.
Ask what happens to pages for towns that never produce enquiries, because a plan without a removal step simply accumulates dead weight.
Ask whether anyone has looked at where existing customers actually are, because that postcode data sits in the invoicing system and beats any assumption about catchment.
Deliverables
A catchment map built from where your existing customers actually are, rather than from a radius
A decision on which towns justify a page of their own and which are better served by honesty about travel
Town pages containing what genuinely differs: travel time, typical jobs, parking, response window, local references
Postcode-level structure where the trade warrants it, because some catchments split inside a town
A service-area statement for businesses without premises, legible to a reader rather than only to a crawler
Internal linking that follows how the areas actually relate geographically, not a flat list in the footer
A removal plan for pages that never produce enquiries, reviewed rather than left to pile up
Built with
Process
We start in your invoicing system rather than in a keyword tool. Exporting customer postcodes and plotting them usually reveals a catchment quite unlike the one described on the website: dense in two or three towns, thin across several that are listed as covered, and extending further in one direction than anyone claimed because of a particular road. That map decides which towns get real pages, which get a sentence, and which should come off the site entirely.
The standard nine stages, discovery, strategy, UX/UI, development, content and SEO, testing, launch, measurement and continuous improvement, apply to every project. The paragraph above is what differs for this one.
What moves the number
Pricing depends on scope, functionality, integrations and content requirements. These are the factors that change it most:
Three ways to cover several towns
One page listing every town you cover
Fits: Businesses whose service genuinely does not vary by area and who would rather invest elsewhere
Limits: Reads as a list to a person and competes for nothing in particular, so do not expect it to win a town
A real page for each town that earns one
Fits: Trades where travel, response time or typical jobs actually differ between places
Limits: Only works where something true can be said about each place, and needs input from whoever does the work
One strong page for the town you are based in
Fits: Newer or smaller businesses whose effort is better spent being unambiguously the answer in one place
Limits: Cedes the surrounding towns for now, which is uncomfortable if a competitor is already established there
Case studies
Nothing has been published. There is no case study for this work yet, and we will not describe local results we cannot evidence. Our London office is at 37th Floor, 1 Canada Square, Canary Wharf, London E14 5AA, and enquiries reach us at uk@mbgdesk.com. Client work will be published when we have permission to name the business.
MBGDesk operates from 4 offices in India, United States, United Kingdom, United Arab Emirates. We hold no industry certifications and do not imply otherwise.
Frequently asked questions
Should we build a page for every town we cover?
No. Build one for every town where you can say something true that you could not say about the next town along: how long you take to get there, what jobs you mostly do, where you park, who you have worked for nearby. If the only distinguishing feature is the name, skip it.
We cover half a county. What should we do?
Stop describing it as the county. Nobody searches for a county when they want a plumber; they search for their town. Work out which towns within that area actually produce work, give those the attention, and describe the rest honestly as a wider travel area.
We have no premises. Can we still do this?
Yes, and a great many British trades are in that position. The site has to state the service area clearly and consistently, and the content has to be specific to places inside it. The profile side, hiding the address, defining coverage, verification, sits on our Google Business Profile page.
How specific should we get: town, borough or postcode?
As specific as your work genuinely varies. For most trades the town is the right unit. For anything where a river, a congestion charge, a parking regime or a single road changes the job, the split is inside the town and postcode sectors are the honest unit. Ask whoever does the driving.
Did town pages stop working?
The trick stopped working; the pages did not. What stopped working was generating the same page repeatedly with a substituted place name. A page describing genuinely different circumstances in a genuinely different place is simply a useful page. The test is whether somebody who lives there would recognise the description.
Which towns should we start with?
The ones where you already have customers, not the ones with the most searches. Presence compounds: existing work nearby gives you something true to write, people to ask for a review, and a plausible claim to being local. Starting where you have never worked means competing from nothing.
How is this different from our UK search work?
Our UK search page handles the wider organic argument for this market, including how town names are targeted in ordinary results. This page is about coverage: how a business working across several adjacent places should be structured, and how far down to go before the detail stops being useful.
Services that connect to this
Talk to us about this
Tell us what you are trying to build and we will come back with scope, approach and an estimate.