Understand the differences between Amazonbot, Amazon SearchBot, and Amazon's user-triggered fetchers so you can avoid mixing search, crawl, and live-fetch policies.
Amazon is a good reminder that a crawler family is usually a cluster, not a single bot. If you care about where your site appears inside Amazon properties, you need to know which Amazon crawler family actually hit your logs.
IPBot uses the source inventory below to decide whether a request is merely known or fully verified.
Swipe sideways to review every verification column.
| Crawler | Intent | Verification | CIDRs | Freshness |
|---|---|---|---|---|
| Amazonbot
Official source
| training | Known IP range | 524
IPv4 524 / IPv6 0 | 2026-04-30 |
| Amazon SearchBot
Official source
| search | Known IP range | 512
IPv4 512 / IPv6 0 | 2025-11-21 |
| Amazon User-Triggered Fetcher
Official source
| user triggered | Known IP range | 1023
IPv4 1023 / IPv6 0 | 2025-11-04 |
Separate Amazon SearchBot from the broader Amazonbot family, and treat user-triggered fetches as their own lane when previews or live retrieval matter to your product.
Use explicit crawler tokens per Amazon crawler family. A single blanket rule is usually too coarse if Amazon search visibility or user-triggered fetch behavior matters.
Keep Amazon rules granular rather than maintaining one large Amazon allowlist. Search and user-triggered traffic should be reviewable independently.
Use `Amazonbot` in `robots.txt` when you want to control Amazon's general crawler access.
Treat as a known crawler range, but keep separate allow/block rules from user-triggered Amazon fetch traffic.
Use the Amazon SearchBot token in your crawler controls when tuning Amazon search indexing behavior.
Good candidate for separate allowlist logic if Amazon search visibility matters.
Treat separately from autonomous crawlers because these requests are triggered by an end-user action.
Do not collapse this into the same rule set as Amazonbot or SearchBot if you care about user-visible previews or fetches.
They treat every Amazon crawler request as identical. Search indexing traffic, broader crawling, and user-triggered fetches can have very different business implications.
IPBot classifies Amazon crawler traffic from the official range inventory, but this v1 surface treats it as known-range evidence rather than DNS-verified evidence.