Plumber Service-Area Pages That Rank Without Getting Flagged as Doorway Pages
Service-area pages are the most abused play in plumber SEO. The pitch is simple: you cover 20 towns, so you spin up 20 pages, swap the town name in the H1, and wait for the leads. It works for about a quarter, then Google quietly stops indexing most of them and your traffic flatlines. What we actually see across the plumber accounts we track is that these networks don't get a dramatic manual penalty. They get filtered — the pages stay live, they just fall out of the index one by one until only your strongest one or two towns survive. That's the doorway problem, and almost nobody selling SAB pages tells you it's happening.
This guide is the free version of what a suburb page actually needs to earn its index slot and rank: real jobsite photos from that specific town, genuine job details your crew ran there, copy that isn't a find-and-replace of the last page, an embedded map tied to real work, and local proof a competitor can't fake.
It is the granular sibling of the outer-grid-squares strategy in our plumber local SEO guide — that guide covers why you build these pages at all; this one covers how to build them so they do not get thrown out. The trade-neutral skeleton lives in the service area page template, and the version tuned for the widest coverage radius of any trade is the window installer city page build. For suburb pages aimed at burst pipes and after-hours calls specifically, pair this with emergency plumber SEO.
What actually trips the doorway filter on plumber SAB pages
Google's doorway definition is narrow but the enforcement is broad: pages built primarily to funnel searchers into the same destination, with little unique value of their own. The tell isn't one thing, it's a stack of them. When we audit a plumber's town pages that stopped ranking, the pattern is almost always identical — the same 350-450 words on every page, the town name swapped in six to eleven spots, the same stock photo of a wrench on a white background, the same three 'services we offer' bullets, and internal links that all point back to the money page. Google reads that stack in aggregate. One thin page is a mistake; forty near-identical ones are a pattern, and the pattern is what gets filtered.
The practitioner detail most guides miss: the filter is comparative, not absolute. A 500-word Naperville page that would index fine as a standalone site gets dropped when it sits next to 19 sibling pages that are 88% the same text. We've watched a 40-town network collapse to a single indexed page within about six weeks of launch — not because any one page was terrible, but because Google only needs one representative of a near-duplicate cluster. Your job on every suburb page is to make it the page that survives, which means making it look nothing like its siblings under a diff tool.
The five things every suburb page needs (the free version)
DataPins and the pin-drop tools sell this as proprietary, but you can do all of it by hand. Ingredient one: two to four photos from an actual job in that town — the truck in that neighborhood, the water heater you pulled, the trench for that sewer lateral. Ingredient two: real job specifics, meaning you name what you actually did there (a PRV replacement on a 1960s ranch, a galvanized-to-PEX repipe in the older part of that suburb). Ingredient three: distinct copy — not spun, genuinely different because the plumbing problems in that town are different. Ingredient four: an embedded map centered on real work, not just a Google Maps iframe of the town centroid. Ingredient five: local proof — a review that names the town, a mention of the local permit office or water utility.
Here's the part only someone running these accounts learns the hard way: you do not need all five perfect on all twenty pages. You need them real on the eight to ten towns you actually work most. The pages for towns where you've done fifteen jobs will carry genuine detail effortlessly; the pages for the two towns you've visited once will always read thin no matter how you dress them up. We tell plumbers to build pages only for towns with at least three or four completed jobs on record, because that's the minimum before you have enough true specifics to clear the filter. A page you can't fill honestly is a page that will get dropped.
Where the photos come from — and why they're the whole game
The single highest-leverage difference between a suburb page that indexes and one that doesn't is original, geo-relevant photos. Not because Google reads EXIF geotags reliably (it doesn't, and phones strip them on upload anyway), but because unique images are the fastest signal that a page represents real work rather than a template. A stock wrench photo appears on ten thousand plumber sites; a photo of your tech feeding a camera down a cleanout on Elm Street appears on exactly one. That uniqueness is what the comparative filter is looking for.
The system that actually works: your crew shoots three or four photos on every job from their phone — the problem, the work in progress, the finished install, and one wide shot with something recognizable in frame. They text or drop them into a shared album tagged with the town. The practitioner reality is that this dies without enforcement — techs forget, the album goes empty, and three months later you're back to stock. The plumbers who keep town pages ranking treat photo capture as part of closing the job, same as collecting payment. On the pages themselves, name the file for the job and write real alt text ('tankless water heater installation in [town], replacing a 40-gallon tank in a two-story colonial') — not because alt text is a ranking lever on its own, but because it's one more field that's genuinely unique per page instead of templated.
Writing copy that's distinct because the town is distinct
The mistake is treating distinct copy as a rewriting exercise — running the same paragraph through a spinner until the sentences differ. Google's near-duplicate detection catches spun text easily now; it's looking at meaning, not just word overlap. The move is to write from the actual plumbing reality of each town, which is genuinely different if you know the housing stock. A suburb built out in the 1950s has cast iron drain lines failing right now and galvanized supply lines that need repiping. A subdivision from 2005 has PEX and the problems are water heaters and pressure-reducing valves, not sewer collapses. A town on well water needs pump and pressure-tank work that a town on municipal water never will.
When we write these for plumber clients, each page leads with the two or three problems that town actually generates calls about, named specifically, before it ever mentions the generic service list. That alone makes every page read differently because the underlying facts differ. Reference the real local details a competitor copying your page can't clone without exposing themselves: the name of the water utility, the fact that a given town requires permits pulled for water heater swaps and the next town over doesn't, the neighborhoods where you keep getting slab-leak calls. A page that says 'we serve [town] and surrounding areas with quality plumbing' is a doorway page. A page that says which streets flood and which decade of homes have the failing supply lines is a local resource, and Google treats the two completely differently.
How many pages, which towns — extending the outer-grid squares play
The hub guide's outer-grid-squares strategy is the reason these pages exist: your Google Business Profile ranks strongly in the grid squares near your physical address and fades as you move outward, so the town pages are how you compete for organic rankings in the squares your map pin can't reach. But the temptation is to build a page for every square, and that's exactly how networks tip into doorway territory. The discipline is to build outward from where you actually work, not where you wish you worked.
In practice that means: build pages first for the ring of towns just outside your strong GBP radius where you already run jobs regularly — that's usually five to eight towns, not twenty. Those pages have real photos and real specifics because you're genuinely there. Only after those are indexed and pulling do you extend to the next ring, and only for towns where you've since done real work. What we see across accounts is that eight genuinely-built town pages outperform thirty templated ones every time, because the eight all stay indexed and the thirty average maybe four survivors. A smaller network that fully survives beats a big network that gets gutted — and it never puts your whole site under the shadow of a low-quality-page pattern.
Knowing it's working — the leading indicators before rankings move
Rankings are the lagging signal; indexation is the leading one. The first thing to check, weekly, is how many of your town pages are actually indexed — run a site: search or check the Pages report in Search Console. If you launched ten pages and only three are indexed after a month, the other seven are being read as thin duplicates and no amount of waiting fixes that; they need real photos and real specifics added, not more time. This is the check almost no plumber runs, and it's the one that would have caught the collapse before it cost them.
The second indicator is impressions per page in Search Console before any clicks arrive — a page that's genuinely unique starts collecting impressions for the town-plus-service queries within two to four weeks even if it's ranking on page two or three. Flat zero impressions after a month means the page isn't being treated as a real answer for anything. When we hand these off to plumber clients, the standing rule is simple: any town page that isn't indexed and collecting impressions within six weeks gets rebuilt with real job content or deleted, because leaving a dead thin page live drags the credibility of the whole set. Prune the ones that don't earn their slot and Google trusts the ones that remain.
This is one piece of the bigger picture. For the complete playbook, read our main guide: Plumber Local SEO.
FAQ
Frequently Asked Questions
Will Google penalize my whole site if some service-area pages are thin?
Not with a manual penalty in most cases, but the effect is worse than people expect. Google filters the thin pages out of the index quietly, and a large cluster of near-identical pages can cast a low-quality shadow that makes even your good town pages harder to rank. It's rarely a dramatic hit — it's a slow erosion where most of your network stops getting indexed. The fix is to keep fewer, genuinely-built pages and delete the ones that never index, which restores trust in the set that remains.
How many words does a plumber service-area page need to avoid being thin?
Word count isn't the real threshold — uniqueness is. We've seen 400-word pages index fine and 1,200-word pages get dropped because the long ones were just padded templates. What matters is how different the page is from your other town pages under a comparison. A page built around the actual plumbing problems, housing stock, and completed jobs in that specific town clears the bar at 500-700 words. A page that's the same text with the town name swapped fails at any length.
Do I need software like DataPins to add jobsite photos and check-ins?
No. The pin-drop tools automate photo posting and map embedding, which is convenient at scale, but every ingredient is doable by hand for free: crew shoots photos on the job, you upload them to the right town page with descriptive filenames and alt text, and you embed a map. The tools sell convenience, not a ranking factor you can't replicate. If you only cover eight to ten towns, manual is entirely manageable and gives you more control over the copy.
Should I build a page for every town in my service area?
No, and this is the most common way plumbers trigger the doorway problem. Build pages only for towns where you've done real, repeat work — usually the five-to-eight-town ring just outside your GBP's strong radius. Those pages fill with genuine photos and specifics naturally. Building twenty pages for towns you rarely visit leaves most of them thin and gets the network filtered. Extend outward only as you accumulate real jobs in the next ring.
How is a service-area page different from just ranking on Google Business Profile?
They cover different squares of the map. Your GBP ranks strongly in the grid near your physical address and fades as you move outward — that's the proximity filter. Service-area pages are the organic play for the outer squares your map pin can't reach, so a searcher two towns over finds your website even when your profile doesn't show in their local pack. The full grid strategy is laid out in the plumber hub guide at /local-seo-for-plumbers; the town pages are one specific tactic within it.
How do I know if my existing town pages are working or getting filtered?
Check indexation first, not rankings. Run a site: search or open the Pages report in Search Console and count how many of your town pages are actually indexed. If most aren't indexed a month after launch, they're being read as thin duplicates. Then watch impressions per page — a genuinely unique page starts collecting impressions for town-plus-service queries within two to four weeks even before it ranks. Flat zero impressions after a month means the page isn't a real answer to anything and needs real job content or deletion.
See where you rank right now
Free local SEO audit — GBP, reviews, and your map rankings. No sales call.
Get your free audit