Bot intelligence record
TikTok
Usually allowUse the TikTok identifier to separate ByteDance link preview, prefetch, or user-triggered rendering traffic from normal visitor requests in server logs.
- Operator
- ByteDance
- Family
- ByteDance
- Type
- Preview
- Source type
- Verified Directory
- Last checked
- 2026-05-20
User-Agent Pattern
ByteDanceTikTok
User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.
Robots.txt Snippet
Click snippet to copyUser-agent: TikTok Disallow: /Click the snippet to copy it, or highlight the text manually.
Handling Guidance
DependsThis bot is usually safe to allow when the request source is verified and the traffic matches your site policy.
Link previews, page rendering, social unfurls, prefetching, or user-triggered content previews.
Record Details
Structured data- Operator
- ByteDance
- Family
- ByteDance
- Type
- Preview
- Purpose
- Preview
- Identity type
- Verified Bot
- Confidence
- Medium
- Last verified
- 2026-04-29
- Last checked
- 2026-05-20
- Source type
- Verified Directory
- Verification
- Compare the observed user-agent against the documented TikTok pattern. Where available, confirm with operator documentation, published IP ranges, reverse DNS, signed-agent metadata, or published operator documentation, reverse DNS, published IP ranges, signatures, or other trust signals.
- Spoofing risk
- User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or reverse DNS/IP verification when available.
Notes
TikTok is listed in the Botcrawl directory as a preview or prefetch bot from ByteDance. The primary identifier for log review is TikTok.
Identification
- User-agent pattern:
TikTok - Family: ByteDance
- Type: Preview
- Kind: Preview
Common use
Link previews, page rendering, social unfurls, prefetching, or user-triggered content previews.
Verification and handling
Confirm the user-agent against server logs and use published operator documentation, IP ranges, reverse DNS, or other trust signals when available.
Directory guidance marks the risk level as Safe and the blocking decision as Depends. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.
Robots.txt handling: Yes.
Evidence and Source
- Compare the observed user-agent against the documented TikTok pattern. Where available, confirm with operator documentation, published IP ranges, reverse DNS, signed-agent metadata, or published operator documentation, reverse DNS, published IP ranges, signatures, or other trust signals.
- Match `TikTok` as a case-insensitive substring in HTTP user-agent logs. Review bot_aliases for alternate names or product labels. Do not treat a user-agent match alone as proof of identity for allow-listing.
- Link previews, page rendering, social unfurls, prefetching, or user-triggered content previews.
- User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or reverse DNS/IP verification when available.
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.