# Bytespider

## In short

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.

| Fact | Value |
| --- | --- |
| 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 | 2026-09-06 |

## 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.

## Source

- https://darkvisitors.com/agents/bytespider (HTTP 200, Verified 2026-09-06)

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.