What is Bytespider?
Bytespider is a crawler name that third-party catalogs attribute to ByteDance. We found no ByteDance page that documents it, its purpose, its IP ranges or its robots.txt behavior, so a Bytespider claim cannot be checked against the operator.
Last verified 2026-09-30 against the operator's documentation. All bots
Bytespider at a glance
- Operator
- Unconfirmed (attributed to ByteDance)
- Type
- Crawlers without operator documentation
- Purpose
- A crawler with no operator documentation.
- robots.txt token
Bytespider- How to verify
- No published method. Observe the networks it comes from and its request rate before deciding.
- Operator documentation
- None published
How often is Bytespider impersonated?
Unconfirmed (attributed to ByteDance) publishes no way to check a request that claims to be Bytespider, so we cannot say which claims are false and show no share.
This directory measures requests between 3 July 2026 and 28 September 2026. The fake crawler report covers its own, earlier window (late June to 21 September 2026), so its figures differ from the ones here. Read it for the method.
Have a request that claims to be Bytespider? Check its IP address.
Should you block Bytespider?
- Allow it if
- you see no load or abuse from it and prefer to observe first.
- Block it if
- its load is noticeable. Since it cannot be verified, enforce the decision at the edge, not only in robots.txt.
- What blocking changes
- Without operator documentation there is no stated effect. A robots.txt rule may or may not be honored.
To block it, add this group to your robots.txt. No operator documentation says whether it obeys robots.txt.
User-agent: Bytespider
Disallow: /robots.txt only asks. It does nothing against a client that ignores it or only pretends to be Bytespider. Stopping those takes verification at your edge.
Bytespider: common questions
See which bots reach your site, and which of them are who they claim to be.
What is Bytespider?
Bytespider is a crawler name that third-party catalogs attribute to ByteDance. We found no ByteDance page that documents it, its purpose, its IP ranges or its robots.txt behavior, so a Bytespider claim cannot be checked against the operator.
How do I verify that a request is really Bytespider?
No published method. Observe the networks it comes from and its request rate before deciding. The user agent alone proves nothing: any client can send it.
How do I block Bytespider in robots.txt?
Add a group for User-agent: Bytespider with Disallow: /. No operator documentation says whether it obeys robots.txt. robots.txt only asks. A client that ignores it, or pretends to be Bytespider, has to be stopped at your edge.
What happens if I block Bytespider?
Without operator documentation there is no stated effect. A robots.txt rule may or may not be honored.