Key takeaways
- A service-area page needs territory evidence, not a swapped town name. A URL you cannot defend is a doorway page waiting to be indexed.
- Run the eligibility test before you publish. Thin town pages stay unpublished; the hub holds the offer.
- Hub-and-location architecture keeps one canonical service page and location pages that add real local detail.
An agency sold you forty city URLs. You drive to three of them. The pages share one paragraph with the town name swapped. Google calls that a doorway.
Service-area pages for local SEO are not a template multiplied by a spreadsheet. They are location-specific pages you can defend because you work there — with jobs, constraints, and proof a buyer in that place would recognise. A town URL without evidence is not local SEO. It is spam that teaches a crawler you are generating pages to catch queries, not to help people.
Local SEO vs national SEO is the map choice. This page is the architecture inside the local map: what earns a URL, what stays on the hub, and what Google’s doorway guidance would reject.
A town name is not a service area
Local SEO wins when the query includes a place and your business can honestly serve it. The useful surfaces are a truthful Business Profile, a site that names the same trade and area, and location pages backed by delivery history — not a grid of slugs for towns you have never visited.
A service-area business does not need an office in every suburb. It does need a radius, licensing, response time, or delivery model you can describe without inventing local presence. Google Business Profile vs website is the longer version of that alignment: the profile states the area; the site should support it, not manufacture virtual storefronts the profile rules would reject.
| Pattern | What it looks like | What search systems read |
|---|---|---|
| Doorway grid | Trade plus town, same copy, swapped landmarks | Pages built to rank, not to help |
| Honest hub | One canonical service page with clear area rules | A real offer with geographic limits |
| Defensible location page | Town-specific proof, constraints, and next step | A page a buyer in that place can use |
Google’s spam policies on doorway pages describe pages created to rank for specific queries and funnel users without adding unique value. Multiple similar pages targeting cities or regions you do not meaningfully serve fit that pattern. The fix is not better synonyms. It is fewer URLs with more evidence.
Run the page eligibility test
Before you publish a location URL, score it against five gates. A page that fails any gate stays unpublished or merges into the hub.
1. Territory: Is the place inside your real service area, travel radius, licensing, or delivery model? 2. Evidence: Can you show jobs, customers, projects, or fulfilment history in that area with permission? 3. Distinction: Can you explain how serving this place differs from the next town — response time, crew, pricing band, regulations, or common job type? 4. Path: Does the page give a local buyer a next step that actually works — call routing, booking rules, or quote process for that area? 5. Relationship: Does the page link to a canonical hub that holds the core offer without duplicating it?
Score each gate pass or fail. Two fails means do not publish. One fail means fix the hub first or write a regional page instead of a city slug.
Monday: list every live location URL. For each, write one sentence of evidence only a team that works that place would know. If you cannot finish the sentence, unpublish or merge the page into the hub. Google’s doorway guidance is the external check; your delivery team is the internal one.
Build the territory evidence map
For every geographic claim on the site or profile, record evidence in one ledger:
- eligible location or accurate service area;
- jobs, customers, projects, or delivery history in the area;
- service constraints — travel radius, licensing, delivery, response time;
- local proof used with permission;
- contact and fulfilment path that serves the place;
- relationship to the canonical service page and Business Profile.
A city name in a heading is not evidence. A paragraph with swapped landmarks is not evidence. If the business cannot distinguish how it serves one area from another, a regional hub or service-area explanation is more honest than dozens of URLs.
Use one territory map across search, sales, ads, and operations. SEO should not promise a city the dispatch team quietly declines. Sales should not quote a town the site cannot show. Ads should not send clicks to a page that contradicts the profile.
For profile and structured-data alignment, see Google Business Profile Help — Representation guidelines and Google Search Central — LocalBusiness structured data.
Design hub-and-location architecture
A healthy local site has layers, not a flat list of town slugs.
Hub page: the canonical service offer — scope, process, proof, pricing band, and area rules. One URL carries the trade. It names how geography works: radius, counties served, or “we come to you within X miles.”
Location or regional pages: pages that add local detail the hub cannot carry — neighbourhood response times, permit notes, photos from jobs in that area, crew coverage, or a local phone route. Each page links up to the hub and sideways to related regions only when the relationship is real.
Profile and listings: the same name, category, area, and primary URL as the hub. Location pages support the profile; they do not replace it with fake offices.
Do not create multiple URLs that target the same intent with minor variation. If two towns get identical service, one regional page or the hub plus a clear area list may be enough. Volume of city pages is not local authority. Defensible territory is.
What you can fix alone
You can audit live URLs against the eligibility test, merge thin town pages into the hub, align the profile service area with delivery reality, and unpublish slugs you cannot evidence. You can rewrite one location page with real job photos and constraints before you add another.
What stays unfinished without build help: a hub that holds the offer cleanly, internal linking between hub and locations, structured data that matches the public facts, and forms that route inquiries by territory. That is SEO content plus web development when the architecture needs to ship, not another spreadsheet of town names.
If the profile and site disagree on where you work, start with GBP repair. If the pages exist but cannot rank because they are thin, start with SEO. The estimator at get started turns the current map into a scoped proposal — evidence first, URLs second.
