Forty towns, one template

Are City Pages Black Hat? Doorway Abuse in Google's Own Words, and the Town Page That Earns Its Place

A town page is not a sin. Forty of them with the names swapped might be. Google's doorway policy turns on what a page does for the person who lands on it, which means you can test yours today, with no agency and a cold cup of coffee.

November 9, 2026 · 11 min read

acmeroofing.com · town page plan
Start with the invoices, not the radius
From forty towns on a proposal to five real pages
Towns on the agency's proposal40
Towns with a job in the last year17(43%)
Towns with enough jobs to show8(47%)
Towns with something distinct to say5(63%)

Twenty-three towns dropped here: the crew has not worked in them, so a page would have nothing true to say

Illustrative: a sample plan for a fictional roofer

The short answer

City pages are not against Google's rules in themselves. Google's doorway abuse policy targets pages built to rank for similar searches that send people to something less useful than the final destination, including city pages that funnel visitors to one page. A town page is fine when it gives someone in that town information the others do not, drawn from real work there.

On this page
  1. The word Google uses is doorway, and the word is narrower than the sales pitch
  2. Google's doorway examples, one clause at a time
  3. Swap the town name, then run two harder tests
  4. The raw material comes from the job folder, not a census page
  5. How many: a count from your records, not a rate card
  6. Already have sixty? Shrink before you rewrite
  7. We publish town pages too, so hold ours to this

The word Google uses is doorway, and the word is narrower than the sales pitch

Two sales calls are going on in this market. One says you need a page for every town within fifty miles, priced per town. The other, usually from the agency replacing the first one, says city pages are black hat and must all come down, at a price. Google says neither. "Black hat" appears in none of its documents, as our spam policy guide explains. What Google has is a doorway abuse policy, in a page last updated August 28, 2026: creating sites or pages to rank for specific, similar queries that lead users to intermediate pages less useful than the final destination.

Note what that leaves alone. A real page about real work in a real town is not named. Our service area page guide already covers when a town deserves a page, what goes on it and how to link it. This page starts where that one stops: reading the policy clause by clause, adding two harder tests to the familiar one, counting from your own records and shrinking a site that already went too far. The white hat SEO hub covers the wider question of checking what "white hat" claims mean.

Google's doorway examples, one clause at a time

The policy gives four examples. The left column stays close to Google's wording without quoting it; the two columns on the right are our reading, and only Google decides how it enforces.

Google's doorway abuse examples, and the question each one asks of a town page
Google's exampleWhere you would see itThe question to ask
Multiple sites with slight variations to the URL and home pageA second and third domain with a town in the nameWhy does a single business need several sites?
Multiple domains or pages targeted at specific regions or cities that funnel users to one pageSixty town pages, each with one button to the same contact formDoes the page give an answer, or only a route to one?
Pages generated to funnel visitors into the usable part of a siteA page whose only job is to reach the real service pageWould anyone miss the page if the link went straight there?
Substantially similar pages closer to search results than a clearly defined, browseable hierarchyTown pages that no menu reaches, findable only through GoogleCan a visitor find this page by browsing your site?
Layered colored-paper scene of a long road lined with identical tiny shops, one different with its own awning and a white paper hat on top, soft shadows
Forty identical storefronts on one road are one storefront, and the different one is the page worth keeping.

Two neighboring policies catch the same pages from other angles. Google's keyword stuffing examples include blocks of text listing the cities and regions a page is trying to rank for, which describes many a footer; see keyword stuffing. And scaled content abuse covers many pages generated to manipulate rankings, however they were made, so a generator or a tired copywriter makes no difference. Our programmatic SEO guide sets the bar for template pages, and AI content covers the drafting side.

Swap the town name, then run two harder tests

Everyone in the trade knows the swap test now, which is why some pages have learned to pass it. A sentence naming the county seat and the high school mascot breaks when the town changes, so it passes, and it still tells a customer nothing about the job. So keep the first test and add two. These are our tests, not Google's, and the towns below are invented.

  1. 1

    The swap test: does it break when you change the town?

    "We proudly serve Elm Fork homeowners with reliable repairs." Change it to Cedar Bend. Still fine, still empty. A sentence about the town should stop being true when the name changes.

  2. 2

    The customer test: does the local fact change what they do?

    "Elm Fork was founded in 1887" passes the swap and helps nobody. "Most Elm Fork homes from before 1970 have a cast iron stack, so we bring the snake and a camera, and a camera visit runs longer" changes what the customer should expect and plan. Keep that kind.

  3. 3

    The delete test: what would be lost?

    Remove the page in your head. Would a person in that town lose something they could not get from your service page? If the page's only unique words are its town name and a map, the answer is no. Google's content guidance, updated October 5, 2026, asks whether an audience would find a page useful if they came to you directly. Would you text this one to a customer?

If the only thing a page knows about a town is its name, it has not been there.

The raw material comes from the job folder, not a census page

Population figures, a founding date and a paragraph on the local parks are what a writer produces with no access to your business. They pass a quick look and tell a customer nothing. The material that earns a page lives in your own records, and it is the reason a rival cannot cheaply copy the page.

Jobs you did there

What you found on which kind of house or building, with your own photos, used with permission. Three real ones outweigh any amount of describing. If you have none, you have no page yet.

What is different about the work

Soil, age of the housing, a permit office with its own habits, water that eats fixtures. Only what you have actually dealt with. Do not research something you have never met.

Honest logistics

Drive time from your base, which days you are there, whether you charge a trip fee, and when you would send someone closer. A page admitting you are 50 minutes away is more believable than one implying you live next door.

Prices, where they vary

If a town's permit fee or job size moves the typical price, say so. A page with a real range is doing something no template does.

Reviews from there

Reviews from customers in that town, quoted as written and with their permission. Never written for the occasion. The page on honest reviews covers how to ask.

A person who goes there

The crew lead who works that area, with a real name if they agree. Google's content page warns against fabricated profiles, so a real person or none.

None of this needs to be long. For one large city with many neighborhoods, our post on local SEO across San Antonio sketches a page tree that stays browseable. Google's content page warns against writing to a word count and says it has no preferred one. Three hundred words that know something beat 1,500 that do not. How to arrange it is in the service area guide, and the broader content edit applies to every page.

How many: a count from your records, not a rate card

A page-count proposal starts with a map and a radius. Start with your invoices. Export last year's jobs and count them by town. Then ask each town the three tests above. Any town that fails becomes a line on a service area page, which is an honest thing to be. The table is invented, for an invented roofer, to show the method.

An invented example of sorting towns by job records, with invented towns
Town (invented)Jobs last yearHas something distinct to say?Decision
Elm Fork48Older homes, an unusual roof mix, plenty of photosA full page
Cedar Bend31Hail claims, with a local adjuster processA full page
Mill Station9A few jobs, nothing different yetOne line, revisit next year
Harper Ridge1NoOne line
Lake Corners0Never been thereLeave it out

The map side has separate rules, and people confuse them. Google's Business Profile guidelines, read November 7, 2026, say a service area should not extend farther than about 2 hours of driving from your base, though larger areas may suit some businesses; its service area help, read the same day, allows up to 20 service areas. A town page needs none of that, and a virtual office to "be in" a town is not eligible, as white hat local SEO explains. A page can honestly say you serve a town. A profile cannot pretend you are in it. The free map pack audit shows where you stand now.

Already have sixty? Shrink before you rewrite

If a past vendor built the sixty, the instinct is to rewrite all of them. That is a large bill for pages most towns never needed. Merge first. Google's policies name consolidating pages as a legitimate use of a redirect, and its canonicalization guide, updated July 10, 2026, calls redirects a strong signal.

  1. 1.Check Manual actions first. Google's help page, read November 7, 2026, lists thin content among its notices, and says fixing only some pages will not earn a partial return. A notice sends you to penalty recovery before anything here.
  2. 2.Export the pages with their numbers. Performance report, Pages tab: clicks and impressions for each town page.
  3. 3.Sort by your job records, not by traffic alone. A page with clicks from a town you do not serve is not an asset.
  4. 4.Keep the few and rewrite those. Use your job folder and the three tests above.
  5. 5.Redirect the rest to a service area page that names each town in a sentence, or to the matching service page. Redirects done properly keep links intact.
  6. 6.Make the survivors reachable. A menu or hub should lead to them. Google's fourth example is pages closer to search results than to a browseable hierarchy, and internal linking is how you fix that.
  7. 7.Delete the city list in the footer while you are in there.

Keep expectations plain. Google's starter guide, last updated December 10, 2025, says some changes might take effect in a few hours and others could take several months. Its spam updates page, the same date, says improvement after a spam update may come if its systems learn "over a period of months" that a site complies. Nothing here is a promise, and our audit of past work can establish what was built before you decide. Some of those sixty may even be earning calls.

We publish town pages too, so hold ours to this

We are a web studio in San Antonio that works across the US by phone, video and a shared project page, and we sell town pages as part of websites and local marketing. If you want a second opinion on the pages you have, the three tests above are the same ones we would run, and they cost nothing to try.

If you would rather not do this alone, the white hat SEO service and local marketing each run from $575 a month, depending on complexity, setup and budget, with no long contract, per our SEO pricing. Cleaning up a large set is quoted after a look at the site. A free site audit is a first check on thin pages. If you serve two towns and your records say two pages, build two pages and keep the money.

Questions owners ask about white hat SEO

Not as such. Google's doorway abuse policy, in a page updated August 28, 2026, targets pages made to rank for similar searches that lead to something less useful than the final destination, including city pages that funnel users to one page. A location page with its own useful information, reachable by browsing the site, is not what that describes. Each page has to do its own work.

Google gives no percentage, and anyone selling a uniqueness score invented one. Rewriting sentences so they differ on paper misses the point, because the question is whether a person in that town gets something the others do not. Local facts from your own work do that. Spinning the same paragraph does not, and synonymizing is named in Google's scaled content abuse examples.

Yes, if you really work there and say so honestly. A page saying you serve a town from a base 40 minutes away is true, and the doorway policy is about the page's usefulness rather than your address. What you may not do is invent a presence: Google's guidelines, read November 7, 2026, say a virtual office is not eligible for a Business Profile, and a local address you do not operate from is a false statement to the customer reading it.

Usually neither first. Merge them: redirect each thin page to a stronger service area page or the matching service page, so any links and visitors land somewhere useful. Noindex keeps a page out of the index but leaves it on your site for visitors. Plain deletion suits a page with no links, no clicks and no purpose. Log what you did and when.

No, and you generally cannot have one. Google's guidelines, read November 7, 2026, say a service-area business without a storefront is allowed one profile, or one per location where it has separate service areas and separate staff at each. They also say not to create more than one profile page for each location. Use the profile's service areas, up to 20, and let your website carry the town detail.

Ask them to show the page and the sentence of the policy. Then check the Manual actions report yourself. If it is clear, you have a possible quality problem, not an announced penalty, and you have time to think. Some pages may deserve to go; some may be earning calls. See audit past SEO work before paying anyone to remove them.

Keep reading

Free · No obligation

Send your town pages and we will sort them

Give us your site and the towns you really work in. A person at DataCram reads the pages and replies with which we would keep, merge or leave out, and why.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote