AI search

atlassian-bot

Indexes connected websites for Atlassian Rovo.

See your agent traffic
PurposeAI search
HTTP identifierNot published in the source
IdentityVerify beyond the name

THE SIGNAL

What this visit tells you

Connector traffic should correspond to a configured website source.

Fetched pages
Failed retrievals
Repeat fetches

Your next move

Review connected content before enabling the crawl: Atlassian says every Teamwork Graph user can access indexed content, including content retrieved with configured authentication.

The technical details

Markdown
How to identify it

The source documents the atlassian-bot robots.txt token, but does not publish a separate HTTP User-Agent string. Use the operator’s verification method to investigate requests.

How to check identity

Use Atlassian’s published IP ranges with product rovo-crawler, and correlate requests with your configured website connector.

Access and robots.txt

The operator documents robots.txt rules for this identifier.

Optional full-site opt-out. Merge with existing rules only if intended. robots.txt does not secure private content.

User-agent: atlassian-bot
Disallow: /
Seeing 403 or 404 responses?

403 means access was denied; 404 means the resource was not found. Compare the public path, request time, edge security event and origin response to find the cause.

Separate intended restrictions and secret-file probes from pages that should work. A User-Agent name alone does not justify allowing a request.

SourcesReviewed 2026-09-14

Identity and purpose are based on these sources. Analytics interpretation and suggested checks are Apostl guidance.

APOSTL Pulse

See atlassian-bot in context

See their requests. Find the pages that matter.

See your agent traffic