CrawlPact

Amazon · User-triggered crawler

Amzn-User

Fetches a page on behalf of an end user or Amazon application, such as responding to an Alexa query that needs up-to-date information; not used for generative AI model training; Amazon's own documentation states it may not follow all robots.txt directives.

Verified against the operator's documentationQuestions and verification details checked

Amzn-User fetches individual pages in direct response to a user action or an Amazon application’s request — for example, retrieving up-to-date information to answer an Alexa query. Amazon’s own documentation states this crawler is not used to train generative AI models.

A robots.txt limitation worth knowing

Amazon’s own documentation states that Amzn-User “may not follow all robots.txt directives” because its requests are triggered by a specific person, not a bulk crawl. A Disallow rule aimed at this token is not a reliable way to prevent this specific page from being fetched on a user’s behalf — see /limitations for what a robots.txt rule can and cannot guarantee more generally.

Site-owner controls

A robots.txt rule for Amzn-User may not be honoured consistently, per Amazon’s own documentation above. It does not affect Amazonbot (Amazon’s mixed-use, possibly-training crawler) or Amzn-SearchBot (search-experience indexing, which does honour robots.txt), both documented separately.

Amazon documents Amzn-User alongside Amzn-SearchBot (search-experience crawling, also excluded from AI training) and Amazonbot (mixed use, including possible AI training) on the same page. See Amazonbot vs. Amzn-SearchBot vs. Amzn-User for a side-by-side comparison.

How to verify Amzn-User requests

Amazon documents this user agent:

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

Amazon publishes Amzn-User's IP addresses at https://developer.amazon.com/amazonbot/live-ip-addresses/. 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 Amzn-User specifically, without affecting any other crawler:

User-agent: Amzn-User
Disallow: /

If no dedicated User-agent: Amzn-User 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.

Related guides

Other Amazon crawlers

Other user-triggered crawlers

See how this applies to your own site

Run a free audit to check your declared AI crawler policy against your own domain, or use the AI crawler checker to see how your robots.txt treats Amzn-User and every other documented crawler.

Analytics preferences

CrawlPact uses optional Google Analytics and Microsoft Clarity on public pages to learn which content is useful. Clarity records clicks and scrolling (session replay), with anything you type masked. Neither runs in the app or admin areas, and CrawlPact works the same whether you accept or decline. See the privacy policy.