Ads & SEO
City pages for service businesses: when they help and when Google sees spam
When city pages bring real calls, when Google treats them as doorway spam, and a simple test for deciding which towns deserve their own page on your site.
City pages help a service business when you genuinely work in that town and the page says something about that town nobody could copy-paste onto the next one: the jobs you've done there, the local conditions that shape the work, how fast you get there. They turn into spam when the page is a template with the city name swapped in. Google's own spam policies describe that second kind almost word for word, and a site full of them can lose rankings it already had. The difference isn't the number of pages. It's whether each one would be worth reading if search engines didn't exist.
What Google actually says about location pages
Google's spam policies have a section on "doorway abuse", defined as "sites or pages created to rank for specific, similar search queries" that lead people to pages that aren't as useful as the final destination. Among the examples Google lists:
- "Having multiple domain names or pages targeted at specific regions or cities that funnel users to one page"
- "Creating substantially similar pages that are closer to search results than a clearly defined, browseable hierarchy"
The same document covers "scaled content abuse": many pages generated mainly to manipulate rankings, "no matter how it's created." It names generating pages with AI tools without adding value, and automated rewording or translating, as examples.
Read those together and the line is clear. Google doesn't object to a page about your work in Laval or Red Deer. It objects to forty pages that differ only in the town name.
Why city pages can work at all
It helps to separate the two places a local search shows results.
The map results (the "local pack") are driven by your Google Business Profile. Google says local ranking is based mainly on relevance, distance and prominence. Distance is measured from your business to the person searching, and no page on your website changes where your business is. A city page will not put you in the map pack of a town 40 km away.
The regular results below the map are where city pages earn their keep. Someone searching "basement waterproofing Whitby" may scroll past the map, or the map may show businesses that don't do that job well. A strong, specific page about waterproofing in Whitby can rank there, even if your shop is in Oshawa.
So city pages are an organic search tactic, not a map tactic. Set your expectations accordingly.
The test: would this page exist without Google
Before writing any city page, answer these five questions for that town:
- Have we done real work there? Jobs, clients, addresses you can describe (without naming customers who didn't agree to it).
- Is there something local that changes the job? Older housing stock, clay soil, municipal permit rules, hard water, a lot of condos versus detached homes, rural properties on wells.
- Do we have local proof? Photos from projects there, reviews from customers in that town, a contract with a local building or institution.
- Is the logistics answer different? Travel time, minimum job size, scheduling days, emergency coverage.
- Would a resident learn something they can't learn on our main service page?
If you can't answer yes to at least three, don't build the page. Mention the town on a broader service-area page instead.
Good city page versus doorway page
| Element | Genuinely useful | Doorway pattern |
|---|---|---|
| Opening paragraph | Names the specific problems you see in that town | "Looking for the best plumber in [City]? Look no further." |
| Body text | Written for that town, different structure where it makes sense | Same 600 words with the name swapped 12 times |
| Photos | Projects actually done there | Stock photos, or the same photos on every page |
| Reviews | From customers in that town, if you have them | The same five testimonials everywhere |
| Practical details | Travel time, which days you're in the area, permit notes | None |
| Links | Reached from a service-area hub, and links to relevant services | 80 town links crammed into the footer |
| Count | A handful of towns where you do real volume | Every town within 200 km |
A useful example
Here's the opening of a roofing company's page for a suburb with a lot of 1970s split-levels:
Most homes we work on in Brookfield were built between 1972 and 1985, and many are on their second or third roof. The low-slope sections over split-level additions are where we find most of the leaks. Over the last three seasons we've replaced 31 roofs here, and the photos below are from those jobs.
Every sentence there is specific, checkable and useful to a homeowner. You couldn't move it to the next town without rewriting it.
A doorway example
Welcome to ABC Roofing, the top roofing company in Brookfield! Our Brookfield roofing experts provide the best Brookfield roof repair and Brookfield roof replacement services. Call today for your free Brookfield roofing quote!
Swap "Brookfield" for any town and nothing changes. That is exactly the "substantially similar pages" pattern Google describes.
What to put on a city page that earns its place
A good city page usually has most of these:
- A plain opening stating what you do there and since when.
- Local conditions that affect the job, written by someone who has done it.
- Two or three recent projects in that town, with photos and one or two sentences each: the problem, what you did, how long it took.
- Reviews from that town, quoted accurately with the reviewer's first name or initials, if they're public on Google.
- Practical answers: how quickly you can usually come, whether there's a travel fee or minimum, which days your crew is there.
- Local rules if relevant: permits, bylaws, utility rebate programs, condo board approvals. Link to the official source rather than paraphrasing it badly.
- Links to the related service pages and back to your service-area overview.
Length follows content. A page with 400 words of real specifics beats one with 1,500 words of filler.
How many city pages to build
Start from your job records, not from a map. Sort last year's jobs by town and look at where the volume and margin really are. A common pattern for a small service company:
- Your home town: covered by your homepage and service pages. A separate city page is often redundant.
- Three to eight nearby towns where you do regular work: these get their own pages.
- Everything else in range: listed on one service-area page, grouped by region, with a sentence about each area if you can say something true.
Add a new city page when you have the projects and photos to make it real, not before. Writing it after you've done ten jobs there is easier and the page is better.
Keep your service area consistent everywhere. Google's Business Profile guidelines say a service area "shouldn't extend farther than about 2 hours of driving time from where your business is based." If your website claims towns four hours away, you're signalling something your profile can't back up, and customers there will be disappointed when you can't come.
Site structure that keeps it clean
- Put city pages under one folder, for example
/service-areas/brookfield/. - Build one hub page at
/service-areas/that lists them with a short description each. - Link to the hub from your main navigation or footer, not to every town individually.
- If you offer several services, don't build a page for every service in every town. "Roofing in Brookfield" plus "Siding in Brookfield" plus "Gutters in Brookfield" is how sites end up with 300 near-identical pages. One page per town that covers your services there is usually enough.
- If your site is bilingual, each language version should be a real page written for that audience, not a machine translation of a template.
Cleaning up an existing pile of city pages
Plenty of sites already have dozens of thin location pages from an old SEO package. To clean up:
- Export the list of location pages and check which ones get any search traffic or leads in your analytics and Search Console.
- Keep and rewrite the few that get traffic and match real work.
- Merge the rest into your service-area hub, and redirect each removed URL (a 301 redirect) to the hub or to the closest real page.
- Remove the footer link block that pointed to all of them.
- Watch Search Console for a few months. Some impressions for long-tail town queries will drop, which is expected; leads are the number that matters.
Google's guidance on helpful content asks whether you're "producing lots of content on many different topics in hopes that some of it might perform well." A pile of template town pages is a textbook case. Trimming them is rarely the risk people fear.
When not to bother
- You serve one compact city and its suburbs. Good service pages will cover it.
- You haven't done work in the town yet. Wait until you have something to show.
- You want to appear in the map pack in a town where you have no location. A city page won't do that; distance is part of how local ranking works.
- You're tempted to buy a tool that generates hundreds of pages. That is close to the definition of scaled content abuse.
Where PNE fits
PNE Solutions handles digital marketing for service businesses, including local SEO, Google Business Profile work and site structure, and we usually start by checking which towns actually produce jobs before writing a single page. If you serve smaller communities, our guide to local SEO for small towns and rural Canada covers the thin-market side of the same problem.