assistant Amazon respects robots.txt

Amzn-User

Amazon uses this crawler to fetch pages in real time when a user asks about them. Fetches pages an Amazon AI assistant user explicitly requested.

Crawler data last reviewed September 18, 2026 · all 61 crawlers

Amzn-User at a glance

OperatorAmazon
TypeAI assistant fetcher
Respects robots.txtYes — a Disallow rule is honored
If you allow itAllowing it means users who ask about you get an accurate, current answer with your page as the source.
If you block itBlocking it only affects user-requested fetches, so the traffic cost is small — but the users you do lose are the highest-intent ones.

What is Amzn-User?

Fetches pages an Amazon AI assistant user explicitly requested. Assistant crawlers fetch a page in real time when a user explicitly asks an AI assistant about it. They do not build a standing index of the web. Blocking them makes the assistant say it cannot access your page instead of summarizing it — a poor experience for users who were actively looking for you.

Allowing it means users who ask about you get an accurate, current answer with your page as the source.

Does Amzn-User respect robots.txt?

Yes. Amzn-User honors robots.txt directives, including wildcard rules and Allow lines. A Disallow rule for this crawler is respected — but remember robots.txt is a voluntary protocol across the whole industry, not a wall.

How to block Amzn-User

Add this group to your robots.txt to deny Amzn-User across your whole site:

User-agent: Amzn-User
Disallow: /

Blocking it only affects user-requested fetches, so the traffic cost is small — but the users you do lose are the highest-intent ones.

How to allow Amzn-User

Amzn-User is allowed by default on every site. It only gets blocked if a matching rule exists — most often a global User-agent: * group with Disallow: /. To exempt it while blocking other bots, put an empty Disallow group for it before the global block:

User-agent: Amzn-User
Disallow:

User-agent: *
Disallow: /

Does blocking Amzn-User hurt your rankings?

No — not for classic search. Amzn-User is not a Google user agent, so a robots.txt rule for it has no effect on Google rankings or indexing. The only thing you give up is what this specific AI assistant fetcher does with your pages, described above.

How to verify Amzn-User is really hitting your site

robots.txt states what a compliant crawler may fetch; your access log shows what actually happened. Search the log for the token:

grep -i "Amzn-User" /var/log/nginx/access.log | tail -50

On Cloudflare the free plan does not expose raw request logs, so use Security Events to see blocked requests, or add a console.log line in a Worker to record the user agent. On Vercel or Netlify, filter the request log by user agent string.

User agents are trivially spoofable, which is why "I saw Amzn-User in my logs" is not proof. Because Amzn-User is documented to honor robots.txt, a request from it that ignores your rules is worth investigating — but a single stray hit is usually a misconfigured tool, not the real crawler.

Should you block Amzn-User?

Is Amzn-User currently allowed on your site?

Paste your robots.txt into the free auditor and see verdicts for all 61 AI crawlers — including the specific paths that matter.

Other AI crawlers from Amazon

Amazon runs 4 distinct user agents. They are configured independently in robots.txt, so blocking one does not block the others — a detail that catches people out when they assume a single rule covers a whole vendor.

CrawlerTyperobots.txtWhat it does
AmazonbotAI searchyesAmazon's crawler for Alexa/retail indexing.
BedrockbotAI trainingyesGathers data for custom models built on AWS Bedrock.
AmazonBuyForMeAI agent browseryesBrowses shopping sites during Amazon Buy For Me agent purchases.
Amzn-User this pageAI assistant fetcheryesFetches pages an Amazon AI assistant user explicitly requested.

Related AI crawlers

Further reading

All 14 GEO guides · Full AI crawler directory