AI search crawlers
atlassian-bot is a bot operated by Atlassian that indexes pages so an AI answer engine can cite them. atlassian-bot is a web crawler used to index website content for its AI search, assistants and agents available in its Rovo GenAI product. It is documented as honouring robots.txt, but no IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine.
Request says
"atlassian-bot"
Checked against
Nothing published
Live check
No operator check exists for atlassian-bot. This still shows what the address really is.
Reference
| User agent | atlassian-botToken only: match on the substring. |
|---|---|
| Operator | Atlassian |
| Purpose | AI search, assistants and agents |
| Respects robots.txt | Honourssource |
| Verification method | Claim onlyNone published, user agent only No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. |
| Crawl pattern | Not published |
| Robots.txt tokens | atlassian-bot |
| Operator documentation | None published |
atlassian-bot is a web crawler used to index website content for its AI search, assistants and agents available in its Rovo GenAI product.
robots.txt
Paste one at the root of your domain. Rules are per token.
User-agent: atlassian-bot
Disallow: /User-agent: atlassian-bot
Allow: /User-agent: atlassian-bot
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking atlassian-bot takes the site out of the index behind its answers, so it stops being cited there. If referral traffic from AI answers matters to you, block the training crawler instead and leave this one alone.
Build a file for every crawlerFAQ
atlassian-bot is a bot operated by Atlassian that indexes pages so an AI answer engine can cite them. atlassian-bot is a web crawler used to index website content for its AI search, assistants and agents available in its Rovo GenAI product. It is documented as honouring robots.txt, but no IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine.
Yes. The operator documents that atlassian-bot reads robots.txt and follows Disallow rules for its own token. Rules take effect on the next fetch of the file, which can be hours or days after you publish them.
You cannot, at least not from the request itself. No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. Compare the source IP against hosting and datacenter ranges instead, and rate limit anything that behaves like a crawler.
Add the atlassian-bot token to robots.txt with Disallow: /. If the crawler ignores robots.txt, match the user agent at your CDN or reverse proxy and return 403 there instead.
Blocking atlassian-bot takes the site out of the index behind its answers, so it stops being cited there. If referral traffic from AI answers matters to you, block the training crawler instead and leave this one alone.