ByteDance's crawler, classed as AI training: it collects public pages for model training. Intent: training. Downloads your content to train AI models.

What is the Bytespider user agent?

Requests from Bytespider carry "bytespider" in the User-Agent header (matching is case-insensitive). The full string includes a version number that changes over time; ByteDance's documentation lists the current one. In robots.txt, the token is Bytespider.

How do I block Bytespider in robots.txt?

Add "User-agent: Bytespider" followed by "Disallow: /" to your robots.txt. robots.txt is a request, not a lock: a scraper using Bytespider's name ignores it, which is why verification matters.

Can I see when Bytespider visits my site?

Yes. HadoSEO logs every Bytespider request by page, and labels it declared, since ByteDance publishes nothing to verify it against. For a one-off look, the free log file analyzer reads a week of your server logs in the browser.

[ AI training crawler · ByteDance ]

Bytespider: ByteDance's AI training crawler.

ByteDance's crawler, classed as AI training: it collects public pages for model training. Its intent is training: downloads your content to train AI models.

traininguser agent only

IP ranges last updated Oct 25, 2026

Check a Bytespider IP All AI crawlers

[ technical facts ]

operator: ByteDance
intent: training
user agent contains: bytespider
robots.txt token: Bytespider
verification: user agent onlydeclared
official IP list: not published
operator docs: bytespider.com

[ verify ]

How to verify a real Bytespider request.

ByteDance publishes no IP list or reverse DNS pattern for Bytespider, so a request using its name can't be confirmed. HadoSEO labels it declared: recognized by user agent only.

01Check the User-Agent header contains "bytespider" (case-insensitive). That is only a claim: anyone can send it.
02ByteDance publishes no IP list or reverse DNS pattern for Bytespider that HadoSEO can check, so there is no way to prove a request is real.
03Treat it as declared: it says it is Bytespider, and nothing confirms or contradicts that.

Skip the lookups: the free bot verifier checks one IP against the same registry, and the log file analyzer checks every Bytespider request in a week of access logs. Requests that fail are flagged as spoofed, not hidden.

[ robots.txt ]

Block or allow Bytespider in robots.txt.

Add one of these groups to the robots.txt at your domain root. The token matches case-insensitively.

block Bytespider

User-agent: Bytespider
Disallow: /

allow Bytespider

User-agent: Bytespider
Allow: /

robots.txt only binds crawlers that choose to follow it. A scraper sending Bytespider's user agent from its own servers won't, which is why HadoSEO checks the IP behind every request.

[ questions ]

Bytespider, answered.

[ free scan ]