Should you build a page for every town you serve?

Do separate town pages actually work?

Yes, when they're real. Someone in Cambridge searching for a plumber will see results weighted toward Cambridge, and a page that speaks specifically about Cambridge has a genuine advantage over a generic Waikato services page.

The catch is that Google has spent twenty years learning to recognise pages generated from a template with the town name swapped out. Those pages don't rank, and a site carrying forty of them can end up looking lower quality overall than one carrying four.

When is a location page worth building?

Ask one question: could a local reading this page tell you actually work here? If the honest answer is no, don't build it yet.

These are the signals that a town deserves its own page.

• You've done real work there — named jobs, photos, a testimonial from someone in that town. This is the single strongest ingredient.
• The terms genuinely differ — a callout fee for Wānaka that doesn't apply in Queenstown, or a different response time once you're over the hill.
• Local conditions change the job — Christchurch foundations, Wellington wind zones, Auckland consent timelines, coastal corrosion in Tauranga.
• There's real search demand — check the numbers before you write. "Electrician Levin" and "electrician Auckland" are not the same investment.

What makes a location page thin — and risky?

Thin pages share a tell: everything on them is true of every other page. Same three service paragraphs, same stock photo, same FAQ, one place name changed. Google has a name for this pattern — doorway pages — and it's explicitly against their guidance.

The damage isn't only that those pages fail to rank. They dilute the pages that would have ranked, because your internal links and crawl budget are spread across dozens of near-identical URLs instead of concentrating on a few strong ones.

• The 30 percent rule — if less than roughly a third of a page is unique to that town, merge it back into your main service page.
• Avoid inventing a presence — don't list an address you don't occupy or claim a Google Business Profile for a town where you have no staffed location. That's a suspension risk, not a shortcut.
• Don't stuff the place name — repeating "Napier" eleven times reads badly to people and does nothing for rankings.

How should you structure them on your site?

Keep it flat and predictable. A URL like yoursite.co.nz/plumber-hamilton or /services/plumbing/hamilton is fine — what matters is that it's consistent and readable, not which pattern you pick.

Link them properly. Each location page should link up to the main service page and across to two or three neighbouring towns, and your main service page should list them all. That internal linking is what tells Google these pages belong to a coherent regional business rather than being scattered orphans.

• One page per town per service at most. Don't multiply towns by every service you offer — that's how a small business ends up with 200 pages nobody reads.
• Add LocalBusiness structured data with a genuine areaServed, so search engines and AI answer engines can read your coverage without guessing.
• Put a real address and phone number in the footer sitewide, matching your Google Business Profile exactly.

How many should you build first?

Three. Pick your three highest-value towns, write them properly with real jobs and real photos, and give them two or three months. You'll learn whether the format works for your market before committing to thirty.

If those three bring enquiries, the pattern is proven and you can scale it with confidence. If they don't, you've spent a fortnight rather than a quarter finding out, and the problem is probably somewhere else — a Google Business Profile that isn't filled out, or reviews you haven't asked for.

Location pages are a content problem before they're a technical one. The businesses that win with them are the ones with actual jobs, photos and reviews from each town to draw on. If you want the underlying site built so those pages load fast, link sensibly and carry the right structured data, that's the kind of thing our web development work is designed to sort from the ground up.