Identification
Its full user-agent string, exactly as it arrives at the gate:
ByteDance does not publish a way to verify Bytespider's traffic. Treat its user agent as a claim, not proof: anyone can send it.
How to block Bytespider
Add these two lines to the robots.txt file at the root of your site. Well-behaved crawlers read it before they crawl, so the change applies from Bytespider's next visit. Nothing else on your site needs to change.
# Block Bytespider from the whole site User-agent: Bytespider Disallow: /
Many site owners report it does not always follow robots.txt. Check its Trap Room record, and consider a server-level block too.
Or let it visit but keep it away from part of the site:
# Let it in, but keep it out of one room User-agent: Bytespider Allow: / Disallow: /members/
Observed behaviour
Nothing on record in the last 30 days.
Requested 0 disallowed pages out of 0 requests. Never read robots.txt.
Has never followed the hidden link to /trap/. Either well trained or very lucky.
Where it comes from
The networks Bytespider's visits came from:
Nothing on record in the last 30 days.
Networks and countries come from the visitor's IP address, looked up in a local copy of the DB-IP database. The addresses themselves are never stored.
Questions site owners ask
Does Bytespider respect robots.txt?
We can't say yet. It has not fetched robots.txt here, and it has not touched a disallowed page either.
Will blocking Bytespider hurt my search rankings?
No. Bytespider isn't used by Google or Bing to rank pages. Blocking it only affects whether ByteDance collects your content.
How often does Bytespider visit?
Here, about 0 requests a day over the last week. Visits to your site depend on its size, how often it changes, and how many links point to it.