What is Bytespider?
Bytespider is a training crawler operated by ByteDance: it collects text to train a model on. It sends nobody to your site, now or later, and it is the only category on this list where that is true.
Training crawler
Should you block Bytespider?
Bytespider is operated by ByteDance. Collects content for model training. Blocking it is a legitimate business choice with no traffic cost.
What Bytespider is
ByteDance runs it as a training crawler, which means it collects text to train a model on. It sends nobody to your site, now or later, and it is the only category on this list where that is true.
What blocking it costs you: Excluded from ByteDance model training. This is the crawler most often reported for ignoring the rule, so verify at the edge rather than trusting robots.txt alone. Nothing, in traffic terms. This is the one group where blocking has a real argument behind it and no visitor cost.
The user agent, and the token a rule matches on
These are two different strings and confusing them is why a rule that looks right does nothing.
A robots.txt rule matches on the product token, case-insensitively, and
ignores the rest of the user-agent header entirely.
| robots.txt token | Bytespider |
|---|---|
| Operator | ByteDance |
| Category | Training crawler |
| Full user agent | Not published by ByteDance. Match on the token above. |
Where an operator has not published the exact string, this page says so rather than inventing a plausible one. A user agent you can grep your logs for is worth nothing if it is a guess.
Allowing Bytespider
Paste this into robots.txt at the root of your domain.
User-agent: Bytespider
Allow: /
Sitemap: https://axray.online/sitemap.xml
An empty Disallow: and Allow: / mean the same thing to a crawler. What does
not mean the same thing is having no rule at all: absence is permission by default, but it is
permission nobody wrote down, and it survives only until somebody adds a blanket
User-agent: * block without thinking about this crawler.
Blocking Bytespider
User-agent: Bytespider
Disallow: /This one is a fair decision to make. A training crawler sends you no visitors, so blocking it costs you nothing in traffic and is a position you are entitled to take. Be clear about what it achieves: robots.txt is honoured by operators who choose to honour it, and does nothing about your text reaching a model through a third-party copy, a screenshot, or somebody pasting it into a chat window.
How the web actually treats Bytespider
Measured on 2026-09-06, by reading the robots.txt of
292 public websites and resolving each one against this crawler specifically.
| Verdict | Sites | Share |
|---|---|---|
| Blocked | 46 | 16% |
| Explicitly allowed | 192 | 66% |
| No rule either way | 54 | 18% |
No site is named, here or anywhere else on this domain. The count is the useful part; a league table of businesses that never asked to be measured is not.
The row worth reading twice is the last one. 54 of 292 sites have written no rule about
Bytespider at all, which means their position on it is an accident rather than a decision — whatever
their User-agent: * block happens to say.
What Bytespider is not
ByteDance runs another crawler with a different job, and this is where the expensive mistake happens. Somebody means “do not train on my content”, writes one rule against the operator’s name as they remember it, and blocks the crawler that would have sent them a customer instead.
| Crawler | What it does instead |
|---|---|
Trae |
Reads documentation while a developer is building against you. Blocking it is how your API gets used wrong. |
Rules are matched per token. Blocking one of these says nothing about the others, which is the point: you can refuse training and keep every crawler that puts your link in front of a person.
Checking what your site does right now
Reading your own robots.txt is not the same as knowing what a crawler concludes from it.
Precedence between a User-agent: * group and a named one, the longest-match rule between
overlapping paths, and a token you spelled slightly wrong all produce a file that looks correct and
behaves otherwise.
npx axray-cli your-site.comThe scan resolves your file against all 54 crawlers on this list individually and reports which ones are allowed, blocked, or covered by nothing. It is free, needs no account, and installs nothing.
Questions people ask about Bytespider
Should I block Bytespider in robots.txt?
Blocking Bytespider costs you no visitors, because it collects content for model training rather than sending anyone to your site. That makes it the one group where the decision is genuinely yours to make on principle. What it does not do is keep your content out of models — it applies only to operators who read robots.txt, and does nothing about a copy reached through somebody else.
What is the Bytespider user agent string?
ByteDance does not publish a full user-agent string for this crawler. The robots.txt product token is Bytespider, and that is what a rule matches on; matching is case-insensitive.
How do I check whether my site is blocking Bytespider right now?
Scan your site with AXRAY. It resolves your robots.txt against 54 named AI crawlers individually rather than reporting one verdict for all of them, so it will tell you whether this specific crawler is allowed, blocked, or covered by no rule at all. It is free and needs no account.
Other training crawlers
GPTBot— OpenAIClaudeBot— AnthropicGoogle-Extended— GoogleApplebot-Extended— Applemeta-externalagent— MetaCCBot— Common CrawlDeepSeekBot— DeepSeekAI2Bot— Ai2
The full reference: all 54 AI crawlers, and who blocks each one.
See which of these 54 crawlers your own site is blocking, and what each one costs you. One scan, no account.