# Amzn-User > Amzn-User is Amazon's crawler for answering questions. Amazon fetching a page for a live answer, including Alexa. An Amazon assistant opened your page while answering someone. **Category:** AI crawlers **Also known as:** Amazon Amzn-User **Updated:** 2026-09-09 **Source:** https://truestat.io/glossary/amazon-amzn-user --- ## What Amzn-User is Amazon crawls for search, for Alexa's answers, and for the models behind Bedrock. It lists its crawler addresses on a web page rather than in a machine-readable file, which is the reason none of its traffic can be verified here despite the addresses technically being public. On this site Amzn-User is counted as an AI answer, which is the row it appears in on your dashboard. The category matters because it decides which number moves when this crawler visits, and the four are reported separately for exactly that reason. ## What its traffic looks like Usually a single request for one URL, arriving while somebody waits — no sweep of the site, no repeated visits, and often no robots.txt fetch first. If you see one hit on one page and nothing else, that is the normal shape. A burst of ten to fifty pages in a few minutes is also normal and means an agent was researching rather than answering a single question. ## How it is verified Amazon publishes neither a machine-readable list of the addresses this crawler uses nor a reverse DNS record pointing back at itself. The user-agent header is therefore the only evidence, and anyone can send it — so a visit is recorded as an unverified claim rather than as a confirmed fetch. That is not a gap in the measurement so much as an honest ceiling. A report that showed these as verified would be inventing a confidence nobody can support, and the number it produced would be the first thing to fall apart when somebody asked where it came from. ## If you block it Amazon's assistant can no longer open your page to answer a question about it. People will still be told about you from whatever the model already knows, but without the current page, a link, or a citation — which is usually the opposite of what a site owner wants. This is the crawler that brings people back. When an assistant fetches a page to answer with, it usually shows the source and links to it, so the visit can turn into a reader. Blocking it removes you from the answer without removing the question. The argument for blocking is the same one that applies to any zero-click surface: if a model can answer from your page, some readers get what they came for without visiting. That matters most if your pages are the product — reference material, calculators, documentation — and least if they exist to sell something the model cannot deliver. ## How it differs from Amazon's other crawlers Amazon sends 3 crawlers and gives each its own token, so they can be allowed and refused separately. The tokens differ by a few characters and what the fetch means does not: Amzn-SearchBot — search indexing. Makes content eligible for Amazon search experiences. bedrockbot — ai training. Fetches content for Amazon Bedrock. Confusing two of these is the most common mistake with this operator, and it is expensive in one direction: a rule meant for the training crawler that lands on the search crawler removes you from results without stopping any training. ## Questions ### Is Amzn-User in my logs really Amazon? There is no way to prove it. Amazon publishes neither an address list nor a reverse DNS record for this crawler, so the user agent is the only evidence and anyone can send it. We record the visit as an unverified claim rather than presenting it as confirmed. ### How do I tell Amzn-User apart from Amazon's other crawlers? By the token, and only by the token. Amazon also sends Amzn-SearchBot, bedrockbot, and the strings differ by a few characters while the jobs differ completely — one may be answering somebody's question while another collects training material. Match on the exact token rather than on the operator's name appearing anywhere in the header, or the four end up counted as one. ### Does Amzn-User run JavaScript? No. It requests the HTML and leaves. That is why a browser-based analytics tag never records these visits: the tag is JavaScript, and nothing runs it. Seeing this crawler at all requires reading it server-side. ### Why is Amzn-User counted as AI answers and not something else? Because that is the job this particular crawler does. Amazon runs more than one — Amzn-SearchBot, bedrockbot — and they are counted separately because the decisions about them are separate. Filing them together under one operator name would let ordinary indexing look like AI interest, which is the single most misleading thing an AI traffic report can do. ### Why does Amzn-User not show up in Google Analytics? Google Analytics runs in the browser. This crawler never opens a browser — it requests the HTML, reads it, and leaves, so the tracking script is never executed and no event is ever sent. Every browser-based analytics tool has the same blind spot, which is why crawler traffic has to be read from the server side to be seen at all. ### Why can a Amzn-User visit not be verified? Amazon publishes neither a machine-readable list of the addresses its crawler uses nor a reverse DNS record pointing back at itself. With neither, the user-agent header is the only evidence, and anyone can send it. Rather than showing a confidence we cannot support, the visit is recorded as an unverified claim — which is also the honest answer to give anyone asking how much of your AI traffic is real. ## Related - https://truestat.io/glossary/amazon-amzn-searchbot - https://truestat.io/glossary/amazon-bedrockbot - https://truestat.io/glossary/fcrdns - https://truestat.io/glossary/spoofed-crawler --- From the TrueStat glossary — https://truestat.io/glossary. Privacy-first web analytics that also shows you which AI assistants are reading your site.