SEOWhat Are Doorway Pages?

What Are Doorway Pages?

Webmasters sometimes use bridge pages or doorway pages to improve traffic. This describes how they are technically implemented, such as using cloaking, and some of the problems they have

Webmasters are sometimes told to submit “bridge” pages or “doorway” pages to search engines to improve their traffic. Doorway pages are created to do well for particular phrases. They are also known as portal pages, jump pages, gateway pages, entry pages, and by other names as well.

The More About Doorway Pages article available to
Search Engine Watch members provides more information about doorway pages & tips on avoiding problems with search engines.
Click here to learn more about becoming a member

Doorway pages are easy to identify in that they have been designed primarily for search engines, not for human beings. This page explains how these pages are delivered technically, and some of the problems they pose.

Low Tech Delivery

There are various ways to deliver doorway pages. The low-tech way is to create and submit a page that is targeted toward a particular phrase. Some people take this a step further and create a page for each phrase and for each search engine.

One problem with this is that these pages tend to be very generic. It’s easy for people to copy them, make minor changes, and submit the revised page from their own site in hopes of mimicking any success. Also, the pages may be so similar to each other that they are considered duplicates and automatically excluded by the search engine from its listings.

Another problem is that users don’t arrive at the goal page. Say they did a search for “golf clubs,” and the doorway page appears. They click through, but that page probably lacks detail about the clubs you sell. To get them to that content, webmasters usually propel visitors forward with a prominent “Click Here” link or with a fast meta refresh command.

By the way, this gap between the entry and the goal page is where the names “bridge pages” and “jump pages” come from. These pages either “bridge” or “jump” visitors across the gap.

Some search engines no longer accept pages using fast meta refresh, to curb abuses of doorway pages. To get around that, some webmasters submit a page, and then swap it on the server with the “real” page once a position has been achieved.

This is “code-swapping,” which is also sometimes done to keep others from learning exactly how the page ranked well. It’s also called “bait-and-switch.” The downside is that a search engine may revisit at any time, and if it indexes the “real” page, the position may drop.

Another note here: simply taking meta tags from a page (“meta jacking”), does not guarantee a page will do well. In fact, sometimes resubmitting the exact page from another location does not gain the same position as the original page.

There are various reason why this occurs which go beyond this article, but the key point to understand is that you aren’t necessarily finding any “secrets” by viewing source code, nor are you necessarily giving any away.

Agent Delivery

The next step up is to deliver a doorway page that only the search engine sees. Each search engine reports an “agent” name, just as each browser reports a name.

The advantage to agent name delivery is that you can send the search engine to a tailored page yet direct users to the actual content you want them to see. This eliminates the entire “bridge” problem altogether. It also has the added benefit of “cloaking” your code from prying eyes.

Well, not quite. Someone can telnet to your web server and report their agent name as being from a particular search engine. Then they see exactly what you are delivering. Additionally, some search engines may not always report the exact same agent name, specifically to help keep people honest.

IP Delivery / Page Cloaking

Time for one more step up. Instead of delivering by agent name, you can also deliver pages to the search engines by IP address, assuming you’ve compiled a list of them and maintain it.

Everyone and everything that accesses a site reports an IP address, which is often resolved into a host name. For example, I might come into a site while connected to AOL, which in turn reports an IP of 199.204.222.123 (FYI, that’s not real, just an example). The web server may resolve the IP address into an address: ww-tb03.proxy.aol.com, for example.

The Page Cloaking article available to Search Engine Watch members provides more information about page cloaking, including links to cloaking software providers.
Click here to learn more about becoming a member

If you deliver via IP address, you guarantee that only something coming from that exact address sees your page. Another term for this is page cloaking, with the idea that you have cloaked your page from being seen by anyone but the search engine spiders.

More Resources

More About Doorway Pages
Provides more information about doorway pages, including tips on avoiding problems with search engines. Available to Search Engine Watch members.

Page Cloaking
Explains issues and some basic technical details of enabling a page “cloaking” system, which often goes hand-in-hand with doorway page efforts. Available to Search Engine Watch members.

Search Engines & Legal Issues
See the pagejacking section for articles involving doorway pages that have resulting in legal action.

Resources

The 2023 B2B Superpowers Index

whitepaper | Analytics The 2023 B2B Superpowers Index

8m
Data Analytics in Marketing

whitepaper | Analytics Data Analytics in Marketing

10m
The Third-Party Data Deprecation Playbook

whitepaper | Digital Marketing The Third-Party Data Deprecation Playbook

1y
Utilizing Email To Stop Fraud-eCommerce Client Fraud Case Study

whitepaper | Digital Marketing Utilizing Email To Stop Fraud-eCommerce Client Fraud Case Study

1y