Atlassian Rovo

Atlassian Rovo combines enterprise search, chat, and agents. Its website crawler brings web content into Atlassian's Teamwork Graph so that those Rovo features can use the indexed pages as organizational knowledge.

The clearest documented workflow is the custom website connector. An Atlassian organization administrator supplies an HTTPS site that the organization owns, then Rovo performs a search crawl and index. This is a configured connection to a chosen website, not a general claim that every Rovo user triggers an open-web crawl through this identity.

Atlassian's connector instructions use the atlassian-bot user agent rather than a Rovo-named token. The crawler reads a standard robots.txt file at the root of the relevant hostname and follows specific allow and disallow paths. Atlassian says the file must be returned directly with a successful response; a redirect can cause connector validation to fail.

The content decision deserves attention on connected sites. Atlassian warns that all Teamwork Graph users can access content made available to this crawler, including pages reached with authentication configured in the connector. Review the crawlable scope before indexing an internal knowledge base.

Allowing this crawler affects discovery inside Rovo Search, Chat, and agents for the connected organization. It is not documented as a way to improve ranking in public AI search, and the crawler record does not say that Atlassian uses the pages to train a general foundation model.

There is no Cloudflare bot entry, Web Bot Auth key directory, or validated IP method attached to Rovo here. The broader atlassian-bot token is useful for robots.txt, but it is not cryptographic identity and should never replace authentication on restricted pages.