Safe Official docs AI & LLM Bots

Amazon User Agent

Operated by Amazon

Quick Facts

User-Agent:
Amzn-User
Category:
AI & LLM Bots
Operator:
Amazon
Safety:
Safe
Blocking Impact:
Low - No SEO ranking impact
SEO Impact Score:
2/10
Official docs:
developer.amazon.com

Confirmed by the operator

Amazon names Amzn-User on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.

What is Amazon User Agent?

Amazon User Agent is an on-demand AI fetcher operated by Amazon. It retrieves a page only when a user explicitly asks an AI assistant or agent to read, summarize, or act on a specific URL. Because it is triggered by real user intent rather than bulk crawling, blocking it mainly prevents users from pulling your content into Amazon's assistant.

Amazon User Agent is an on-demand AI fetcher operated by Amazon. It retrieves a page only when a user explicitly asks an AI assistant or agent to read, summarize, or act on a specific URL. Because it is triggered by real user intent rather than bulk crawling, blocking it mainly prevents users from pulling your content into Amazon's assistant.
Amazon User Agent uses the user-agent token Amzn-User. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.

What happens if you block Amazon User Agent?

✅ No SEO Impact - Blocking Amazon User Agent does not affect your rankings in Google, Bing, or any other search engine. Amazon User Agent is an AI crawler, not a traditional search indexer. You can freely block it via User-agent / Disallow: / without any SEO penalty.
Generally safe to allow; provides legitimate crawling value.

Want to see whether Amazon User Agent actually visits you? Read how do I monitor AI bot traffic to my website?

How to block Amazon User Agent with robots.txt

<code>User-agent: Amzn-User</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)
User-agent: Amzn-User Disallow: /
Allow all (robots.txt)
User-agent: Amzn-User Allow: /
Block private only (robots.txt)
User-agent: Amzn-User Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Hard-block Amazon User Agent if ($http_user_agent ~* "Amzn-User") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Hard-block Amazon User Agent SetEnvIfNoCase User-Agent "Amzn-User" bad_bot Order Allow,Deny Allow from all Deny from env=bad_bot
Meta robots tag
<meta name="robots" content="noindex, nofollow">
X-Robots-Tag header
X-Robots-Tag: noindex, nofollow

Is Amazon User Agent safe to allow?

Yes, Amazon User Agent is a safe and legitimate crawler operated by Amazon. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.
Verify by reverse-DNS lookup: legitimate Amazon User Agent requests resolve to Amazon's domain.

What does Amazon User Agent do?

Understanding Amazon User Agent's purpose helps you decide whether to allow or block it.

  • Fetches a page only when a user asks an AI assistant to read it
  • Summarizes or extracts the URL the user provided
  • Triggered by real user intent, not bulk crawling
  • Low traffic volume compared with training crawlers
  • Blocking it prevents users from pulling your content into the assistant

Amazon User Agent in context

Amazon User Agent is a user-triggered agent operated by Amazon. In plain terms, it fetches a page when a person asks an assistant or app to open it. Our database files it under AI and LLM crawlers and ranks it Tier 2, important crawlers from established AI and search operators. 74 of the 104 AI and LLM crawlers in our database share this tier.

Its safety rating is safe and its blocking impact is low. So the decision about Amazon User Agent rests on what you want from Amazon, not on its behaviour. How we rate safety and impact.

How site owners treat Amazon User Agent

Our robots.txt study of the Tranco top 10,000 did not track Amzn-User as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.

Does it follow robots.txt?

Amazon User Agent's operator says it follows robots.txt, so a correctly written Amazon User Agent group is enough to control it.

Amazon crawlers and close alternatives

Amazon User Agent is one of 8 Amazon crawlers in our database. A User-agent: Amzn-User group controls Amazon User Agent only; the other Amazon tokens below need their own lines.

  • Amzn-User: this crawler (Tier 2)
  • Amazon Kendra: Amazon Kendra, harvests pages for a dataset or data product (Tier 6)
  • amazon-QBusiness: Amazon Q Business, builds a search or answer index (Tier 3)
  • Amazonbot: Amazon Nova AI, collects pages to train AI models (Tier 2)
  • AmazonBuyForMe: Amazon Buy For Me, fetches a page when a person asks an assistant or app to open it (Tier 2)
  • Amzn-SearchBot: Amzn-SearchBot, builds a search or answer index (Tier 3)
  • bedrockbot: AWS Bedrock Bot, collects pages to train AI models (Tier 2)
  • NovaAct: Amazon Nova Act, harvests pages for a dataset or data product (Tier 2)

To give Amazon User Agent the same answer as its siblings, stack User-agent: Amzn-User with their lines above one set of rules; to treat Amazon User Agent differently, give it its own group.

Other AI and LLM crawlers that do the same job (fetches a page when a person asks an assistant or app to open it) include ChatGPT Agent from OpenAI, ChatGPT Operator from OpenAI, ChatGPT-User from OpenAI, ChatGPT-User/2.0 from OpenAI, Claude-SearchBot from Anthropic, Claude-User from Anthropic. Deciding about Amazon User Agent is usually a decision about the whole group, so check how your file treats these too.

We first recorded Amzn-User on June 18, 2026. Amazon documents it on developer.amazon.com, and we recheck that page before each release.

Which rule Amazon User Agent actually follows

Amazon User Agent reads exactly one group in robots.txt, the most specific one that names Amzn-User, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: Amzn-User
Disallow: /drafts/
  1. Find the group. Amazon User Agent looks for a group naming Amzn-User. One exists, so it ignores User-agent: * completely.
  2. Apply only that group. It is refused /drafts/ and nothing else.
  3. The surprise. /private/ is open to Amazon User Agent, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.
Test yourself: does a rule under User-agent: * apply to Amazon User Agent if the file also has a User-agent: Amzn-User group?

No. Once a group names it, Amazon User Agent reads only that group. Put every rule you want it to follow inside its own group.

Test yourself: will blocking Amazon User Agent remove your pages from AI answers?

Often, yes. Amazon User Agent is a user-triggered agent, so pages it cannot fetch can drop out of the answers or results it supports.

Test yourself: is User-agent: amzn-user the same as User-agent: Amzn-User?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow Amazon User Agent? Decide by situation

Recommended setting for Amazon User Agent by type of site
If you are...Recommended setting
You publish content and want AI answers to cite itAllow it. Amazon User Agent fetches pages for answers, so blocking it can remove you from them.
You license content and want to stop AI trainingBlocking it does not stop training, because Amazon User Agent is a user-triggered agent. Block the operator's training crawler instead.
You run an online shopAllow it on product and category pages, which are the pages shoppers ask assistants about.
Your server is under load from botsRate-limit before blocking. It is rated safe in our database.

Check Amazon User Agent on your own site

  1. Open /robots.txt on your domain and search for Amzn-User. If it is not named, it follows User-agent: *.
  2. List the Disallow lines in the group Amazon User Agent follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
  3. Look beyond the file. A firewall or bot manager can refuse Amazon User Agent even when robots.txt allows it, and that never shows in the file.
  4. Run our AI search visibility check to see how Amazon User Agent and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Amazon User Agent

The errors we see most often with Amazon User Agent in the files and firewalls we test:

  1. Assuming a robots.txt rule will stop Amazon User Agent. User-triggered fetches act for a person, and some operators say robots.txt may not apply to them. Check the operator's statement above.
  2. Blocking Amazon User Agent as if it were a bulk crawler. It fetches one page because a person asked; blocking it means that person's assistant cannot read your page.
  3. Counting Amazon User Agent visits as crawl volume. Each request maps to a real user question, which makes the paths it requests a useful signal of what people ask about you.

All three hide inside a file that looks correct, so check Amazon User Agent from outside after every change.

Spotting Amazon User Agent in your logs

robots.txt says what Amazon User Agent may do; your access logs show what it actually did.

Count requests

On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):

grep -iE "Amzn-User" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "Amzn-User" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the Amazon User Agent user-agent, so confirm the source before acting on a match:

  • Amzn-User: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Amazon User Agent request with caution.

Frequently Asked Questions

What is the official user-agent string for Amazon User Agent?
The official user-agent string for Amazon User Agent is: Amzn-User. Use this exact string in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. Matching in robots.txt is case-insensitive. Verify a request genuinely comes from Amazon User Agent by performing a reverse-DNS lookup on the source IP.
Is Amazon User Agent safe?
Yes, Amazon User Agent is a safe and legitimate crawler operated by Amazon. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.
Will blocking Amazon User Agent hurt my SEO?
✅ No SEO Impact - Blocking Amazon User Agent does not affect your rankings in Google, Bing, or any other search engine. Amazon User Agent is an AI crawler, not a traditional search indexer. You can freely block it via User-agent / Disallow: / without any SEO penalty.
How do I block Amazon User Agent in robots.txt?
Add the following lines to your /robots.txt file:
User-agent: Amzn-User
Disallow: /

This instructs Amazon User Agent not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).
Does Amazon User Agent respect robots.txt?
Amazon User Agent is operated by Amazon and is expected to fetch and parse /robots.txt before crawling, following RFC 9309. For hard enforcement, combine robots.txt with server-level IP or user-agent blocking.
How do I verify if Amazon User Agent is crawling my site?
Search your web server access logs for the string Amzn-User (case-insensitive: grep -i "Amzn-User" /var/log/nginx/access.log). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).

Related Bots

WhatsApp us