Doorway Pages vs Cloaking: Which Is Worse for SEO?

Doorway pages vs cloaking: both are spammy SEO tactics that violate Google’s policies, but they work differently and carry different risks. A doorway page is a low-quality page built to rank for a specific search term and push visitors to a single destination. A cloaked page shows one version of itself to a search engine crawler and a different version to a human visitor. Both violate Google's spam policies, but they work differently and carry different risks. Here is how to tell them apart, how Google catches each one, what a penalty looks like, and how to audit your own site before either practice hurts you.

What Is a Doorway Page vs a Cloaked Page?

The distinction matters because the two practices often look similar from the outside — a reader lands on a page that does not feel useful and disappears quickly. The difference is in intent and mechanism.

A doorway page exists to capture a search term, then redirect or push the user onward. It may be a landing page for a service in a city where the business has no office. It may be a "page per keyword" cluster that swaps only the location name across many templates. Google calls this doorway abuse: pages made to rank for similar searches that funnel users to the same place. Pages targeted at different cities that funnel visitors to one page are explicitly listed as an example of doorway abuse under Google's spam policies. The policy applies when the pages exist primarily to manipulate search results rather than to serve real users.

Cloaking is a delivery technique. A page serves one HTML response to a search engine crawler and a different response to a human browser. Common methods include:

• Serving content based on the user-agent string in the HTTP request header.
• Using JavaScript redirects that trigger only for non-bot browsers.
• Hiding content behind layers that bots cannot render but humans can see after clicking.
• Returning different text via server-side logic that checks the visitor's IP or referrer.

The key point is the split delivery: the crawler sees something optimized, the visitor sees something else.

Both practices violate spam policy. Doorway pages create thin, repetitive content that adds little value to the search results. Cloaking attempts to deceive the indexer itself. In practice, doorway pages are far more common because they require no technical trickery — just many low-effort pages. Cloaking requires access to server configuration or JavaScript that can branch on the request context.

A doorway page is not automatically a problem if the page genuinely serves users and the business operates in that location. Pages built for each city where a company has a physical office, staff, and inventory are legitimate location pages when they include real content about that place. The line is crossed when the page exists only to capture a search term and push the reader somewhere else.

How Search Engines Detect Each Practice

Google does not rely on a single signal. It uses automated systems, behavioral analysis, and human review to catch both practices. Understanding the mechanisms helps you audit your own site without guessing.

User-agent detection for cloaking. A crawler identifies itself with a user-agent string in its HTTP request header. Googlebot's user-agent string is not simply 'Googlebot'; it includes additional identifiers that distinguish it from other crawlers. When a server sees that string, it can choose to return one response. When it sees a browser user agent like Mozilla/5.0, it can return another. This split is what cloaking depends on. Google checks whether the URL you submitted to it renders differently than what a human sees at the same address. If the HTML differs between the two views, the page is flagged as cloaked. JavaScript-based cloaking is harder to detect because the bot must render the page fully before comparing it to what a visitor sees, but Google's rendering pipeline handles this.

Machine learning for doorway pages. Doorway pages rarely use technical tricks. They show up through patterns:

1. Clusters of pages built from the same template structure.
2. Pages that share a layout and swap only a few words — city name, service name.
3. High internal link density pointing from all those pages toward one destination.
4. Low average time on page and high bounce rates when crawled by bots.
5. Keyword phrases that overlap heavily across pages rather than representing distinct topics.

Google's ranking systems look for these signals collectively. A single template-driven page is not enough to trigger an action. The system evaluates the cluster as a group — if many pages exist solely to capture similar queries and funnel readers elsewhere, the pattern itself is the signal.

Behavioral analysis of user interactions. Both practices leave traces in how people behave after clicking a result. A doorway page often produces:

• A search result that looks promising (the title matches the query) but the page offers nothing specific to the searcher.
• A quick exit because the reader realizes the page does not serve their intent.
• A redirect or button that sends them to a different URL, sometimes outside the original domain.

Cloaking leaves a different behavioral trace. The visitor sees content that does not match the search intent that brought them there — perhaps because the page they see is the "human" version, which may be thinner, promotional, or misleading relative to what Google indexed. When Google compares its indexed content with what users experience at that URL, the mismatch becomes visible over time.

Detection is not instant. A new doorway page cluster may take weeks or months before Google's automated systems flag it. Cloaking can be caught faster if a search engine crawler renders the page and immediately sees a discrepancy. But neither practice guarantees a penalty — detection leads to a review, and the outcome depends on scale and intent.

What Happens When Your Site Gets Penalized

A penalty for doorway pages or cloaking varies depending on how widespread the practice is and whether Google finds it through automated systems or human review.

Here is what happens next: Google identifies pages that violate spam policy. If the violation is isolated, Google may remove only those pages from search results. If the pattern is systemic — hundreds of template pages, a network of locations with no real presence, or widespread cloaking across the site — Google can apply a manual action against the entire property. A manual action means the site's pages stop appearing in Google Search results until someone submits a reconsideration request and fixes the problem.

The recovery process has three steps:

1. Identify every offending page. This requires checking each URL that exists solely to capture a query and push readers elsewhere. For cloaking, you must verify the server returns identical HTML to both a search engine crawler and a browser at every address.
2. Remove or consolidate the pages. Delete the low-quality pages, merge them into legitimate content, or redirect them to a single authoritative page that genuinely serves the location or topic.
3. Submit a reconsideration request if a manual action was applied. The request should describe the changes made and confirm that the pages violating the guidelines have been removed.

Recovery time depends on severity. A handful of removed pages may take one or two reindexing cycles for Google to reflect the change. A full-site manual action typically takes several weeks after the fix because Google must re-crawl and re-evaluate the entire property before restoring it. The longer the violation persists, the more pages accumulate, and the longer the cleanup takes.

How to Audit Your Site for These Practices

You do not need to guess which pages are problematic. A systematic audit catches both doorway pages and cloaking without relying on a single tool. Run these checks in order to identify problematic pages systematically.

Page-level checks. For each URL on your site:

• Open the page and read the content. Does it provide specific information about the topic, location, or service? Or does it swap a few words from a template and push the reader elsewhere?
• Check the internal links. Do multiple pages link to the same destination page? A cluster of pages funneling to one address is the hallmark of doorway abuse.
• Verify the HTML you see in a browser matches what a search engine crawler sees. Use a user-agent switcher or a tool that lets you view the page as a search engine crawler would. If the text, images, or offers differ between the two views, the page is cloaked.
• Review the meta description and title tag. Identical descriptions across dozens of pages signal a template rather than unique content. Even if Google rewrites the snippet, identical titles across many URLs still point to a structural problem.
• Check for hidden content. Elements with CSS display: none, zero-height containers, or text colored the same as the background can indicate content shown only to humans while the bot sees something else.

Site-wide checks. Look at the architecture as a whole:

• Count how many pages exist for the same type of content (location pages, service pages). More than a dozen pages built from the same template usually means the site has crossed into doorway territory.
• Google's crawl budget guide is for very large or frequently updated sites; a typical small business site does not need to manage crawl budget (duplicates matter because Google picks one URL to show).
• Identify duplicate content. Duplicate content on your own site is not a spam violation — Google picks one canonical URL to show — but near-duplicate pages still dilute your site's authority. Consolidate them.
• Check structured data. Structured data makes a page eligible for a rich result; it does not guarantee one. If you have structured data on pages that are essentially duplicates, you are marking up thin pages that add no value to the search results.
• Review the robots.txt file. Blocking a web crawler from accessing a page prevents it from seeing whether the page is cloaked. Never block JavaScript or CSS resources that affect how a page renders. Check Google Search Central for the current details.

A practical checklist you can run through before publishing any new page:

1. Does this page offer unique information that a user searching for this term would need?
2. Does this page link to a different destination instead of providing the answer here?
3. Does this page's HTML match exactly what a human visitor sees at the same URL?
4. Is this page part of a larger cluster of template pages swapping only location or keyword names?
5. Does this page exist because the business genuinely operates in that place, or because a query exists for it?

If the answer to question 4 is "yes" and the answer to question 5 is "no," the page is likely a doorway page. Remove it. Consolidate its content into a legitimate location page where the business has real operations, or delete it entirely if the location is not served.

Related reading: Doorway Pages vs Location Pages · How to Create Location Pages for SEO · Doorway Pages vs Landing Pages

Every post here was written by Vannor. Researched, written and reviewed by the Vannor Engine on our own infrastructure.

Start your 7-day free trial