Location and Service-Area Pages That Rank (Without Thin Templates)
“More pages means more chances to rank” is the exact thinking that gets local businesses penalized. Spinning up 40 city pages from one template is now a doorway problem, not a strategy. Here’s how to build location pages Google rewards instead of suppresses.
By Rahul Saini, Author at Search Counsel Co. Last updated [JULY] 2026.
Featured answer: how do you create location pages that rank?
Build one page per market you truly serve, not one per place you’d like to. Give each page real local content, the neighborhoods you cover, local property types or conditions, area-specific proof and FAQs, and a clear service-area statement, so roughly half the page is unique to that location. Use a unique URL and LocalBusiness schema, and never publish near-identical pages with only the city name swapped. Fewer, deeper pages outrank a pile of thin templates every time.
The Trap
City-swap
Same template, new city name. Google’s spam policy calls this a doorway page.
The Threshold
~95% same
The point where near-duplicate city pages get flagged as automation, not a real presence.
The Bar
Half unique
Roughly 40 to 60% of each page should be genuine, location-specific content.
Build When
3 criteria
Real presence, real search demand, and something unique to say. All three, or skip it.
Location pages are either your biggest local SEO asset or a fast track to a penalty, and the difference is entirely about whether they’re real. A page built for a market you actually serve, with content a local would recognize, ranks and converts. A page that’s your template with the city name changed 12 times is a doorway page, and Google has been catching those since 2015.
This guide shows you when to build a location page, how to make it authentically local, and how to keep the whole set on the right side of Google’s spam policies. The keyword side, which terms each page targets, is covered in local keyword research, and the schema in LocalBusiness schema. Here we’re building the pages themselves.
Key takeaways
- “More pages” is the trap, not the strategy. Dozens of near-identical city pages match Google’s definition of doorway abuse and can suppress your whole site.
- Google’s policies specifically target this. The doorway policy (since 2015) plus the March 2024 scaled content abuse policy cover pages built mainly to rank, whether written by humans, AI, or both.
- Build a page only when three things are true: you truly serve that market, there’s real search demand, and you have something unique to say about it. Miss one and skip the page.
- Aim for roughly half the page to be unique and location-specific: neighborhoods, local property types or conditions, area proof, and area FAQs. Around 800 words of real local value, not a 200-word template.
- Match the page model to your business. A storefront gets a location page; a service-area business gets a service-area page. Don’t use one template for both.
- Don’t city-stuff. Google’s spam policy flags blocks of text that just list the cities and regions a page is trying to rank for.
- The machine-readable layer is often missing. Add LocalBusiness schema that matches the visible content, since many location pages skip it entirely.
Jump to what you need
Article note: Written by Rahul Saini at Search Counsel Co. This covers building the pages. For the terms each page targets, see local keyword research. For the structured data these pages need, see LocalBusiness schema. For internal-linking mechanics, see our on-page SEO guide.
How we researched this
Every factual claim on this page is traced to a named primary source, listed near the end. The policy points come from Google’s own spam documentation, not third-party summaries alone. Where a threshold comes from practitioner analysis rather than a Google statement, we label it as such.
Google’s spam policies and enforcement evolve, so figures and policy points are dated and re-verified on each update. If you find something out of date, tell us and we’ll fix it.
1) The doorway trap
Start with the mistake, because avoiding it is most of the job. Someone builds a template, swaps the city name across 40 pages, and reasons that more pages mean more chances to rank. For a while, sometimes, it works. Then indexed pages stall, impressions slide, and the phone goes quiet.
That pattern is exactly what Google’s spam policies target. Google defines doorway abuse as pages created to rank for specific, similar queries that lead users to a less useful destination, and its examples include “having multiple pages targeted at specific locations or cities that funnel users to one page.” The doorway policy has been enforced since 2015. Then, in March 2024, Google formalized its scaled content abuse policy: producing many pages mainly to rank, with little value, whether written by humans, by AI, or by a mix. That AI clause is the point in 2026, because spinning up a hundred suburb pages with a language model is precisely what it’s hunting.
The automation fingerprint. Practitioner analysis of the August 2025 spam update found the flag threshold sits around 95% identical content across a set of city pages. That’s the tell Google’s pattern detection reads as automation rather than a real local presence. Generic template-swapping, changing only the city name in boilerplate, is the bullseye. Treat “95% the same” as the line you never want your page set to cross.
A simple test: open five of your city pages side by side. If a customer wouldn’t care which one they landed on because the content barely changes, Google won’t either, and the cluster is a liability, not an asset.
2) When to build a location page
The fix starts before you write a word: build far fewer pages, and only for markets that are real. A useful three-part test, only build a dedicated page when all three are true:
- You truly serve that market. You have staff, vehicles, or equipment that realistically cover it, so you can handle the jobs the page attracts.
- There’s real search demand. Your keyword research shows a viable volume of local searches for your service in that specific place.
- You have something unique to say. The area has distinct housing stock, common local issues, regulations, or conditions you can write about truthfully. A pest control firm’s page for an old port town (dockside rodent control) reads nothing like its page for a farming village, because the work is different.
Don’t overextend your coverage. Google’s own guidance suggests a service area shouldn’t stretch beyond roughly two hours’ driving time from your base. Build rich pages for your most important markets first, then expand to smaller communities only when you have something genuine and useful to say about them. Two strong city pages beat twenty thin ones.
3) Location pages vs service-area pages
These aren’t the same page, and using one template for both confuses users and search engines. Match the model to how your business actually operates.
| Page type | For whom, and what it must say |
|---|---|
| Location page | A business with a physical branch customers visit. One page per real location, with its address, hours, team, embedded map, and local proof. Link it from that location’s Google Business Profile. |
| Service-area page | A business that travels to customers (plumber, cleaner, contractor). One page per market served, explaining where you serve, how dispatch and scheduling work there, and why local customers should choose you. No fake address. |
The service-area page is how a business with no public storefront still earns rankings for “service in city” searches. Its whole job is to answer one question clearly: “Can you help me here, and what happens next?” Vague coverage language like “we serve everywhere” fails that test and pulls in out-of-area leads.
4) The fixed + variable method
You can’t hand-write a bespoke essay for every market, and you don’t need to. The workable approach is to split each page into fixed and variable sections.
Roughly half the page can be shared: your brand story, service standards, guarantees, and company background stay the same across the site. The other half, and this is the half that saves you, must be specific to the location. Aim for around 40 to 60% unique content per page, which usually means something like 800 words of real local value rather than a 200-word boilerplate with a swapped name. The unique half is what keeps the page clear of the doorway line and useful to an actual visitor.
Build freshness in. Use variable modules that pull live, location-specific data: recent reviews from customers in that area, local team names, real project photos, area-specific offers. That keeps pages current without manual rewrites, and it deepens the unique layer at the same time.
5) What real local content looks like
“Unique” doesn’t mean spinning synonyms, which Google’s scaled content policy also targets. It means information a local would recognize as true and specific. Pull from this list:
| Element | Why it reads as authentically local |
|---|---|
| Neighborhoods and landmarks served | Names a local recognizes, shown as a clear list, not a keyword-stuffed paragraph. |
| Local property types or conditions | Older housing stock, hard water, coastal corrosion, regional regulations. The stuff that changes the job. |
| Area-specific proof | Real project examples, before-and-after photos, and reviews from customers in that market. |
| Operational reality | Travel fees, service radius, realistic scheduling windows, same-day availability for that area. |
| Area-specific FAQs | The questions customers in that place actually ask, answered plainly. |
| A clear service-area statement | “Based in X, serving Y and nearby neighborhoods,” plus any coverage limits. |
Finish each page with one primary intent (usually “service plus city”) and a strong call to action that sets expectations: what happens next, response times, how to book. A single “Contact us” line underperforms a clear next step.
6) The technical layer
A few technical details separate a page that ranks from one that gets ignored. None are complicated.
- Unique URL per page, including the city and the core service, in a clean, browseable structure rather than a flat pile of near-duplicates.
- LocalBusiness schema matching the visible content: business name, address or service area, phone, hours, and services. Many location pages skip this entirely, so it’s an easy edge. The full markup is in LocalBusiness schema.
- Consistent NAP that matches your Google Business Profile exactly, down to “Street” versus “St.” The details are in NAP consistency.
- Internal links from each location page to the relevant service pages, and from your Google Business Profile to the matching page. Avoid orphan pages nothing links to. Linking mechanics live in our internal linking guide.
- An embedded map and a mobile-first layout, since most local searches happen on phones.
For coverage breadth, use a hub. Don’t cram a long list of every town into a single page’s copy; Google’s spam policy calls that out as keyword stuffing. Instead, build a clean, navigable “Areas we serve” section that links to your real location or service-area pages. That keeps the structure browseable, which is the opposite of a doorway funnel.
7) Location pages and AI search
There’s a newer reason to get these pages right. A location page used to be judged only on whether it could rank for a city-and-service term. That’s still true, but it’s no longer the whole job.
When someone asks an AI assistant who to hire, the system has to resolve a specific local question: which branch serves this job, what services it performs, what proof supports it, and how to get in touch. For a multi-location business, the location page is often the cleanest owned source for that answer, if it contains clear, crawlable facts and matching structured data. A thin city-name template gives the machine nothing to work with; a page with real local proof and clean schema gives it everything.
The gap is real: one product audit of location pages found only a small fraction carried LocalBusiness structured data at all, meaning the page was readable to humans but the machine-readable local entity layer was missing. Treat schema as a clarification layer that helps crawlers and answer engines parse facts that should already be visible, not as a ranking trick. This connects to the wider discipline in local AI search and our AI search optimization guide.
Free tool
Local AI Visibility Grader
Once your location pages are live, see whether they’re doing the second job. The Grader checks whether ChatGPT, Gemini, and Perplexity recommend your business for its “best [service] in [city]” prompts, and health-checks your profile and citations.
8) Fixing existing thin pages
If you’ve inherited a set of thin city pages, cleaning them up usually helps rather than hurts. Sites with clear doorway patterns get caught, and consolidating rarely costs you traffic; more often it lifts it.
- Audit the set. Open similar pages side by side and read the titles and body copy together. If they differ only by city name, mark the cluster.
- Keep the markets that are real and rewrite those pages around genuine local need. If a page still reads like a template with a swapped name, it’s still a doorway risk.
- Consolidate or remove the rest, and 301-redirect each retired URL to the closest relevant page.
- Fix internal links and navigation so they support the surviving pages instead of feeding dead ends.
- Request reindexing for the key pages and monitor for eight to twelve weeks. Expect uneven movement before things settle.
9) Sources used for this guide
| Claim | Source |
|---|---|
| Doorway abuse definition and examples (location pages funneling to one page); enforced since 2015 | Google Search spam policies (doorways); Search Engine Land |
| Scaled content abuse policy (March 2024) covers pages made mainly to rank, human, AI, or mixed | Google Search Central spam policies |
| ~95% identical content across city pages flagged as automation (Aug 2025 update) | Practitioner analysis of the August 2025 spam update |
| Three build criteria; fixed + variable structure (~half unique); ~2-hour service-area guidance | Search Engine Journal; Search Engine Land |
| Keyword stuffing policy flags blocks of text listing cities/regions to rank for | Google Search spam policies (keyword stuffing) |
| Location pages often lack LocalBusiness schema; schema clarifies rather than ranks | Cheers location-page audit (small product sample); Google Search Central |
FAQ
Are location pages good or bad for SEO?
Both, depending on how you build them. Truly local pages for markets you serve rank and convert well. Near-identical templates with only the city name swapped are doorway pages and can suppress your whole site. The deciding factor is whether each page offers real, location-specific value.
What is a doorway page?
Google defines doorway abuse as pages created to rank for specific, similar queries that lead users to a less useful destination, including multiple pages targeted at different cities that funnel users to one place. For local businesses it usually shows up as dozens of near-identical “service in city” pages. Google has enforced against this since 2015.
How many location pages should I have?
Only as many as you can make truly useful. Build a page when you truly serve the market, there’s real search demand, and you have something unique to say about it. Two strong city pages beat twenty thin ones, and Google’s guidance suggests not stretching your service area beyond about two hours’ drive from your base.
What’s the difference between a location page and a service-area page?
A location page is for a physical branch customers visit, with its address, hours, and map. A service-area page is for a business that travels to customers, explaining where you serve and how scheduling works there, without a public storefront address. Don’t use the same template for both, since it confuses users and search engines.
How much unique content does each page need?
Aim for roughly 40 to 60% of the page to be truly location-specific, which usually means around 800 words of real local value rather than a short boilerplate. Practitioner analysis suggests that once city pages are about 95% identical, Google’s systems flag the set as automation.
Can I use AI to write my location pages?
Only with heavy, genuine localization and human review. Google’s scaled content abuse policy explicitly covers pages produced mainly to rank whether written by humans, AI, or a mix, and bulk AI-generated suburb pages are a primary target. AI can help draft, but the local specifics, proof, and accuracy have to be real.
Do location pages need schema?
Yes. Add LocalBusiness schema that matches the visible content, since many location pages skip it and it helps both search engines and AI answer engines parse your local facts. Treat it as a clarification layer, not a ranking trick. The full setup is in LocalBusiness schema.
How do I fix thin location pages I already have?
Audit the set, keep and rewrite the pages for markets you truly serve, and consolidate or remove the rest with 301 redirects to the closest relevant page. Fix internal links to support the survivors, then request reindexing and monitor for eight to twelve weeks. Cleanup usually helps performance rather than hurting it.
Conclusion: fewer pages, more real
The whole discipline of location pages comes down to one honest choice: build fewer pages and make each one real. The businesses that lose are the ones that treated city pages as a volume game, spun up a template, and swapped the name. The businesses that win build a truly useful page for each market they actually serve, and let depth do the work that padding never could.
That’s also what future-proofs them. A page rich enough to rank for “service in city” is the same page an AI assistant can read to recommend the right branch to the right customer. Thin templates give neither surface anything to work with.
So pick your real markets, write pages a local would recognize, add the schema, link them properly, and stop there. Then support them with the terms from local keyword research and the markup in LocalBusiness schema.
Editorial note: This guide is general marketing information, not a guarantee of results. Google’s spam policies and their enforcement change over time, and some thresholds cited here come from practitioner analysis rather than official Google statements. Verify against Google’s current documentation before making structural changes to your site.