Doorway Pages

TL;DR — Doorway pages are pages built to rank in search and then push you somewhere else, instead of being useful on their own. The classic modern example is a business with hundreds of near-identical “[service] in [city]” pages that all dump you onto the same contact form. Google treats them as spam. Real location pages are fine — the difference is whether each page actually gives you something specific to that place.

What a doorway page is

Google’s spam policies define doorway abuse as pages or sites created to rank for similar queries that funnel users to intermediate destinations. Evidence for this claim Official or primary documentation supporting the adjacent article claim, with scope limited to the source's published description. Scope: No ranking guarantee or undisclosed system mechanics are inferred beyond the cited source. Confidence: high · Verified: 2026-07-14 Google: Spam policies A legitimate location page needs distinct, useful purpose; the policy label cannot be decided from a template alone. Evidence for this claim Official or primary documentation supporting the adjacent article claim, with scope limited to the source's published description. Scope: No ranking guarantee or undisclosed system mechanics are inferred beyond the cited source. Confidence: high · Verified: 2026-07-14 Google: Spam policies

A doorway page exists to grab a ranking for a search, not to help the person who clicks. You land on it, realize there’s nothing genuinely useful there, and the page’s only real job is to shuffle you along to wherever the site actually wants you to go. Google calls this “doorway abuse” and classifies it as spam.

The name covers a few related ideas you may also hear — doorway sites, gateway pages, bridge pages — but they all describe the same pattern: a page whose purpose (ranking) and value (close to zero) don’t match.

The easiest example to picture

Imagine a plumber who wants to rank in every nearby town. So they generate 200 pages:

• “Plumber in Springfield”
• “Plumber in Shelbyville”
• “Plumber in Ogdenville”

…and so on. Every page is the same text with one town name swapped in, and every page has the same “Call us!” button leading to the same form. The plumber doesn’t have an office, staff, or anything genuinely different in 200 towns — they just want to show up when someone searches each one. Those are doorway pages.

Real location pages are NOT doorways

This is the part people get wrong. A page that targets a city is not automatically a doorway. If you have a real shop in Springfield with its own address, hours, staff, photos, and reviews, a page about that location is genuinely useful — and Google is fine with it.

The simple gut check: does each page give the visitor something specific and real about that place, or is it the same page with a different name pasted in? If it’s the latter, and everything funnels to one destination, you’ve built doorways.

Why this matters if you’re doing pages at scale

This is the most common trap in programmatic SEO — generating lots of pages from a template. The technique itself is fine; the problem is when the pages are thin and exist only to capture rankings. Google penalizes that with both visible penalties and silent ranking drops.

Want the deeper version — Google’s six self-test questions, the manual-vs-algorithmic difference, and how to fix a stack of pages that crossed the line? Switch to the Advanced tab.

TL;DR — Doorway pages are pages or sites built to rank for specific, similar queries that funnel users to an intermediate destination less useful than the final one. In programmatic SEO the modern form is templated [service] in [city] stacks where the content is nearly identical from page to page and everything funnels to one contact form. The test is intent + unique value, not whether you target a location. Google’s 2015 update shipped six diagnostic questions — use them as a checklist. Doorways overlap with, but are distinct from, scaled-content abuse and thin content. Enforcement is both manual (visible in Search Console) and algorithmic (silent), and it’s an active policy — Google’s March 2024 core update added new spam policies, including scaled content abuse, that raise the bar for templated pages. The fix is consolidation, genuine differentiation, or pruning.

What Google actually says

The policy focuses on intent and user journey, not a fixed page-count or word-count threshold. Evidence for this claim Official or primary documentation supporting the adjacent article claim, with scope limited to the source's published description. Scope: No ranking guarantee or undisclosed system mechanics are inferred beyond the cited source. Confidence: high · Verified: 2026-07-14 Google: Spam policies Apply it by reviewing whether pages independently satisfy users rather than automatically treating scaled pages as violations. Evidence for this claim Official or primary documentation supporting the adjacent article claim, with scope limited to the source's published description. Scope: No ranking guarantee or undisclosed system mechanics are inferred beyond the cited source. Confidence: high · Verified: 2026-07-14 Google: Spam policies

Straight from the spam policies: “Doorway abuse is when sites or pages are created to rank for specific, similar search queries. They lead users to intermediate pages that are not as useful as the final destination.” Sites that violate the policy “may rank lower in results or not appear in results at all” — and can also pick up a manual action.

The policy lists its own examples of the pattern, and they read like a description of a badly-executed programmatic project:

• “Having multiple websites with slight variations to the URL and home page to maximize their reach for any specific query”
• “Having multiple domain names or pages targeted at specific regions or cities that funnel users to one page”
• “Generating pages to funnel visitors into the actual usable or relevant portion of a site”
• “Creating substantially similar pages that are closer to search results than a clearly defined, browseable hierarchy”

The funnel-to-one-destination test

If I had to give you one practical test, it’s this: do all the pages ultimately funnel users to the same destination? A plumber’s 200 city pages that each lead to the same contact form, differing only in the city in the H1, are doorways by Google’s own definition. Genuine location pages lead to genuinely different content — the actual location, the local staff, the portfolio of work done in that area. Same template, different substance.

Doorways are the most common modern programmatic trap

The classic doorway — separate domains cloaking and redirecting to one site — is largely extinct. The version I see in audits now is templated programmatic pages at scale: [service] in [city] pages generated from a spreadsheet, nearly identical page to page, with minimal unique value per URL. Google’s systems have gotten progressively better at catching this at scale, because scale is exactly what makes it detectable — identical content profiles, engagement signals showing users bounce immediately, and internal-link structures that point at dead-end pages.

That [service] in [city] pattern is the one I flag earliest in any programmatic plan. It’s the modifier that’s most likely to produce real, useful pages and the one most likely to produce doorways — it all comes down to whether the data behind each page is real.

Google’s six questions — use them as a self-audit

The most useful thing Google ever published on this came with the March 2015 doorway update (the algorithm rolled out the following month). It introduced six questions you can run your own pages against. I treat these as a checklist:

1. “Is the purpose to optimize for search engines and funnel visitors into the actual usable or relevant portion of your site, or are they an integral part of your site’s user experience?”
2. “Are the pages intended to rank on generic terms yet the content presented on the page is very specific?”
3. “Do the pages duplicate useful aggregations of items (locations, products, etc.) that already exist on the site for the purpose of capturing more search traffic?”
4. “Are these pages made solely for drawing affiliate traffic and sending users along without creating unique value in content or functionality?”
5. “Do these pages exist as an ‘island?’ Are they difficult or impossible to navigate to from other parts of your site?”
6. “Are links to such pages from other pages within the site or network of sites created just for search engines?”

If you’re answering “yes” to several of these about your own pages, you’re in doorway territory — regardless of word count.

The “island” red flag

Question five deserves its own callout because it’s where programmatic projects fail quietly. Generate thousands of URLs with no internal-linking integration and you’ve built exactly the orphan/island pattern Google asks about — pages a user can only reach from a search result, never by browsing the site. That’s both a crawl/indexing problem and a doorway signal. Build a real hub-and-spoke structure or you’re flagging yourself.

Doorways vs. scaled content vs. thin content

People conflate three distinct (but overlapping) Google policies. Keep them separate:

• Doorway abuse — pages created to rank, then funnel users to a final destination.
• Scaled content abuse — content generated primarily to manipulate rankings, “no matter how it’s created.”
• Thin content — pages with little substantive original content.

A single programmatic location page can trip all three at once, but each has its own policy language and its own enforcement path. Knowing which one you’ve triggered tells you what the fix is.

Manual actions vs. algorithmic demotion

A myth worth killing: “doorways only get manual penalties, so I’ll be notified.” Not true. Doorway pages get hit two ways:

• Manual actions — a human reviewer flags the site; you see it in Search Console and can file a reconsideration request after fixing it.
• Algorithmic demotion — your pages just quietly stop ranking, with nothing in Search Console to tell you why.

Most modern enforcement is the silent, algorithmic kind. If a location-page stack lost traffic around a known update and you got no manual action, that’s the most likely explanation.

Enforcement is live, not historical

This isn’t a 2015 curiosity. The 2015 update established the modern policy; in November 2022, around the October 2022 spam update, location-page stacks took visible hits and Danny Sullivan reiterated that intent is the issue; and Google’s March 2024 core update added new spam policies — including scaled content abuse — aimed squarely at low-value content produced at scale, templated location pages included. I haven’t found a Google statement singling out location-page stacks by name in the 2024–2025 updates, but the direction is consistent: treat doorway risk as actively enforced, not a historical artifact.

What a legitimate geo page looks like

Google explicitly anticipates the “but I have real offices” objection — and accommodates it. A geo-targeted page is not a doorway when it has:

• Unique, locally verifiable information — specific address, hours, local staff, local case studies, local reviews.
• Real integration into the site’s navigation — reachable by browsing, not just from a search result.
• No duplication of an aggregation that already exists elsewhere on the site.
• Standalone value — content a user would find useful independent of whether it ranks.

Adding word count does not convert a doorway into one of these. Google evaluates whether the page delivers distinct, verifiable value for that location, not whether it’s 800 or 1,500 words.

What Mueller said about city pages

The clearest rep guidance came from John Mueller in a December 2019 hangout (documented by Barry Schwartz at Search Engine Roundtable; the exact wording is from secondary reporting, not a clean transcript). An SEO described a plan to build 1,300 city landing pages targeting keyword-plus-city combinations. Mueller’s response: that would be a doorway strategy and against Google’s guidelines — the problem being swapping out one word on a page where the rest of the content is the same. His recommended alternative is the one I give too: pick 15–20 key service areas and make those pages genuinely excellent rather than generating hundreds of thin copies.

How to fix doorway pages

Three moves, in rough order of preference:

1. Consolidate. If 200 city pages all funnel to one form and add nothing per location, replace them with a small number of genuinely strong pages — or a single excellent service page plus a real list of areas served.
2. Genuinely differentiate. If you do have real, distinct value per location, surface it: real local content, real internal links, real reasons the page exists. Make each page pass Google’s six questions.
3. Remove or noindex the rest. Combinations with no demand and no real data shouldn’t have indexable pages. Prune them or noindex them — this is the same index-bloat discipline that governs any programmatic project.

The honest framing: doorway risk is a data problem, not a template problem. If deleting the city name leaves a generic page, no amount of template polish saves it. Fix the data or don’t publish the page.

AI summary

A condensed take on the Advanced version:

• Doorway pages = pages or sites built to rank for specific, similar queries that funnel users to an intermediate destination “not as useful as the final destination.” Google classifies them as spam.
• Modern form = templated [service] in [city] stacks that are nearly identical page to page and all funnel to one contact form — the most common programmatic-SEO trap.
• The test is intent + unique value, not location targeting. Real geo pages (address, hours, local staff, local content, browseable) are explicitly fine.
• The funnel test: if all pages ultimately lead to the same destination and differ only by a word in the H1, they’re doorways.
• Use Google’s six 2015 questions as a self-audit — purpose, generic-vs-specific mismatch, duplicated aggregations, affiliate funneling, “island” pages, search-only internal links.
• “Island”/orphan pages (reachable only from search) are a key red flag — fix with hub-and-spoke internal linking.
• Three distinct policies: doorway abuse, scaled content abuse, thin content — a programmatic page can trip all three at once.
• Enforcement is manual (visible in Search Console) AND algorithmic (silent). Most modern enforcement is silent.
• Live, not historical: 2015 update, 2022 spam update, and the March 2024 core update’s new spam policies (scaled content abuse, etc.) all point the same direction — no single Google statement names location-page stacks specifically in 2024–2025.
• Mueller on 1,300 city pages: do 15–20 areas genuinely well instead.
• Fix: consolidate, genuinely differentiate, or prune/noindex. It’s a data problem, not a word-count problem.

Official documentation

The primary-source policies that decide whether your pages cross the line.

Google

• Spam policies — Doorways — the canonical definition and Google’s own examples of doorway abuse.
• An update on doorway pages (March 2015) — the foundational modern statement, including the six diagnostic questions. (Original: webmasters.googleblog.com.)
• Spam policies — Scaled content abuse — the related policy programmatic pages also trip (“no matter how it’s created”).
• Creating helpful, reliable, people-first content — the “Who, How, Why” self-assessment that backs the intent test.

Bing / Microsoft

• Bing Webmaster Guidelines — Bing classifies doorway pages under deceptive tactics, alongside cloaking and keyword stuffing; the framing is the same as Google’s (pages built for crawlers, not the visitor).

Quotes from the source

On-the-record statements on doorway pages from Google. Each Google-docs link is a deep link that jumps to the quoted passage.

Google — the definition and examples

• “Doorway abuse is when sites or pages are created to rank for specific, similar search queries. They lead users to intermediate pages that are not as useful as the final destination.” — Google Search Central, spam policies. Jump to quote
• “Having multiple domain names or pages targeted at specific regions or cities that funnel users to one page.” — Google’s own example of doorway abuse, spam policies. Jump to quote
• “Creating substantially similar pages that are closer to search results than a clearly defined, browseable hierarchy.” — Google’s own example of doorway abuse, spam policies. Jump to quote

Danny Sullivan, Google — intent is the issue, not format

• “content written primarily for search engines rather than humans is the issue.” — Danny Sullivan, Google (November 2022, around the October 2022 spam update). Read the coverage

John Mueller, Google — city/location pages (via Barry Schwartz, Search Engine Roundtable; documented through secondary reporting, not a verbatim transcript)

• Mueller warned an SEO against building 1,300 city-based landing pages, describing the problematic pattern as swapping out one word on a page where the rest of the content is the same, and recommending a focus on a small set of genuinely excellent service-area pages instead. Read the coverage

Doorway self-audit — Google’s six questions

Run each page (or page template) against Google’s 2015 questions. A “yes” is a warning sign; several “yes” answers means you’ve likely built doorways.

• Purpose — Are these pages built to optimize for search and funnel visitors into the “real” part of the site, rather than being an integral part of the user experience?
• Generic-vs-specific mismatch — Are the pages aimed at generic terms while the content on them is oddly specific (or vice versa)?
• Duplicated aggregations — Do they duplicate aggregations of locations/products that already exist elsewhere on the site, just to capture more traffic?
• Affiliate funneling — Do they exist only to draw traffic and send users onward without adding unique content or functionality?
• Island pages — Are they difficult or impossible to reach from other parts of the site (reachable only via search)?
• Search-only links — Are internal links to these pages created just for search engines rather than for users?

The practical doorway gut-check

• Funnel test — Do all the pages ultimately lead to the same destination (one contact form, one signup)? If yes, that’s the doorway signature.
• Delete-the-modifier test — Remove the city/keyword from a page. Is what’s left a generic, could-be-anything page? Then it’s thin.
• Verifiable local value — Does each page carry real, location-specific info (address, hours, staff, local work) a user would value independent of ranking?
• Navigability — Can a human reach the page by browsing the site, not only from a SERP?
• Scale sanity — Are you generating a page for every grid combination regardless of demand and real data? Prune the ones with neither.

The mental models

1. Purpose vs. value — the core mismatch. Every doorway has the same defect: its purpose is ranking and its value is negligible. Hold any page up to that. If it exists to capture a query and the visitor gets nothing distinct, the format doesn’t matter — it’s a doorway.

2. The funnel-to-one-destination test. Trace where every page sends the user. If 200 pages all end at the same form and differ only by a word in the H1, they’re doorways by Google’s own definition. Genuine location pages lead to genuinely different content.

3. Intent, not format (Sullivan’s line). The policy targets pages written primarily for search engines rather than humans. AI-written, human-written, spun, templated — none of that decides it. Intent and value do. Conversely, a templated page is fine if it genuinely serves the user.

4. The three “not the same” policies. Doorway abuse ≠ scaled content abuse ≠ thin content. They overlap and a single page can trip all three, but each has its own language and enforcement. Identify which one you triggered to know the fix.

5. The fix ladder — consolidate → differentiate → prune. Consolidate thin stacks into a few strong pages; genuinely differentiate the ones with real value; noindex or remove the combinations with no demand and no data. Start at the top of the ladder unless you can prove distinct per-page value.

6. Data problem, not template problem. The recurring root cause. If deleting the modifier leaves a generic page, the dataset is too shallow — adding text won’t fix it. Fix the data or don’t publish the page.

Doorway vs. legitimate location page — cheat sheet

Doorway vs. neighboring policies

Fast facts

• Definition: pages built to rank that funnel users to a more useful destination.
• Modern form: templated [service] in [city] stacks at scale.
• The test: intent + unique value — not whether you target a location.
• 2015 update: introduced the six diagnostic questions; algorithm rolled out April 2015.
• Enforcement: manual (visible in Search Console) and algorithmic (silent).
• Mueller’s number: prefer 15–20 strong service-area pages over 1,300 thin ones.

Playbook: a location-page stack loses search traffic

Use this when a large set of similar geo pages drops after a core or spam update, especially when Search Console shows no manual action. This is a diagnosis and cleanup sequence, not a promise that rankings will return.

Step 1 — Separate manual from algorithmic enforcement. Check Search Console’s Manual Actions report and record the drop date by page template. If a doorway-related manual action exists, preserve its wording and affected scope for the eventual reconsideration request. If there is no manual action, continue with an algorithmic-quality investigation; do not assume the absence of a message clears the pages.

Step 2 — Inventory the whole pattern. Export every URL built from the location template, its final destination, index state, organic trend, internal-link source, and the location-specific fields it renders. If the drop is isolated to one template, keep the audit scoped there. If multiple templates fell together, repeat the inventory for each.

Step 3 — Run the funnel and modifier tests. Group pages that send users to the same contact or service destination, then remove the city or region references from samples. If what remains is generic, mark the cluster for consolidation or removal. If the page still contains verifiable local value, send it to Step 4 for a stricter review.

Step 4 — Apply Google’s six doorway questions. Check purpose, generic-versus-specific mismatch, duplicated aggregations, affiliate-style funneling, island pages, and search-only links. If several answers are “yes,” treat the page as part of the doorway pattern. If answers are “no,” document the unique evidence instead of adding generic copy merely to make the page longer.

Step 5 — Assign one honest disposition per cluster. Consolidate substantially similar pages into a strong service or areas-served page. Keep and genuinely differentiate pages backed by real locations, staff, hours, reviews, or local work. Remove or noindex combinations with no demand and no distinct data. Redirect a retired URL only when a genuinely equivalent destination exists; do not funnel every URL to an unrelated homepage.

Step 6 — Repair discovery paths. Update internal links, hubs, navigation, canonicals, and sitemaps to reflect the surviving set. If a kept page remains an island, integrate it into a browseable hierarchy. If no user-facing route to it makes sense, revisit whether the page should remain indexable.

Step 7 — Validate and monitor the pattern. Crawl the section to confirm that removed URLs, redirects, directives, internal links, and sitemaps agree. Track the surviving template rather than repeatedly submitting individual URLs. If a manual action was present, request reconsideration only after the full pattern is fixed and explain the scope, evidence, and cleanup. If the impact was algorithmic, allow for reassessment with no guaranteed recovery date.

Prompts for a doorway-page review

Score a location template against the doorway questions

Paste the rendered copy from several pages, their URLs, internal-link paths, and final destinations. Expect evidence-based flags, not a verdict based on word count.

Audit these location pages for doorway risk using Google's six diagnostic areas:
1. Search-ranking purpose versus an integral user experience.
2. Generic-query and overly specific-content mismatch.
3. Duplication of a useful location or product aggregation already on the site.
4. Funneling traffic onward without unique content or functionality.
5. Island pages that users cannot reach by browsing.
6. Internal links created mainly for search engines.

Also run two practical checks: whether many pages funnel to the same final destination,
and whether deleting the location modifier leaves generic copy.

For each URL, return low, medium, or high risk; quote the supplied evidence for every
flag; identify what verifiable local value is present; and recommend keep-and-improve,
consolidate, noindex, or remove. Do not treat location targeting or a shared template as
proof by itself. Do not invent offices, staff, reviews, local work, or demand.

[PASTE PAGE SAMPLES, NAVIGATION PATHS, AND DESTINATIONS]

Build a consolidation map for a flagged stack

Paste a URL inventory with location, destination, traffic, internal links, and distinct local fields. Expect a proposed disposition with uncertainty called out.

Create a cleanup map for this suspected doorway-page stack.

Group substantially similar URLs by service and final destination. For each URL, choose
one proposed action: retain because supplied local evidence supports standalone value;
consolidate into a broader service/area page; noindex while it remains useful to users;
or remove. Recommend a redirect only when the inventory contains a genuinely equivalent
destination. List the internal links, hubs, canonicals, and sitemap entries that must
change for each group.

Separate facts from judgment and flag rows that need a human to verify real-world local
operations. Do not manufacture a destination, local differentiator, or recovery promise.

[PASTE LOCATION-PAGE INVENTORY]

Resources worth your time

My related writing

• Programmatic SEO — the pillar this risk sits under; where templated pages succeed and where they cross into doorways.
• Canonicalization — duplicate-content signals that overlap with how doorways get detected.
• The Beginner’s Guide to Technical SEO — where thin content and site architecture (the “island” signal) fit in the bigger picture.
• When Should You Worry About Crawl Budget? — relevant because large doorway stacks waste crawl on dead-end URLs.

From around the industry

• An update on doorway pages (Google Search Central) — the source for the six questions; still the clearest statement of the policy.
• Google’s Spam Policies — Doorways — the current canonical policy text and examples.
• Location pages and the October 2022 spam update (Search Engine Land) — Danny Sullivan on intent over format, in the context of location-page deindexing.
• Google: City Landing Pages Can Be Doorway Pages (Search Engine Roundtable, Barry Schwartz) — Mueller’s 1,300-city-page warning.
• Google’s Doorway Algorithm Update (Search Engine Watch) — contemporary coverage of the 2015 rollout.
• Location pages vs. doorway pages (Manning Marketing) — a practical look at where the line sits for local businesses.

Test yourself: Doorway Pages

Five quick questions on what doorway pages are and how to spot them. Pick an answer for each, then check.

Doorway Pages

Doorway pages are pages or sites built to rank for specific search queries that then funnel users to a different destination instead of being useful in their own right. Google treats them as spam.

Related: Programmatic SEO, Thin Content

Doorway Pages

Doorway pages are pages — or whole sites — created to rank for specific, similar search queries that then send users on to a different, more useful destination rather than serving as genuinely valuable content themselves. Google puts it plainly: “Doorway abuse is when sites or pages are created to rank for specific, similar search queries. They lead users to intermediate pages that are not as useful as the final destination.” The defining trait is a mismatch between a page’s purpose (ranking) and its value (negligible): the visitor is just passing through.

The classic version — separate domains cloaking and redirecting to one site — is mostly extinct. The modern version is templated location or keyword pages at scale: hundreds of [service] in [city] pages, nearly identical page to page, that all funnel users to the same contact form. That makes doorway abuse the most common spam trap in programmatic SEO, where one template plus a shallow dataset stamps out URLs whose only differentiator is a word in the H1.

The line isn’t whether a page targets a city — Google explicitly allows legitimate geo-targeted pages. The test is intent and unique value. A real location page gives users something specific to that location (address, hours, local staff, local work) and is reachable from the rest of the site; a doorway is a thin clone that only exists to capture ranking. As Danny Sullivan framed it, content written primarily for search engines rather than humans is the issue.

Enforcement is both manual (a manual action you’ll see in Search Console) and algorithmic (silent demotion). Google’s 2015 doorway update established the policy, and its March 2024 core update added further spam policies — including scaled content abuse — aimed at low-value content produced at scale; no Google statement names location-page stacks specifically, but the direction is consistent — this is a live risk, not a historical one.

Related: Programmatic SEO, Thin Content

Changelog