Training crawlers
Factset_spyderbot is a bot operated by Factset that collects pages used to train AI models. Scrapes data for AI training. 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
"Factset_spyderbot"
Checked against
Nothing published
Live check
No operator check exists for Factset_spyderbot. This still shows what the address really is.
Reference
| User agent | Factset_spyderbotToken only: match on the substring. |
|---|---|
| Operator | Factset |
| Purpose | AI model training. |
| 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 | Factset_spyderbot |
| Operator documentation | None published |
Scrapes data for AI training.
robots.txt
Paste one at the root of your domain. Rules are per token.
User-agent: Factset_spyderbot
Disallow: /User-agent: Factset_spyderbot
Allow: /User-agent: Factset_spyderbot
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking Factset_spyderbot keeps your pages out of the next training run. It does not remove anything already collected, and it has no effect on how the site ranks in ordinary search.
Build a file for every crawlerFAQ
Factset_spyderbot is a bot operated by Factset that collects pages used to train AI models. Scrapes data for AI training. 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 Factset_spyderbot 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 Factset_spyderbot 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 Factset_spyderbot keeps your pages out of the next training run. It does not remove anything already collected, and it has no effect on how the site ranks in ordinary search.