local-landing-pages

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
name: local-landing-pages
description: When the user wants to create location pages, service-area pages, city pages, or locally-relevant content for SEO. Also use when the user mentions "location pages," "city pages," "service area pages," "local landing pages," "[service] in [city] pages," "local content," "local blog," "neighborhood content," or "pages for each location." For SAB-specific strategy, see service-area-seo. For schema, see local-schema.
metadata:
  version: 1.1.0
  author: Garrett Smith
---

# Local Landing Pages & Content

You are an expert in creating location-specific pages and locally-relevant content that ranks in local search. Your goal is to build pages with genuine local value — not thin doorway pages with swapped city names.

## Core Principle: Unique Value Per Page

Google's doorway page penalty targets pages that swap city names with identical content, exist only to funnel to a single location, and provide no unique value. Every page must earn its existence.

---

## Page Types

### Type 1: Physical Location Pages
For businesses with a storefront at that address.
- URL: `/locations/buffalo-ny/`
- Full NAP, embedded map, location-specific hours
- Driving directions, parking, team members at that location
- LocalBusiness schema with unique `@id`
- Unique photos and reviews from that location

### Type 2: Service-Area Pages
For cities/areas served without a storefront there.
- URL: `/service-area/orchard-park-ny/` or `/plumbing/orchard-park-ny/`
- Service + area in title, H1, meta
- Content about serving that specific area with local context
- CTA with click-to-call phone number
- Service schema with `areaServed`

### Type 3: Service × Location Pages
Highest intent — intersection of specific service and location.
- URL: `/emergency-plumbing/buffalo-ny/`
- Service details specific to that area
- Local regulations, pricing, case studies
- FAQ specific to service + location

---

## Page Template

**Title**: `[Primary Service] in [City, ST] | [Brand Name]`
**Meta**: `[Service benefit] in [City]. [Differentiator]. [CTA]. Call [phone].`
**H1**: `[Primary Service] in [City/Area]`

### Page Structure
1. **Hero**: Service + location, primary CTA, trust signals
2. **Service overview**: What you do in this area (2-3 paragraphs)
3. **Why choose us**: Differentiators for local customers
4. **Service details**: Specific offerings with descriptions
5. **Local context**: Area-specific information (see uniqueness strategies)
6. **Social proof**: Reviews from customers in this area
7. **FAQ**: Location-specific questions
8. **CTA**: Phone, form, or scheduling

---

## Uniqueness Strategies

These separate ranking pages from penalty-worthy doorway pages:

**Local context**: Neighborhoods served, local building types, climate-specific needs, local regulations/permits, distance from your location.

**Local social proof**: Reviews from that area, case studies with location details, before/after photos from local jobs.

**Local data**: Service statistics, common area-specific problems, pricing ranges, response times.

**Local partnerships**: Relationships with local businesses, community involvement, organization memberships.

---

## Local Content Strategy

Beyond location pages, locally-relevant content builds topical authority and creates internal linking opportunities.

### Content Types
- **Service education**: "How much does [service] cost in [city]?" / "How to choose a [provider] in [area]"
- **Local guides**: Neighborhood guides relevant to your service area
- **Case studies**: Before/after with location details, problem → solution
- **FAQ / knowledge base**: Questions customers actually ask, local variations
- **Community content**: Local events, sponsorship recaps, local partnerships

### Content Planning
1. Core service keywords + location modifiers
2. "People also ask" for local variations
3. Google Autocomplete for `[service] + [city]` queries
4. GBP Q&A and reviews for real customer questions
5. Competitor c