Building forty city pages without them reading as the same page forty times.

Why the naive approach gets suppressed

Taking one template and find-replacing the city name produces pages that are word-for-word identical apart from a proper noun. Google's systems are built specifically to detect this pattern and will typically keep only one version in the index, usually not the one you wanted.

The fix is not writing forty completely unique essays from scratch. It is building a template with enough genuinely variable content blocks that each page earns its own reason to exist.

What actually varies between city pages

Local service area detail, real neighbourhood names, region-specific pricing or regulatory notes, and locally relevant FAQs all give a page substance that a city name swap does not. If you have technicians or staff based in a city, name them and their coverage area specifically.

Pull in structured data that is genuinely different per location: local reviews, local project photos, local phone numbers with area codes, and driving distance or service radius from that city.

Internal linking and hub structure

Build a single hub page listing all city pages with real descriptive anchor text, and link each city page back to relevant service pages and neighbouring city pages. This gives search engines a clear signal about the hierarchy instead of forty orphaned pages competing with each other.

Avoid linking every city page to every other city page in a flat mesh. That dilutes relevance signals and looks manipulative at scale.

Content governance as you scale past forty

Set a minimum bar for launching a new city page, such as a threshold number of completed jobs or reviews in that area, so you are not publishing empty shells purely for coverage. A smaller number of substantive pages consistently outperforms a large number of thin ones.