Bytespider
Bytespider is a web crawler that identifies itself with the Bytespider token and is attributed to ByteDance, the company behind TikTok. ByteDance does not publish documentation for it, so its purpose, IP addresses and robots.txt behavior are not officially confirmed.
Bytespider at a glance
| Owner | Attributed to ByteDance. ByteDance has not published crawler documentation. |
| Purpose | Not published by ByteDance |
| User agent string | Contains the token Bytespider. The full string is not published by ByteDance. |
| robots.txt token | Bytespider (the token sites use; ByteDance does not document it) |
| IP verification | None. ByteDance does not publish an IP list or a reverse DNS hostname. |
| Runs JavaScript | Not published |
| Respects robots.txt | Not published by ByteDance |
What a Bytespider visit means for your site
Because ByteDance has not said what Bytespider is for, a Bytespider hit tells you only that a client using that name fetched the page. It could be the real crawler or something else using its name: without a published IP list there is no reliable way to tell them apart.
In the AI crawler directory, Bytespider is grouped with bots that collect training data, because that is how it is commonly described. ByteDance has not confirmed it.
How to block Bytespider
You can add a robots.txt rule, but ByteDance has not said whether Bytespider follows it:
User-agent: Bytespider
Disallow: /If you want a hard block, refuse the requests on your server or CDN by user agent. In nginx:
if ($http_user_agent ~* "bytespider") {
return 403;
}This blocks anything that uses the name. It cannot stop a crawler that uses a different user agent, and with no published IP list there is no way to allowlist the genuine bot.
Check your site's AI crawler access
How to find Bytespider in your logs
Find requests whose user agent contains Bytespider, with the response status:
grep -i "bytespider" /var/log/nginx/access.log | awk '{print $1, $9}' | sort | uniq -c | sort -rnIf you added a block, the status column should show 403. If you only added robots.txt, a steady number of 200 responses after the change shows the rule is not being followed by whatever is using the name.
How Sitenumbers shows Bytespider
Bytespider does not appear in JavaScript analytics, so Sitenumbers counts it on your server or CDN with a Cloudflare Worker or an nginx log shipper. The AI crawler table shows Bytespider's hits, the pages it read, when it was last seen and the last response status, so you can check whether a block works. Because ByteDance publishes no IP list or reverse DNS hostname, Sitenumbers cannot verify Bytespider: its hits are always shown as unverified.
| Bot | Verified hits | Pages | Last seen | Status |
|---|---|---|---|---|
| GPTBot | 1,284 | 312 | 2 h ago | 200 OK |
| ClaudeBot | 846 | 207 | 5 h ago | 200 OK |
| OAI-SearchBot | 391 | 118 | 1 day ago | 403 blocked |
| ChatGPT-User | 120 | 34 | 20 min ago | 200 OK |
Read more about how Sitenumbers counts AI crawlers.
FAQ
What is Bytespider?
Bytespider is a web crawler attributed to ByteDance. ByteDance has not published documentation that describes what it does.
Does Bytespider respect robots.txt?
ByteDance has not published a statement on it. If you need a guaranteed block, refuse the requests by user agent on your server or CDN.
Can I verify that a Bytespider request is genuine?
No. ByteDance publishes no IP list and no reverse DNS hostname, so a request that says Bytespider cannot be confirmed as ByteDance.
Should I block Bytespider?
That depends on whether you are comfortable with an undocumented crawler reading your site. Blocking it has no documented effect on any search product, because ByteDance has not published one that it feeds.