# Bytespider

ByteDance's crawler: what it does, robots.txt handling per the operator, and observed behaviour on this property.

- Operator: ByteDance
- Purpose: No operator statement
- robots.txt token: `Bytespider`
- Appears in access logs: yes
- User-agent: 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
- Verification: No published IP list or verification method exists.
- Documentation: none exists (searched 2026-08-04)
- Note: 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.

Block it:
```
User-agent: Bytespider
Disallow: /
```

Observed on this property (logged since 2026-08-04):
- Not observed here yet.

---

Source: https://agentvisibilitytools.com/crawlers/bytespider/ · HTML version of this page.
Full index: https://agentvisibilitytools.com/agents.md · JSON: https://agentvisibilitytools.com/api/tools
Free to quote with attribution to The Agent Visibility Directory, https://agentvisibilitytools.com.