Amzn-User
Amazon's user-triggered fetch crawler.
Quick answer
Amzn-User is Amazon's on-demand fetch agent. It retrieves a specific page when a customer action, such as an Alexa request, needs current information from the web, rather than crawling proactively the way a search or training bot would, and it is controlled separately from Amazonbot.
What it does
Amzn-User fetches individual pages in response to a specific customer action, for example when someone asks Alexa a question that needs up to date information from a web page. Because the fetch happens on behalf of a real user request rather than as a broad proactive crawl, Amazon says Amzn-User may not follow every robots.txt directive the way a standard crawler would. Amazon also states that Amzn-User does not crawl content for generative AI model training, which separates it from Amazonbot, Amazon's broader crawler used for product improvement and AI training. Amazon publishes a separate IP address list specifically for Amzn-User's live fetch traffic, so site owners can verify requests from this agent against that published list.
Facts
Operator
Amazon
Robots token
Amzn-User
User agent string(s)
- (see developer.amazon.com/en/amazonbot for the current format)
Purpose
User-triggered fetch
Respects robots.txt
Not stated by the operator
IP ranges
https://developer.amazon.com/amazonbot/live-ip-addresses/
From Amazon's documentation, checked Oct 2026.
Should you block it?
Because Amzn-User only fetches a page when a customer specifically asked for information from it, such as through an Alexa query, blocking it mainly affects whether that live, on-demand answer can pull from the site rather than broad visibility in AI training or search indexing. A brand whose customers might ask Alexa about it, its hours, or its products would generally want those live lookups to succeed, since refusing them could mean Alexa cannot answer with current information from the site. The counterpoint is that Amazon says this agent may not fully honor robots.txt since the action is user-initiated, so a disallow rule here is less certain to be respected than with a standard crawler. Amzn-User does not feed AI training, so the usual training-data concern does not apply to it the way it does to Amazonbot.
How to block it
robots.txt can carry this rule for Amzn-User: User-agent: Amzn-User Disallow: / Amazon notes that because Amzn-User responds to a specific user action, it may not follow every robots.txt directive consistently.
Frequently asked questions
Does Amzn-User train Amazon's AI models?
No. Amazon states that Amzn-User does not crawl content for generative AI model training.
Will blocking Amzn-User definitely stop it?
Not necessarily. Amazon says Amzn-User may not follow every robots.txt directive because its fetches are triggered by a specific user action.
What triggers an Amzn-User fetch?
A customer action that needs current web information, such as an Alexa query, triggers Amzn-User to fetch the relevant page.
Related
- AI crawler directory — every AI crawler's robots.txt token, purpose and facts in one place.
- Free AI crawler checker — check which AI crawlers a domain's robots.txt actually allows or blocks.
- Glossary — definitions of the AI-visibility terms that come up alongside crawler behavior.
Sources
- Amzn-User supports user actions like responding to Alexa queries that need up-to-date information, and may not follow all robots.txt directives since it's user-initiated. Source: https://developer.amazon.com/en/amazonbot (checked Oct 2026)
- Amzn-User does not crawl content for generative AI model training. Source: https://developer.amazon.com/en/amazonbot (checked Oct 2026)
MarketHQ tracks brand mentions across communities, news, blogs, social and AI answers, and turns them into gap analysis and action plans.