Bytespider
Operated by ByteDance · Trains a model
If you block it
Unknown. With no published statement, there is no basis to say what a disallow does.
What ByteDance says it is for
No first-party statement from ByteDance has been located. Its user agent carries a contact address (spider-feedback@bytedance.com) rather than a link to documentation — unlike CCBot, which links its FAQ, or Meta, which links its page.
Published details
- robots.txt
- Operator publishes no documentation
- User agent
- Not published as a full string. ByteDance publishes only the token.Match on the prefix
Bytespiderrather than the whole string: operators version these, and an exact match stops working on the next release. - Verification
- No published method.ByteDance publishes no IP list and no reverse-DNS method, so anyone can put this name in a user agent and nothing can contradict it. A visit claiming to be Bytespider can never be confirmed, and must never be reported as forged.
Not addressed in the documentation
- As of , ByteDance’s documentation does not address any of it: no first-party documentation has been located.
Third-party reports
Not published by ByteDance. Each statement is attributed to its source.
- Reported to ignore robots.txt. — Fortune
- Named as one of three agents found fetching disallowed paths on nearly half of European sites surveyed. — TollBit research, 2026
- Some sources argue those fetches are explained by robots.txt re-fetch delay rather than disregard. — Third-party bot trackers
Source: no first-party documentation found. Read .