When I first started writing my first website, I did not really think that I would ever have
any reason why I would want to create a
robots.txt file. After all, did I not want
search engine robots to spider and thus index every document in my site? Yet today, all my sites,
robots.txt file in their root directory. This article explains why you might also want to
include a robots.txt file on your sites, how you can do so, and notes some
common mistakes made by new webmasters with regards the
For those new to the
robots.txt file, it is merely a text file implementing what is known as
the Standard for Robot Exclusion. The file is placed in the main directory of a website and
advises spiders and other robots which directories or files they should not access. The file
is purely advisory — not all spiders bother to read it let alone heed it. However, most, if
not all, the spiders sent by the major search engines to index your site will read it and obey
the rules contained within the file (provided those rules make sense).
What is the purpose of a
Many, if not most websites, have some sort of scripts (computer programs) that run on their website. For example, many websites have some sort of contact form, such as that created using the Free Feedback Form Script Wizard. Some also have a search engine on their site, such as that which you see in the left column of every page on thesitewizard.com.
When search engine robots or spiders index your site, they actually call your scripts just as a browser would. If your site is like mine, where the scripts are solely meant for the use of humans and serve no practical use for a search engine (why should a search engine need to invoke my feedback form or use my site search engine?) you may want to block spiders from the directories that contain your scripts. For example, I block spiders from my feedback form, search engine and CGI-BIN directory. Hopefully, this will reduce the load on the web server that occurs when scripts are executed by removing unnecessary executions.
Of course there are the occasional ill-behaved robots that hit your server at high speed. Such spiders can actually bring down your server or at the very least slow it down for the real users who are trying to access it. If you know of any such spiders, you might want to exclude them too. You can do this with a robots.txt file. Unfortunately though, ill-behaved spiders often ignore robots.txt files as well.
If you look at your website's web statistics,
you will undoubtedly find many requests for the
robots.txt file by various search engine spiders. The search engines try to retrieve
robots.txt file before indexing your website, to see if you have any special instructions for them.
If you don't have a
robots.txt file, your web server will return a 404 error page to the engine instead. For those who have
customized their 404 error document, that customised 404 page
will end up being sent to the spider repeatedly throughout the day. Now, if you have customized your 404 page, chances are that it's bigger
than the standard server error message "404 File Not Found" (since you will want your error page to say more than the default error message).
In other words, failing to create a
robots.txt will cause the search engine spider to use up more of your bandwidth as a result of
its repeated retrieval of your large 404 error file. (How much more depends, of course, on the size of your 404 error page.)
Some spiders may also request for files which you feel they should not. For example, some
search engines also index graphic files (like ".gif", ".jpg" and ".png" files"). If you don't want them to do so,
you can ban it from your graphic files directory using your
I don't know about you, but one of the things I check from my web statistics is the list of URLs that visitors tried to access, but met with a 404 File Not Found Error. Often this tells me if I made a spelling error in one of the internal links on one of my sites (yes, I know — I should have checked all links in the first place, but mistakes do happen).
If you don't have a
robots.txt file, you can be sure that
/robots.txt is going to feature in
your web statistics 404 report, adding clutter and perhaps unnecessarily
distracting your attention from the real bad URLs that need your attention.
Sometimes you don't want a particular spider to index your site for some reason or other. Perhaps the robot is ill-behaved and spiders your site at such a high speed that it takes down your entire server. Or perhaps you prefer that you don't want the images on your site indexed in an image search engine. With a robots.txt file, you can exclude certain spiders from indexing your site with a robots.txt directive, provided the spider obeys the rules in that file.
robots.txt file is extremely easy. It's just an ASCII text file that you place at
the root of your domain. For example, if your domain is
place the file at
www.example.com/robots.txt. For those who don't know what an ASCII text file is, it's just a plain
text file that you create with a type of program called an ASCII
text editor. If you use Windows, you already have an ASCII text editor on your system, called Notepad. (Note: only
Notepad on the default Windows system is an ASCII text editor; do not use WordPad, Write, or Word.)
The file basically lists the names of spiders on one line, followed by the list of directories or files it is not allowed to access on subsequent lines, with each directory or file on a separate line. It is possible to use the wildcard character "*" (just the asterisk, without the quotes) instead of naming specific spiders. When you do so, all spiders are assumed to be named. Note that the robots.txt file is a robots exclusion file (with emphasis on the "exclusion") — there is no universal way to tell spiders to include any file or directory.
Take the following robots.txt file for example:
The above two lines, when inserted into a robots.txt file, inform all robots (since the
wildcard asterisk "*" character was used) that they are not allowed to access anything in
cgi-bin directory and its descendents. That is, they are not allowed to access
cgi-bin/whatever.cgi or even a file or script in a subdirectory of
cgi-bin, such as
If you have a particular robot in mind, such as the Google image search robot, which collects images on your site for the Google Image search engine, you may include lines like the following:
This means that the Google image search robot, "Googlebot-Image", should not try to access any file in the root directory "/" and all its subdirectories. This effectively means that it is banned from getting any file from your entire website.
You can have multiple Disallow lines for each user agent (ie, for each spider). Here is an example of a longer robots.txt file:
The first block of text disallows all spiders from the
images directory and the
The second block of code disallows the Googlebot-Image spider from every directory.
It is possible to exclude a spider from indexing a particular file. For example, if you don't
want Google's image search robot to index a particular picture, say,
you can add the following:
Remember to add the trailing slash ("/") if you are indicating a directory. If you simply add
the robots will be disallowed from accessing
privatedata.html as well as
as well as the directory tree beginning from
/privatedata/ (and so on). In other words,
there is an implied wildcard character following whatever you list in the Disallow line.
If you have a particular spider in mind which you want to block, you have to find out its name. To do this, the best way is to check out the website of the search engine. Respectable engines will usually have a page somewhere that gives you details on how you can prevent their spiders from accessing certain files or directories.
Here are some mistakes commonly made by those new to writing robots.txt rules.
As mentioned earlier, although the robots.txt format is listed in a document called "A Standard for Robots Exclusion", not all spiders and robots actually bother to heed it. Listing something in your robots.txt is no guarantee that it will be excluded. If you really need to block a particular spider ("bot"), you should use a .htaccess file to block that bot. Alternatively, you can also password-protect the directory (also with a .htaccess file).
Anyone can access your robots file, not just robots. For example, typing
http://www.google.com/robots.txt will get you Google's own robots.txt file. I notice that some
new webmasters seem to think that they can list their secret directories in their robots.txt
file to prevent that directory from being accessed. Far from it. Listing
a directory in a robots.txt file often attracts attention to the directory. In fact,
some spiders (like certain spammers' email harvesting robots) make it a point to check the
robots.txt for excluded directories to spider.
Don't try to be smart and put multiple directories on your Disallow line. This will probably not work the way you think, since the Robots Exclusion Standard only provides for one directory per Disallow statement.
A recent update to the robots.txt format now allows you to link to something known as a sitemaps protocol file that gives search engines a list of all the pages on your website. Please read the article How to Get Search Engines to Discover (Index) All the Web Pages on Your Site for more information about this extension.
Even if you want all your directories to be accessed by spiders, a simple robots file with the following may be useful:
With no file or directory listed in the Disallow line, you're implying that every directory on your site may be accessed. At the very least, this file will save you a few bytes of bandwidth each time a spider visits your site (or more if your 404 file is large); and it will also remove Robots.txt from your web statistics bad referral links report.
Do you find this article useful? You can learn of new articles and scripts that are published on thesitewizard.com by subscribing to the RSS feed. Simply point your RSS feed reader or a browser that supports RSS feeds at http://www.thesitewizard.com/thesitewizard.xml. You can read more about how to subscribe to RSS site feeds from my RSS FAQ.
This article is copyrighted. Please do not reproduce this article in whole or part, in any form, without obtaining my written permission.
It will appear on your page as: