Location-specific landing pages exist for service areas

A multi-area business served by a single homepage competes for every [service] in [city] query with one generic page, which loses to competitors who operate a dedicated page per service area. Google's local ranking weighs on-page geographic relevance; without per-city content it has nothing to match against long-tail local queries. The findability taxon applies directly — the pages that do not exist cannot rank, and the homepage cannot rank for cities it never mentions.

Create a dynamic route at app/locations/[city]/page.tsx that generates a unique page per service area from a data source. Each page needs genuinely local content — neighborhood names, local projects, area-specific pricing — not a templated page with only the city name swapped. Thin duplicates are treated as doorway pages and demoted.

export async function generateStaticParams() {
  return cities.map((city) => ({ city: city.slug }))
}