Bot intelligence record

Amazon Q

Usually allow

Use the amazon-QBusiness identifier to separate Amazon search indexing or content discovery traffic from normal visitor requests in server logs.

Search Ai Training Official Documented Confidence: High Verified: Yes robots.txt: Yes
Operator
Amazon
Family
Amazon
Type
Search
Source type
Official
Last checked
2026-05-20

User-Agent Pattern

Amazon
amazon-QBusiness
Verification note

User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.

Robots.txt Snippet

Click snippet to copy
User-agent: amazon-QBusiness Disallow: /

Click the snippet to copy it, or highlight the text manually.

Handling Guidance

Depends

This bot is usually safe to allow when the request source is verified and the traffic matches your site policy.

Search indexing, content discovery, rendering, or search-result freshness checks.

Record Details

Structured data
Operator
Amazon
Family
Amazon
Type
Search
Purpose
Ai Training
Identity type
Official Documented
Confidence
High
Last verified
2026-04-19
Last checked
2026-05-20
Source type
Official
Verification
Use the documented robots.txt token amazon-QBusiness from AWS documentation. Validate identifiers before creating hard allow rules.
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 Q is listed in the Botcrawl directory as a search crawler from Amazon. The primary identifier for log review is amazon-QBusiness.

Identification

  • User-agent pattern: amazon-QBusiness
  • Family: Amazon
  • Type: Search
  • Kind: Crawler

Common use

Search indexing, content discovery, rendering, or search-result freshness checks.

Verification and handling

Use the documented robots.txt token amazon-QBusiness from AWS documentation. Validate identifiers before creating hard allow rules.

Directory guidance marks the risk level as Safe 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: Yes.

Evidence and Source

  • Use the documented robots.txt token amazon-QBusiness from AWS documentation. Validate identifiers before creating hard allow rules.
  • Match `amazon-QBusiness` as a case-insensitive substring in HTTP user-agent logs. Review bot_aliases for alternate names or product labels. Do not treat a user-agent match alone as proof of identity for allow-listing.
  • Search indexing, content discovery, rendering, or search-result freshness checks.
  • 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.

Monitor This Bot In Edge

Botcrawl Edge

Use Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.