Forum Moderators: phranque
Thanks, Wiz
Google does recognize my 410, and does not index these pages any more. It only seems to be ask.com, teoma, and ibm that keep the gone pages in their listings, hence sending unqualified traffic to me.
For example: this is from this AM:
wfp2.almaden.ibm.com - - [03/May/2004:22:27:34 -0400] "GET /leatherworks/business4sale.html HTTP/1.0" 410 1619 "-" "http://www.almaden.ibm.com/cs/crawler [c01]" And this is from Teoma, a couple of days ago:
egspd447.teoma.com - - [01/May/2004:14:34:27 -0400] "GET /robots.txt HTTP/1.0" 200 1829 "-" "Mozilla/2.0 (compatible; Ask Jeeves/Teoma)"
egspd447.teoma.com - - [01/May/2004:14:43:00 -0400] "GET /leatherworks/index.html HTTP/1.0" 410 1618 "-" "Mozilla/2.0 (compatible; Ask Jeeves/Teoma)" Both spiders looked at my Robots.txt, where they should have read Disallow: /leatherworks/
and
Disallow: /leatherworks/business4sale.html
Yet, despite the directory and file being set to not be indexed, they looked for it anyway, as they do every month, got my 410, and apparently, ignored it.
Wiz
[edited by: Wizcrafts at 3:03 pm (utc) on May 4, 2004]
ah, sorry misread that. Yes, I think they may be stagnent but don't know for sure.
Your edit then suggests that they are getting the 410 code so there maybe little more you can do.
I can only suggest maybe direct manual removal requests to each of them.
brain over
[edited by: davidpbrown at 3:08 pm (utc) on May 4, 2004]
I use 404 for all HTTP/1.0 requests, since 410 was added in HTTP/1.1
Be aware that Ink takes about a year to give up on requesting pages, and Ask takes awhile too, though I'm not sure how long.
The snippet below returns an explicit 410-Gone for removed pages in response to an HTTP/1.1+ request. If the request is HTTP/1.0, the code does nothing; The server will simply return the default 404 response.
# Respond with 410-Gone status to HTTP/1.1 requests for removed resources.
RewriteCond %{SERVER_PROTOCOL} ^HTTP/(1\.[1-9]¦[2-9]\.[0-9])
RewriteCond %{REQUEST_URI} ^/(announcements¦whatsnew¦weather)\.html$ [OR]
RewriteCond %{REQUEST_URI} ^/events/03_(tickets¦info)\.html$ [OR]
RewriteCond %{REQUEST_URI} ^/(contact_us/¦elections/)
RewriteRule .* - [G]
I have borrowed JD's example and now limit the 410 response to HTTP 1.1.0 and newer.
This is a minor matter, but I couldnt understand why these spiders read robots.txt, ignored the directive to disallow the directory, then kept coming back to look for gone files. I tried contacting Teoma/Ask, but they refused to assist me because I am not a paying member.
Wiz
What is the benefit of serving a 410 (when possible) instead of a 404?
404 means the filename was not found at the specified location. That could be because it was renamed, or relocated to another directory, or sub-site, hence, may still exist somewhere else on the server, but we forgot to issue a 301 Moved response for it.
410 means Gone Permanently, don't bother looking for it again, delete it from your index of this website.
I use a 410 response for directories and files that have been deleted, as opposed to those that have been renamed or relocated to other directories. Unfortunately, it appears that some search engine spiders are using a server protocol that does not recognize 410 as a valid response, and they keep looking for long gone directories and files.
IHTH, Wiz
As a result of this ambiguous response, some search engines will keep trying requests for resources that return a 404 response, on the assumption that the problem may be temporary and may be corrected so that the resource will become available again. In cases where a 404 is caused by a temporary error, they are doing us a big favor by retrying, but in other cases, it's just a waste of bandwidth.
The 410-Gone response was added to HTTP/1.1 in order to remove this ambiguity.
Jim
Jim