Training crawlers
Sidetrade indexer bot is a bot operated by Sidetrade that collects pages used to train AI models. AI product training. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
Request says
"Sidetrade indexer bot"
Checked against
Nothing published
Live check
No operator check exists for Sidetrade indexer bot. This still shows what the address really is.
Reference
| User agent | Sidetrade indexer botToken only: match on the substring. |
|---|---|
| Operator | Sidetrade |
| Purpose | Extracts data for a variety of uses including training AI. |
| Respects robots.txt | No policy |
| Verification method | Claim onlyNone published, user agent only No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. |
| Crawl pattern | Not published |
| Robots.txt tokens | Sidetrade indexer bot |
| Operator documentation | None published |
AI product training.
robots.txt
Paste one at the root of your domain. Rules are per token.
User-agent: Sidetrade indexer bot
Disallow: /User-agent: Sidetrade indexer bot
Allow: /User-agent: Sidetrade indexer bot
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking Sidetrade indexer bot keeps your pages out of the next training run. It does not remove anything already collected, and it has no effect on how the site ranks in ordinary search.
Build a file for every crawlerFAQ
Sidetrade indexer bot is a bot operated by Sidetrade that collects pages used to train AI models. AI product training. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
Not documented. No operator statement says whether Sidetrade indexer bot reads robots.txt, so add the rule but verify in your logs that the requests actually stop.
You cannot, at least not from the request itself. No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. Compare the source IP against hosting and datacenter ranges instead, and rate limit anything that behaves like a crawler.
Add the Sidetrade indexer bot token to robots.txt with Disallow: /. If the crawler ignores robots.txt, match the user agent at your CDN or reverse proxy and return 403 there instead.
Blocking Sidetrade indexer bot keeps your pages out of the next training run. It does not remove anything already collected, and it has no effect on how the site ranks in ordinary search.