atlassian-bot
atlassian-bot is listed as a search crawler, and the community reference lists its operator as Atlassian. In October 2026, 103 sites block it, a 1.7% share of readable files.
Who runs atlassian-bot?
| Fact | atlassian-bot reference entry |
|---|---|
| Operator | “Atlassian” |
| Purpose | “AI search, assistants and agents” |
| Does atlassian-bot obey robots.txt? | “Yes” |
| Frequency | “No information provided.” |
| Cloudflare managed list for atlassian-bot | No |
These facts quote the stored community ai.robots.txt reference.
“atlassian-bot is a web crawler used to index website content for its AI search, assistants and agents available in its Rovo GenAI product.”
The listed use here is search. Using a page as a search result can send people to it. Training models uses its contents for another purpose, which an owner may refuse.
How many sites block it?
A User-agent line names it in 110 files, 1.8% of 6,171 readable files. Whole-site bans, written Disallow: /, total 103, or 1.7%. That leaves 6,068 without a recorded ban.
Breaking out the leading 1,000 sites gives 552 readable files, with 21 naming the crawler, or 3.8%. Whole-site blocking appears in 18 of them. Blocking is more common among the leading sites, at 3.3%. Beyond those ranks, 5,619 files have a blocking total of 85, 1.5% of that sample.
| Readable files | Named by | Named share | Blocked by | Blocked share |
|---|---|---|---|---|
| atlassian-bot, all ranks | 110 | 1.8% | 103 | 1.7% |
| atlassian-bot, top 1,000 | 21 | 3.8% | 18 | 3.3% |
| atlassian-bot, remaining ranks | 89 | 1.6% | 85 | 1.5% |
This total covers whole-site bans recorded for this name. A blanket User-agent: * rule alone is outside this measure. Of 103 blocks, 1 does not also appear in our count of files naming it. The overlap between naming and blocking is 102 files. Naming without a whole-site ban accounts for 8, and 6,061 files never name it. We ignore capitalization and repeated names.
How to block or allow it
Use your site’s root file, robots.txt. Specific groups for atlassian-bot take precedence over User-agent: *, according to the robots.txt standard.
Block the whole site
User-agent: atlassian-bot
Disallow: /Allow access
User-agent: atlassian-bot
Allow: /It's the 55th most-named crawler of the 171 we counted in the crawler index.
How we counted
For atlassian-bot, the survey covered 10,000 top Tranco sites, collected on 19 October 2026. A request timed out after 8 seconds, with files capped at 262,144 bytes. Missing, unreachable and oversized files do not contribute to these shares. Later readings are included in results from scripts/robots_2026_08_06.py (robots.py at app commit 07104ff). See the full survey method.
Common questions
Can a file name it and still allow it?
This survey includes 8 files with the name and no whole-site ban, out of 110 naming files.
How do the shares compare by rank?
Leading files record 3.8% with the name and 3.3% blocking it. Across all readable files, the corresponding shares are 1.8% and 1.7%.
What other entry is close in the index?
The nearby Amzn-SearchBot entry reports 109 files that name it and 307 whole-site blocks, 5.0% of readable files. Here, 110 files mention the name and 103 block access, or 1.7%.