Service Area Pages for Contractors: Rank Without Doorway Pages

That definition sits in Google's spam policies, last updated August 28, 2026 when we checked. Two of its four examples describe the classic contractor mistake: a page per city, each a near-copy, each funneling to the same contact form.

The same page covers scaled content abuse: many pages generated mainly to manipulate rankings rather than help users, with little to no value 'no matter how it's created.' One of Google's examples is using generative AI tools to produce many pages without adding value. Fifty AI-written city pages fit that description.

Notice what Google does not say. It doesn't ban location pages, and it doesn't cap how many you can have. The test is usefulness: would a homeowner in that city learn something on this page they couldn't learn on your main service page?

Google's guidance on helpful content asks questions like: does the content provide original information, reporting, research or analysis? Does it provide substantial value compared with other pages in search results? A page that opens 'Looking for reliable roof repair in Plano? Our Plano roofers...' and then repeats the same 400 words as the Frisco page fails both.

It also fails the reader. A homeowner in Plano wants to know whether you actually work there, what jobs you've done nearby, how fast you can come out and whether you handle the city's permits. The name-swap page answers none of that.

And it fails commercially. Even when a thin city page ranks, it gives the visitor no reason to call you instead of the next result, whose page might show a real job two streets away.

Start with the three to five cities where you have the most proof, and add more as jobs and reviews come in. Six strong city pages are easier to keep current, and more useful to visitors, than sixty thin ones.

How long should it be? Google's helpful content guidance says plainly that it has no preferred word count. Write until the proof is on the page, then stop. Here is the block order we use:

Job photos. Ask crews for before-and-after photos on every job, with the address logged internally so you can label the neighborhood without publishing anyone's house number.

Crew notes. A two-line note per job, what the problem was and what you did, is enough raw material for a local project write-up.

Customer quotes. Ask at job completion, in writing, whether you may quote the customer with first name and neighborhood, and keep the permission on file.

Permit experience. Your office manager already knows which cities take longest to issue permits and what each inspection office expects. That is local knowledge a competitor's copywriter can't fake.

This gives Google the 'clearly defined, browseable hierarchy' its doorway policy contrasts with near-duplicate pages, and it gives visitors a way to find their town without a menu of 40 links. Keep the hub in the main navigation or footer, not every city, and link each project write-up to the city page it belongs to.

Skip the footer wall. A block of 50 '[service] in [city]' links on every page adds nothing for readers and resembles the funnel pattern Google's doorway policy describes. One 'Areas we serve' link does the same job honestly.

If city pages are live but calls aren't coming in, the problem may be elsewhere on the site. Our checklist for a website that isn't generating leads covers the usual suspects. A simple URL structure looks like this:

Schema.org defines areaServed as the geographic area where a service or offered item is provided. It accepts a place, an administrative area, a geographic shape or plain text, can be used on an Organization or a Service, and supersedes the older serviceArea property.

Schema.org's HomeAndConstructionBusiness type has more specific subtypes, including Electrician, GeneralContractor, HVACBusiness, Plumber and RoofingContractor. Use the closest one on your homepage or contact page, with your real address if you have a public one.

On each city page, a Service item with areaServed set to that city describes what the page is about without pretending to be a location. Structured data describes the page; it doesn't replace the local proof above.

In a Business Profile you can set up to 20 service areas by city, postal code or other area. Google says the overall area shouldn't extend more than about two hours' driving time from where the business is based, and a radius is no longer an option. If you don't serve customers at your address, Google says to remove it and list only service areas.

Google says local results are based mainly on relevance, distance and prominence. Distance is the one a city page can't change, because your profile is still based where it is. Prominence, Google adds, draws on information such as how many websites link to your business and how many reviews you have.

Local Services Ads have their own service-area settings: you include or exclude counties, cities or zip codes in the ads dashboard. A customer who finds you through an ad, the map or a city page should see the same coverage. For paid search, send traffic to a dedicated landing page instead of a city page; our guide to Google Ads landing pages for service businesses explains why.

Search Console's Performance report shows clicks, impressions, click-through rate and average position, grouped by query or page, and lets you compare periods. Review city pages quarterly, and if you'd rather have someone else run it, this is part of our SEO and search growth work.