Most service businesses operate in multiple cities. A plumber based in Denver also takes jobs in Arvada, Westminster, Lakewood, and Aurora. An HVAC company headquartered in Nashville covers a 40-mile radius. A roofing contractor has trucks in three counties.
The question is always the same: how do you rank in all those places when you only have one Google Business Profile address?
The answer is location pages — city-specific pages on your website built to rank organically for searches like "plumber in Aurora CO" or "HVAC repair Lakewood." Done right, they extend your footprint into every city you serve. Done wrong, they get treated as doorway page spam and suppressed.
The difference between the two comes down to a handful of decisions that most businesses get wrong.
What Location Pages Are (and What They're Not)
A location page is a dedicated page on your website targeting service searches in a specific city you serve. Its job is to rank for "[service] + [city]" queries and convert that traffic into calls or form submissions.
What a location page is not: a template page where you swapped the city name. Google has a name for those — doorway pages — and it has specific guidance penalizing them.¹
Google's doorway page policy targets pages "created solely to funnel traffic to another page" and pages that provide "substantially the same content" with only superficial geographic variation. If your Arvada plumbing page and your Westminster plumbing page are identical except for the city name in the headline and meta title, you've built doorway pages. Google knows. It suppresses them.
The practical test: if you removed the city name from the page, would it still contain genuinely different content from every other location page on your site? If the answer is no, the page isn't earning its place.
The Signals That Separate a Real Location Page from Thin Content
Google is specifically evaluating whether a page was built for a real audience in a real place, or built to manipulate rankings.
Community context. Real location pages include references that demonstrate actual familiarity with the area — neighborhood names, local landmarks, regional climate factors that affect the service, nearby municipalities the contractor also covers. A legitimate roofing page for Boise, Idaho might reference the weight load requirements from winter snowpack in the Treasure Valley. That's a detail that can't be copy-pasted from a template.
Local social proof. Reviews from customers in that city, case study references ("We replaced the ductwork in a 1970s ranch on the East Bench last winter"), or testimonials that mention local neighborhoods anchor the page to a real service history in that area.
Unique service context. Different cities can have genuinely different service conditions: water hardness variations that affect plumbing, soil types that affect irrigation or foundation work, permit requirements that vary by municipality. If those differences exist, your location page should address them.
Consistent NAP signals. The page should clearly state your business name, phone number, and the service area it covers. The phone number and business name must match your Google Business Profile exactly. NAP inconsistencies across location pages and your GBP are a trust signal problem.
LocalBusiness schema. Each location page should include a schema block that encodes the specific service area, your business name, phone, and address. This gives Google machine-readable confirmation that the page is about a real business serving a real geography. The schema markup guide covers the exact types to use — for trade businesses, use the industry sub-type (Plumber, HVACBusiness, RoofingContractor) rather than the generic LocalBusiness type.
How to Structure a Location Page
A location page is not a homepage with the city swapped in. It has a specific structure designed to satisfy both the search engine signal requirements and the user who lands on it.
H1: Service + City. Keep it literal. "Plumbing Services in Aurora, CO" or "HVAC Repair and Installation — Westminster, Colorado." This is not the place for clever taglines. The H1 and title tag tell Google exactly what query this page answers.
Opening section: What you do in this specific city. Two to three paragraphs on your service offering in that location. Mention the city naturally — not keyword-stuffed, but genuinely. Name the types of jobs you take there. If you have a local insight (older home stock, common issue patterns), lead with it.
Community context section. This is the content that makes the page real. Reference the neighborhoods you serve within that city. Mention local landmarks if they're relevant to service coverage. Include a sentence or two about the area that only someone who actually works there would write.
Social proof. At minimum, a review or testimonial from a customer in that city. Ideally two or three, pulled from your Google reviews and attributed. If you don't have reviews from that specific city yet, this section can reference a relevant case study from nearby work.
Services section. A clear list of every service you offer in that location. This is also where you cross-link to your service pages — the location page and the service page reinforce each other.
CTA. Phone number, contact form link, or both. Make the next step obvious.
FAQ. Three to five questions specific to that market: "Do you serve [nearby neighborhood]?", "Are you licensed in [state/county]?", "What's your service call fee in Aurora?" FAQs drive FAQ schema markup and answer the specific questions searchers in that city are asking.
How Many Location Pages to Build and in What Order
Don't create location pages for every city in your state. Create them for cities where you can realistically win business and where search demand exists.
Start with your highest-revenue markets. Where do you already have the most jobs, the most reviews, and the most word-of-mouth? Build those pages first. A location page for a city where you've done 50 jobs is more credible than a page for a city where you've done two.
Tier your targets. Group your service area into primary cities (high population, real search volume, you actively work there), secondary cities (suburbs and adjacent markets, moderate volume), and tertiary markets (smaller towns, lower volume, you'll serve if called but don't actively prospect there). Build pages in that order.
Set a minimum content bar. If you can't write 400 words of genuinely unique content about serving a specific city — real community context, real service history — don't build the page yet. A thin location page that gets suppressed is worse than no page. Earn the page by doing real work in the market first.
Realistic targets: Most local service businesses need 5–15 location pages. Businesses with large regional operations might need 20–30. If someone is recommending you build 100 location pages from a template, they're recommending doorway pages.
The Connection Between Location Pages and Map Pack Rankings
Your Google Business Profile ranks in the Map Pack based on three factors: relevance, distance, and prominence.² Distance is the one you can't change — Google anchors your GBP to your registered address, and businesses physically closer to the searcher rank higher in the local pack.
Location pages work alongside your GBP, not instead of it. They target organic rankings for city-specific searches where distance is less determinative. When someone in Aurora searches "plumber near me," your GBP distance matters most. When they search "plumber in Aurora CO" or "Aurora plumbing company," organic results compete with the Map Pack — and a strong location page can rank in both the organic results and influence how Google weighs your overall prominence for that city.
The full mechanism is covered in How to Rank in Google Maps, but the key point is this: location pages build topical and geographic relevance signals for your website, which feed back into how Google evaluates your GBP's authority in a market. They're complementary, not competing.
The Mistakes That Get Location Pages Suppressed
The city-swap template. You build one page, swap the city name in the H1 and meta title, and publish 20 versions. Google identifies the duplication through content fingerprinting and either ignores the pages or treats them as doorway content.
No local signals. A page that mentions "Aurora" in the headline and then says nothing else specific to Aurora reads as a template to both users and Google's quality evaluators. Community context isn't decoration — it's the primary signal that the page was built for a real audience.
Missing or malformed schema. Location pages without schema miss the machine-readable trust signal that tells Google this page represents a real business serving a real geography. This is one of the highest-leverage technical fixes on any location page — 15 minutes of schema work per page.
Not linking internally to location pages. Location pages that aren't linked from your homepage, service pages, or navigation don't accumulate the authority they need to rank. Build a service area hub page that links out to all your location pages, and make sure your homepage footer or navigation links to your primary markets.
Treating them as landing pages, not content pages. A location page is not an ad. It should read like a resource for someone in that city who is evaluating whether to hire you — not like a PPC landing page designed to capture a lead in four seconds. Depth of content correlates with rankings. The Local SEO Checklist 2026 treats location page content depth as a distinct audit item for exactly this reason.
Want a professional assessment of where you stand right now? Run your free SEO audit → — it scores your GBP, citation consistency, review profile, schema markup, and 5 other categories in under 5 minutes.
This framework is drawn from Chapter 15 of the AI-First Authority Framework™ — the full chapter includes the location page template, the city prioritization worksheet, schema block code for each trade type, and the internal linking architecture for a 10–30 page service area footprint. Get the complete 21-chapter framework at /playbook.