AI crawler · registry

Amzn-User

Amazon · Live retrieval · robots.txt token amzn-user

ignores robotsMeasured across 29,991 sites with a robots.txt policy record for this agent, out of 29,996 on record.
The measurement

0.7% of 29,991 measured domains disallow amzn-user in robots.txt at the site root. Separately, and independently of robots.txt, 17.0% of 29,996 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-11-21 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-11-21. https://crawlcensus.com/bot/amzn-user

0.7%
of measured sites block it
208
sites blocking
29,783
sites allowing
no
honors robots.txt

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.

Amazon documents that this agent may fetch pages regardless of robots.txt. A disallow is recorded here because it states intent, but it is not the control.
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

User-agent string
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Amzn-User/0.1) Chrome/W.X.Y.Z Safari/537.36
Verify your own edge is not refusing it
curl -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

Allow it
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.

Block 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.

robots.txt is not sufficient for this agent. Block it at the edge on the user-agent string, since Amazon does not treat the file as binding.

Sites that block it 60 shown

DomainAI access scoreRank
cnn.com 50 190
bbc.com 76 207
bbc.co.uk 77 226
elpais.com 49 647
cnet.com 79 662
people.com 44 801
investopedia.com 44 913
healthline.com 80 941
onet.pl 76 977
theconversation.com 62 1,019
as.com 84 1,061
nypost.com 81 1,083
franceinfo.fr 60 1,098
nu.nl 49 1,191
furaffinity.net 39 1,223
dagbladet.no 74 1,376
darkero.com 67 1,639
twkan.com 43 1,641
zdnet.com 76 1,831
ign.com 62 1,993
mashable.com 61 2,010
justice.gov 54 2,084
medicalnewstoday.com 81 2,085
nontondrama.my 77 2,348
pcmag.com 63 2,423
allrecipes.com 44 3,184
lifehacker.com 65 3,342
nzherald.co.nz 56 3,368
abc.es 81 3,576
findagrave.com 41 3,906
kompas.com 77 4,161
verywellhealth.com 44 4,285
verywellmind.com 44 4,344
marthastewart.com 44 4,625
thespruce.com 44 4,644
eatingwell.com 44 4,747
channel4.com 56 4,866
cadenaser.com 78 4,925
ew.com 44 4,983
everydayhealth.com 60 5,146
travelandleisure.com 44 5,171
diigo.com 35 5,457
nj.com 47 5,566
metal-archives.com 43 5,638
dn.se 60 5,678
seriouseats.com 44 5,686
thebalancemoney.com 44 5,708
francetvinfo.fr 53 5,714
rtl.nl 47 5,731
pagesix.com 80 5,912
thoughtco.com 44 6,008
oregonlive.com 47 6,068
azcentral.com 74 6,089
eurogamer.net 57 6,246
freep.com 73 6,356
telegram.com 73 6,512
sandiegouniontribune.com 78 6,513
procyclingstats.com 56 6,609
maxroll.gg 59 6,816
elcorreo.com 80 6,822

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.