Atlassian Rovo
Operated by Atlassian
Quick Facts
- User-Agent:
- atlassian-bot
- Category:
- AI & LLM Bots
- Operator:
- Atlassian
- Safety:
- Safe
- Blocking Impact:
- Low - No SEO ranking impact
- SEO Impact Score:
- 2/10
- Official docs:
- None published by Atlassian
Reported, not operator documented
Atlassian has not published a crawler page that names atlassian-bot. It is listed here on our own evidence. Verified by AI Crawler Check: 111 of the 5,583 valid robots.txt files in the Tranco top 10,000 carry a rule for atlassian-bot, 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. Atlassian Rovo crawler token; the Atlassian support page that named it has moved.
What that means for you: the atlassian-bot rule on this page is the best available spelling, but Atlassian has made no statement of purpose, crawl rate or robots.txt compliance. Treat a atlassian-bot 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 Atlassian Rovo?
Atlassian Rovo is an AI search-index crawler operated by Atlassian. It collects and indexes web content so it can be surfaced as citations or answers inside Atlassian's AI search experience. Allowing Atlassian Rovo can increase your visibility in AI-powered search results, which is why most sites choose to permit it.
Atlassian Rovo is an AI search-index crawler operated by Atlassian. It collects and indexes web content so it can be surfaced as citations or answers inside Atlassian's AI search experience. Allowing Atlassian Rovo can increase your visibility in AI-powered search results, which is why most sites choose to permit it.
Atlassian Rovo uses the user-agent token atlassian-bot. 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 Atlassian Rovo?
User-agent / Disallow: / without any SEO penalty.Want to see whether Atlassian Rovo actually visits you? Read how do I monitor AI bot traffic to my website?
How to block Atlassian Rovo with robots.txt
<code>User-agent: atlassian-bot</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.
Is Atlassian Rovo safe to allow?
What does Atlassian Rovo do?
Understanding Atlassian Rovo's purpose helps you decide whether to allow or block it.
- Indexes web pages for AI-powered search answers
- Surfaces your content as citations inside AI search results
- Builds a knowledge index used to answer user questions
- Allowing it can increase visibility in AI search
- robots.txt behaviour not documented by the operator
Atlassian Rovo in context
Atlassian Rovo is a retrieval crawler that feeds AI search answers operated by Atlassian. In plain terms, it builds a search or answer index. 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 Atlassian Rovo rests on what you want from Atlassian, not on its behaviour. How we rate safety and impact.
How site owners treat Atlassian Rovo
In our own scan of the Tranco top 10,000 (5,583 valid robots.txt files), 111 files (2%) name atlassian-bot 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?
Atlassian Rovo's operator does not clearly document how it treats robots.txt. Write the Atlassian Rovo rule anyway, then confirm in your logs that its requests stop.
Atlassian crawlers and close alternatives
Atlassian runs only this one crawler in our database, so a single User-agent: atlassian-bot group controls everything Atlassian fetches through it.
Other AI and LLM crawlers that do the same job (builds a search or answer index) include AddSearchBot from AddSearch, AIWebIndex from Lyrenth, AzureAI-SearchBot from Microsoft, Cloudflare-AI-Search from Cloudflare, Cloudflare-AutoRAG from Cloudflare, ExaBot from Exa. Deciding about Atlassian Rovo is usually a decision about the whole group, so check how your file treats these too.
We first recorded atlassian-bot on September 22, 2026. We could not find a page where Atlassian names it, so treat the token as reported rather than documented.
Which rule Atlassian Rovo actually follows
Atlassian Rovo reads exactly one group in robots.txt, the most specific one that names atlassian-bot, and never combines rules across groups. This short file shows the trap:
User-agent: *
Disallow: /private/
User-agent: atlassian-bot
Disallow: /drafts/- Find the group. Atlassian Rovo looks for a group naming
atlassian-bot. One exists, so it ignoresUser-agent: *completely. - Apply only that group. It is refused
/drafts/and nothing else. - The surprise.
/private/is open to Atlassian Rovo, 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 Atlassian Rovo if the file also has a User-agent: atlassian-bot group?
No. Once a group names it, Atlassian Rovo reads only that group. Put every rule you want it to follow inside its own group.
Test yourself: will blocking Atlassian Rovo remove your pages from AI answers?
Often, yes. Atlassian Rovo is a retrieval crawler that feeds AI search answers, so pages it cannot fetch can drop out of the answers or results it supports.
Test yourself: is User-agent: atlassian-bot the same as User-agent: atlassian-bot?
Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.
Should you allow Atlassian Rovo? Decide by situation
| If you are... | Recommended setting |
|---|---|
| You publish content and want AI answers to cite it | Allow it. Atlassian Rovo fetches pages for answers, so blocking it can remove you from them. |
| You license content and want to stop AI training | Blocking it does not stop training, because Atlassian Rovo is a retrieval crawler that feeds AI search answers. Block the operator's training crawler instead. |
| You run an online shop | Allow it on product and category pages, which are the pages shoppers ask assistants about. |
| Your server is under load from bots | Rate-limit before blocking. It is rated safe in our database. |
Check Atlassian Rovo on your own site
- Open
/robots.txton your domain and search foratlassian-bot. If it is not named, it followsUser-agent: *. - List the
Disallowlines in the group Atlassian Rovo 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 Atlassian Rovo even when robots.txt allows it, and that never shows in the file.
- Run our AI bot checker to see how Atlassian Rovo and every other crawler we track are treated in one pass, including firewall refusals.
Common mistakes with Atlassian Rovo
The errors we see most often with Atlassian Rovo in the files and firewalls we test:
- Blocking Atlassian Rovo while trying to stop AI training. Retrieval crawlers fetch pages so answers can cite them; blocking it can remove you from those answers without affecting training.
- Letting a firewall or bot-fight mode refuse Atlassian Rovo while robots.txt allows it. The file looks right, but the crawler still gets a 403 or a challenge page.
- Forgetting that once a
User-agent: atlassian-botgroup exists, Atlassian Rovo ignores every rule underUser-agent: *.
All three hide inside a file that looks correct, so check Atlassian Rovo from outside after every change.
Spotting Atlassian Rovo in your logs
robots.txt says what Atlassian Rovo 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 "atlassian-bot" /var/log/nginx/access.log \
| awk '{print $4}' | cut -d: -f1 | sort | uniq -cAnd this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:
grep -iE "atlassian-bot" /var/log/nginx/access.log \
| awk '{print $7}' | sort | uniq -c | sort -rn | head -20Check the requests are genuine
Anyone can send the Atlassian Rovo user-agent, so confirm the source before acting on a match:
atlassian-bot: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Atlassian Rovo request with caution.
Frequently Asked Questions
What user-agent string does Atlassian Rovo use?
atlassian-bot. Evidence that the spelling is in real use comes from our own robots.txt study: 111 of the 5,583 valid robots.txt files in the Tranco top 10,000 name it (fetched October 20, 2026), not from Atlassian, 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 Atlassian Rovo safe?
Will blocking Atlassian Rovo hurt my SEO?
User-agent / Disallow: / without any SEO penalty.How do I block Atlassian Rovo in robots.txt?
/robots.txt file:User-agent: atlassian-bot Disallow: /
This instructs Atlassian Rovo not to crawl any path on your site. To block only specific sections, replace / with the path (e.g.,
Disallow: /blog/).Does Atlassian Rovo respect robots.txt?
atlassian-bot will stop a client that chooses to honour it; for enforcement, add a firewall or CDN rule as well.How do I verify if Atlassian Rovo is crawling my site?
atlassian-bot (for example grep -i "atlassian-bot" /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 Atlassian sent it.