Bot intelligence record

Amazon Buy For Me

Review first

Use the AmazonBuyForMe identifier to separate Amazon commerce, ad, checkout, or payment-related traffic from normal visitor requests in server logs.

Ecommerce Ecommerce Verified Bot Confidence: Medium Verified: Yes robots.txt: No

User-Agent Pattern

Amazon
AmazonBuyForMe

Robots.txt Snippet

Copy-ready
User-agent: AmazonBuyForMe Disallow: /

Handling Guidance

Depends

Use this record as bot intelligence, then verify the request source and behavior before allowing, blocking, or rate limiting.

Commerce, checkout, product, advertising, or payment-related verification requests.

Record Details

Structured data
Operator
Amazon
Family
Amazon
Type
Ecommerce
Purpose
Ecommerce
Identity type
Verified Bot
Confidence
Medium
Last verified
2026-04-01
Last checked
2026-05-20
Source type
Verified Directory
Spoofing risk
User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.

Notes

Amazon Buy For Me is listed in the Botcrawl directory as a commerce-related fetcher from Amazon. The primary identifier for log review is AmazonBuyForMe.

Identification

  • User-agent pattern: AmazonBuyForMe
  • Family: Amazon
  • Type: Ecommerce
  • Kind: Fetcher

Common use

Commerce, checkout, product, advertising, or payment-related verification requests.

Verification and handling

Confirm the user-agent against server logs and use published operator documentation, IP ranges, reverse DNS, or other trust signals when available.

Directory guidance marks the risk level as Neutral and the blocking decision as Depends. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.

Robots.txt handling: No.

Evidence and Source

  • Validate the identifying user-agent or signature against the operator documentation before creating hard allow rules.
  • Match `AmazonBuyForMe` as a case-insensitive substring in HTTP user-agent logs. Use bot_http_agent for full user-agent examples when the client sends a longer browser-like string. Do not treat a user-agent match alone as proof of identity for allow-listing.
  • Commerce, checkout, product, advertising, or payment-related verification requests.
  • User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.

WordPress Bot Protection

Bot Blocker for WordPress

Monitor bot traffic, review live activity, and control AI crawlers, scrapers, scanners, spam bots, and fake trusted bots from one clean WordPress dashboard.