Bytespider
Bytespider is widely observed as a ByteDance crawler. Without published ranges, a User-Agent match is a claim, not a proof of origin.
- Operator
- ByteDance
- Motif family
- other_ai
- Motif class
- Model-related crawler
- In Motif classifier
- Yes
- robots.txt
- Behavior varies; confirm against current vendor statements
- Executes JavaScript
- No
- Verified in Motif
- No published IP list Motif relies on
What Motif will and will not claim
Motif classifies Bytespider as family other_ai, class model, on tracker or collector hits. Motif does not present the hit as vendor-verified.
Revenue
Not a visitor. Blocking or allowing it is a data-policy call, not an acquisition ranking.
Vendor documentation
No durable official crawler document Motif will treat as source of truth. Motif stores the controlled token from a self-reported User-Agent.
Bytespider User-Agent example
Mozilla/5.0 (compatible; Bytespider; +http://www.bytespider.com)Allow Bytespider in robots.txt
User-agent: Bytespider
Allow: /Block Bytespider in robots.txt
User-agent: Bytespider
Disallow: /Does Bytespider count as a visit in Motif?
No. If Bytespider hits the Motif tracker or collector it increments AI crawlers. It does not create a visitor and cannot win a recommendation.
Will Motif show Bytespider on my HTML pages?
Only if that client requested /m.js or POST /v1/events. HTML-only crawls of the origin never reach Motif. Saying otherwise would be a product lie.
Should I block Bytespider?
Model-related crawlers are a data-policy call. Allowing or blocking them does not create Stripe customers. Motif will not pretend a crawler hit is demand.