Key takeaways
- Google’s doorway-abuse examples explicitly include similar regional or city pages that funnel visitors onward.
- A unique title, hero photograph, or weather fact does not make the underlying page useful or distinct.
- Keep a page when it resolves a local decision; consolidate or remove it when it merely repeats the main service page.
- Audit the whole template family, because doorway risk is a pattern-level problem rather than a single awkward paragraph.
01
Put the page family on one table
A single city page can look polished in isolation. The problem becomes visible when 40 of them sit side by side: identical promise, identical proof, identical FAQ, identical call to action, and a place name swapped through the headings. Export every regional URL with its title, description, headings, word count, internal links, conversions, and indexed status before reviewing individual sentences.
Group pages by service, market level, and intent. A country hub, state page, city page, and service-location combination should not all fight to answer the same question. Decide which level owns which decision before rewriting anything.
02
Score distinct usefulness, not cosmetic uniqueness
Search systems do not need 100 percent different words; visitors need a reason to choose this URL over the parent page. Score whether the page changes eligibility, service delivery, timing, price framing, regulation, proof, recommended approach, or the next step. A local skyline photograph is atmosphere, not a new answer.
Swipe to compare every column
| Audit question | Keep when | Consolidate when |
|---|---|---|
| Does the market change the work? | The page explains a material delivery or strategy difference | Only the city name changes |
| Is the proof locally relevant? | Evidence genuinely applies and its limits are stated | The same unsupported result appears everywhere |
| Is the page navigable? | It belongs to a clear regional and service hierarchy | It exists mainly for search entry |
| Does it earn a next step? | The CTA preserves market and service context | Every page dumps visitors into one generic form |
03
Choose among rewrite, merge, canonicalize, or remove
Rewrite when the market deserves a distinct page and the team can supply real substance. Merge sibling pages into a useful hub when their differences are too small. Use canonicalization for genuine duplicate or near-duplicate variants when a representative URL should carry the signals. Remove or redirect obsolete pages whose promise no longer exists.
Do not use robots.txt as a canonicalization tool. Google may still index a blocked URL without seeing the content. Likewise, noindexing a large weak section may hide it from search but does not make the navigation, maintenance, or customer experience coherent.
04
Build a publishing gate that can say no
Require a short brief before a new market URL is created: audience, distinct question, evidence, service availability, owner, review date, internal-link plan, and the page it would replace or complement. If the brief cannot name the new decision, keep the information on the hub.
This is the uncomfortable part of scalable SEO: the system needs a stopping rule. Publishing fewer pages can create more useful coverage when each surviving URL is easier to find, update, trust, and connect to the next action.
Primary sources and further reading
Use the source material to validate details against your own context and current platform configuration.
- Google Search Central: Spam policies and doorway abuse
- Google Search Central: Canonicalization
- Google Search Central: Specify a canonical URL
- Google Search Central: People-first content guidance
This field note follows the XenGrowth editorial policy: primary sources where available, visible limitations, material review dates, and no invented first-hand experience.
Stay with the problem
