Doorway Pages

What are doorway pages?

Doorway pages are low-value pages built to rank for specific searches (usually a keyword or a city name) that funnel every visitor to the same destination instead of serving them directly. Google treats them as a spam-policy violation, so getting caught risks a manual action or an algorithmic demotion that can quietly bury a whole section of your site.

The tell is intent: the page exists for the search engine, not the person. If a visitor lands on it and immediately gets shoved somewhere else, or realizes the page is one of fifty near-identical clones swapping out a town name, that's a doorway. Google has enforced against these since 2015, and the pattern still shows up constantly in local and affiliate setups.

A real example of the doorway pattern

Say a plumber operates out of one shop but wants to rank in forty towns. The doorway approach spins up forty URLs that are byte-for-byte identical except for the place name, and every one of them dumps the user onto the same contact form:

<!-- /plumber-springfield/ -->
<h1>Emergency Plumber in Springfield</h1>
<p>Need a plumber in Springfield? Call now for fast Springfield service.</p>
<meta http-equiv="refresh" content="0; url=/contact/">

<!-- /plumber-riverside/ -->
<h1>Emergency Plumber in Riverside</h1>
<p>Need a plumber in Riverside? Call now for fast Riverside service.</p>
<meta http-equiv="refresh" content="0; url=/contact/">

Nothing on either page is unique except the town. There's no local address, no photos of that job site, no service details that differ by location, and the meta-refresh proves the page was never meant to be read. That's the whole game, and it's exactly what gets flagged.

Doorway pages vs. legitimate landing pages

Location pages and campaign landing pages are fine when each one earns its own keep. Here's where the line sits:

How to check it on your own site

1. Pull your indexed URLs. In Google Search Console, open the Pages report or run site:yourdomain.com and look for clusters of near-identical URLs (city names, service+city combos, "cheap/best/near me" permutations).
2. Diff a sample. Grab five of those pages and compare the body copy. If the only difference is a swapped noun, treat it as a doorway candidate.
3. Follow the click. Load each page as a normal visitor. If it fires a redirect, a meta-refresh, or a JS bounce to a central page, that's a red flag.
4. Check for local proof. Does each location page carry a real, distinct address, phone, hours, and on-the-ground detail? If they all share one NAP, they're clones.
5. Ask the "search-off" test. If search engines vanished tomorrow, would this page still exist and help someone? If the honest answer is no, rebuild or consolidate it.
6. Watch for manual actions. In Search Console under Security & Manual Actions, a "Thin content with little or no added value" flag often points straight at doorway clusters.

Common mistakes and how to fix them

• Spinning up a page per city with no local presence. Fix: only build a location page where you have a real address or genuine service footprint, and fill it with things only a local would know.
• Meta-refresh or JS redirect to a "master" page. Fix: kill the redirect. Let the page stand on its own, or consolidate the thin variants into one strong page with a proper 301.
• Templated copy with a swapped keyword. Fix: write unique content per page (photos, pricing, staff, testimonials, project examples) or don't publish the page at all.
• Confusing pagination or filtered URLs with doorways. Fix: those aren't doorways, but if they're thin and indexable, handle them with canonicals or noindex rather than deleting blindly.
• Deleting everything in a panic after a warning. Fix: consolidate and 301 the good intent into one quality page instead of mass-404ing, which throws away any real links and signals you had.

Frequently asked questions

Are location pages the same as doorway pages?

No. A location page becomes a doorway only when it's templated, thin, and exists purely to catch a search term. If you have a real office in that city and the page has distinct, useful content, it's legitimate. The problem is scale-without-substance, not the concept of a per-city page.

Will Google penalize me automatically or does a human review it?

Both paths exist. Algorithms like the ones behind quality updates can demote doorway clusters on their own, and a human reviewer can also issue a manual action you'll see in Search Console. Doorways often overlap with thin content, so a Panda-style quality demotion is common even without a manual flag.

How is a doorway page different from cloaking or hidden text?

They're separate violations that often travel together. A doorway funnels users through a thin gateway page; cloaking shows search engines different content than users; and hidden text stuffs keywords a visitor can't see. All three are forms of black hat SEO and all three can trigger enforcement.

I inherited a site full of doorway pages. What now?

Audit them, then consolidate. Merge the thin city clones into a smaller set of genuinely useful pages, 301 the retired URLs to their best replacement, and remove any auto-redirects. Don't just noindex-and-forget everything; keep and strengthen the pages that can actually serve a visitor.

Can building better local landing pages at scale ever be safe?

Yes, if each page earns its place with unique local detail and a real reason to exist. The scaled-content policy targets pages made mainly to game rankings, not every templated page. The safe version takes more work per page, which is exactly why it doesn't get flagged.