How to Build Landscaping Service-Area Pages That Rank (Without Doorway Penalties)

Why landscapers trip the doorway filter more than most trades

A doorway page, in Google's own definition, is a page created to rank for a specific location or query that funnels users to the same destination as every other near-identical page, adding nothing a real local page would add. The tell is substitutability: if you can regenerate the page by find-and-replacing the town name and nobody would notice, it's a doorway. Landscapers walk into this more than plumbers or electricians because landscaping copy is easy to write generically. "We offer lawn care, mulching, and hardscaping in [Town]" is true in every town, so the template writes itself, and that is exactly the problem.

What we actually see across the landscaping accounts we track: the doorway penalty rarely shows up as a dramatic ranking drop. It shows up as a ceiling. The town pages plateau at positions 8-15, never crack the map pack, and the whole cluster stops passing internal authority. One account we took over had 22 service-area pages and 19 of them were indexed but had received zero organic clicks in six months, Google was effectively holding them in a penalty box without ever sending a manual action. We consolidated the nine thinnest ones into the hub and rebuilt the rest with real local substance. The point of this page is to make sure your town pages land on the right side of that line before you build 20 of them.

The page architecture that survives

A service-area page that holds up has a spine, not a template. The spine is: a location-specific H1, a genuinely local opening (200+ words that could only describe this town), the services you perform there framed against local conditions, at least one piece of proof from that town (a photo of a job you did there with the street or neighborhood named, a review from a resident, a permit you pulled), an embedded map or directions that reference real landmarks, and internal links up to the hub and sideways to two or three neighboring town pages. The template is only allowed to own the furniture, the header, footer, and contact form. Everything in the body has to earn its place.

The ratio we hold our own build to is roughly 60/40: at least 60 percent of the visible body copy on each town page must be content that does not appear on any other town page, verified by literally diffing the pages against each other. If two pages are more than 40 percent identical after you strip the header and footer, you have a clone, not a service-area page. Most landscapers have never run that diff, which is why they don't know their pages are near-duplicates until the rankings tell them.

One structural rule that saves people: do not create a town page until you actually serve that town and have something specific to say about it. An empty-promise page for a town you've never worked in is the fastest way to look like a doorway, because there's nothing real to fill it with. It is far better to have six substantial town pages than 20 hollow ones.

Where the genuinely unique content comes from

This is where landscapers have an unfair advantage over most trades, and almost none of them use it. Landscaping is one of the few home services where the local physical environment materially changes the work, which means you have real, defensible content that a copywriter three states away cannot fake. Four sources carry most of the weight. Soil and climate: the hardiness zone, and whether the town sits on heavy clay, sandy loam, or rocky fill, changes what you plant and how you grade. A town on clay needs aeration and drainage amendment that a sandy-soil town two exits away doesn't. Say that, by name, on the page.

HOA and municipal rules: this is the richest vein and the most ignored. Specific subdivisions have covenants dictating approved plant palettes, fence heights, front-yard turf percentages, and irrigation restrictions. If you know that a particular development requires HOA architectural-review approval before a paver patio goes in, or that a town bans certain invasive ornamentals, writing that down is content no template can produce, and it's genuinely useful to the homeowner reading it. Drainage is the third: which neighborhoods flood, which lots slope toward the foundation, where French drains and dry wells actually get installed. Popular styles is the fourth, because a historic-district town wants different hardscape than a new-build subdivision.

What we actually see: the town pages that pull the strongest are the ones where the landscaper dictated two paragraphs from memory about a specific neighborhood's conditions, and we transcribed it. That five-minute voice note beats an hour of polished generic copy every time, because it contains the operational detail that signals a real local operator to both Google and the homeowner. The crew knows which streets flood. Get it out of their heads and onto the page.

Engineering relevance for towns outside your proximity core

Here's the part that connects directly to the proximity playbook on the hub. Google's local pack is heavily weighted by proximity, the distance from the searcher to your Business Profile pin. For towns within a few miles of your address, the map pack does most of the lifting and the service-area page is a support asset. But for towns 10, 15, 20 miles out, proximity works against you, you will almost never win the map pack there, and the organic (non-map) result becomes your only realistic entry point. That is precisely where a strong service-area page earns its keep.

To rank organically in a town where your pin gives you nothing, the page has to manufacture the relevance that proximity would otherwise supply. That means denser local entity signals: named neighborhoods, named landmarks, the specific soil and drainage detail, a real completed project in that town with geotagged photos, and ideally a review or two from residents there. It also means links, both internal (the hub and neighboring town pages passing authority in) and external where you can get them (a mention in that town's community Facebook group, a local sponsorship, a chamber listing). We've moved landscaping town pages from unranked to page one for "[town] landscaping" purely on organic strength while the map pack in that town stayed locked to businesses physically located there. The service-area page isn't competing with the map pack in far towns, it's the parallel path that gets you found at all.

The honest framing to give clients: near towns, invest in the profile and reviews; far towns, invest in the page. The service-area page is your proximity workaround, and it only works if it's substantive enough to stand on content alone.

The build workflow that keeps clones out

The workflow matters as much as the content, because doorway pages are almost always a process failure, not an intent failure. Nobody sets out to build clones, they just start with a template and run out of unique things to say by town four. So invert the order. Before writing a single page, run a discovery pass with the owner or the crew lead and fill a simple grid: one row per town, columns for soil type, hardiness zone, known HOA restrictions, drainage issues, dominant home style or era, and one real project you've completed there. If a row has empty cells, that town either isn't ready for a page or needs a site visit's worth of notes first.

Only build pages for towns whose rows are full, and write from the grid, not from the template. Then verify: run a text-diff of each finished page against every other, and reject anything over roughly 40 percent similar in the body. We keep a checklist that every town page has to clear before it ships, real photos from that town, at least one location-specific fact in the first 150 words, a named neighborhood or landmark, internal links up and sideways, and a unique meta title and description. Pages that fail any item go back, they don't publish. That one gate is the difference between a service-area cluster that compounds and one that sits in Google's penalty box for a year.

Skip the JSON-LD FAQ schema, by the way, Google deprecated FAQ rich results, but keep genuine FAQ content on the page, because it's still read by AI answer engines and by homeowners deciding whether to call you.