How to build local landing pages that rank (and aren't doorway pages)
Build local landing pages only where people search and you have something real to say. How to choose cities, what to put on them, and the doorway line.

On this page9 sections
- What local landing pages are for
- The doorway line: what Google's policy says
- Step 1: Choose places by search demand, not by map
- Step 2: Decide what each page needs to prove
- How to create content for local landing pages
- Technical details that matter
- What about all the towns that don't get a page?
- What I'd do
- Frequently asked questions
Short answer
Build local landing pages only for places where people actually search for what you do and where you can say something genuinely local: an office, a team, real jobs, local rules, local reviews. Skip the rest. A page per suburb with the town name swapped in is what Google calls doorway abuse, and it rarely works anyway.
Local landing pages are one of the most useful things a service business can build, and one of the most abused. It's common to find sites with dozens of city pages that differ by a single word. The fix usually isn't more effort. It's choosing the right places and putting real substance on them.
Here's how I'd approach it: how to pick which cities get a page, how to create content for local landing pages that isn't filler, and where Google draws the line.
What local landing pages are for
A local landing page answers one question for one place: "Can this business help me, here?" A good one does three jobs at once:
- Tells Google you're relevant to that place for the services on the page.
- Gives a local searcher confidence, with details only a business that really works there would know.
- Gives your Google Business Profile a strong page to link to, if you have a location there.
What it isn't: a way to rank in every town within 50 miles by repeating the town name. That approach has a name in Google's documentation.
The doorway line: what Google's policy says
Google's spam policies define doorway abuse as creating sites or pages "to rank for specific, similar search queries." Two of its examples are exactly what bad city pages look like:
- "Having multiple domain names or pages targeted at specific regions or cities that funnel users to one page"
- "Creating substantially similar pages that are closer to search results than a clearly defined, browseable hierarchy"
Its neighbor, scaled content abuse, covers "many pages generated for the primary purpose of manipulating search rankings and not helping users," however they were produced.
So the test isn't "how many city pages do you have?" It's "would each page still be useful if search engines didn't exist?" A page with your Naperville team, jobs and permit notes passes. A page that's your Chicago page with "Naperville" pasted in eleven times doesn't.
Step 1: Choose places by search demand, not by map
Most businesses decide which city pages to build by drawing a radius on a map. I'd start with search data instead, because it tends to be surprising.
When we looked at Semrush US data (monthly averages) for our own services around Chicago and Denver, the pattern was stark. "Web design naperville" shows about 480 searches a month and "seo naperville" about 390. "Web design fort collins" shows about 390, and "seo colorado springs" about 1,000. Meanwhile most suburbs show between 0 and 20 a month for "web design [town]" or "seo [town]": Arlington Heights, Oak Lawn and Tinley Park around 10, Wheaton around 20, Englewood around 10, Golden around 20.
So we practised what we preach. We built Chicago and Denver pages, where our teams actually are, and we didn't spin up a page for every suburb that gets ten searches a month. I break the data down further in local search in Chicago vs Denver, and the method is in how to find local SEO keywords.
Search volume isn't the only test. You also need something real to say. Put the two together and the decision gets simple.
Step 2: Decide what each page needs to prove
Before writing, list the local proof you actually have for that place. If you can't fill most of this list, the page probably shouldn't exist yet.
- A physical office or a team based there (with address and hours if customers visit)
- Jobs, projects or clients you've done there, with photos you took
- Local specifics that change the work: permits, codes, climate, soil, HOA rules, parking, access
- Reviews from customers in that area
- Service details that differ there: response times, availability, pricing, travel fees
- Staff who work that area, with names and roles
How to create content for local landing pages
This is where most pages fall down. Here's the structure I'd use, with what makes each section genuinely local.
- A headline and opening that answer the search. "Kitchen remodeling in Naperville" followed by two sentences on what you do there and for whom. No "Welcome to our Naperville page."
- Proof you work there. Two or three recent local jobs with real photos and one or two sentences each: the neighborhood, the problem, what you did. Label them honestly; don't invent projects.
- What's different about working there. The permit office's typical turnaround, older housing stock, winter scheduling, whatever is true and useful. This is the section a competitor can't copy by find-and-replace.
- Services offered in that area, linking to your main service pages rather than duplicating them.
- Local reviews, quoted with permission or embedded from your profile, from customers in that place.
- Practical details: address, hours, phone, parking or service area, how fast you can usually get there.
- A short FAQ with questions people in that area actually ask you.
- One clear call to action, with a phone number that works on mobile.
If you use AI to help draft, use it for structure and editing, not for the local facts. A model will happily invent a permit process or a neighborhood that sounds right.
Technical details that matter
- URL structure: something plain like
/locations/napervilleor/naperville. Keep it consistent. - Internal links: link each page from a locations hub and from relevant service pages, so it's part of a "clearly defined, browseable hierarchy" rather than an orphan.
- Business Profile link: if you have a verified location in that city, I'd point its website link at the matching location page rather than your homepage.
- Structured data: mark up real locations with
LocalBusinessschema, with the same name, address and phone as your profile. - Don't fake an address. If you're a service-area business without an office in that town, don't list one. Describe the area you serve instead.
What about all the towns that don't get a page?
You still serve them. You just don't need a page per town to say so.
- Add a "Areas we serve" section on your main service or location pages, listing towns in plain text, with a sentence or two about how you cover them.
- Set your service area in your Google Business Profile.
- Mention towns naturally in project write-ups ("a basement finish in Wheaton") where it's true.
- Revisit the decision once a year. If a town grows into real demand, or you open an office there, build the page then.
What I'd do
If I were starting a local page plan for a service business tomorrow:
- Pull search volumes for "[service] [town]" across every place you serve.
- Mark which places you have genuine local substance for: an office, jobs, reviews, staff.
- Build pages only where both are true. For most small businesses that's one to five pages, not fifty.
- Write each page from scratch around real local proof, then link it from a locations hub and the relevant service pages.
- Cover every other town with an "areas we serve" section and your profile's service area.
- Check Search Console after a few months. Pages that get impressions for their town are working. Pages that get none need more substance or should be merged.
Frequently asked questions
How many local landing pages should I have?
As many as you can make genuinely useful, and no more. For a single-office service business, that's often just the home city plus a few nearby places with real demand and real jobs.
Can I use the same template for every city page?
Yes, the layout can be shared. The content inside it can't be. A shared structure with different proof, photos, details and FAQs is fine. A shared structure with the same paragraphs is the problem.
I don't have an office in a city I want to rank in. Can I still have a page?
You can, if you genuinely work there and can show it with projects, reviews and specifics. Just don't imply an office you don't have. And be realistic: in Google's local results, distance from the searcher still matters.
If you'd like help deciding which places deserve a page, and building the ones that do, that's core to our local SEO work. We'll start with your data, not a radius on a map.


