Factset_spyderbot
CautionUser-agent: Factset_spyderbot
Category: Data Scrapers
SEO impact if blocked: 2/10
FactSet
1 crawler operated by FactSet
Who FactSet is, for site owners
FactSet operates 1 crawler in our directory, filed under Data Scrapers. Its crawl behaviour is rated caution.
Blocking FactSet carries an SEO impact score of 2/10. Blocking impact is rated: Low - No SEO ranking impact.
Our recommendation for FactSet: Consider blocking based on your content strategy.
FactSet at a glance
| Operator | FactSet |
|---|---|
| Crawler in directory | 1 |
| Categories | Data Scrapers |
| SEO impact if blocked | 2/10 |
| Crawl behaviour | 1 rated caution |
Crawler operated by FactSet
How to block or allow FactSet in robots.txt
This rule covers the single crawler FactSet operates. Add it to the robots.txt file at the root of your domain.
Block FactSet completely
User-agent: Factset_spyderbot
Disallow: /
Allow FactSet explicitly
User-agent: Factset_spyderbot
Allow: /
robots.txt is a request, not an enforcement mechanism. A crawler that ignores it needs a block at the server or CDN layer. Rules are case-sensitive on the path and matched against the user-agent token, not the full user-agent string.
Frequently asked questions about FactSet
What crawler does FactSet run?
FactSet operates 1 crawler in our directory: Factset_spyderbot (user-agent Factset_spyderbot).
Should I block FactSet?
Consider blocking based on your content strategy. The SEO impact score for blocking is 2/10, where 10 means blocking costs you the most visibility.
How do I block FactSet in robots.txt?
Add the following to robots.txt at your domain root: User-agent: Factset_spyderbot then Disallow: /.
Does blocking FactSet hurt my search rankings?
Blocking impact is rated: Low - No SEO ranking impact. Google's own ranking crawler is Googlebot, which this operator does not run, so blocking FactSet does not by itself remove you from Google's index. What it can change is whether AI assistants and analytics tools can read your pages.