Amzn-User
Amazon · Live retrieval · robots.txt token amzn-user
0.6% of 30,223 measured domains disallow amzn-user in robots.txt at the site root. Separately, and independently of robots.txt, 17.4% of 30,223 reachable domains refuse an AI crawler user agent at the network edge on two consecutive probes from different locations - a refusal the site's own robots.txt does not declare and its owner often has not chosen.
Measured 2026-10-07 by direct request to every domain in the corpus. Method: how this is measured. Reuse under CC BY 4.0 with attribution.
Cite as: Crawl Census, "Amzn-User blocking rate", measured 2026-10-07. https://crawlcensus.com/bot/amzn-user
What it is definition
Fetches live pages to answer a user's Alexa question; Amazon documents it may not follow all robots.txt rules.
Amzn-User is operated by Amazon and classified here as live retrieval. These agents fetch a single URL because a user asked about it. Disallowing one means the assistant answers from an older copy or from someone else's summary instead of the live page. Several are documented as not bound by robots.txt, because the request is user-initiated rather than a crawl.
Disallowing amzn-user stops the fetch that happens when a user asks Amazon's AI products about one of your URLs. The answer still gets written, from an older copy or from a third party's description of the page, and you no longer control what it says.
- robots.txt token
- amzn-user
- Operator
- Amazon
- Purpose
- Live retrieval
- Honors robots.txt
- no
- Documentation
- https://developer.amazon.com/amazonbot
Identity on the wire exact string
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Amzn-User/0.1) Chrome/W.X.Y.Z Safari/537.36curl -A 'Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Amzn-User/0.1) Chrome/W.X.Y.Z Safari/537.36' https://example.com/Replace the host with your own. A 403, a challenge page or an empty body means the edge is blocking the agent whatever robots.txt says.
How to allow it, how to block it robots.txt
User-agent: amzn-user
Allow: /Absent any rule, the agent is already allowed, so this group only matters when your * group disallows something. Naming the agent replaces the * group for it entirely, so repeat here every disallow you still want to apply to it.
User-agent: amzn-user
Disallow: /Disallowing amzn-user stops the fetch that happens when a user asks Amazon's AI products about one of your URLs. The answer still gets written, from an older copy or from a third party's description of the page, and you no longer control what it says.
Sites that block it 60 shown
See every measured domain that blocks Amzn-User
This list is served from a cache rebuilt just now. It is discarded the moment a rescan records a policy change for this agent, so a site that has just changed its robots.txt will drop off it within one scan rather than waiting for the cache to expire.
Compare Amazon
Amazon runs 3 agents in this registry, and they do different jobs. Blocking one says nothing about the others.
Common questions answered
Does blocking Amzn-User remove me from Amazon's AI products?
Partly. Amzn-User fetches a page only when a user asks about it, so disallowing it does not delist you from Amazon's AI products. It does mean the answer is composed without your live page, from a stale copy or a third-party summary. Amazon documents this agent as not bound by robots.txt, so the disallow is a request rather than a control; see the blocking section for the edge rule that is.
How do I verify Amzn-User requests are genuine?
Amazon documents reverse DNS verification. The source address must resolve to a host under amazonbot.amazon, and a forward lookup of that host must return the same address.
Check your own site free
See whether your robots.txt admits Amzn-User today, and whether your edge agrees with it.