Service-area SEO
Service-area SEO — how to rank when customers don't visit your premises.
Trades, decorators, plumbers, builders, roofers, landscapers, cleaners and restoration businesses have one base and many places they work. That's a genuinely different SEO problem to a shop with a single visible address — and it needs a different website structure to match.
The challenge
One base, many places you actually work.
You operate from one yard, workshop or home office, but the work happens across a spread of towns. A website built like a shop's — one address, one "we're here" story — doesn't reflect that, and a search engine can't work out where you're actually relevant to serve someone.
The wrong fix is generating a page for every town within reach, each one a copy of the last with the place name changed. It reads as padding because it is padding, and it tends to weaken the pages that actually deserve to rank.
The right fix is a website architecture that separates what you do from where you do it, and only builds a location page when there's something real behind it.
Website architecture
How a service-area site should be laid out.
Homepage
States clearly what you do and roughly how far you travel, in the first screen.
Service pages
One strong page per service, written for the person searching it — this is where most of your ranking potential lives.
Location pages
Built only where genuine demand, presence and proof justify a dedicated page — not one per town on the map.
Project pages
Completed jobs written up properly. They double as local proof and as content.
FAQs
Answering the practical questions people have before they'll ring a business that comes to them rather than the other way round.
For how services and locations should relate to each other, see service pages vs. location pages, and for what a location page should actually contain, see local landing pages.
When a location deserves its own page
Five things that need to be true.
- It's an area you genuinely, currently serve — not somewhere you'd technically drive to for the right job.
- There's distinct customer demand for that place, not just proximity to your base.
- You have enough real, specific information to say about it — not a paragraph with the town name swapped in.
- You have actual projects or experience there, ideally with photos and a proper write-up.
- There's a meaningful local reason it deserves its own page, rather than being covered adequately by a wider service-area statement.
When not to build one
Never just because the town exists.
A location page should never be created for reasons like these:
- The town exists and is roughly nearby.
- A competitor has a page for it.
- You want another URL to publish, regardless of whether it says anything new.
- It fills a gap in a spreadsheet of 'towns within 20 miles', not a gap in genuine coverage.
If none of the five criteria on this page are met, the honest answer is to fold that town into a broader "areas we cover" statement rather than manufacture a page for it.
Two related, different things
GBP service areas vs. website location pages.
Your Google Business Profile service areas tell Google roughly where you're willing to work — set inside the profile itself, invisible as a page anyone lands on. Website location pages are separate, visitor-facing pages that argue your case for a specific place with proof, not a settings field.
The two should agree with each other — don't list a GBP service area you have no website content or presence to support — but they're not the same job, and one doesn't substitute for the other.
Projects as local proof
A finished job is better evidence than a paragraph.
A written-up project does the work a location page tries to do, but with actual proof behind it — a real problem, a real approach, a real result.
More on trade-specific SEO: see SEO for trades, or the wider picture on local SEO.
Before you ask
Service-area SEO questions, answered plainly.
For the build order behind services and locations, see service pages vs. location pages.
Next step
Cover a wide patch but no premises to point to?
Let's build a site that argues it properly.
Tell us where you actually work and what proof you've got. We'll tell you honestly which areas deserve a page and which don't.