Dataset builders
Spider is a bot that crawls pages into a dataset that may be reused or shared with third parties, and its operator has not been publicly identified. The token has been seen in server logs, but no operator has published documentation for it. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
Request says
"Spider"
Checked against
Nothing published
Live check
No operator check exists for Spider. This still shows what the address really is.
Reference
| User agent | SpiderToken only: match on the substring. |
|---|---|
| Operator | Not publicly identified |
| Purpose | Dataset builders |
| Respects robots.txt | No policy |
| Verification method | Claim onlyNone published, user agent only No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. |
| Crawl pattern | Not published |
| Robots.txt tokens | Spider |
| Operator documentation | None published |
No operator documents this token. Everything here comes from the string and the traffic.
robots.txt
Paste one at the root of your domain. Rules are per token.
User-agent: Spider
Disallow: /User-agent: Spider
Allow: /User-agent: Spider
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking Spider keeps your pages out of the datasets it builds from future crawls. It does not remove anything collected earlier, and how each operator uses or shares its data varies, so check their policy.
Build a file for every crawlerFAQ
Spider is a bot that crawls pages into a dataset that may be reused or shared with third parties, and its operator has not been publicly identified. The token has been seen in server logs, but no operator has published documentation for it. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
Not documented. No operator statement says whether Spider reads robots.txt, so add the rule but verify in your logs that the requests actually stop.
You cannot, at least not from the request itself. No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. Compare the source IP against hosting and datacenter ranges instead, and rate limit anything that behaves like a crawler.
Add the Spider token to robots.txt with Disallow: /. If the crawler ignores robots.txt, match the user agent at your CDN or reverse proxy and return 403 there instead.
Blocking Spider keeps your pages out of the datasets it builds from future crawls. It does not remove anything collected earlier, and how each operator uses or shares its data varies, so check their policy.