ByteDance · Search index
TikTokSpider
The most informative fact about this token belongs to its sibling. ByteDance demonstrably knows how to document a crawler: `Bytespider` has a whole webmaster platform behind it, with published user agents, IP ranges, reverse-DNS instructions, a robots-matching specification, a crawl-rate console and a support mailbox, and it has extended none of that here; the platform's complete 22-document handbook covers that one crawler, and no TikTok or Douyin equivalent exists. What this agent fetches, whether it feeds TikTok's in-app search or something else, and whether it reads robots.txt at all are undocumented, and the search-index classification it is usually given has no vendor basis we could find. Nothing published lets you verify it either, and the `*.bytedance.com` hostname guarantee is scoped by ByteDance to Bytespider alone: extending it to this name would be an invention, not a deduction.
- Operated by
- ByteDance
- Purpose
- Search index
- robots.txt token
- TikTokSpider
- Verification
- User agent only
Crawls continuously to build and refresh an AI search index.
How to verify TikTokSpider
ByteDance publishes no list of IP addresses for TikTokSpider, so nobody (us included) can prove that a request carrying this user agent really came from ByteDance. The name is trivial to copy. Treat it as a claim the visitor is making about itself, not as an identity anyone has checked.
There is no range list to confirm. This entry was last reviewed against ByteDance's own documentation on .
User agent
ByteDance has not published a full user-agent string for TikTokSpider. Requests are identified by the TikTokSpider product token appearing in the User-Agent header; we match that token rather than a whole string, because the rest of the header varies and matching it would miss real traffic.
robots.txt for TikTokSpider
Block
User-agent: TikTokSpider
Disallow: /Allow
User-agent: TikTokSpider
Allow: /robots.txt is a request, not an enforcement mechanism. It is honoured by convention, and a crawler that ignores it is stopped at your edge, not in a text file.
What blocking TikTokSpider costs you
The risk worth flagging here is not the search one. No ByteDance page ties this token to a surface that returns visitors, so no referral loss can honestly be quantified; the concrete hazard is different: if this agent is what renders a preview when someone shares your URL inside TikTok, a hard block turns shared links into blank cards, a visible cost with nothing to do with AI or indexing. That mechanism is unconfirmed, which makes it something to test with one shared URL before committing rather than a cost to accept on faith, and it lands on consumer brands with TikTok distribution far harder than on anyone else.
Vendor documentation
ByteDance does not publish documentation for TikTokSpider that we could find. Everything on this page comes from what they do publish elsewhere and from observed behaviour, so treat it accordingly.