GeoPromptTracker

AI crawler profile

What is Amazonbot? How to allow or block Amazon's crawler

User-agent string to match in robots.txt and server logs: Amazonbot

Operator

Amazon

Purpose

Training + search

robots.txt

Respects robots.txt

Amazonbot crawls the web to improve Amazon products such as Alexa's question answering, and its collected content can also feed Amazon's AI model development. Because it serves both search-style features and training, blocking it trades Alexa answer visibility against training opt-out.

Does Amazonbot respect robots.txt?

Amazon documents Amazonbot and states it respects robots.txt, including wildcard rules.

Verify it's really Amazonbot

Amazon publishes no IP-range file for Amazonbot, so it can only be identified by its user-agent string — which anything can send. Treat traffic claiming this agent as unverified, and prefer a reverse-DNS check where the operator documents one before acting on it.

Block Amazonbot with robots.txt

robots.txt — block
User-agent: Amazonbot
Disallow: /

Explicitly allow Amazonbot

robots.txt — allow
User-agent: Amazonbot
Allow: /

Block Amazonbot at the server or CDN

robots.txt is the right first step for Amazonbot, since Amazon honors it. Use these only if you want the block enforced rather than requested — for example to stop agents spoofing the user agent. Matching on the user-agent string still trusts a self-declared header — and no IP-range file exists for this agent, so treat it as best-effort.

nginx
if ($http_user_agent ~* "Amazonbot") {
    return 403;
}
apache — .htaccess
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} Amazonbot [NC]
RewriteRule .* - [F,L]
cloudflare — WAF expression
(http.user_agent contains "Amazonbot")

Find Amazonbot in your server logs

shell
grep -i "Amazonbot" /var/log/nginx/access.log | wc -l

Should you block Amazonbot?

It's a genuine trade-off: Amazonbotserves both search-style features (which send you visibility) and model training (which you may want to opt out of). Since one user agent controls both, you can't split the decision — weigh which matters more using our blocking decision guide.

Check and monitor Amazonbot on your site

Related reading

Frequently asked questions

What is Amazonbot?

Amazonbot is Amazon's crawler serving both AI search features and model training. Crawls content for Amazon's search and AI products, including Alexa.

Does Amazonbot respect robots.txt?

Amazon documents Amazonbot and states it respects robots.txt, including wildcard rules.

How do I block Amazonbot?

Add "User-agent: Amazonbot" followed by "Disallow: /" to your robots.txt file. The change takes effect the next time the bot fetches your robots.txt.

Does blocking Amazonbot hurt my Google rankings?

No. Amazonbot is separate from Googlebot, which handles Google Search indexing. Blocking Amazonbot has no effect on your traditional search rankings, but it does remove your pages from the AI answers Amazon's assistant serves to its users.

How can I tell if Amazonbot is crawling my site?

Search your server access logs for the string "Amazonbot" — for example: grep -i "Amazonbot" /var/log/nginx/access.log | wc -l. Our free AI Bot Log Analyzer does this in your browser: paste a log file and it counts hits per AI crawler, including Amazonbot, with per-path breakdowns.

How do I use Amazonbot?

You don't — Amazonbot isn't a tool you run. It's Amazon's own crawler, operated by Amazon, that visits your site from their infrastructure. The only control you have over it is whether you allow or block it, via robots.txt or a server rule. If you're looking to crawl other sites yourself, you'd write your own crawler or use a crawling library; sending "Amazonbot" as your user agent would be impersonating Amazon.

Where is the official Amazon documentation for Amazonbot?

Amazon publishes it at https://developer.amazon.com/amazonbot. That page is the authoritative source for the user-agent string and Amazon's stated crawling policy.

Part of our directory of every known AI crawler, refreshed monthly. Last verified: 2026-08-14.