Service pages vs location pages: which do you actually need?

Here is the quick decision: a service page describes one thing you do, and a location page targets one place you do it in. If you serve a single town, you almost certainly need clear service pages and no location pages at all. You only reach for location pages when you genuinely operate across several distinct areas - and even then, you build far fewer than you think.

The confusion between the two is behind a lot of bloated, thin websites, so let me sort out what each is for and when to build which.

What a service page is for

A service page exists to rank for, and explain, one thing you do. If you are a physio, that is a page for sports injuries, one for back pain, one for post-surgery rehab. Each page goes deep on that single service: the problem, how you treat it, what to expect, who it suits.

This solves a problem I see constantly, which is owners expecting the homepage to carry everything. It cannot. Your homepage is a jack-of-all-trades and Google struggles to rank it for any one specific thing - I explain exactly why in why your homepage can't rank for everything. Service pages are how you give each offering its own proper shot at ranking.

What a location page is for

A location page targets a specific place. It is for the business that genuinely operates in several areas and wants to rank in each - say a plumbing firm with real coverage across Wellington, Porirua and the Hutt Valley. A good location page is not a copy of another with the town name swapped in. It has local substance: the areas you cover, real jobs you have done there, local specifics, ideally a physical presence.

The test is simple. Do you have a real, distinct connection to that location - customers, jobs, maybe an office? If yes, a location page can earn its place. If you are just hoping to appear in a town you have never worked in, that page will be thin and it will not rank.

The service x location matrix

When you do multiple services across multiple areas, people panic and imagine a page for every combination. Three services across four towns sounds like twelve pages. Resist that instinct. In practice you want:

• One strong service page per service, covering the service in depth regardless of location.
• One location page per area where you genuinely operate, covering the services you offer there.
• A full service-times-location grid only if you are large, truly established in each area, and can give every page real, unique content.

For most small and medium businesses, that means a handful of service pages plus a couple of location pages - not a sprawling matrix of near-identical thin pages.

Every page you publish is a promise to Google that it is worth ranking. Thin location pages break that promise at scale.

- Tom McSherry

The thin-page trap

The reason I keep hammering restraint is that more pages does not mean more rankings. Often it means fewer. When you spin up twenty barely-different location pages, Google sees low-value, near-duplicate content, and it can drag your whole site down. I have watched sites rank worse after adding pages - the mechanics are in more pages, worse rankings. Quality per page beats quantity, every time.

So which do you need?

• Single-location business: service pages only. Skip location pages entirely.
• Service-area business in one region: service pages, maybe one location or 'areas we cover' page.
• Genuinely multi-location business: service pages plus a real location page per area you actually operate in.

If you are in that last camp and juggling several branches, the planning gets more involved - keeping pages distinct, avoiding branches competing with each other, structuring URLs sensibly. I have pulled that together in the multi-location SEO guide, which is where to go once you have more than a couple of real locations to manage.

Strip it back to the principle and it is easy. Build a page for every real thing you do and every real place you do it - and not one page more.