The essentials
- When: one page per real location, one page per significant service area; never a page per town "to cover the ground".
- The template: NAP, hours, a map, a local description, services, photos of the place, the team, reviews, local completed jobs, a call to action, LocalBusiness structured data.
- Structure: /branches/town/ or /town/service/ depending on the number of locations and services.
- The trap: town pages identical word for word, which Google treats as duplicate content or spam.
The Google Business Profile listing gets a business into the local pack; the site's local pages do the rest: they answer "activity + town" queries in the organic results, strengthen the listing's relevance (Google compares the site and the listing) and convert the visitor. Well structured, they are the most durable local SEO asset. Done badly (copied from one town to the next), they are ignored or penalised. This guide gives the template and the structure for your situation.
When to create local pages
| Situation | Pages to create | Example URL |
|---|---|---|
| A single location | One "location" page or an enriched contact page, plus a localised home page | /our-practice-in-nantes/ |
| Several locations | One page per location, under a "our branches" page | /branches/nantes/, /branches/rennes/ |
| One location, several service areas | One page per area you genuinely work (5 to 10 at most), with its own content | /plumber-saint-herblain/ |
| Several services × several towns | Town pages + service pages, and only the crossings with strong demand | /nantes/, /water-heater-repair/, /nantes/water-heater-repair/ if the volume justifies it |
| A franchise or national network | One page per outlet, generated from a database, with real local fields | /stores/lyon-part-dieu/ |
The rule: a local page must have something local to say. If you can't fill the template below with information specific to the town, don't create the page.
The template of a local page
| Block | Example | Why |
|---|---|---|
| Title and H1 | "Activity in Town | Brand"; an H1 with the activity and the town | The target query |
| NAP and hours | Identical to the Google listing, with a clickable phone number | Consistency, conversion |
| A map | Google Maps embedded, access, parking, transport | Usefulness, a local signal |
| A local description | 150 to 300 words on what you do here : the neighbourhoods served, specifics, how long you've been there | Its own content |
| Services | A list of the services available at this location, with links to the service pages | Relevance, internal linking |
| Photos of the place and the team | Real ones, named with the town | Trust, uniqueness |
| Reviews | Extracts from this location's Google reviews, with a link to the listing | Reassurance |
| Local completed jobs | Projects, case studies, news from the area | Unique, living content |
| A call to action | Call, quote, booking, directions | Conversion |
| Structured data | LocalBusiness (or a subtype) with the NAP, hours and GPS coordinates | Reading by Google; see local Schema.org |
The structure and the internal linking
- A hub page "Our branches" or "Areas we serve" lists every local page, with a map.
- Every local page is reachable in two clicks from the home page (the menu or the footer).
- The service pages link to the local pages where the service is offered, and vice versa.
- The footer shows the main location's NAP; for a network, links to the branch pages.
- Every Google listing points to its local page, not to the home page, with UTM.
This organisation follows the logic of the semantic cocoon : one theme (the area), a parent page (the branch), child pages (the local services).
The duplicate content trap
Creating thirty "Plumber + town" pages by changing only the town's name is the most widespread and least effective practice: Google recognises near-identical pages, indexes only some of them and can rank them among the "doorway pages" targeted by its anti-spam policies. Three rules to avoid it:
- Only create a page for an area where you have a real presence: a location, completed jobs, customers, a team.
- Fill each page with its own information: neighbourhoods, completed jobs, photos, reviews, local particularities (planning rules, housing stock, local grants).
- Group small towns into one area page rather than multiplying them.
The detection mechanisms and the fixes are described in duplicate content.
Measure
In Search Console, filter the queries containing the town's name and look at the pages answering them; in GA4, sessions and conversions by local landing page. A local page receiving traffic but not converting has a content or call-to-action problem; one receiving nothing after three months lacks internal linking or its own content. For networks, multi-listing and multi-page steering is covered in multi-location local SEO.
How GreenRed helps
Rather than juggling several tools, GreenRed's SEO module brings these metrics together in a single dashboard, compares them over time and tells you which actions come first. You can try it free, with no card, from the Pricing.
Frequently asked questions
Do you need a page per town for local SEO?
One page per town where you have a real presence (a location, an area you genuinely work, completed jobs), with content specific to that town. Multiplying town pages identical word for word is counter-productive: Google treats them as duplicate content and can consider them spam.
What should go on a local page to make it unique?
The location's NAP and hours, a map and access details, a description of your business in that area (neighbourhoods, specifics), the services available, real photos of the place and the team, reviews from that location, local completed jobs and LocalBusiness structured data.
What URL should you choose for local pages?
For several locations: /branches/town/ or /stores/town/. For service areas: /activity-town/ or /town/. For service × town crossings: /town/service/, only where demand justifies it. What matters is a consistent, short, readable structure, with no later changes.
Should the Google listing point to the home page or the local page?
To the location's local page, especially for a network: it strengthens consistency between the listing and the site, and converts better than a generic home page. Add UTM parameters to the link so you can measure that traffic in GA4.