Pages for Multiple Cities: When You Need Them and What Content They Should Have

City pages are almost always built the same way: you take the service page, swap the place name, and repeat it for twenty towns. The result is twenty pages saying the same thing, that no one reads to the end, and that give no one — not a search engine, not a reader, not a system generating answers — a reason to prefer any one of them. This guide exists to decide which local pages have content of their own and which shouldn’t exist.

Three different things we call “location”

The confusion starts before the writing, when a single list of cities is compiled by lumping together situations that have nothing in common.

• The location: where you physically are, with an address, people, and hours. It’s a fact, and it’s the basis of your local presence.
• The service area: where you go to work. It can be a province, a region, a radius in kilometers, and doesn’t imply an address in every town.
• The commercial target: the areas where you’d like to work more. It’s a goal, not a reality, and it’s the one that generates the worst pages, because there’s nothing to tell yet.

Locations and service areas have genuine content from the start. A commercial target only has content once you’ve started working there: until then, a page that pretends otherwise is a risk, not an investment.

The test: what would actually change

Before opening a page for a city, try writing the list of what would be different from the general page. If after five minutes the list contains only the town’s name, the page isn’t needed.

• Does the need change? In an area of historic buildings and one of warehouses, people ask the same installer different things.
• Does the way of working change? Response times, days on site, same-day site visits, limited-traffic zones, access difficulties.
• Do the rules change? Local constraints, permits, the practices of a municipal office: these are the kind of content no competitor can copy, because they require having actually worked there.
• Do the references change? Jobs done there, citable references, collaborations with local businesses.

Two solid answers out of four are enough to justify a page. With zero answers, you don’t start writing: you choose an area page instead.

Two pages compared

The example that follows is illustrative and concerns a systems company based in one city with activity across two provinces.

The right-hand column isn’t weak because it’s “duplicated” in a technical sense. It’s useless because it doesn’t answer any question the general page doesn’t already answer.

The local content that can be proven

The material for a credible local page already exists inside the company, but it’s written nowhere: it’s in the heads of the people who work there.

• Jobs done in the area, with the problem addressed and the context. If the client doesn’t want to be named, the case can be told without the name and still be useful.
• Real operating conditions: when there’s a team in the area, how long it typically takes to arrive, which jobs get done same-day and which don’t.
• The recurring questions from that territory, collected by whoever answers the phone. It’s the best source and the least used.
• Verifiable references: local vendors and partners, associations, event presence. Only if they’re real and checkable.

If gathering this material for a city takes someone who’s been there half an hour, the page can be made. If it requires inventing it, it can’t.

When an area page is the better choice

The area page — a province, a region, a district — is the right choice far more often than people think, and it isn’t a compromise.

• It honestly covers what you do: you work across the whole province, and you say so.
• It concentrates the proof instead of diluting it: three jobs told well on one page are worth more than three lines spread across twenty pages.
• It’s maintainable. Twenty local pages would need to be updated twenty times, and in practice they never will be.

If in the future a city genuinely becomes important — a location, a team, a number of jobs you can show — then you spin off its own page, with the material that’s accumulated in the meantime. That’s the right sequence: the work first, then the page.

How the local pages fit together

Even when they’re justified, how the pages link to one another changes how useful they are.

• The general service page stays the reference: the local ones tell the service in that context, they don’t re-explain it from scratch.
• Links between local pages should be kept few and sensible. A list of forty towns at the bottom of the page doesn’t help the reader and convinces no one.
• Titles and descriptions are written one by one. If they’re generated by swapping a single word, that’s proof the content is too.
• Every local page must stand on its own: it says what you do, where, with what proof, and how to get in touch.

What this guide doesn’t cover

This decides which pages by location make sense and what they should contain. What someone searching for a business in their area should find outside the site — listings, maps, up-to-date operational information — is covered separately. The case of two existing pages already saying the same thing, and the choice of whether to merge or differentiate them, also has its own guide.