Bytespider
ByteDance · No operator statement
What it does
ByteDance says nothing: there is no documentation page, no published user-agent string and no compliance statement. What is known about Bytespider comes from access logs like the observed section below.
The facts
| Operator | ByteDance |
| robots.txt token | Bytespider |
| Appears in access logs | Yes |
| User-agent string | Not published by the operator |
| robots.txt | No statement published. ByteDance publishes no compliance claim to hold it to. Independent bot databases report it does not honor robots.txt directives; that is their claim, not ByteDance's. |
| IP list | Not published |
| Documentation | None exists. Searched 4 Aug 2026. |
Allow or block it in robots.txt
To block Bytespider entirely:
User-agent: Bytespider Disallow: /
To allow it everywhere:
User-agent: Bytespider Allow: /
Verify a request is really Bytespider
No published IP list or verification method exists.
ByteDance publishes no documentation page for Bytespider at all (searched 2026-08-04). Every other crawler in this index has an operator page to cite; this one's entry is defined by that absence. The user-agent string seen in access logs carries a spider-feedback@bytedance.com contact address, which is the only operator-published artifact, and it is inside the request itself.
Observed on this property
Not observed here yet. This site logs every request from 15 named AI agents; logging began 4 Aug 2026. When Bytespider first fetches a page, this section fills in from the log.