Amazonbot: Robots.txt & Crawl Policy Reference

AI Summary: Amazonbot is Amazon's primary web crawler. It is used to improve Amazon's products and services, including providing answers for Alexa and potentially training Amazon's AI models.

Role and policy boundary

Amazonbot operates as a background crawler to index web content. Amazon states that the data collected helps provide accurate information to customers (like Alexa responses) and may be used to train Amazon AI models. Blocking this bot opts your site out of both Alexa indexing and Amazon's AI data collection.

A robots rule is a declaration of intent; it does not replace authentication, authorization, or rate limiting. Start with a dedicated group:

User-agent: Amazonbot
Allow: /
Disallow: /staging/
Disallow: /internal/

To stop access for the entire site, use:

User-agent: Amazonbot
Disallow: /

Avoid assuming that User-agent: * expresses the same business intent. A wildcard can affect assistant and training crawlers too, and it makes later audits harder because the source of the decision is less specific.

Layered verification

Verify the same URL through each control plane instead of assuming that one green signal represents the whole request path. Compare the bot-specific robots group, the page-level metadata, and the response headers captured at the public edge.

Amazonbot officially respects robots.txt directives. However, Amazon notes that Amazonbot currently does not support the crawl-delay directive in robots.txt or page-level meta tags like nofollow and noindex. To stop Amazonbot, you must use a strict Disallow in robots.txt.

The Policy Engine evaluates the selected user-agent, path scope, and the other supplied layers independently. It can therefore explain why a bot is allowed while another is blocked, rather than returning one blended website score.

Page-level directives can still override the intended outcome for indexing:

<meta name="robots" content="noindex, nofollow">

X-Robots-Tag: noindex, nofollow

If a response uses these tags, the report marks the result as blocked or conflicting even if the crawler-specific robots group is permissive. This is especially important for canonical pages served through an edge cache where headers may differ from the origin response.

WAF and Nginx remediation examples

To enforce a block at the network layer and prevent bandwidth consumption from Amazonbot, use a WAF rule:

{
  "description": "Block Amazonbot",
  "expression": "lower(http.user_agent) contains \"amazonbot\"",
  "action": "block"
}

Use your platform's actual middleware response pattern rather than copying this simplified example without review. Never place a secret, verification token, or internal policy identifier in a public response header.

map $http_user_agent $block_amazonbot_private {
    default 0;
    ~*amazonbot 1;
}

server {
    location ~ ^/(admin|account|private|licensed|internal|api)/ {
        if ($block_amazonbot_private) { return 403; }
        try_files $uri $uri/ =404;
    }
}

Review checklist

Use this checklist after every policy change and after a CDN or WAF migration. Record the request URL, User-Agent, HTTP status, final redirect, and the exact evidence used to reach the decision.

Verify that the dedicated group appears before relying on a wildcard, test a representative public and private path, and compare live response headers with robots.txt. Keep the policy close to the content owner's intent and record whether the site wants discovery, citation, or no access at all.

Need to optimize your entire site for AI search visibility? Run a comprehensive audit with Geolify.ai.