Bytespider: robots token, verification and how to allow or disallow it
Bytespider is an AI crawler operated by ByteDance. Its robots.txt token is Bytespider, and the vendor documentation we fetched on 2026-09-06 is the source for every statement on this page.
| Robots token | Bytespider |
|---|---|
| Vendor | ByteDance |
| Purpose | training corpus |
| Documented verification | none published |
| Vendor documentation last verified | 2026-09-06 |
| Share of read domains disallowing it for / | 18.0% of 128 |
| Last verified |
Identity
| Robots token | Bytespider |
|---|---|
| Matched as | bytespider |
| Vendor | ByteDance |
| Purpose | training corpus |
| Documentation | None |
| Documented verification | none published |
documentation_url is null because we found no vendor page for this token that we could fetch on 2026-09-06. We record no claim about whether it obeys robots.txt: that is a widely repeated third party assertion we have not verified from the vendor.
Allow or disallow it
User-agent: Bytespider Allow: /
User-agent: Bytespider Disallow: /
A robots.txt rule is a request that a well behaved crawler honours. It is not an access control, and this page does not tell anyone what to choose.
Questions
How do I allow Bytespider in robots.txt?
Add this group to the robots.txt at the root of the host: User-agent: Bytespider Allow: /. The token is matched case insensitively as a substring of the user agent by RFC 9309, and the longest matching rule wins.
How do I disallow Bytespider in robots.txt?
Add this group to the robots.txt at the root of the host: User-agent: Bytespider Disallow: /. A robots.txt rule is a request that a well behaved crawler honours; it is not an access control.
How do I verify a request really came from Bytespider?
We have not found a documented verification method for Bytespider: the vendor publishes neither an IP range file nor a reverse DNS convention that we could fetch. Without one, a user agent string is not evidence of origin.
What we measure
Of the 128 seeded domains whose robots.txt we have read, 23 disallow Bytespider for / and 105 allow it, which is 18.0% disallowed, week 2026-W37. Counts only: no domain is named.
The weekly AI crawler access index
Sources
| Source | Type | HTTP | Verified | Note |
|---|---|---|---|---|
| https://darkvisitors.com/agents/bytespider | aggregator | 200 | 2026-09-06 | third party aggregator, only source found; volatile source: identical byte count but a different content hash on every fetch (verified twice on 2026-09-06), so the refresher compares byte counts for it, not hashes |
Free data
Check a domain against every token
AEO Watch is an independent, factual monitor. It is not affiliated with, endorsed by or speaking for any crawler vendor. Every statement is an observation with the date it was made and the raw evidence behind it: a robots.txt line, an HTTP status code, a header. There are no scores, no grades and no verdicts here, and nothing on this page is advice. A site opts out at any time and the opt out is honoured automatically and permanently.