atlassian.com

Whether agents can crawl you, find you in the registries and searches they check, and trust what they find.

• ✓Sitemap present & freshrequired4/4

  Sitemap at https://www.atlassian.com/sitemap.xml: 4606 entries, freshest <lastmod> 2026-08-17 (0 days ago)

  Resolved the sitemap from robots.txt or /sitemap.xml, validated XML, and checked lastmod freshness

  spec ↗report issue
• ✓Brand search discoverabilityrequired4/4

  Both searches ("Atlassian" and "Atlassian productivity") cited atlassian.com: https://support.atlassian.com/confluence/kb/how-to-report-on-links-in-a-confluence-instance/, https://support.atlassian.com/platform-experiences/docs/produce-reports-and-integrate-with-other-apps-using-smart-links/, https://support.atlassian.com/jira-software-cloud/docs/generate-a-report/, https://support.atlassian.com/jira-software-cloud/docs/export-search-results/, https://support.atlassian.com/jira-software-cloud/docs/manage-search-results/

  Ran clean brand-name web searches and checked whether your domain is cited in the results

  report issue
• —MCP registry listingsrecommendedna

  No MCP server detected for this product

  Queried the official MCP registry, Smithery, Glama, and PulseMCP for servers matching your domain

  spec ↗report issue

Whether your robots policy, bot protection, and agent guidance actively admit AI agents instead of blocking them.

• ✓robots.txt present & parseablerequired2/2

  /robots.txt parses: 2 User-agent group(s), 2 Sitemap line(s)

  Fetched /robots.txt and validated it parses as a robots policy

  spec ↗report issue
• ✓AI crawler policyrequired5/5

  All 12 AI crawler user-agents (GPTBot, ClaudeBot, PerplexityBot, …) are allowed at / by robots.txt

  Evaluated robots.txt groups for the major AI agent user-agents (GPTBot, ClaudeBot, PerplexityBot, …)

  report issue
• ✗Content Signals directivesemerging0/2

  No Content-Signal lines in robots.txt

  fix → Declare Content Signals in robots.txt (e.g. `Content-Signal: search=yes, ai-train=no`) to express AI usage preferences machine-readably.

  Looked for Content-Signal lines in robots.txt

  spec ↗report issue
• !Agent user-agent paritybetarequirederror

  Browser UA received HTTP 200 with bot-challenge markers — cannot evaluate parity (the site may be blocking our scanner)

  Compared responses served to browser and AI-agent user-agents (informational while in beta)

  report issue
• ✗agents.mdrecommended0/3

  No agents.md: https://atlassian.com/agents.md → HTTP 404, https://atlassian.com/AGENTS.md → HTTP 404

  fix → Add /agents.md: what agents may do on your site, key URLs, auth, rate limits, and who to contact.

  Fetched /agents.md and checked for substantive agent guidance

  spec ↗report issue

Whether your pages carry machine-readable identity: structured data, llms.txt, clear copy an agent can quote.

• ✓Homepage states what you arerequired3/3

  Homepage clarity rated 5/5 — an agent can confidently say what this company does (model's one-sentence read: "Atlassian provides collaboration software for software, IT, and business teams, offering tools for project management, knowledge sharing, service management, and software development.")

  An LLM read your homepage as an agent would and rated how confidently it could say what you do

  report issue
• ✓OpenGraph / social metadatarecommended2/2

  Homepage has og:title, og:description, and og:image (twitter:card="summary_large_image" present)

  Parsed homepage og:title / og:description / og:image and twitter:card meta tags

  spec ↗report issue
• ✓llms.txtrecommended4/4

  /llms.txt is valid llmstxt.org shape: H1 "Atlassian", 105 markdown link(s)

  Fetched /llms.txt and validated it against the llmstxt.org shape (H1, summary, curated links)

  spec ↗report issue
• ✓llms-full.txtbonusrecommended2/2

  /llms-full.txt serves 35281 chars of markdown

  Fetched /llms-full.txt and checked for substantial inline markdown content

  spec ↗report issue
• ✓JSON-LD structured datarequired4/4

  7 JSON-LD block(s) on homepage and pricing page (types: Organization, WebSite, WebPage, SoftwareApplication); Organization block is well-formed

  Extracted and validated application/ld+json blocks on the homepage and pricing page

  spec ↗report issue
• ✗Markdown content negotiationrecommended0/3

  GET / with `Accept: text/markdown` returned HTTP 200 text/html; no .md twins found (2 probed)

  fix → Serve text/markdown when clients send `Accept: text/markdown` (or expose .md twins of key pages) — agents get far more signal per token.

  Requested key pages with Accept: text/markdown and probed .md twin URLs

  report issue

Whether the artifacts an agent needs to build on you — docs, API specs, SDKs, MCP servers — exist and are findable.

• ✓Developer resource discoverabilityrecommended3/3

  Search "Atlassian API documentation" cited your own domain: https://developer.atlassian.com/cloud/jira/platform/rest/v2/intro/, https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issue-search/, https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/, https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/, https://developer.atlassian.com/cloud/confluence/rest/v1/intro/

  Searched for your brand with developer-keyword suffixes and checked which official resources are cited

  report issue
• ✗OpenAPI spec discoverablerequired0/5

  No OpenAPI spec found: checked docs-page links and /openapi.json, /openapi.yaml, /swagger.json, /api/openapi.json, /docs/openapi.json, and api-subdomain locations

  fix → Publish your OpenAPI spec at /openapi.json and link it from docs — it's the single highest-leverage artifact for agent integration.

  Probed standard OpenAPI locations and docs links for a fetchable, parseable spec

  spec ↗report issue
• ✓Docs discoverablerequired4/4

  Docs found at https://www.atlassian.com/software/rovo-dev (via homepage link, 11232 chars of readable text)

  Followed homepage nav/footer links and probed /docs, /developers, docs.{domain}

  report issue
• ◐MCP server discoveryrequired2.5/5

  MCP evidence found only as a mention in llms.txt: "https://www.atlassian.com/platform/remote-mcp-server" — no well-known server card

  fix → Publish /.well-known/mcp/server-card.json describing your MCP endpoint so agents can autodiscover it. Evidence found: llms.txt.

  Probed /.well-known/mcp/server-card.json, mcp.json, and docs mentions for an MCP endpoint

  spec ↗report issue
• ✗npm SDKrecommended0/2

  No official npm SDK found: probed 6 candidate(s) (@atlassian/sdk, @atlassian/atlassian, atlassian, atlassian-sdk, atlassian-api, atlassian-js) — registry unavailable for: atlassian (Request budget exhausted), atlassian-sdk (Request budget exhausted), atlassian-api (Request budget exhausted), atlassian-js (Request budget exhausted)

  fix → Publish an official npm SDK (suggest @atlassian/sdk) with your domain in package.json homepage so agents can verify it's official.

  Searched the npm registry for an official, domain-verified SDK package

  report issue
• ✗PyPI SDKrecommended0/2

  No official PyPI SDK found: probed 4 candidate(s) (atlassian, atlassian-sdk, atlassianapi, atlassian-python) — found but not domain-verified: atlassian

  fix → Publish an official Python SDK (suggest "atlassian") with your domain in the project URLs so agents can verify it's official.

  Searched PyPI for an official, domain-verified SDK package

  report issue

Whether your specs, docs, and tools are complete and descriptive enough for an agent to use them without guessing.

• —OpenAPI validity & qualityrecommendedna

  No OpenAPI spec found — nothing to lint

  Linted the spec: descriptions, operationIds, securitySchemes, servers

  report issue
• ✗Docs qualityrecommended0/3

  Docs at https://www.atlassian.com/software/rovo-dev scored clarity 3/5, completeness 1/5, runnable examples 0/5, agent-friendliness 1/5 (mean 1.3/5)

  fix → Docs scored 0/5 on runnable examples. The documentation is a marketing page for a product and does not contain any API specifications or integration guides for an AI agent.

  An LLM rated your docs for clarity, completeness, runnable examples, and agent-friendliness

  report issue
• ✗Quickstart / getting startedrecommended0/2

  No quickstart/getting-started link or heading found on docs page https://www.atlassian.com/software/rovo-dev (searched 91 links)

  fix → Add a copy-pasteable quickstart (auth → first API call) — agents follow it literally.

  Looked for a quickstart/getting-started guide containing code blocks

  report issue
• —MCP tool qualityrecommendedna

  No tools listed by the MCP endpoint — nothing to lint

  Linted listed tools for descriptions, typed input schemas, and naming

  report issue

Response hygiene, TLS and redirect discipline, and security contact channels agents depend on at runtime.

• ✓TLS & redirect hygienerequired2/2

  http://atlassian.com/ upgrades to https in 1 hop(s), 2 redirect(s) total, final HTTP 200; HSTS present

  Checked http→https redirect behavior, chain length, and TLS health

  report issue
• ◐Response speed & weightrequired0.5/1

  Homepage TTFB 430ms, payload 2061KB, Content-Encoding: br — one target missed: payload 2061KB (target ≤1536KB)

  fix → Fix: payload 2061KB (target ≤1536KB). Enable compression and trim payload — agents run on strict timeouts.

  Measured homepage TTFB, payload size, and compression

  report issue
• ✓security.txtrecommended1/1

  Valid security.txt at https://atlassian.com/.well-known/security.txt: Contact https://www.atlassian.com/trust/security/report-a-vulnerability, Expires 2027-02-04

  Fetched /.well-known/security.txt and validated Contact + Expires

  spec ↗report issue

Whether agents can discover your auth model machine-readably (OAuth metadata) and follow documented steps to credentials.

• ✗OAuth authorization server metadatarecommended0/3

  Neither /.well-known/oauth-authorization-server nor /.well-known/openid-configuration resolved (HTTP 404 / HTTP 404)

  fix → Serve RFC 8414 metadata at /.well-known/oauth-authorization-server with PKCE (S256) and a registration_endpoint so agents can self-onboard.

  Fetched /.well-known/oauth-authorization-server (and openid-configuration fallback)

  spec ↗report issue
• ✗OAuth protected resource metadatarecommended0/2

  No RFC 9728 metadata: https://atlassian.com/.well-known/oauth-protected-resource → HTTP 404

  fix → Serve RFC 9728 metadata at /.well-known/oauth-protected-resource naming your authorization servers so agents can discover how to authenticate.

  Fetched /.well-known/oauth-protected-resource

  spec ↗report issue
• ✗Auth documentationrecommended0/2

  No auth/API-key link found among 91 links on docs page https://www.atlassian.com/software/rovo-dev, and /auth.md is absent

  fix → Document auth end-to-end (key creation → header format → example call), or ship /auth.md.

  Looked for /auth.md or an authentication docs page with code examples

  report issue

Whether pricing is discoverable and machine-readable, and whether you support agent payment protocols.

• ◐Pricing discoverablerequired2.5/5

  Pricing page found at https://www.atlassian.com/company/contact/purchasing-licensing (via homepage link) but no legible price signals in 5232 chars of page text — no currency amounts, "per month"/"/mo", or "free plan" terms (reads as contact-sales only).

  fix → Add literal plan prices to https://www.atlassian.com/company/contact/purchasing-licensing; 'Contact sales'-only pricing means agents can't complete a purchase evaluation.

  Followed nav/footer links and probed /pricing for a page with legible price signals

  report issue
• ✗Machine-readable pricingrecommended0/5

  No pricing plans could be extracted from https://www.atlassian.com/company/contact/purchasing-licensing (extraction confidence 0.00); no Offer JSON-LD on the page.

  fix → Add Offer JSON-LD per plan (name, price, priceCurrency, billing period) to https://www.atlassian.com/company/contact/purchasing-licensing so pricing parses without inference.

  Looked for Offer JSON-LD, then had an LLM attempt structured extraction of your plans

  spec ↗report issue
• ✗x402 payment supportbonusrecommended0/2

  /.well-known/x402 returned HTTP 404. No x402 support detected (bonus check — absence costs nothing).

  fix → Support x402: serve payment requirements at /.well-known/x402, or answer unauthenticated API calls with HTTP 402 plus an x402 payment-requirements payload (x402Version, accepts[]).

  Probed /.well-known/x402 and API endpoints for HTTP 402 payment-required envelopes

  spec ↗report issue
• ✗AP2 readinessemerging0/1

  No AP2 hints found — scanned llms.txt, docs page (https://www.atlassian.com/software/rovo-dev); /.well-known/ap2 returned HTTP 404.

  fix → Adopt AP2 to accept delegated agent payments — see https://ap2-protocol.org.

  Scanned fetched artifacts and well-known paths for AP2 hints

  spec ↗report issue
• ✗Agentic Commerce Protocolemerging0/1

  No Agentic Commerce Protocol hints found — scanned llms.txt, docs page (https://www.atlassian.com/software/rovo-dev); /.well-known/acp returned HTTP 404.

  fix → Adopt the Agentic Commerce Protocol so agent checkouts can complete against your store — see https://developers.openai.com/commerce.

  Scanned docs and specs for agentic checkout endpoints

  spec ↗report issue
• ✗Other agent payment protocolsbonusemerging0/1

  No UCP/MPP hints found — scanned llms.txt, docs page (https://www.atlassian.com/software/rovo-dev).

  fix → Track emerging agent payment protocols (UCP, MPP) and adopt the ones your buyers' agents use.

  Scanned fetched artifacts for UCP/MPP protocol hints

  report issue

Whether an end user's agent can operate on their behalf: working MCP tools, published skills, agent configs.

• —Agent skill publishedbonusemergingna

  Requires the analysis phase — not yet evaluated

  Checked /skill.md, /.well-known/skills/, and skills.sh for published agent skills

  report issue
• ✗MCP handshake & tools listrequired0/4

  MCP endpoint https://www.atlassian.com/platform/remote-mcp-server failed handshake: Not a JSON-RPC endpoint

  fix → MCP endpoint https://www.atlassian.com/platform/remote-mcp-server failed handshake: Not a JSON-RPC endpoint. Support streamable HTTP with protocol version negotiation; if auth-gated, return RFC 9728 metadata in WWW-Authenticate.

  Performed a streamable-HTTP initialize + tools/list against the MCP endpoint

  spec ↗report issue
• —Agent configs in public repobonusemergingna

  Requires the analysis phase — not yet evaluated

  Checked your public GitHub org's main repos for AGENTS.md / .claude / .cursor configs

  report issue

Whether the site itself is legible to non-rendering and browser agents: semantic HTML, no JS walls, accessibility.

• ✗NLWeb endpointemerging0/1

  No NLWeb endpoint detected: /.well-known/nlweb.json returned HTTP 404 (text/html); GET /ask?query=hello returned HTTP 200 (text/html)

  fix → Consider exposing an NLWeb /ask endpoint (and /.well-known/nlweb.json) for conversational access to your content.

  Probed /.well-known/nlweb.json and the /ask endpoint

  spec ↗report issue
• ◐Semantic HTML structurerequired1.5/3

  3/6 semantic signals present on the homepage (missing: <header>/<footer>, no heading-level skips, text-to-markup ratio ≥ 0.10)

  fix → Add the missing structure: <header>/<footer>, no heading-level skips, text-to-markup ratio ≥ 0.10. Agents parse structure, not pixels.

  Scored landmark elements, heading hierarchy, and text-to-markup ratio on the homepage

  report issue
• ✓Content readable without JavaScriptrequired2/2

  Homepage raw HTML contains 12983 chars of visible text without JavaScript

  Measured visible text in the raw, unrendered homepage HTML

  report issue
• ✓Accessibility basicsrequired2/2

  Homepage accessibility: 5/5 checks passed

  Static checks: lang attribute, title, alt coverage, labeled inputs, landmarks

  report issue
• ✗WebMCPemerging0/1

  No WebMCP evidence on homepage: no application/webmcp script and no navigator.modelContext reference

  fix → Consider WebMCP to expose page actions as tools to browser agents.

  Looked for WebMCP script declarations on the homepage

  spec ↗report issue