Service page vs location page: which do you need?
Two page types do the heavy lifting on every local services site, and most underperforming sites have confused one for the other. The definitions take a minute; the architecture follows from them.
The definitions
A service page sells one service everywhere you offer it: what the work involves, what affects the price, proof you do it well. A location page (or service-area page) sells one service in one place: the same offer, anchored by evidence that you genuinely work there. The service page answers “boiler installation”; the location page answers “boiler installation in Lewes”.
| Service page (the hub) | Location / service-area page (a spoke) | |
|---|---|---|
| What it sells | One service, everywhere you offer it | One service, in one place |
| The query it answers | “boiler installation” | “boiler installation in Lewes” |
| What it carries | The full sales argument: the work, what affects price, proof you do it well | The local evidence that you genuinely work there |
| How many you need | One strong page per service | As many as you can defend with something true and local |
| When it earns its place | Always | Once you serve several towns from one base |
| Role in the architecture | The hub, linking down to every area page | A spoke, linking back up to the hub |
When service pages alone are enough
A business serving one town does not need location pages – the whole site is already about that place. Put the town in the service pages naturally, keep your Google Business Profile sharp, and spend the writing time on depth instead of geography. Location pages for a single-town firm are decoration at best and doorway risk at worst.
When location pages earn their place
The moment you serve several towns from one base, each town-level search is invisible to a generic service page. That is the job service-area pages exist for – and the discipline of choosing how many to build is deciding where you can actually say something true and local.
How the two fit together
The architecture that works is a hub and its spokes: the service page is the hub, carrying the full sales argument and linking down to every area page; each area page carries the local evidence and links back up. The linking pattern is its own guide, but the principle is one strong page per service, supported by exactly as many local pages as you can defend.
The duplication trap
The classic mistake is pasting the service page’s copy into every location page and swapping the town name. Now the pages compete with each other, none of them is distinct, and the estate reads as near-duplicate content. Shared structure is fine; shared substance is the trap. The service detail lives once, on the hub – the area pages add what is local and link up for the rest.
Can one page do both jobs?
For a single-town business, yes – the service page is implicitly local. For a multi-town business, no: a page cannot be the canonical answer for a service and for each of eight towns at once.
Two towns five minutes apart – one page or two?
If you would say different true things about working in each, two pages can stand. If everything you would write is identical, publish one honest page covering both rather than two substitutable ones.
Where Townsmith fits
Townsmith generates the spokes and the hub: area pages from one blueprint, each scored before publishing, with a hub page per service anchoring the links. The free plugin covers one service across five areas – one hub and its first ring of spokes.