In short. AmazonProductDiscoverybot collects public product details for Amazon, follows documented robots.txt controls and signs its requests for verification.

Definition: As of October 2026, AmazonProductDiscoverybot is Amazon's web crawler for collecting publicly available product details from selling partner, brand and retailer websites. Amazon uses this collection to improve the accuracy and completeness of product information available on Amazon.

Key facts

Amazon's Product Bot documentation says changes to supported robots.txt directives can take up to 24 hours to reach its systems.
The IETF's Robots Exclusion Protocol places the robots.txt file at the service's top-level /robots.txt path.
The IETF's HTTP Message Signatures specification defines Signature-Input for covered message components and parameters, and Signature for the signature value.

What information does it collect?

Amazon's Product Bot documentation describes collection of public product details to help customers see correct and complete information while shopping. The collection includes websites belonging to Amazon selling partners, brands and retailers.

The same page documents a separate identifier, AmazonSellerInitiatedListing, for a seller workflow that accepts a website URL to help create product pages in Amazon's store. This distinction matters when interpreting requests: the documentation assigns product-information collection to AmazonProductDiscoverybot and seller-provided URL retrieval to AmazonSellerInitiatedListing.

Which robots.txt token controls access?

A user-agent string is the identification text sent with a request. Amazon's identification guidance gives this identifying component:

AmazonProductDiscovery/1.0

Its robots.txt example uses a different spelling for the User-agent directive. The following rule matches Amazon's example for excluding all directories:

User-agent: AmazonProductDiscoverybot
Disallow: /

Amazon says the crawler honors user-agent and disallow directives. It treats a robots.txt file that cannot be fetched as absent, and does not support crawl-delay, nofollow or noindex directives.

For file placement and format, the IETF's Robots Exclusion Protocol specifies a lowercase /robots.txt path, UTF-8 encoding and the text/plain media type. Its security guidance recommends application-level protection, such as HTTP authentication, for restricting access to content; robots.txt paths are publicly visible.

How can a request be verified?

Amazon's verification guidance says every AmazonProductDiscoverybot request carries Signature, Signature-Input and Signature-Agent HTTP headers. Verification involves fetching Amazon's public key from the directory identified by Signature-Agent and validating the signature against that key.

For the signature fields, the IETF's HTTP Message Signatures specification describes a signature base as the formatted input to the cryptographic operation. Its verification process parses both fields, identifies the covered components, obtains trusted key material, reconstructs the signature base and applies the verification algorithm. Corresponding values in both fields must use the same label. A key that the verifier does not know or trust causes verification to fail.

FAQ

Which identifier should I put in robots.txt?

Use AmazonProductDiscoverybot, as shown in Amazon's robots.txt example. The request identification component is AmazonProductDiscovery/1.0.

Can I use Crawl-delay to slow this bot?

The same Amazon guidance lists crawl-delay among the unsupported directives. It documents Disallow rules for excluding paths.

What should I check in a signed request?

Amazon's Product Bot documentation identifies the signature headers and the public-key directory. The IETF's verification procedure also requires evaluating the trustworthiness of the verification key.

Sources

Check how a page reads to answer engines. Open the GEO score analyzer