Writing Location Pages That Aren’t Doorway Pages
Location pages avoid doorway-page risk by proving genuine local relevance. A practical framework for building pages that pass Google policy.
A location page avoids becoming a doorway page by proving it serves a genuinely distinct location rather than swapping a city name into an otherwise identical template. Google’s spam policies specifically target pages “created to rank for specific, similar search queries” that funnel visitors to the same destination — which is exactly what a location page becomes when the only thing that changes between “plumber in Austin” and “plumber in Dallas” is the header. The fix isn’t avoiding location pages altogether; multi-location and service-area businesses need them. The fix is making each page carry real, unique information specific to that location: staff, service radius, local project photos, area-specific pricing or availability, and genuine local context a competitor’s templated page couldn’t copy in five minutes.
Key takeaway
- Google’s doorway page policy targets pages built to rank for near-identical queries that all funnel to the same outcome — thin, templated location pages fit that pattern exactly.
- Location pages are legitimate and often necessary; the risk isn’t the page type, it’s thin, duplicated content with nothing but a swapped city name.
- Each page needs a reason to exist independently: local staff or team info, area-specific service details, real project photos from that location, and content a competitor couldn’t clone by find-and-replace.
- Structured NAP data, an embedded map, and a unique LocalBusiness schema entry per location all reinforce that the page represents a real, distinct place.
What actually makes a location page a doorway page
Google defines doorway pages as pages built primarily to rank for specific search queries, often through templated or duplicated content, that funnel users toward the same ultimate destination rather than offering distinct value at each URL. The classic pattern: a service business creates “[service] in [city]” pages for every city in a service radius, changes the city name and maybe the phone number, and leaves the rest of the copy identical. Search engines have gotten measurably better at detecting this pattern at scale — near-duplicate content across dozens of near-identical URLs is now easier to flag algorithmically than it was even a couple of years ago, and AI writing tools have made the thin-template problem more common, not less, which means enforcement has tightened accordingly.
Where the line actually sits
A location page is legitimate when it represents something real and distinct: an actual office, a licensed service technician assigned to that area, inventory specific to that store, or a genuinely different service radius with its own pricing or availability. It crosses into doorway territory when the only distinguishing element is the city name in the H1 and URL, while the body content, images, testimonials and calls to action are identical across every page in the set. The test worth applying to your own pages: if you deleted the city name from the page, could a reader tell which location it describes from the content alone? If not, the page isn’t doing its job.
| Element | Doorway-page pattern | Legitimate location page |
|---|---|---|
| Body copy | Identical text with city name swapped throughout | Unique paragraphs describing that location’s team, service area and specifics |
| Photos | Generic stock imagery, same across every page | Real photos of that location, staff, or completed local projects |
| Reviews/testimonials | Same testimonials repeated on every page, or none | Reviews or case studies specific to customers in that area |
| Contact info | One central phone number and address on every page | Local phone number, address or service radius specific to that page |
| Structured data | No schema, or one schema block reused sitewide | Unique LocalBusiness schema entry per location matching that page’s NAP |
| Internal linking | Pages orphaned or linked only from a single directory list | Linked contextually from relevant blog content and the main navigation |
What genuinely distinct content looks like
The businesses that get location pages right treat each one as a small standalone page, not a mail-merge output. That means naming the actual technician, manager or team based at that location if there is one; describing the specific service radius and any area-specific constraints (permit requirements, drive-time limits, local building codes); including recent project photos taken at or near that location rather than generic stock shots; and pulling in reviews that specifically mention that location or its staff by name, where you have them. None of this needs to be lengthy — a genuinely useful location page can run 400 to 600 words of unique content plus supporting elements like a map, hours, and service list, as long as none of it is copy-pasted from a sibling page.
- List the real staff, technician or manager assigned to that location, with a name and photo where possible.
- Describe the specific service area or radius in concrete terms — neighbourhoods, ZIP codes, or a driving-time boundary — not just the city name.
- Include location-specific photos: the storefront, the team, or completed work in that area, not stock imagery reused across every page.
- Pull in reviews or testimonials tied to that specific location, and update them as new ones come in.
- Embed a real Google Map centered on that location, not a generic map of the wider region.
- Add unique LocalBusiness schema per page matching that location’s exact name, address and phone number.
The delete-the-city-name test
A fast internal audit: strip the city name from a location page’s body copy. If nothing left on the page identifies which specific location it describes, the page is functioning as a doorway page regardless of how it was intended — and it’s a strong candidate for consolidation or a genuine content rewrite.
Source — Google Search Central spam policies on doorway pages, applied practically to multi-location content audits
When to consolidate instead of expanding
Not every city or neighbourhood you serve needs its own page. If you genuinely cannot produce distinct, useful content for a location — no local staff, no location-specific detail, nothing beyond “we also serve this area” — it’s usually better to fold that area into a broader regional page or a single service-area list than to publish a thin page purely to capture the keyword. A smaller number of genuinely substantive location pages consistently outperforms a large set of thin ones, both because Google is less likely to flag the set as doorway content and because each remaining page is more likely to earn its own internal and external links rather than competing with near-duplicate siblings for the same signals. Businesses managing this at real scale — ten locations or more — need a more structured approach to page architecture; see our multi-location SEO guide for how to structure that without triggering the same duplicate-content risk.
Reinforcing location pages with the rest of your local footprint
A well-built location page works best as one piece of a consistent local signal, not a standalone bet. The name, address and phone number on the page need to match your Google Business Profile listing for that location exactly — even small formatting differences undermine the NAP consistency that helps Google confirm a location is real. Pairing location pages with genuinely local blog content, rather than more templated location pages, also helps demonstrate topical relevance to the area beyond the transactional page itself; our local content strategy guide covers how to build that layer without falling into the same city-name-swap trap.
A common pattern worth recognising in your own site
A frequent scenario: a regional service business with several branches publishes “[service] in [city]” pages from a single content template — identical intro paragraph, identical service list, identical stock photo of a technician who doesn’t actually work at any of the listed branches. Pages like this typically plateau well below the top few results and rarely earn external links on their own, because there’s nothing on the page distinct enough for anyone to reference. The fix is never to delete the pages; it’s rewriting each one around what’s actually different at that branch: the manager’s name and a short local bio, a real photo of that branch’s team or vehicles, the specific neighbourhoods its technicians cover, and reviews pulled from customers at that location. Pages rebuilt this way have unique content worth ranking on its own — a structural advantage no amount of link building can substitute for on a templated page.
Frequently asked questions
Are location pages automatically doorway pages?
No. Location pages are a legitimate, often necessary page type for multi-location and service-area businesses. They become doorway pages only when the content is thin, templated and effectively identical across locations aside from the city name.
How much unique content does a location page need?
There’s no fixed word count, but 400 to 600 words of genuinely unique content — covering local staff, service area specifics, and location-specific photos or reviews — is a reasonable practical floor for a page to stand on its own merits.
Should every city I serve get its own page?
Not necessarily. If you can’t produce genuinely distinct content for a smaller service area, fold it into a broader regional page instead. A smaller set of substantive pages performs better than a large set of thin, near-duplicate ones.
Does duplicate content across location pages get penalised automatically?
Google doesn’t apply a blanket penalty for similar pages, but pages that match the doorway pattern — built to rank for near-identical queries with no distinct value — can be filtered out of rankings or, in clear cases, targeted by a manual action.
Does each location page need its own schema markup?
Yes. Each location page should carry its own LocalBusiness structured data matching that specific location’s name, address and phone number exactly — a single reused schema block across pages undermines the signal that each location is distinct.
The bottom line
Location pages aren’t the problem — thin, templated location pages are. Build each page around what’s genuinely true and specific to that location: real staff, real photos, a real service area, and structured data that matches it exactly. Where you can’t produce that, consolidate rather than publish a placeholder. Done this way, location pages remain one of the most direct ways to earn local rankings across multiple markets, covered in full in our local SEO guide.
If you’re not sure whether your existing location pages read as doorway content, our SEO plans include a page-by-page audit as part of onboarding.
