Amzn-User: robots token, verification and how to allow or disallow it
Amzn-User is an AI crawler operated by Amazon. Its robots.txt token is Amzn-User, and the vendor documentation we fetched on 2026-09-17 is the source for every statement on this page.
| Robots token | Amzn-User |
|---|---|
| Vendor | Amazon |
| Purpose | user-initiated fetch |
| Documented verification | published IP ranges |
| Vendor documentation last verified | 2026-09-17 |
| Share of read domains disallowing it for / | 4.2% of 12373 |
| Last verified |
Identity
| Robots token | Amzn-User |
|---|---|
| Matched as | amzn-user |
| Vendor | Amazon |
| Purpose | user-initiated fetch |
| Documentation | https://developer.amazon.com/amazonbot |
| Documented verification | published IP ranges: https://developer.amazon.com/amazonbot/live-ip-addresses/ |
Vendor text fetched on 2026-09-17: 'Amzn-User supports user actions, such as responding to Alexa queries that require up to date information.' The same page states 'Amzn-User does not crawl content for generative AI model training', so no training purpose is recorded here. obeys_robots_per_documentation is null because the page documents both a general commitment for these user agents, 'Automated crawling from these listed user agents respects the Robots Exclusion Protocol', and a user initiated exception, 'Because actions taken by Amzn-User can be initiated by a user, it may not follow all robots.txt directives': neither true nor false would restate the page honestly. Documented UA sample contains 'compatible; Amzn-User/0.1'.
Allow or disallow it
User-agent: Amzn-User Allow: /
User-agent: Amzn-User Disallow: /
A robots.txt rule is a request that a well behaved crawler honours. It is not an access control, and this page does not tell anyone what to choose.
Build a robots.txt with Amzn-User and every other documented token
Questions
How do I allow Amzn-User in robots.txt?
Add this group to the robots.txt at the root of the host: User-agent: Amzn-User Allow: /. The token is matched case insensitively as a substring of the user agent by RFC 9309, and the longest matching rule wins.
How do I disallow Amzn-User in robots.txt?
Add this group to the robots.txt at the root of the host: User-agent: Amzn-User Disallow: /. A robots.txt rule is a request that a well behaved crawler honours; it is not an access control.
How do I verify a request really came from Amzn-User?
The vendor publishes the IP ranges this crawler fetches from at https://developer.amazon.com/amazonbot/live-ip-addresses/. Check the address of the request against that file. A user agent string on its own proves nothing, because anyone can send one.
What we measure
Of the 12373 seeded domains whose robots.txt we have read, 518 disallow Amzn-User for / and 11855 allow it, which is 4.2% disallowed, week 2026-W41. Counts only: no domain is named.
The weekly AI crawler access index
Sources
| Source | Type | HTTP | Verified | Note |
|---|---|---|---|---|
| https://developer.amazon.com/amazonbot | vendor | 200 | 2026-09-17 | 9 occurrences of Amazonbot, 8 of Amzn-SearchBot and 7 of Amzn-User; robots.txt discussed 10 times; the page names one published IP address URL per user agent |
| https://developer.amazon.com/amazonbot/live-ip-addresses/ | vendor | 200 | 2026-09-17 | the published IP list for this user agent, printed as JSON inside a code block on the page rather than served as a JSON document: 1023 addresses under a prefixes array with an ipv4Prefix field and no mask, which read as single hosts, creationTime 2025-11-04. Identical bytes and hash on two fetches on 2026-09-17, so it is not a volatile source; also refreshed weekly into data/bot_ranges.json |
Free data
- The AEO Watch dataset
- Tranco top 1,000 AI crawler policy (CSV, CC BY 4.0)
- The AEO Watch API
- The checker as a command line tool (one file, no install)
Check a domain against every token
Check your own site
The same checks, run on your domain now: what robots.txt tells each AI crawler, whether the edge answers them, and whether the text is readable without JavaScript. Free, no signup.
Limits: 8 checks and 5 different domains per address per hour; a repeat of the same domain inside 7 days is answered from what we already hold.
AEO Watch is an independent, factual monitor. It is not affiliated with, endorsed by or speaking for any crawler vendor. Every statement is an observation with the date it was made and the raw evidence behind it: a robots.txt line, an HTTP status code, a header. There are no scores, no grades and no verdicts here, and nothing on this page is advice. A site opts out at any time and the opt out is honoured automatically and permanently.