Amazon · Search index
Amzn-SearchBot
Amazon names a concrete retrieval surface for this one: permitting it makes your content "eligible to appear in search experiences such as Alexa," and the load-bearing sentence is the disclaimer that it "does not crawl content for generative AI model training." Where Amazonbot's crawl may reach a model's weights, this crawl builds an index that gets queried, and it builds it ahead of time, which is what separates it from Amzn-User's fetch at the moment a question is asked. Its published range file is the odd one out at Amazon: the only one of the three using an `ip_prefix` key with real CIDR notation, all `/32`, 512 entries. A verification routine written against Amazonbot's `ipv4Prefix` format returns zero prefixes here and fails silently, as "never verified" rather than as an error.
- Operated by
- Amazon
- Purpose
- Search index
- robots.txt token
- Amzn-SearchBot
- Verification
- IP verified
Crawls continuously to build and refresh an AI search index.
How to verify Amzn-SearchBot
Amazon publishes the IP ranges Amzn-SearchBot crawls from, and we fetch that list on a schedule. A request claiming to be Amzn-SearchBot can therefore be checked against 816 published ranges: one that does not match is not this crawler.
Published ranges last confirmed by us on .
User agent
Amazon publishes this user agent for Amzn-SearchBot. Match on the Amzn-SearchBot product token rather than the whole string: vendors revise the surrounding version and URL fragments without notice.
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Amzn-SearchBot/0.1) Chrome/W.X.Y.Z Safari/537.36robots.txt for Amzn-SearchBot
Yes, under Amazon's shared RFC 9309 policy, plus one rule neither sibling has: "If robots.txt files don't mention Amzn-SearchBot but allow other search bots, Amzn-SearchBot will crawl in accordance with the robots.txt directives given to other search bots." A site that allows Googlebot and never mentions Amazon is granting this token access by implication.
Block
User-agent: Amzn-SearchBot
Disallow: /Allow
User-agent: Amzn-SearchBot
Allow: /robots.txt is a request, not an enforcement mechanism. It is honoured by convention, and a crawler that ignores it is stopped at your edge, not in a text file.
What blocking Amzn-SearchBot costs you
Eligibility is conditional on access in Amazon's own framing, so a disallow stops your pages being candidates for Alexa search results: the one Amazon token whose block costs discoverability rather than only training inclusion. Amazon publishes no impression or traffic figures for those surfaces, so the magnitude is genuinely unknown and nobody should imply it is large. The trap is the fallback rule: a site trying to shut Amazon out must name this token explicitly, because a generic `User-agent: *` allow plus a `User-agent: Amazonbot` disallow leaves Amzn-SearchBot fully permitted through your Googlebot rules.