Amazon Nova Act
Operated by Amazon
Quick Facts
- User-Agent:
- NovaAct
- Category:
- AI & LLM Bots
- Operator:
- Amazon
- Safety:
- Safe
- Blocking Impact:
- Low - No SEO ranking impact
- SEO Impact Score:
- 2/10
- Official docs:
- None published by Amazon
Reported, not operator documented
Amazon has not published a crawler page that names NovaAct. It is listed here on our own evidence. Verified by AI Crawler Check: 64 of the 5,583 valid robots.txt files in the Tranco top 10,000 carry a rule for NovaAct, so site owners treat it as a real crawler name (how we measure this). That proves the spelling is in use, not who sends it. Amazon Nova Act agent token. Amazon's bot page does not list it.
What that means for you: the NovaAct rule on this page is the best available spelling, but Amazon has made no statement of purpose, crawl rate or robots.txt compliance. Treat a NovaAct request in your logs as a clue, not proof of who sent it, and add a firewall rule if that traffic matters to you. If the operator publishes documentation, this profile moves to Official docs.
What is Amazon Nova Act?
Amazon Nova Act is a developer-facing extraction agent operated by Amazon. It fetches and structures web content on behalf of applications and AI agents built on Amazon's platform. Traffic volume depends on how third-party developers configure it, so monitor your logs if you see heavy activity.
Amazon Nova Act is a developer-facing extraction agent operated by Amazon. It fetches and structures web content on behalf of applications and AI agents built on Amazon's platform. Traffic volume depends on how third-party developers configure it, so monitor your logs if you see heavy activity.
Amazon Nova Act uses the user-agent token NovaAct. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.
What happens if you block Amazon Nova Act?
User-agent / Disallow: / without any SEO penalty.Want to see whether Amazon Nova Act actually visits you? Read how do I monitor AI bot traffic to my website?
How to block Amazon Nova Act with robots.txt
<code>User-agent: NovaAct</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.
Is Amazon Nova Act safe to allow?
What does Amazon Nova Act do?
Understanding Amazon Nova Act's purpose helps you decide whether to allow or block it.
- Extracts and structures web content for developer applications
- Powers AI agents built on the operator platform
- Volume depends on third-party developer configuration
- Monitor logs if you notice heavy activity
- Can be rate-limited via robots.txt or server rules
Amazon Nova Act in context
Amazon Nova Act is a utility crawler operated by Amazon. In plain terms, it harvests pages for a dataset or data product. Our database files it under AI and LLM crawlers and ranks it Tier 2, important crawlers from established AI and search operators. 74 of the 104 AI and LLM crawlers in our database share this tier.
Its safety rating is safe and its blocking impact is low. So the decision about Amazon Nova Act rests on what you want from Amazon, not on its behaviour. How we rate safety and impact.
How site owners treat Amazon Nova Act
In our own scan of the Tranco top 10,000 (5,583 valid robots.txt files), 64 files (1.1%) name NovaAct in a User-agent line. That shows site owners treat the token as a real crawler worth a rule. It does not, on its own, prove who operates it.
Does it follow robots.txt?
Amazon Nova Act's operator does not clearly document how it treats robots.txt. Write the Amazon Nova Act rule anyway, then confirm in your logs that its requests stop.
Amazon crawlers and close alternatives
Amazon Nova Act is one of 8 Amazon crawlers in our database. A User-agent: NovaAct group controls Amazon Nova Act only; the other Amazon tokens below need their own lines.
NovaAct: this crawler (Tier 2)Amazon Kendra: Amazon Kendra, harvests pages for a dataset or data product (Tier 6)amazon-QBusiness: Amazon Q Business, builds a search or answer index (Tier 3)Amazonbot: Amazon Nova AI, collects pages to train AI models (Tier 2)AmazonBuyForMe: Amazon Buy For Me, fetches a page when a person asks an assistant or app to open it (Tier 2)Amzn-SearchBot: Amzn-SearchBot, builds a search or answer index (Tier 3)Amzn-User: Amazon User Agent, fetches a page when a person asks an assistant or app to open it (Tier 2)bedrockbot: AWS Bedrock Bot, collects pages to train AI models (Tier 2)
To give Amazon Nova Act the same answer as its siblings, stack User-agent: NovaAct with their lines above one set of rules; to treat Amazon Nova Act differently, give it its own group.
Other AI and LLM crawlers that do the same job (harvests pages for a dataset or data product) include FirecrawlAgent from Firecrawl, iaskspider from iAsk, CloudflareBrowserRenderingCrawler from Cloudflare. Deciding about Amazon Nova Act is usually a decision about the whole group, so check how your file treats these too.
We first recorded NovaAct on March 17, 2026. We could not find a page where Amazon names it, so treat the token as reported rather than documented.
Which rule Amazon Nova Act actually follows
Amazon Nova Act reads exactly one group in robots.txt, the most specific one that names NovaAct, and never combines rules across groups. This short file shows the trap:
User-agent: *
Disallow: /private/
User-agent: NovaAct
Disallow: /drafts/
- Find the group. Amazon Nova Act looks for a group naming
NovaAct. One exists, so it ignoresUser-agent: *completely. - Apply only that group. It is refused
/drafts/and nothing else. - The surprise.
/private/is open to Amazon Nova Act, because that rule lives in the*group it no longer reads. To keep it out of both, repeatDisallow: /private/inside its own group.
Test yourself: does a rule under User-agent: * apply to Amazon Nova Act if the file also has a User-agent: NovaAct group?
No. Once a group names it, Amazon Nova Act reads only that group. Put every rule you want it to follow inside its own group.
Test yourself: will blocking Amazon Nova Act remove your pages from AI answers?
Often, yes. Amazon Nova Act is a utility crawler, so pages it cannot fetch can drop out of the answers or results it supports.
Related: how AI engines choose their sources
Test yourself: is User-agent: novaact the same as User-agent: NovaAct?
Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.
Should you allow Amazon Nova Act? Decide by situation
| If you are... | Recommended setting |
|---|---|
| You publish content and want AI answers to cite it | Low stakes either way. It does not decide whether AI answers cite you. |
| You license content and want to stop AI training | Blocking it does not stop training, because Amazon Nova Act is a utility crawler. Block the operator's training crawler instead. |
| You run an online shop | Allow it unless your logs show it is costly. |
| Your server is under load from bots | Rate-limit before blocking. It is rated safe in our database. |
Check Amazon Nova Act on your own site
- Open
/robots.txton your domain and search forNovaAct. If it is not named, it followsUser-agent: *. - List the
Disallowlines in the group Amazon Nova Act follows and test your key URLs against them; the longest match wins, andAllowwins a tie. - Look beyond the file. A firewall or bot manager can refuse Amazon Nova Act even when robots.txt allows it, and that never shows in the file.
- Run our AI search visibility check to see how Amazon Nova Act and every other crawler we track are treated in one pass, including firewall refusals.
Common mistakes with Amazon Nova Act
The errors we see most often with Amazon Nova Act in the files and firewalls we test:
- Treating Amazon Nova Act as an AI or search crawler. Blocking it has little effect on visibility; decide based on load and what it does with your data.
- Relying on robots.txt alone when Amazon Nova Act is rated caution or aggressive. Back the rule with a server-side block.
- Blocking Amazon Nova Act by IP alone. Ranges change; match the token and verify with logs.
All three hide inside a file that looks correct, so check Amazon Nova Act from outside after every change.
Spotting Amazon Nova Act in your logs
robots.txt says what Amazon Nova Act may do; your access logs show what it actually did.
Count requests
On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):
grep -iE "NovaAct" /var/log/nginx/access.log \
| awk '{print $4}' | cut -d: -f1 | sort | uniq -c
And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:
grep -iE "NovaAct" /var/log/nginx/access.log \
| awk '{print $7}' | sort | uniq -c | sort -rn | head -20
Check the requests are genuine
Anyone can send the Amazon Nova Act user-agent, so confirm the source before acting on a match:
NovaAct: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Amazon Nova Act request with caution.
Frequently Asked Questions
What user-agent string does Amazon Nova Act use?
NovaAct. Evidence that the spelling is in real use comes from our own robots.txt study: 64 of the 5,583 valid robots.txt files in the Tranco top 10,000 name it (fetched October 20, 2026), not from Amazon, which has not published crawler documentation naming it. Use it in robots.txt as the best available match, and treat a request carrying it as a clue rather than proof of who sent it.Is Amazon Nova Act safe?
Will blocking Amazon Nova Act hurt my SEO?
User-agent / Disallow: / without any SEO penalty.How do I block Amazon Nova Act in robots.txt?
/robots.txt file:User-agent: NovaAct Disallow: /
This instructs Amazon Nova Act not to crawl any path on your site. To block only specific sections, replace / with the path (e.g.,
Disallow: /blog/).Does Amazon Nova Act respect robots.txt?
NovaAct will stop a client that chooses to honour it; for enforcement, add a firewall or CDN rule as well.How do I verify if Amazon Nova Act is crawling my site?
NovaAct (for example grep -i "NovaAct" /var/log/nginx/access.log). Because the operator publishes no IP ranges or reverse-DNS pattern, a match shows that something used the name, not that Amazon sent it.