Local Landing Pages

A local landing page is a dedicated page on a multi-location business’s website targeting a specific city, region, or service area. Done well, local landing pages give each location independent ranking potential for local queries. Done badly, they create a thin-content footprint that Google’s spam policies treat as doorway abuse, and the usual outcome is that the pages drop out of the index.

When local landing pages are needed

Multi-location businesses. A chain of physical locations, each serving a defined catchment. Each location warrants its own page so it can rank for queries in its area.

Service-area businesses. Tradespeople, delivery services, and consultants who serve customers across multiple cities or regions without a physical premises in each. Landing pages can establish geographic relevance for areas where you don’t have a physical address.

Franchise or distributed networks. Businesses where each location operates semi-independently. Local landing pages support both individual location SEO and the broader brand’s local pack visibility.

When you don’t need local landing pages

Single-location businesses. A business with one physical location doesn’t need separate city pages; the homepage and About/Contact pages cover the location adequately.

Online-only businesses without local relevance. SaaS products, ecommerce stores without local pickup, and other purely digital businesses don’t benefit from local landing pages.

Businesses without genuine presence in claimed locations. Creating “we serve Manchester” pages for a business with no real Manchester presence (no clients, no projects, no service capability) is the pattern Google’s spam policies describe as doorway abuse.¹ Asked directly about building 1,300 city landing pages, John Mueller replied: “That sounds like doorway pages, not something I’d recommend.”² Google’s policy does not use the language of presence or penalties, so treat this as a strong signal about how the pattern is viewed rather than a documented enforcement threshold.

What makes a local landing page work?

The single most reliable predictor of whether a local landing page ranks: it has unique, locally-relevant content that wouldn’t apply identically to any other location.

The concrete patterns:

Location-specific information. Address, phone, opening hours, photos of the actual location, named local team members, parking and transport details. Generic landing pages with only the city name swapped in don’t rank.

Locally-relevant case studies or projects. Examples of work completed in the local area, with named clients (where possible) and project details. Establishes genuine local presence.

Local market context. Information about the specific area’s market, regulations, conditions, or considerations. A solicitor’s London page might cover relevant local courts; a roofer’s Edinburgh page might cover local stone-and-slate considerations.

Local citations and inbound links. Links from local newspapers, chambers of commerce, regional directories. The off-site profile reinforces the on-site signal.

Locally-focused testimonials. Reviews and testimonials from named local customers. Stronger trust signal than generic reviews.

Specific service area description. Not “we serve London”; “we serve London Zones 1-3, with response times under 2 hours in central London”. Specificity is credibility.

Templated local pages

The most common failure mode in local landing page strategy is templated content. The pattern:

1. One template with [city name] as a placeholder
2. Auto-generated 200-500 pages, one per city in a list
3. Identical content except the city name

Google’s spam policies cover this under doorway abuse, defined as sites or pages “created to rank for specific, similar search queries” that “lead users to intermediate pages that are not as useful as the final destination”. The listed examples include “having multiple domain names or pages targeted at specific regions or cities that funnel users to one page” and “creating substantially similar pages that are closer to search results than a clearly defined, browseable hierarchy”.¹

Since March 2024 a second policy also applies: scaled content abuse, covering “many pages generated for the primary purpose of manipulating search rankings and not helping users”, explicitly “no matter how it’s created”.¹ That closes a loophole worth naming, because “each page needs unique content” is often read as “hand-write it and you’re safe”. Under this policy the test is whether each page is useful to a reader, not whether a human or a script produced it.

Be careful about the mechanism, though. Core updates are not the enforcement route: Google states they “don’t target specific sites or individual web pages”, and its own analogy is that sites moving down “aren’t necessarily bad”.³ Doorway and thin-content problems are handled through the spam policies and, where enforcement is manual, through the “Thin content with little or no added value” manual action, whose examples list doorways explicitly.⁴

Location pages generated this way are a form of programmatic SEO, and they carry the same thin-content risk: the template must add genuinely distinct value per page, not just swap a variable. The fix is not impossible but it isn’t cheap. For businesses with hundreds of locations, this is real editorial work, not a content-generation script.

How the failure actually shows up

In practice the symptom is not a ranking penalty but disappearance from the index. Search Engine Land documented this across a large group of service-area business sites after Google’s late-2022 helpful content and spam updates: “sites weren’t getting directly penalized by rank. Instead, pages were being automatically deindexed, which in turn caused ranks to drop for queries related to the corresponding location pages.”⁵

That makes indexation the thing to watch, not rankings. In Search Console, filter the Pages report to the location path and look for Crawled, currently not indexed and Duplicate without user-selected canonical. A cluster of location pages sitting in either state is the earliest clear signal that Google has judged the set thin, and it shows up before the traffic decline does.

Structure for a local landing page

A workable template (with the understanding that the actual content per page must be unique):

Title and H1. “Service in City” pattern. “Plumbing Services in Bristol” or “SEO Consultancy London”.

Introduction paragraph. What service is offered in this city; what makes the local team or local market specific.

Location details. Address, phone, opening hours, embedded map. For service-area businesses, the service area description.

Services offered. Either the standard service list or a locally-customised version highlighting services particularly relevant to this area.

Local case studies or examples. Genuine local work with as much specificity as can be shared.

Local team. Named individuals based at this location, with photos and brief bios.

Local testimonials. Reviews from customers in this city.

FAQs. Locally-relevant questions (parking, transport, opening hours, area-specific considerations).

Schema markup. LocalBusiness schema with the specific location’s NAP and opening hours. Only name and address are required; geo, telephone, url, and openingHoursSpecification are recommended.⁶ Service-area data belongs in the Business Profile, where Google demonstrably consumes it, rather than in schema. One trap to avoid: don’t mark up your own testimonials. Google’s review snippet guidance states that where “the entity that’s being reviewed controls the reviews about itself”, pages using LocalBusiness or any other Organization type “are ineligible for star review feature”.⁷ Local testimonials are still worth publishing for readers, but they can’t carry review markup.

Local landing pages and Google Business Profile

A local landing page should be linked from the corresponding GBP listing’s website field. This connects the on-site presence with the GBP listing and reinforces the local signal in both directions.

For multi-location businesses, every GBP listing should point to its specific local landing page, not the generic homepage. Pointing all GBP listings to the homepage misses the chance to associate each location with its specific page.

Local landing pages and AI search

Two things are worth separating here, because the headline figure and the practical implication point in different directions.

The headline is that AI Overviews are common in local searches. Whitespark’s May 2025 study of 540 queries across three US cities and six industries found that AI Overviews appear in 68% of local business queries.⁸ That aggregate is the number usually quoted.

The intent split matters more. In the same study, AI Overviews appeared for only 15% of local-intent queries, while local packs appeared for 93% of them. The relationship inverts for informational queries: AI Overviews 92%, local packs 6%.⁸ So for the transactional “[service] in [city]” queries a location page exists to serve, the local pack and the standard organic result still dominate. AI Overviews show up on the research-stage questions around them.

That argues for a split approach rather than a rewrite. Keep location pages built for transactional local intent, and treat the informational questions in each market (costs, regulations, how to choose a provider) as the material with AI Overview exposure.

Google’s local AI answers also draw mainly on Maps data rather than on your site. Grounding with Google Maps, generally available since September 2025, connects generative applications to “over 250 million businesses and places worldwide”, including daily-updated details such as current hours and whether a shop is temporarily closed.⁹ For Google’s AI surfaces, the Business Profile record is the primary representation of a location, and the landing page supports it rather than replacing it. This applies to Google’s own systems; other AI platforms retrieve local information differently.

Common local landing page mistakes

Mistake	Effect
Templated pages with city-name swaps only	Deindexing; doorway abuse under Google’s spam policies
Pointing all GBP listings to the homepage	Missed page-level local relevance
No NAP on the local landing page	Weak local signal
Generic stock photos instead of real location imagery	Reduced credibility; weaker engagement
Same testimonials across all location pages	Templated appearance
Service area pages for areas you don’t actually serve	Doorway page risk

Scaling local landing pages

For businesses with many locations, the editorial cost of unique content per page is real. Practical approaches:

Tiered investment. Top-revenue locations get fully bespoke pages; mid-tier locations get partially customised pages with a stronger common framework; long-tail locations get a minimal page or share a regional page.

Local input. Each location’s manager or team contributes content (testimonials, photos, project details, local team bios). The central team handles structure and editing.

Phased rollout. Don’t launch 500 location pages on day one. Start with a smaller set, demonstrate they rank, then expand.

Auditing existing pages. Many businesses have inherited templated location pages from earlier SEO efforts. Auditing these usually produces lift before any new pages are written, and consolidation is often the higher-return move: redirect the thin pages into a single regional page covering the same catchment, and keep the ones with genuine local substance. Given that the typical failure is deindexing rather than a penalty, cutting 200 near-duplicate pages down to 30 real ones tends to help the 30.

How do you tell whether a location page is working?

Location pages are expensive to do properly, so gate the spend on evidence:

• Indexation first. The Search Console Pages report filtered to the location path. An unindexed page cannot rank, and this is where the thin-content failure surfaces first.
• Page-level Search Console performance filtered to queries containing the city name, which separates genuine local demand from brand and generic traffic.
• Business Profile performance for the profile linked to that page: calls, direction requests, and website clicks.
• Geo-grid rank tracking for the pack, since a single rank check won’t show how visibility varies across a catchment.

A page that has been live for two quarters with no indexed status, no city-modified impressions, and no profile activity is a candidate for consolidation rather than further investment.

Frequently asked questions

Can I rank a local landing page without a physical address in that city?
Yes, in standard organic results for “[service] in [city]” queries. Service-area businesses can also appear in local packs, so the common claim that they can’t is wrong. The real constraints are Google’s service-area rules: a service-area business gets one profile for the whole area it serves, you can’t define that area as a radius, you can list up to 20 service areas by city or postcode, and the overall boundary “shouldn’t be more than about 2 hours of driving time” from where the business is based.¹⁰ Within those limits, distance from the searcher still governs pack visibility. The bar for genuinely useful, locally-specific content is higher when there’s no physical presence to back it up.

How many local landing pages should I have?
As many as you have genuine local presence to support. A national franchise with 200 locations should have 200 pages. A small business serving three cities should have three. Don’t manufacture pages for areas you don’t really serve.

Should each local page be in a separate URL structure?
Yes. /locations/london/, /locations/manchester/, and so on. This keeps the set organised for internal linking and sitemaps, and gives you a clean path to filter on in Search Console. Google frames readable URLs in comprehension terms rather than as a ranking signal,¹¹ so don’t expect the pattern itself to move rankings.

Footnotes

1. Spam policies for Google web search — Google Search Central ↩ ↩² ↩³

2. Google: 1,300 City Landing Pages Sounds Like Doorway Pages — Search Engine Roundtable ↩

3. Google Search’s core updates — Google Search Central ↩

4. Manual Actions report — Google Search Console Help ↩

5. Location pages in Google’s crosshairs after October spam update — Search Engine Land ↩

6. Local business (LocalBusiness) structured data — Google Search Central ↩

7. Review snippet structured data — Google Search Central ↩

8. Case study: the prevalence of AI Overviews in local search — Whitespark ↩ ↩²

9. Your AI is now a local expert: Grounding with Google Maps is now GA — Google Developers Blog ↩

10. Manage your service areas for service-area and hybrid businesses — Google Business Profile Help ↩

11. Keep a simple URL structure — Google Search Central ↩