| 12:01 am on Jan 24, 2001 (gmt 0)|
1. name it robots.txt *not* spider.txt
2. make a list of everything on your site you DON'T want robots/spiders to visit, and list in in robots.txt like so:
The * after disallow means NO spider is supposed to visit the files & directories in this section.
If you only want to ban specific robots from certain files, add a second section like so (replace the * with the user-agent of the spider you want to ban):
| 12:29 am on Jan 24, 2001 (gmt 0)|
Thanks for that, now a question I suppose shouldn't be posted here, but I use Frontpage 2000, how does one incorporate the robots.txt file into a website.
I've had a look at all the help files I can find, but am getting nothing.
| 12:35 am on Jan 24, 2001 (gmt 0)|
Well... you don't "incorporate" it into your website. You'd create it in Notepad, or some other plain text editor, save it as a plain text file, and upload it to your webserver.
Don't let it get anywhere near Frontpage... who knows what could happen to it!
| 11:23 am on Jan 24, 2001 (gmt 0)|
mivox, how about excluding from an entire site? And, will adding robots.txt disallowing all spiders result in a site being removed from the index?
| 4:21 pm on Jan 24, 2001 (gmt 0)|
The following disallows a (polite) spider from the entire site:
However, I have seen it take about 3 months after a spider visting and reading robots.txt before they think about removing the disallowed pages from their index. Of course, in most cases, it is entirely in the search engines interest to remove disallowed content, because often a link to this content is useless.
| 8:37 pm on Jan 24, 2001 (gmt 0)|
I have a problem with my robots.txt. In my site there is a directory with lot of very similar files there. I want to exclude these files from SE robots. The problem is that there are subdirectories in this folder as well, and I don't want them to be excluded. To change the structure of the site is also complicated.
What should I use?
I have read about it somewhere, but I forgot it :-(
Could anyone help me?
| 8:49 pm on Jan 24, 2001 (gmt 0)|
Seems to work fine.
In your case, you can write a separate disallow line for each file in that directory you don't want spidered, but still allow access to the directory itself and therefore the subdirectories:
It may result in a long robots.txt file, but it should do the trick.
| 10:35 pm on Jan 24, 2001 (gmt 0)|
Thank you mivox!
This was what I suspected to be right.
I know that writing separate lines for each files would also work, but there is nearly one hundred of them. Maybe I'm too lazy :-)
Anyway it could be a warning for those who have same site structure. I really didn't want to spam SEs, these (asp) files contain one single line (response redirect), but it might led to Google's dropping me off completely! I don't know for sure, but...SEs are getting to be more and more clever.
Thank you again
| 10:47 pm on Jan 24, 2001 (gmt 0)|
I personally try to keep my websites structured with no more than 1 directory level down from root:
The only time I use second level subdirectories is to hold administrative or data/graphics files:
I disallow everything from my image and admin directories anyway, so that keeps everything else nice and clean.... either I allow the spiders into the directory or not.
I'm lazy too... I hate having to redesign and reorganize things once I build them! A lesson for the lazy: it's worth spending the extra time to plan out a site structure at first that will allow you to be lazy later! ;)