alexa site audit
alexa site audit is a search-engine crawler operated by Amazon. Its job is to find, fetch, and index web pages so they can be returned in organic search results.
Traffic is regular and bounded by your robots.txt. Allowing it is generally how your site stays discoverable through the corresponding search engine, blocking it almost always reduces visibility there.
For most sites, search-engine crawlers are still the largest source of bot traffic and the largest source of human visitors that follow.
See alexa site audit on your own site
Match the User-Agent header on incoming requests against the pattern below.
regex
Verify by IP
For higher confidence, also verify the source IP against the operator's published ranges. UA strings can be spoofed; IP ownership is harder to fake.
Renders JavaScript
No
IP verification
Published IP ranges
Crawl frequency
Continuous
Honors robots.txt
Yes
Honors Crawl-delay
Yes
Amazon runs 38 bots in total. Each one is a separate user-agent so you can allow or block them independently.
Live-Fetch AI
11- Amzn-User
- Amazon Bedrock AgentCore Browser (AP Northeast)
- Amazon Bedrock AgentCore Browser (AP South)
- Amazon Bedrock AgentCore Browser (AP Southeast 1)
- Amazon Bedrock AgentCore Browser (AP Southeast)
- Amazon Bedrock AgentCore Browser (EU Central 1)
- Amazon Bedrock AgentCore Browser (EU West 1)
- Amazon Bedrock AgentCore Browser (US East 1)
- Amazon Bedrock AgentCore Browser (US East 2)
- Amazon Bedrock AgentCore Browser (US West 2)
- Amazon Buy For Me
Training Crawler
7Brand Intelligence
3Agentic Browser
3AI Search Index
2Generic Crawler
2DevOps & Monitoring
2Shopping Bot
2Search Engine
1- alexa site auditYou are here
Task Automation
1Ad Verification
1Ads Network Bot
1Link Unfurler
1AI Coding Tool
1Should I let alexa site audit through?
In most cases, yes. Blocking traditional search crawlers reduces organic-search visibility. Allowing is the default for almost all sites. If volume gets noisy, rate-limit it before you block it outright.
Does blocking alexa site audit affect my Google rankings?
Only on Amazon alexa site audit feeds. Each search engine runs its own crawler, so blocking alexa site audit only removes you from that one index. Your visibility on Google, Bing, or anything else is untouched.
How do I confirm a request is really from alexa site audit?
Two checks. The User-Agent header should match a known alexa site audit string, and the request's source IP should fall inside Amazon's published ranges. The User-Agent alone is trivially spoofable, so the IP check is what gives you confidence. Amazon publishes the ranges so you can validate at the CDN or edge.
What happens to my traffic if I block alexa site audit?
Your pages drop out of Amazon's index, which means losing the organic share you get from that engine. Not catastrophic if Amazon is a minor player, much more painful if it's a meaningful source of your traffic. Check your analytics for Amazon's actual referral share before deciding.
How is alexa site audit different from Amazon's other bots?
Amazon splits work across multiple user-agents so site owners can decide on each one independently. Training crawlers, live-fetch agents, search indexers, and agentic browsers each get their own name. Worth scanning the rest of the Amazon family above to see which ones actually matter for your site.
What's the cleanest way to control alexa site audit?
Two layers. Robots.txt for the polite crawlers that read it, and rules at your CDN or edge for the ones that don't. Rankly's Agent Experience handles both from a single config, so you can allow, block, rate-limit, or serve a stripped-down version per bot. Agent Analytics handles the observation half so you know which bots are actually worth a rule.
Verify everything above against the operator's own documentation.