Should I make a page for each city I serve?

When location pages make sense

Location pages help when you genuinely serve several distinct places and people search by place name. A Calgary roofer working in Airdrie, Cochrane and Okotoks may get searches like “roofer Airdrie” that the main site doesn’t rank for. A page about Airdrie, with Airdrie jobs, can.

They also make sense for businesses with more than one physical location. Each office deserves its own page with its address, hours, team and directions.

What makes one useful, not thin

• Real projects or clients in that area, with photos.
• Details that only apply there: local permit quirks, common home types, travel times.
• Reviews from customers in that place.
• Answers to questions locals actually ask.

If you swap “Airdrie” for “Cochrane” and the page still reads the same, it’s thin content. Google’s guidance on helpful content and spam policies on doorway abuse both work against near-identical pages, and they can weaken trust in the whole site.

Start small and expand

Begin with your main city on your core service pages. Add a location page only where you have real work and real demand, and where you can write something worth reading. Link each one from a clear “areas we serve” section and from relevant service pages. A few strong pages beat dozens of hollow ones. Industry pages like landscapers or renovation contractors show how this varies by trade.

I build location pages only when a client has real work to show in that area. For a contractor, that might mean three pages for Calgary, Airdrie and Okotoks, each with projects, photos and notes specific to the place, not thirty pages generated from a template. When I do build pages at scale, each one has to carry unique, useful content. If we can’t say anything distinct about a town, I’d rather mention it in a service area list and leave it there.