# Préparation de atlassian.com à l'IA

> Mesuré sur la page d'accueil. Note globale : Bon.

Score 72/100, note Bon. Mesuré 2026-09-04T21:42:00.726+00:00, moteur ax-audit@4.0.0.

## Vérifications

### Contenu — 80/100

#### Content Negotiation — 0/100

- **FAIL** Homepage does not serve Markdown via content negotiation
  Got text/html (HTTP 200) for "Accept: text/markdown"
  Serve a Markdown representation of your pages when agents request "Accept: text/markdown". Agents like Claude Code and Cursor ask for it, and Markdown cuts token usage by roughly 80% against HTML. Cloudflare ("Markdown for Agents") and Vercel can enable this without code changes.
  https://axrush.com/guides/content-negotiation#not-supported
- **WARN** No <link rel="alternate" type="text/markdown"> fallback found on the homepage
  If you cannot enable content negotiation, advertise a Markdown version with <link rel="alternate" type="text/markdown" href="/index.md"> so agents can discover it.
  https://axrush.com/guides/content-negotiation#no-alternate

#### Opérabilité par les agents — 90/100

- **PASS** 369/369 interactive elements have an accessible name
- **WARN** Heading hierarchy skips 2 level(s)
  h2 → h5
  Agents outline a page from its headings. A skipped level puts a section under the wrong parent, so a summary attributes it to the wrong topic.
  https://axrush.com/guides/agent-operability#heading-skips
- **WARN** 62/63 images, frames or videos have no declared dimensions
  Undeclared dimensions shift the layout as media loads. An agent working from a screenshot clicks where the button was a moment ago. Set width and height, or aspect-ratio.
  https://axrush.com/guides/agent-operability#unsized-media
- **PASS** Method note: this reads markup, not a rendered accessibility tree
  Labels attached by script and roles computed at runtime are invisible here, so treat low proportions as a prompt to check the real tree rather than as a count. Every finding is also a plain accessibility defect.

#### Structured Data — 95/100

- **PASS** 1 JSON-LD block(s) found
- **PASS** @context references schema.org
- **PASS** @graph array present (multi-entity structured data)
- **PASS** Key types found: Organization, WebSite, WebPage
- **WARN** No BreadcrumbList found
  Add a BreadcrumbList entity to help AI agents understand your site navigation hierarchy.
  https://axrush.com/guides/structured-data#no-breadcrumb
- **WARN** No author declared in structured data
  An assistant deciding whether to cite a page weighs where it came from. Add author as a Person or Organization, not a bare string.
  https://axrush.com/guides/structured-data#no-author
- **PASS** 6 sameAs link(s) tie your entity to external identifiers
  https://x.com/Atlassian, https://www.linkedin.com/company/atlassian/, https://www.facebook.com/Atlassian, https://www.instagram.com/atlassian/
- **PASS** Organization carries disambiguating detail (registration, legal address or contact point)
- **PASS** Content last dated 2026-08-31 (4 days ago)
- **PASS** Structured-data headings appear in the visible text

#### HTML Rendering — 85/100

- **PASS** Server-rendered content detected (2381 words, 17525 chars of visible text)
- **WARN** Low text-to-markup ratio (0.7%)
  Recommended minimum: 5%
  A very low text-to-markup ratio is a typical SPA-shell symptom. Inline more content directly into the HTML response.
  https://axrush.com/guides/html-rendering#low-ratio
- **PASS** Semantic landmarks present (main, section, footer, nav)
- **PASS** Single <h1> heading: "Unleash your teams and their agents"
- **WARN** Heavy JavaScript with no <noscript> fallback
  30 executable <script> tags
  Provide a <noscript> fallback that explains the site or links to a non-JS variant. This helps agents that disable JS.
  https://axrush.com/guides/html-rendering#no-noscript
- **PASS** 57/57 <img> tags have alt attributes

#### SEO Basics — 100/100

- **PASS** <title> length 70 chars: "Collaboration software for software, IT and business teams | Atlassian"
- **PASS** Meta description length 128 chars
- **PASS** Canonical URL: https://www.atlassian.com
- **PASS** <html lang="en">
- **PASS** UTF-8 charset declared
- **PASS** Viewport meta present: "width=device-width, initial-scale=1"

### Accès — 92/100

#### TLS / HTTPS — 90/100

- **PASS** Site is served over HTTPS
- **PASS** HTTP requests redirect to HTTPS
- **PASS** HSTS max-age=63072000
- **WARN** HSTS does not include subdomains
  Add includeSubDomains to apply HSTS across api., docs., etc. Required for preload list submission.
  https://axrush.com/guides/tls-https#hsts-no-subdomains
- **WARN** HSTS has preload directive but does not satisfy preload-list requirements
  Preload requires max-age >= 31536000 and includeSubDomains. See https://hstspreload.org.
  https://axrush.com/guides/tls-https#hsts-preload-invalid

#### Agent Access — 100/100

- **PASS** All 10 core AI crawler user-agents receive the same page as a regular client

#### Directives IA — 100/100

- **PASS** Homepage is indexable
- **PASS** No directive restricts how AI assistants may use this page

#### Hygiène HTTP — 80/100

- **WARN** A missing page redirects (301) instead of returning 404
  Location: https://www.atlassian.com/ax-audit-probe-t4kqnu4e
  A redirect on a nonexistent path hides the error. Return 404 or 410 so a client can tell the difference.
  https://axrush.com/guides/http-hygiene#soft-404-redirect
- **PASS** Homepage answers after 1 redirect
  301 → https://www.atlassian.com/
- **PASS** HEAD requests are supported
- **PASS** Content-Type: text/html with charset

#### Crawl Efficiency — 60/100

- **PASS** Response compressed with Brotli (br)
- **WARN** No ETag or Last-Modified header — conditional requests unsupported
  Send an ETag or Last-Modified header so crawlers can revalidate with If-None-Match / If-Modified-Since and receive a cheap 304 Not Modified instead of the full body.
  https://axrush.com/guides/crawl-efficiency#no-validators
- **WARN** Homepage is very large (2.4 MB decompressed)
  Large documents inflate crawl cost and token usage. Trim inlined data, split content, or serve a Markdown representation to agents (see the content-negotiation check).
  https://axrush.com/guides/crawl-efficiency#large-page
- **WARN** Roughly 4,381 tokens of content in 623,505 tokens of response (99% markup)
  Estimated at four characters per token.
  An agent pays to receive the markup and then discards it. Serving Markdown on Accept negotiation is the direct fix.
  https://axrush.com/guides/crawl-efficiency#markup-overhead
- **PASS** Homepage responded in 585ms

### Découverte — 78/100

#### LLMs.txt — 100/100

- **PASS** /llms.txt exists
- **PASS** /llms.txt Content-Type OK (text/plain)
- **PASS** H1 heading: "Atlassian"
- **PASS** Blockquote description present
- **PASS** 13 section heading(s) found
- **PASS** 105 link(s) found
- **PASS** /llms-full.txt also available (bonus)
- **WARN** No rel="describedby" link to llms.txt
  llms.txt v2 uses this relation so a page can name the file that covers it. Add <link rel="describedby" href="/llms.txt"> or the equivalent Link header, so an agent that landed on a deep page does not have to guess that an index exists.
  https://axrush.com/guides/llms-txt#no-describedby
- **WARN** 4 duplicate link(s) in llms.txt
  Each URL should appear once. Duplicates spend an agent’s budget re-reading what it already has.
  https://axrush.com/guides/llms-txt#duplicate-links
- **PASS** 15 sampled link(s) resolve
- **WARN** 1 sampled link(s) redirect
  https://www.atlassian.com/software/atlas → https://www.atlassian.com/platform/platform-apps
  Point llms.txt at the final URL. Each redirect is a round trip the agent pays for on every visit.
  https://axrush.com/guides/llms-txt#redirecting-links
- **WARN** No per-page Markdown mirror found
  Tried /index.md and /index.html.md.
  llms.txt v2 documents appending .md to a URL for its Markdown version. The index tells an agent which pages exist; the mirrors are what make reading them cheap.
  https://axrush.com/guides/llms-txt#no-markdown-mirror
- **PASS** Consumer note: llms.txt is read by coding agents, not by search
  Google has stated that Search ignores llms.txt, and adoption studies find most published files are never fetched by an AI search crawler. Claude Code, Cursor and OpenCode do fetch it. Treat it as developer tooling, not as a search-visibility signal.

#### Robots.txt — 60/100

- **PASS** /robots.txt exists
- **FAIL** No core AI crawlers explicitly configured
  Expected: GPTBot, ClaudeBot, Meta-ExternalAgent, Google-Extended, Applebot-Extended, Amazonbot, Bytespider, CCBot, OAI-SearchBot, Claude-SearchBot, PerplexityBot, ChatGPT-User
  Add User-agent entries for core AI crawlers in your robots.txt. For each crawler, add: User-agent: <name> followed by Allow: / on the next line.
  https://axrush.com/guides/robots-txt#no-core-crawlers
- **PASS** Sitemap directive present
- **WARN** No Content-Signal directive found (optional)
  Declare how crawlers may use your content after access with the Content Signals Policy, e.g.: Content-Signal: search=yes, ai-train=no. Known signals: search, ai-input, ai-train, plus the optional use=immediate|reference|full. Generate yours at contentsignals.org.
  https://axrush.com/guides/robots-txt#missing-content-signals
- **WARN** 0/57 known AI crawlers have explicit rules
  Add explicit User-agent entries for more AI crawlers to maximize discoverability.
  https://axrush.com/guides/robots-txt#low-coverage

#### Meta Tags — 54/100

- **WARN** No AI meta tags (ai:*) found
  Add AI meta tags to your HTML <head>: <meta name="ai:summary" content="Brief description">, <meta name="ai:content_type" content="website">, <meta name="ai:author" content="Your Name">.
  https://axrush.com/guides/meta-tags#no-ai-meta
- **WARN** No rel="alternate" link to llms.txt in HTML
  Add to your <head>: <link rel="alternate" type="text/plain" href="/llms.txt" title="LLM-optimized content">
  https://axrush.com/guides/meta-tags#no-llms-alternate
- **WARN** No rel="alternate" link to the Agent Card in HTML
  Add to your <head>: <link rel="alternate" type="application/json" href="/.well-known/agent-card.json" title="Agent Card">
  https://axrush.com/guides/meta-tags#no-agent-alternate
- **WARN** No rel="me" identity links found
  Add rel="me" links to verify your identity across platforms: <link rel="me" href="https://github.com/yourname">, <link rel="me" href="https://twitter.com/yourname">.
  https://axrush.com/guides/meta-tags#no-rel-me
- **PASS** OpenGraph required tags present (og:title, og:description, og:url, og:type)
- **PASS** Twitter Card required tags present (twitter:card, twitter:title, twitter:description)

#### Sitemap — 100/100

- **PASS** Sitemap located: https://www.atlassian.com/sitemap.xml
- **PASS** Content-Type is XML (application/xml)
- **PASS** Sitemap-index references 8 child sitemap(s)
- **PASS** 3/3 sample child sitemap(s) reachable
- **PASS** Sample yielded 3341 URL(s) across 3 child(ren)

#### HTTP Headers — 85/100

- **PASS** 5/7 security headers present
- **WARN** No Link header for AI discovery (llms.txt, Agent Card)
  Add a Link response header pointing to your AI discovery files: Link: </llms.txt>; rel="alternate"; type="text/plain", </.well-known/agent-card.json>; rel="alternate"; type="application/json"
  https://axrush.com/guides/http-headers#no-link-header
- **WARN** No machine-readable discovery relations beyond llms.txt and the Agent Card
  describedby — llms.txt v2 uses this relation to point a page at the llms.txt that covers it.
api-catalog — RFC 9727: the catalog of APIs this publisher offers.
service-desc — RFC 8631: a machine-readable API description.
service-doc — RFC 8631: human documentation for the API.
ai-catalog — Draft: the AI catalog listing agent cards and MCP server cards.
c2pa-manifest — C2PA 2.4: content provenance for media on the page.
license — RSL and other machine-readable licensing terms.
  Advertise what you publish with Link relations so agents stop guessing paths. Add the ones that apply, for example: Link: </llms.txt>; rel="describedby", </.well-known/api-catalog>; rel="api-catalog". Informational in 3.x: this does not affect your score.
  https://axrush.com/guides/http-headers#discovery-relations

### Protocoles — 0/100

#### Agent Card (A2A) — 0/100

- **FAIL** /.well-known/agent-card.json not found
  Site is agent-facing (an API surface (navigation into an API or developer area)). Also tried the pre-0.3 path /.well-known/agent.json. IANA-registered well-known URI.
  This site offers something an agent could call, but nothing tells an agent what. Publish an A2A Agent Card at /.well-known/agent-card.json. A minimal 1.0 card needs name, description, version, capabilities, supportedInterfaces, defaultInputModes, defaultOutputModes and skills. Spec: https://a2a-protocol.org/latest/specification/
  https://axrush.com/guides/agent-card#not-found

#### OpenAPI Spec — 0/100

- **FAIL** API surface present but no machine-readable description found
  Evidence of an API: navigation into an API or developer area. Checked /.well-known/api-catalog, Link and <link> rel="service-desc", and /.well-known/openapi.json, /openapi.json, /openapi.yaml, /.well-known/openapi.yaml, /api/openapi.json, /v1/openapi.json, /swagger.json, /api-docs, /asyncapi.json, /arazzo.json
  The API exists; nothing describes it in a form an agent can read, so using it requires a human to read your documentation first. Serve an OpenAPI description at /openapi.json and advertise it with Link: </openapi.json>; rel="service-desc". For several APIs, publish an RFC 9727 catalog.
  https://axrush.com/guides/api-discovery#not-found

#### MCP (Model Context Protocol) — N/A

- **PASS** No MCP server — MCP discovery does not apply to this site
  A server card describes an MCP server so agents can find it. A site that runs none has nothing to advertise. Run with --profile mcp to audit as though it did.

#### Catalogue IA — 0/100 (informe, ne note pas)

- **WARN** No agent resource catalog found
  Checked robots.txt Agentmap: directive, Link header rel="ai-catalog", <link rel="ai-catalog">, well-known path and /.well-known/ai-catalog.json, /.well-known/ard.json. Both specifications are drafts.
  A catalog is one document listing everything an agent can call here — agent cards, MCP servers, APIs, skills — so a client stops probing four conventions to find out. Worth publishing once you have more than one of those. Informational: both ai-catalog.json and ard.json are still drafts, so this never affects your score.
  https://axrush.com/guides/ai-catalog#not-found

#### Compétences d'agent — 0/100

- **WARN** No Agent Skills published
  Checked /.well-known/agent-skills/index.json, /.well-known/skills/index.json, /skill.md, /SKILL.md. Draft specification — the path may still change. Cloudflare RFC v0.2.0 (2026-03-12). Not registered; a competing shorter path (/.well-known/skills/) also ships.
  This site has documentation, so it has procedures worth teaching. A skill is a SKILL.md an agent installs and follows: setup steps, argument shapes, the mistakes to avoid. Publish one per task at /.well-known/agent-skills/{name}/SKILL.md and list them in /.well-known/agent-skills/index.json.
  https://axrush.com/guides/agent-skills#not-found

#### WebMCP — N/A

- **PASS** No forms and no WebMCP code — nothing here for an agent to invoke as a tool

#### Découverte commerce — N/A

- **PASS** No commerce surface — agentic-commerce discovery does not apply to this site
  No Product or Offer structured data, cart links, or product price tags found.

#### Découverte d'authentification — N/A

- **PASS** Nothing on this site requires authorization — auth discovery does not apply
  No API description, API catalog, MCP server card or commerce profile found.

### Politique — 51/100

#### Security.txt — 100/100

- **PASS** /.well-known/security.txt exists
- **PASS** Required field "Contact" present
- **PASS** Required field "Expires" present
- **PASS** Expires date is in the future (2027-02-04)
- **PASS** 5/5 optional fields present

#### RSL License — 0/100

- **FAIL** No RSL license discovery found
  Checked robots.txt License directive, Link header, and <link rel="license" type="application/rsl+xml">
  Declare machine-readable licensing terms for your content with Really Simple Licensing. Add to robots.txt: License: https://your-site.com/license.xml — then publish the RSL document. See https://rslstandard.org.
  https://axrush.com/guides/rsl#not-found

#### Politique d'usage — 40/100

- **WARN** No machine-readable usage policy declared
  Checked robots.txt Content-Signal and Content-Usage, the Content-Usage and content-signal response headers, an RSL licence, TDMRep, and the noai meta directive.
  State your terms where they can be read without a lawyer. The lowest-effort option is a Content-Signal line in robots.txt: Content-Signal: search=yes, ai-input=yes, ai-train=no. Absence is neutral, not permission — but it also gives you nothing to point at.
  https://axrush.com/guides/usage-policy#no-policy

---

Représentation Markdown de https://axrush.com/report/atlassian.com