Bright Data Crawler
AggressiveUser-agent: Brightbot
Category: Scrapers
SEO impact if blocked: 2/10
1 crawler operated by Bright Data
Bright Data operates 1 crawler in our directory, filed under Scrapers. Its crawl behaviour is rated aggressive.
Blocking Bright Data carries an SEO impact score of 2/10. Blocking impact is rated: Low - No SEO ranking impact.
Our recommendation for Bright Data: Generally safe to allow; provides legitimate crawling value.
| Operator | Bright Data |
|---|---|
| Crawler in directory | 1 |
| Categories | Scrapers |
| SEO impact if blocked | 2/10 |
| Crawl behaviour | 1 rated aggressive |
| Official crawler docs | Bright Data crawler documentation |
Bright Data runs 1 crawler in our database. Grouped by the job each one does:
BrightbotThe highest-priority token is Tier 6. That makes Bright Data a lower-priority operator for most sites: worth a deliberate decision, but rarely the one that decides your visibility.
None of Bright Data's tokens were among the names tracked in our robots.txt study of the Tranco top 10,000, which usually means few large sites write rules for them yet. Your own logs are the best evidence of how often they visit.
A robots.txt file cannot say "Bright Data"; it can only name Bright Data's tokens, one group at a time. With a single token, one group is the whole policy.
# One token controls everything Bright Data fetches through it
User-agent: Brightbot
Disallow: /private/
Allow: /
User-agent: *.* group, so copy any Disallow lines you still want it to obey.User-agent: Bright Data block all of Bright Data's crawlers?No. robots.txt matches crawler tokens, not company names. Use the token Brightbot.
No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.
A one-paragraph brief for every Bright Data token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
Brightbot, Tier 6): a training crawler that collects pages to train AI models. Rated aggressive. Bright Data Crawler's robots.txt behaviour is documented with exceptions or has been publicly questioned, so pair a Bright Data Crawler rule in robots.txt with a server-side rule if blocking matters to you. Not tracked in our robots.txt study.The errors we see most often with Bright Data's crawlers in the files and firewalls we test:
User-agent: * rule that also catches search engines. Name Brightbot in its own group instead.All three hide inside a file that looks correct, so check Bright Data's crawlers from outside after every change.
Everything below comes from the AI Crawler Check bot database and our two most recent robots.txt scans of the Tranco top 10,000, not from Bright Data's marketing. Bright Data has one token in our database, so the whole picture fits in one place.
Brightbot in our recordsWe first recorded Brightbot on September 22, 2026. Bright Data documents it on brightdata.com, and we recheck that page before each release. No file in our top-10,000 scans names Brightbot, so any rule you write for it puts you ahead of almost every large site.
Among the 39 data scrapers in our database, Brightbot sits seventh by priority (Tier 6), level with Amazon Kendra, ApifyBot, Barkrowler, BLEXBot. 4 of the 39 share its aggressive rating. Other operators with a crawler that collects pages to train AI models: ClaudeBot (Anthropic, Tier 1), Google-Extended (Google, Tier 1), GPTBot (OpenAI, Tier 1), Meta-ExternalAgent (Meta, Tier 1), AI2Bot (Allen Institute for AI, Tier 2). A policy for Brightbot is usually a policy for these too.
BrightbotTeams that review crawlers once a quarter keep one short entry per token, so anyone can see why a rule exists and when it was last checked. Filled in from our data, the Brightbot entry reads:
User-agent: Brightbot
Disallow: /
Paste the line into the validator with one of your own URLs before it goes live. Revisit the Brightbot entry sooner than most: a aggressive rating means Bright Data traffic deserves a monthly look at your logs.
Brightbot on your own siteBecause Bright Data runs only Brightbot in our records, one check covers the whole operator. Search your access logs for the string Brightbot over the last 30 days, note how many requests it made and which paths it asked for, then compare that with what your robots.txt allows. Match the requests against what Bright Data publishes about the crawler, since that page is the only authority on its behaviour. A Tier 6 crawler rated aggressive rarely needs more than a quarterly look, and our log checker does the counting for you.
From our robots.txt study of the Tranco top 10,000 (5,583 valid files, fetched October 20, 2026):
None of the tokens for Bright Data's crawlers is tracked by name in our study. For scale, 20.1% of top-site files block at least one AI training crawler and 4.3% refuse every unnamed crawler with User-agent: * and Disallow: /, which would catch Bright Data's crawlers too.
Brightbot, add Disallow lines for the paths to keep private and Allow lines for exceptions. The longest matching rule wins.User-agent group per decision and repeat any shared rules inside it.This rule covers the single crawler Bright Data operates. Add it to the robots.txt file at the root of your domain.
These Bright Data rules ask; they do not enforce. If a Bright Data token ignores them, block it at the server or CDN. Paths are case-sensitive, and each rule matches the token, not the full user-agent string.
Text size
Saved on this device only. Drag the round button to move it. Accessibility statement