Amazonbot

Questions about Amazonbot

What is Amazonbot?

Amazonbot is Amazon's crawler for improving its products and services. Amazon says the data may be used to train Amazon AI models, which is why CrawlPact classifies it as mixed-use.

Does blocking Amazonbot block Amazon's search crawler?

No. Amazon documents each user agent's settings as independent, so Amzn-SearchBot (search experiences such as Alexa) and Amzn-User (user-initiated fetches) are addressed separately. Amazon says robots.txt changes may take about 24 hours to take effect.

Can I keep a page out of Amazon's model training without blocking crawling?

Amazon documents a page-level option: a robots meta tag with noarchive tells its crawlers not to use the page for model training. Amazon also says its crawlers do not support Crawl-delay.

Amazon’s own developer documentation states that “Amazonbot is used to improve our products and services. This helps us provide more accurate information to customers and may be used to train Amazon AI models.” Its full user-agent string includes the token Amazonbot/0.1.

Why this is categorised as “mixed”

Amazon’s documentation does not separate Amazonbot into distinct training/search/product tokens the way some other operators do — a single crawler serves multiple stated purposes at once. CrawlPact’s registry marks this as mixed purpose rather than guessing which use applies to any specific request.

Site-owner controls

Disallowing Amazonbot opts this content out of Amazon’s general product-improvement crawling, including any possible AI-model-training use its documentation describes. It does not affect the separate Amzn-SearchBot (search-experience indexing) or Amzn-User (user-triggered fetches) tokens Amazon documents on the same page — both explicitly excluded from AI training use, and evaluated independently by CrawlPact. See /limitations for what a robots.txt rule can and cannot guarantee.

Related crawlers

Amazon documents Amzn-SearchBot (search-experience indexing, excluded from AI training) and Amzn-User (user-triggered fetches, excluded from AI training) alongside Amazonbot on the same page. All three respond to different queries such as “amazonbot user agent” because they share a common Amazon origin, but they are distinct tokens with distinct rules — see Amazonbot vs. Amzn-SearchBot vs. Amzn-User for a side-by-side comparison, including how each one’s robots.txt compliance actually differs.

How to verify Amazonbot requests

Amazon documents this user agent:

                  Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Amazonbot/0.1) Chrome/W.X.Y.Z Safari/537.36
                

Amazon publishes Amazonbot's IP addresses at https://developer.amazon.com/amazonbot/ip-addresses/. The Chrome version in the user agent varies (shown as W.X.Y.Z in Amazon's documentation). Operator documentation.

A user-agent string alone can be copied by anyone; confirming a request really came from Amazon needs your server or CDN logs. CrawlPact audits declared policy and does not see your traffic.

Example robots.txt configuration

To disallow Amazonbot specifically, without affecting any other crawler:

User-agent: Amazonbot
Disallow: /

If no dedicated User-agent: Amazonbot group exists in a domain'srobots.txt, this crawler falls back to whatever the wildcard User-agent: * group says (RFC 9309) — see robots.txt syntax basics for how group selection works. A robots.txt rule is a published instruction; it does not technically prevent access.

Official source

https://developer.amazon.com/amazonbot

Verified against the source above as of 8 September 2026 — see how CrawlPact verifies crawler information.