Local landing page

Long definition

A local landing page exists to rank for one geo-modified query (or a tight cluster of them) and to convert the user once they land. The two jobs are tightly coupled: a page that ranks but doesn't convert wastes the click, and a page that converts beautifully but doesn't rank gets no clicks.

The required elements for both jobs:

• Identity — visible NAP matching the location's Google Business Profile, hours of operation, and a clear primary CTA (call, book, directions).
• Geo-anchored content — H1 and title tag with location and service, body content referencing local landmarks, neighborhoods, or events, embedded Google Map of the location, photos taken at or near the location.
• Trust signals — reviews specific to that location (not the homepage's mixed pool), staff named and pictured, certifications relevant to the locale.
• Schema — LocalBusiness (or a more specific subtype like Dentist, Plumber) with address, geo, openingHoursSpecification, and aggregateRating when third-party review data is available.
• Internal linking — included in the site's main location index, linked from the homepage's location selector, cross-linked from related city pages.

The single most common failure is the "templated near-duplicate" — 50 location pages where only the city name and address change. Google's spam policies and Helpful Content System target this pattern explicitly. The differentiation that survives audit is local truth: the actual phone, the actual staff, the actual reviews, the actual stories of work done in that location.

Distance-based heuristics matter for content depth. A landing page for a single physical office should be richer than a service-area page for a region the SAB visits — the office page is the canonical location of the entity, the service-area page is a directory entry into one of many areas served. Both have a place; treating them identically is what produces thin-content classifications.

URL structure is usually /locations/<city> or /<service>/<city>. Either works. What matters is that each URL maps to one entity-location combination, the slug is geo-modified, and the page is reachable in two clicks from the homepage.

Common misconceptions

• "One page per city is enough." For multi-service operators, the unit is location × service, not just location. A dentist with implants and orthodontics in three cities probably needs six or nine pages, not three.
• "Templated pages with city name swaps work fine." They rank briefly and crash on the next core update. Doorway-page enforcement and the Helpful Content System target exactly this pattern.
• "Embedding a Google Map boosts rankings." It improves UX and conversion. The ranking signal comes from on-page geo-relevance and the wider local-SEO ecosystem (citations, GBP, reviews) — not the iframe itself.
• "You can scale to 1,000 location pages with AI-generated content." Google's spam policy explicitly addresses scaled, low-effort content. Quality bar is per-page; volume without truth fails.