Local Pages and Doorway Abuse

Are Pages per City Spam?

It depends on what is behind the page, not on the fact that there is one page per city. According to Google Search Central, doorway abuse is pages built mainly to rank for similar searches and funnel visitors to a less useful intermediate page. A real operation with a physical presence in several cities can justify a page per city; a template with the city name swapped and nothing else different is the pattern the policy targets.

What Separates the Two Cases

Doorway
Abuse category named by Google Search Central
Purpose
The policy checks why the page exists, not its URL pattern
Physical presence
A branch, a technician assigned or a real inventory in that city is evidence, not the page itself
Near-duplicate
Pages differing only in the city name are the pattern the policy targets

Does creating a page for each city hurt my site?

Direct Answer

Only when the pages exist mainly to rank for similar city-plus-product searches and funnel to a less useful page — the pattern Google Search Central names as doorway abuse. A page per city that describes a real branch, real inventory or a real service team is a different thing.

The signal is not the URL structure. It is whether the page could stand on its own if a person landed on it directly: does it name a real address, a real contact, real lead times for that location, or does it repeat the same three paragraphs with the city name swapped? The second pattern is what the policy describes, regardless of how many cities are listed.

The definition Google actually uses

According to Google Search Central, doorway abuse is a set of pages, whether on one domain or across many, built to rank for specific, similar search queries by funneling users to a less useful intermediate page. The definition names the mechanism — rank for similar queries, then funnel — not the topic or the URL pattern.

A page-per-city pattern fits that mechanism exactly when each page is a thin variation built for the search "product plus city name" and the destination adds no location-specific value. The policy is not about geography — the same mechanism applies to pages built per product variant, per zip code, or per any other search-query slice.

A branch is evidence; a template is not

What Should Differ Between Cities

Real address and contact
A branch, a warehouse or an assigned technician the buyer can actually reach in that city.
Location-specific facts
Lead time, freight, local stock or regulations that genuinely change from one city to another.
Different enough text
If removing the city name from two pages leaves them identical, there was no location-specific content to begin with.

An industrial distributor with branches in five cities has a legitimate reason to publish five pages, each naming its own address, stock and delivery radius. A manufacturer with one plant that publishes fifty near-identical pages hoping to rank for fifty cities it does not serve is the pattern the policy targets, regardless of intent.

One question that decides most cases

Before publishing a page for a new city, or before deciding whether to keep an existing one, ask whether it would survive with the city name removed. If what is left is a generic product description that could apply to any location, the page is not adding the local value the policy expects — and it is competing against your own pages for the same search, which weakens both.

A related failure mode inside the same family of abuses is publishing high volumes of thin articles instead of thin city pages — the subject of the scaled content and penalties.

FAQ

Does creating a page for each city hurt my site? +
Only when the pages exist mainly to rank for similar searches and funnel to a less useful page, which is the doorway abuse Google Search Central names. A page per city describing a real branch or real local terms is a different case.
What is doorway abuse, exactly? +
According to Google Search Central, it is a set of pages built to rank for specific, similar search queries by funneling users to a less useful intermediate page. The definition targets the mechanism, not a particular topic or URL pattern.
How many cities can I list before it looks like spam? +
There is no count that decides it. What matters is whether each page reflects real operations in that city. Five pages for five cities with no real presence in any of them can fit the abuse; fifty pages for fifty branches with real stock and contact usually does not.
Does having a distributor network justify local pages? +
It can, as long as each page describes that specific distributor's real address, stock and contact rather than repeating a generic template with the city swapped. The physical presence is the evidence; the page is only where that evidence gets published.
How do I test whether my existing city pages are a problem? +
Remove the city name from two of them and compare. If the remaining text is identical, or nearly so, the pages have no location-specific value and fit the pattern the policy targets, independent of intent.
Should I consolidate city pages into one national page? +
Consolidate the ones that fail the removal test. Keep separate the ones tied to a real branch, a real service radius or real regulatory differences, since those carry genuine information a single national page would lose.
Is this the same abuse as scaled AI content? +
They are related but named separately. Doorway is about pages built to rank for similar queries and funnel elsewhere; scaled content abuse is about volume of pages made mainly to manipulate rankings, whatever the topic or tool used to produce them.
Can this cause a manual action, or only an algorithmic drop? +
Both are possible. Doorway abuse is one of the practices covered by Google Search Central spam policies, which can be enforced by a manual action or reflected in ranking systems without a named action. Checking the Manual Actions report in Search Console tells you which one applies to your case.

Check your local pages before deciding to consolidate

The diagnosis reads which of your local pages carry real, location-specific information and which ones are a template repeated with the city swapped.

Find the BottleneckEvidence per city, not a blanket rule