What a city service page should include across towns

A city service page should prove you work in that town, say whether people can visit a staffed place or whether you travel to them, and give a visitor something they cannot get from the same paragraph with a different city name. Google's current spam policies describe doorway abuse as pages built to rank for specific, similar queries. The examples include pages aimed at regions or cities that funnel people to one page, and substantially similar pages that behave more like a stack of search results than a browseable part of a site. [1] Covering more than one town is not the problem. A copied page that only swaps the town name is.

Say whether this town is a place you staff or a place you travel to

The page has to say which kind of place this town is. Some businesses have a door customers can walk through. Others go to the customer. Google's Business Profile help separates those promises, and a visitor needs the same answer: can I show up, or are you coming to me?

A service-area business visits or delivers to customers and does not serve customers at its business address. Google's overview uses a plumber or a pet walker. [6] A hybrid business does both, and that overview uses an auto shop with roadside help as the example. [6] The service-area help page adds that without permanent on-site signage, a business is not eligible to present the place as a storefront. Its hybrid example is a dine-in restaurant that also delivers. [5]

If customers can come to a shop, office, or yard in this town while your staff is there, say so: the address, the hours a person is available, what a walk-in can do, and a photo of the place. On a Business Profile, a hybrid business can show the storefront address, set hours for when staff is available, and also name a service area. [5] If nobody serves customers at an address in this town, do not print one. On the Business Profile, Google's help says to remove the address when you do not serve customers there, and to enter both the address and the service area when you do. [5] A suite number or a mail drop invented so the town looks staffed is the opposite claim. Say where the crew starts and which jobs you take.

On a Business Profile, a service-area business can have only one profile for the whole area it serves. The help page also says that area's boundaries should not be more than about 2 hours of driving time from where the business is based, and that the area should be specific and accurate. [5] That is profile guidance, not a cap on how many towns a website may mention, and not a ranking formula. If you cannot actually reach a town from your base, do not write the page as if you were the local shop.

Two real shops are different from two town names. Each staffed place has its own door, its own hours, and its own work, so each can support its own page. Towns where you only send a truck do not become shops because you gave them a URL.

Put proof on the page that only this town would have

After the relationship is clear, the page has to show the work. Google's people-first guidance asks whether content offers original information, and whether it shows first-hand expertise, including expertise that comes from having visited a place. [3] A city name in a headline does not do that. A job you did on a street in that town can.

Useful proof is specific and checkable. Name the property types you actually see. Older crawl-space houses in one town and new slab houses in the next are different pages because the work is different. Write a permit step, a local rule, or a street constraint only when your crew dealt with it. If you do not know the detail, leave it out. A wrong landmark is worse than a short page.

Photos should come from the work or from the staffed place: your crew, your truck at a finished job, or the front of a shop you operate. Stock skylines do not show that you were there. On main content, Google treats original analysis as effort, and it treats large amounts of generative text with no manual oversight as little to no effort. Crediting other sources does not replace that effort. [3] For a city page, effort looks like crew notes, photos, and a pass by someone who knows which jobs were in which town.

Say what differs, and say what is the same when that is the truth. Readers are not harmed by learning that one crew covers three towns from one shop. They are harmed by a page that implies a local office and local projects that do not exist. A true line about which weekdays you schedule the town, and how long the drive is, beats a slogan whose only local fact is the town's name. Describe the job type and the problem you solved without publishing a customer's name, house number, or a photo of their face or paperwork. The test is simple: the two town pages should not survive a name swap.

Make the page part of the site, not a side door

Google's doorway examples include pages whose role is to funnel visitors into the "real" part of a site, and substantially similar pages that are closer to search results than to a clearly defined, browseable hierarchy. [1] The repair is a hierarchy a person can use, not a ban on mentioning cities.

A service page can explain the work. An index can list the staffed sites and the areas you actually cover. A town gets its own URL only when that URL can carry its own facts. Menus and in-page links should reach those pages the way a visitor would, not as a block of links whose only job is to expose more URLs.

A 2015 Google Search Central post from the webspam team is old enough to read as history next to the current policy. Its questions still sort real pages from side doors. Is the page there to funnel people into the usable part of the site, or is it part of the experience? Does it duplicate a location list the site already has, only to catch more searches? Is it an island the rest of the site hardly links to? [2] If the town URL exists so a query has somewhere to land, and the useful material always sits one click away on a generic page, you have built the pattern the current policy names. [1]

A contact path can sit on the town page. Someone who has seen how you work in that town should be able to ask for that work. What fails is a thin URL made of a slogan and a button, or a bounce to a page that never mentions the town again.

Keyword stuffing is a related failure, and it is not the same move as publishing several real town pages. Google's spam policies give blocks of text that list cities and regions a page is trying to rank for as an example of keyword stuffing. [1] A paragraph that recites every suburb is that example. It is a list, not a city service page.

Why a swapped town name is a doorway problem

Picture two pages that match except for the city: same services, same stock photo, same quality sentences, and a bold town name. The visitor who opens the second result after rejecting the first has not been given a new page. The 2015 post described that frustration. Searchers can get a list of results that all lead to the same site, so the next click returns them to an experience they already rejected. [2] That shape is what the current doorway policy names. [1]

A city in the title is not automatically spam. A page aimed at a town can be a normal part of the site when it is useful on its own. The line is whether the page adds something a person needed, or only captures the query. Unique location pages sit on the safe side. Interchangeable ones do not.

Scaled content abuse is the mass-production version of the same failure. Google defines it as many pages generated mainly to manipulate rankings rather than to help users: large amounts of unoriginal content with little or no value, no matter how the pages were produced. One example is using generative AI tools to generate many pages without adding value for users. [1] Running a city name through a template is that shape when the new page never gains real local information.

A second outcome is easy to confuse with a penalty. Some duplicate content is normal, and Google's canonicalization documentation says that duplicate content, by itself, is not a spam-policy violation. [4] It can still make the copies pointless. When the primary content is the same or very similar, Google clusters those pages, chooses one canonical URL, and usually points the search result at that URL. [4] Swapped city pages can fail under doorway or scaled-content policy if they exist to collect queries without helping anyone. Even as ordinary duplicates, they may be folded so searchers see one URL. More copies do not create more local proof.

The fix is a different centerpiece. If the honest version is one shop page plus a clear list of towns you travel to, publish that. If three towns have three bodies of work, the text, photos, and specifics should still differ after you cover the town name in the headline. Pointing every town URL at one canonical page, while hoping each URL still ranks alone, recreates the funnel.

Use tools to structure notes you already have

Generative tools are not banned, and they are not a source of local facts. Google's guidance on generative AI content, updated in October 2026, says these tools can help you research a topic and add structure to original content. The same page says that using them to generate many pages without adding value for users may violate the scaled content abuse policy. [7] It also says the models predict a likely sequence of words rather than retrieving facts, so the output can be wrong, and a person should fact-check it before publishing. That review includes the title, the description, image alternative text, and structured data, because those can show in search results. [7]

The dangerous output is a confident local sentence nobody on the team lived: a permit desk on the wrong street, or a housing style the town does not have. The page looks specific and is false. Compare every local claim with a job record, a photo, or a person who was there, and cut anything that has no source inside the business.

A May 2025 Google Search Central post says to make unique content visitors will find helpful, content that is not interchangeable, and it notes that unique value matters for ordinary blue-link results as well. [9] A city page is interchangeable when any other town could wear it.

If you mark the page up, mark up what a visitor can see. Google's local business structured data documentation says to define each local business location as a LocalBusiness type, and a physical address is required. That address is the physical location of the business. You may add the markup on any page, though it makes more sense on a page about the business. [8] Use it on a real staffed location, with the same address and hours the prose shows. Do not give a service-area town a postal address the page does not have. The May 2025 post says structured data should match the visible content. [9]

A tool can still turn crew notes into a consistent order, or draft a pass that a person checks against the job file. Publishing stays with someone who can delete a sentence that is not true of that town. Google's people-first questions flag extensive automation across many topics, and mass-produced pages that never get much individual care. [3] A stack of town pages nobody has read is in that zone, even if each one sounds local.

Decide town by town, then stop

You do not owe every town in a metro its own URL. Give a town a page when customers can visit a staffed location there, when the crew has distinct work to show, or when the way you do the job changes in a way you can explain from experience. Otherwise fold the town into the service-area statement on the staffed page that covers it. Google's service-area help tells businesses to be specific and accurate about where they serve, which is a better standard than a long list of place names. [5] If you later do real work in a town that had no page, add the page after you have something to put on it.

Read the draft once as a stranger from the next town. If you can swap the names and the page still works, it is not done. If you would hand it to a customer who had the work done there, it is on its way to being a real city service page.

Practical takeaways

• State whether this town has a staffed place customers can visit or is an area you travel to. Do not invent an address where nobody serves customers.
• Put proof on the page that would be wrong on the neighboring town's page: job types, conditions you have handled, photos from your work, and how scheduling or access actually works.
• Link the page from the service and from the index of places you really cover. A thin URL that only pushes people to one generic page matches the doorway pattern Google describes. [1]
• Treat a swapped-city template as a failed draft. Near-duplicate pages can be clustered so one URL represents them, and unoriginal pages produced at scale can fall under spam policy. [1] [4]
• Use software to organize notes you already trust. Fact-check every local sentence, including titles and structured data, before the page goes up. [7]
• Save LocalBusiness address markup for a real location, and match it to the address and hours printed on that page. [8] [9]

How we can help

Have more questions or want to get in touch? If you cover more than one town and you want a second look at which places deserve a page, our team can talk through the difference between a staffed location, a service area, and a copy that only changes the city name. Start on our contact page.

Citations

1. Google Search Central, "Spam policies for Google web search" (2026-08-28)
2. Google Search Central Blog, "An update on doorway pages" (2015-03-16)
3. Google Search Central, "Creating helpful, reliable, people-first content" (2026-10-05)
4. Google Search Central, "What is canonicalization" (2026-08-20)
5. Google Business Profile Help, "Manage your service areas for service-area & hybrid businesses" (n.d.)
6. Google Business Profile Help, "Business Profile for service businesses overview" (n.d.)
7. Google Search Central, "Google Search's guidance on using generative AI content on your website" (2026-10-01)
8. Google Search Central, "Local business (LocalBusiness) structured data" (2026-09-08)
9. Google Search Central Blog, "Top ways to ensure your content performs well in Google's AI experiences on Search" (2025-05-21)