How do you build location pages that are not doorway pages?
A location page tells people everything they need to visit or book one branch: address, hours, team, parking, services offered there. Built for real places, location pages rank and convert. Built for towns you merely want to rank in, they become doorway pages.
What is a location page?
A location page is a page on your website for one physical place your business operates from, such as a branch, clinic or office. It holds that place's name, address, phone, hours, directions, team and the services offered there, and it is usually the website link on that location's Google Business Profile.
Single-location businesses often do not need one: the homepage and contact page cover it. Location pages become essential once you have two or more places customers can visit, or a service-area business with crews based in different towns.
Location pages connect your website to the map. Someone who finds your Kitchener branch in Maps and taps Website should land on the Kitchener page, not on a homepage that makes them hunt for the right branch. See multi-location SEO for the wider plan.
When should a business create a location page?
Create a location page when there is a real place behind it. The table covers the common cases.
| Situation | Location page? | Why |
|---|---|---|
| A branch, clinic or store customers visit | Yes, one per branch | Matches the Business Profile for that address |
| A service-area business with a crew or depot in a town | Yes, for that base | Real staff, real jobs, a real starting point |
| A town you serve often from another base, with many past jobs there | Maybe, as a service-area page | Only if you can show genuine local work and details |
| A town inside your service area with no special detail | No | List it on the service area section instead |
| A city you want to rank in but do not serve | No | This is the doorway pattern |
Service-area pages sit in a grey zone. A plumber with 200 completed jobs in Barrhaven, local photos and a technician who lives there can build a genuinely useful Barrhaven page. A plumber with none of that cannot. Storefront or service-area explains how the profile side differs.
What should a location page include?
Start with the facts that only this location has, then add the content that helps someone choose and arrive.
Think of the page as the front door of that branch. Everything a first-time visitor would ask the receptionist belongs on it.
- Name, address and phone exactly as on that location's Business Profile, in text, not only in an image.
- Hours, including holiday hours, kept in step with the profile.
- How to get there: parking, transit stops, entrance, accessibility, landmarks.
- Who works there: named staff with roles and real photos.
- Services offered at this location, with links to the service pages. Note anything not offered here.
- Local proof: photos of the actual premises, recent work nearby, community involvement that is real.
- An embedded map or directions link and a tappable phone number.
- Structured data for this branch only.
Google's local business structured data guide says to use the most specific LocalBusiness type and to include the address and name, plus recommended properties such as geo coordinates, telephone, url and opening hours. On a multi-location site, each location page carries its own markup. The detail is in LocalBusiness schema.
What does a genuine location page look like?
A mock-up for one branch of a fictional physiotherapy group with three clinics in Waterloo Region. Notice how much of it could not be reused for the other two branches.
Ground-floor clinic at 712 Belmont Ave W. Free parking behind the building; iXpress stop at the corner.
- Open Mon to Fri 7:00 to 19:00, Sat 8:00 to 13:00
- Direct billing to most extended health plans
- Wheelchair-accessible entrance and treatment rooms
/locations/All clinics, with a map and links/locations/kitchener-belmont/Own address, team, hours, photos/locations/waterloo-uptown/Own address, team, hours, photos/locations/cambridge-hespeler/Own address, team, hours, photos/physiotherapy/Service page, links to all three clinics/vestibular-therapy/Service page, notes it is Belmont onlySwap test: change the city name. Does anything else need to change?
If the only edit a page needs to become another city's page is the city name, it is a doorway page. A real location page would need a new address, team, photos, hours and directions.
Where is the line between a location page and a doorway page?
Google's spam policies list doorway abuse, and one of the examples is having pages targeted at specific regions or cities that funnel users to one page. In practice that means a set of city pages that all say the same thing and all push the visitor to the same contact form.
| Signal | Genuine location page | Doorway pattern |
|---|---|---|
| Address | A real address with a Business Profile | None, or the head office on every page |
| Content | Branch-specific team, hours, directions, photos | Template text with the city name swapped |
| Purpose for the visitor | Visit or book this branch | Get them to one generic page |
| Number of pages | Matches the number of real locations | Dozens or hundreds of towns |
| Would a customer miss it if removed? | Yes | No |
If you already have dozens of thin city pages, consolidate them. Keep pages for real bases, merge the rest into a service area section, and redirect the removed URLs to the most relevant remaining page.
How do you measure location pages?
Measure each location page against its own branch: actions from the page, visits from that branch's Business Profile and whether the page appears for searches that name the area.
| Measure | Why it matters | Source |
|---|---|---|
| Calls, bookings and direction clicks from the page | The page's real job | Analytics events, call tracking |
| Visits from the branch's profile link (UTM tagged) | Maps visitors land on the right branch | Analytics |
| Queries containing the area or branch name | Local relevance of the page | Search Console |
| Indexing status of each location URL | Thin or duplicate pages may be left out | Search Console page indexing |
| Bounce to the locations hub | Visitors who landed on the wrong branch | Analytics path report |
Watch the indexing report closely after launching new pages. Location pages Google chooses not to index are often a sign they look too similar. The internal linking guide shows how to make each one easy to reach.
Frequently asked questions
Is a location page the same as a city page?
Not always. A location page is for a real place you operate from. A city page targets a town; it is only useful when you have genuine local presence or work to show there.
How many location pages should I have?
As many as you have real locations, and possibly a few service-area pages for towns where you have a base or a large body of local work. Not one per town on a map.
Can location pages share some content?
Yes. Service descriptions and company background can be similar. Each page still needs enough branch-specific detail that it is clearly about that place.
What are doorway pages?
Google describes doorway abuse as pages created to rank for specific searches that funnel users elsewhere, including pages targeted at specific regions or cities that funnel users to one page.
Should my Business Profile link to the location page?
Yes for multi-location businesses. Each profile should link to the page for that branch so visitors from Maps land on the right address, hours and team.
Do location pages need schema markup?
It helps. Each location page can carry LocalBusiness markup for that branch, using the most specific type with its own address, phone, hours and coordinates.
What should I do with old thin city pages?
Keep the ones tied to real locations, merge the others into a service area section and redirect their URLs to the closest relevant page.
Where should location pages sit in the URL structure?
Usually under a /locations/ folder with a hub page linking to each branch. Service-area and city-plus-service URLs are covered on the site architecture page.
Sources & further reading
Regulator rules, platform policies and local data change. These sources let you check the facts on this page, last checked October 7, 2026.