Operated by FactSet
The web crawler for FactSet, a financial data and software company, used to gather market intelligence.
The web crawler for FactSet, a financial data and software company, used to gather market intelligence.
Factset_spyderbot is a data aggregation crawler. Unlike search bots or AI crawlers, its purpose is typically to collect content for private datasets, price monitoring, or research. Blocking Factset_spyderbot via robots.txt or at the server level has NO negative SEO impact. If you see excessive crawl volume from this bot in your logs, a hard block is recommended.
<code>User-agent: Factset_spyderbot</code> — Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.
Understanding Factset_spyderbot's purpose helps you decide whether to allow or block it.
Factset_spyderbot. This is the exact string you must use in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. User-agent matching in robots.txt is case-insensitive, but the string must be spelled correctly. You can verify that a request genuinely comes from Factset_spyderbot by performing a reverse-DNS lookup on the source IP — legitimate bots resolve back to their operator's domain./robots.txt file:
User-agent: Factset_spyderbot Disallow: /This instructs Factset_spyderbot not to crawl any path on your site. The Disallow: / directive covers the entire domain including subfolders. To only block specific sections, replace / with the path (e.g.,
Disallow: /blog/). Note: robots.txt is publicly readable — any bot or human can inspect it at yourdomain.com/robots.txt.Factset_spyderbot (case-insensitive grep: grep -i "Factset_spyderbot" /var/log/nginx/access.log). You can also check Google Search Console → Coverage → Crawl Stats for Googlebot variants. For Factset_spyderbot specifically, filter by user-agent in your log analysis tool (GoAccess, AWStats, etc.).Disallow: / you can restrict Factset_spyderbot to specific paths:
User-agent: Factset_spyderbot Disallow: /private/ Disallow: /staging/ Allow: /This allows Factset_spyderbot everywhere except the listed paths. Path matching in robots.txt uses prefix matching —
Disallow: /private/ blocks /private/page.html but NOT /public/private/.Crawl-delay: 30 below the User-agent directive in robots.txt.
2. Rate-limit the user-agent via Nginx's limit_req_zone or Apache's mod_ratelimit.
3. Block it outright at Cloudflare WAF with rule: http.user_agent contains "Factset_spyderbot".
4. Use fail2ban to auto-block IPs exceeding request thresholds.Check instantly with our free AI Bot Checker
Check Your Website