Amazonbot

What Amazonbot does

Amazonbot crawls public pages to power Alexa answers and, more broadly, Amazon's AI features. Amazon documents the user agent and states it respects robots.txt, including crawl-delay. It has grown into one of the higher-volume crawlers on content sites.

Why it visits your site

Question-answering features need a broad index of factual content; informational pages attract it most.

The bigger picture: AI training crawlers

Training crawlers are the most economically lopsided visitors your server has. A search crawler takes your content and pays you back in ranked listings and click-throughs; a training crawler takes the same content to improve a commercial model and, by design, sends nothing in return. The visit itself is the entire transaction. That asymmetry is why training bots - not AI in general - are where most of the blocking debate actually lives, and why the publishing industry's response has split between refusal and negotiation: several large publishers block these crawlers outright, while others have signed licensing deals with the same operators. Both strategies start from the same place - knowing, concretely, how much of your archive is being read and by whom.

The norms here are young and still hardening. The better operators now publish user agents, IP ranges, and opt-out tokens, and honor robots.txt; others publish nothing and, by widely credited reports, crawl through disallow rules. Treat each crawler on its record rather than assuming the category behaves uniformly - and remember that a robots.txt line only ever governs the polite end of the spectrum.

Should you block it?

Alexa answers rarely drive measurable web traffic, so the referral upside of allowing it is thin. If crawl volume bothers you, a crawl-delay or a block costs little; some publishers keep it in the allowed set on the theory that assistant answers still build brand familiarity.

Block via robots.txt

Add these lines to the robots.txt at your site root to ask Amazonbot to stay away:

User-agent: Amazonbot
Disallow: /

Remember that robots.txt is a request, not a lock - compliance is voluntary, and enforcement happens at the server. Viz's AI Control pairs robots.txt rules with server-level 403 responses and then probes your site to verify the block is actually holding.

How to see Amazonbot traffic on your site

You have three windows onto it, each with a catch. Raw hosting access logs contain every Amazonbot request, but many managed WordPress hosts don't expose them, and when they do you are grepping text files by hand. A CDN dashboard sees the traffic at the edge, but it lives outside WordPress and speaks in totals, not in your site's terms. And JavaScript analytics - GA4 and friends - will never show it at all, because Amazonbot doesn't run scripts.

Viz's answer is the request log: filter to Amazonbot and read exactly which URLs it fetched and when, right inside wp-admin - then watch the same filter after any blocking decision to see whether the visits stopped, slowed, or kept coming.