Robots Exclusion Standard

From Wikipedia, the free encyclopedia

(Redirected from Robots exclusion protocol)

For restricting Wikipedia bots, see Template:Bots.

The robots exclusion standard, also known as the Robots Exclusion Protocol or robots.txt protocol, is a convention to prevent cooperating web spiders and other web robots from accessing all or part of a website which is, otherwise, publicly viewable. Robots are often used by search engines to categorize and archive web sites, or by webmasters to proofread source code. The standard complements Sitemaps, a robot inclusion standard for websites.

A robots.txt file on a website will function as a request that specified robots ignore specified files or directories in their search. This might be, for example, out of a preference for privacy from search engine results, or the belief that the content of the selected directories might be misleading or irrelevant to the categorization of the site as a whole, or out of a desire that an application only operate on certain data.

For websites with multiple sub-domains, each sub-domain must have its own robots.txt file. If example.com had a robots.txt file but a.example.com did not, the rules that would apply for example.com will not apply to a.example.com.

The protocol, however, is purely advisory. It relies on the cooperation of the web robot, so that marking an area of a site out of bounds with robots.txt does not guarantee privacy. Some web site administrators have tried to use the robots file to make private parts of a website invisible to the rest of the world, but the file is necessarily publicly available and its content is easily checked by anyone with a web browser.

There is no official standards body or RFC for the robots.txt protocol. It was created by consensus in June 1994 by members of the robots mailing list (robots-request@nexor.co.uk). The information specifying the parts that should not be accessed is specified in a file called robots.txt in the top-level directory of the website. The robots.txt patterns are matched by simple substring comparisons, so care should be taken to make sure that patterns matching directories have the final '/' character appended, otherwise all files with names starting with that substring will match, rather than just those in the directory intended.

With ACAP 1.0 (Automated Content Access Protocol) a possible add-on for the Robots Exclusion Standard was released on November 30, 2007.

Of recent interest is the percentage of website pages that have robots.txt files and which specific robots are given privileges to crawl specific website files. To help understand these issues, a publicly available robots.txt search engine, BotSeer, has been developed to search and index robots.txt files.

1 Examples
- 1.1 Compatibility
2 Nonstandard extensions
3 Extended Standard
4 Alternatives
- 4.1 HTML meta tags for robots
5 References
6 See also
7 External links

This example allows all robots to visit all files because the wildcard "*" specifies all robots:

User-agent: *
Disallow:

This example keeps all robots out:

User-agent: *
Disallow: /

The next is an example that tells all crawlers not to enter into four directories of a website:

User-agent: *
Disallow: /cgi-bin/
Disallow: /images/
Disallow: /tmp/
Disallow: /private/

Example that tells a specific crawler not to enter one specific directory:

User-agent: BadBot
Disallow: /private/

Example that tells all crawlers not to enter one specific file:

User-agent: *
Disallow: /directory/file.html

Note that all other files in the specified directory will be processed.

Example demonstrating how comments can be used:

# Comments appear after the "#" symbol at the start of a line, or after a directive
User-agent: * # match all bots
Disallow: / # keep them out

In order to prevent access to all pages by robots, do not use

Disallow: *

as this is not a stable standard extension.

Instead:

Disallow: /

should be used.

The Sitemap parameter is supported by major crawlers (including Google, Yahoo, MSN, Ask). Sitemaps specifies the location of the site's list of URLs. This parameter is independent from User-agent parameter so it can be placed anywhere in the file.

Sitemap: http://www.example.com/sitemap.xml.gz

An explanation of how to author SiteMap files can be found at sitemaps.org

Several major crawlers support a Crawl-delay parameter, set to the number of seconds to wait between successive requests to the same server: ^[1] ^[2]

User-agent: *
Crawl-delay: 10

Some major crawlers support an Allow directive which can counteract a previous Disallow directive.^[3] ^[4]

For example:

User-agent: Googlebot
Disallow: /folder1/
Allow: /folder1/myfile.html

An Extended Standard for Robot Exclusion has been proposed, which adds several new directives, such as Visit-time and Request-rate. For example:

User-agent: *
Disallow: /downloads/
Request-rate: 1/5         # maximum rate is one page every 5 seconds
Visit-time: 0600-0845     # only visit between 6:00 AM and 8:45 AM UT (GMT)

The first version of the Robot Exclusion standard does not mention anything about the "*" character in the Disallow: statement. Modern crawlers like Googlebot and Slurp recognize strings containing "*", while MSNbot and Teoma interpret it in different ways. ^[5]

While robots.txt is the older and more widely accepted method, there are others (which can be used together with robots.txt) that allow greater control, like disabling indexing of images only or disabling archiving of page contents.

HTML meta tags can be used to exclude robots according to the contents of web pages. Again, this is purely advisory, and also relies on the cooperation of the robot programs. For example,

 name="robots" content="noindex,nofollow" />

within the HEAD section of an HTML document tells search engines such as Google, Yahoo!, or MSN to exclude the page from its index and not to follow any links on this page for further possible indexing.

If the author of the web page doesn't have access to the domain root, then creating a robots.txt file is not an option for excluding robots from indexing the page. In this situation the meta tag comes in as a handy alternative.

(See HTML Author's Guide to the Robots META tag.)