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

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

Score 46/100, note Faible. Mesuré 2026-09-04T21:07:34.903+00:00, moteur ax-audit@4.0.0.

## Vérifications

### Contenu — 50/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 — 70/100

- **PASS** 148/150 interactive elements have an accessible name
- **PASS** 2/2 form controls are labelled
- **WARN** 6 link(s) lead nowhere without JavaScript
  2 with no href, 4 with a javascript: href
  A link with no destination cannot be followed by a fetch-only agent and cannot be opened in a new tab by a browsing one. Give it a real href, or make it a <button> if it is an action rather than a destination.
  https://axrush.com/guides/agent-operability#dead-links
- **WARN** 1/1 tables have no header cells
  Without <th>, a table is a grid of strings: an agent reading a price table cannot tell which column is the price. Add header cells, with scope on anything non-trivial.
  https://axrush.com/guides/agent-operability#tables-no-headers
- **WARN** Heading hierarchy skips 1 level(s)
  h3 → 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** 18/20 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 — 0/100

- **FAIL** No JSON-LD structured data found
  Add a <script type="application/ld+json"> block in your HTML <head> with schema.org structured data describing your site, organization, or person.
  https://axrush.com/guides/structured-data#not-found

#### HTML Rendering — 65/100

- **PASS** Server-rendered content detected (794 words, 4985 chars of visible text)
- **WARN** Low text-to-markup ratio (0.6%)
  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
- **WARN** Only 2 semantic landmark(s) found
  Found: header, nav. Missing: main, article, section, footer
  Use semantic HTML tags so AI agents can understand page structure: <header>, <nav>, <main>, <article>, <section>, <footer>.
  https://axrush.com/guides/html-rendering#few-landmarks
- **WARN** No <h1> heading found
  Add a single <h1> describing the page. Agents and search engines treat the H1 as the primary topic indicator.
  https://axrush.com/guides/html-rendering#no-h1
- **WARN** Only 15/20 <img> tags have alt attributes
  Add descriptive alt="" to every <img>. Agents use alt text to understand images they cannot process visually.
  https://axrush.com/guides/html-rendering#missing-alt

#### SEO Basics — 90/100

- **PASS** <title> length 35 chars: "Amazon.com. Spend less. Smile more."
- **WARN** Meta description is long (366 chars)
  Trim to 70-160 characters; longer descriptions get truncated.
  https://axrush.com/guides/seo-basics#long-description
- **PASS** Canonical URL: https://www.amazon.com/
- **PASS** <html lang="en-us">
- **PASS** UTF-8 charset declared
- **WARN** Missing or incomplete viewport meta tag
  Add <meta name="viewport" content="width=device-width, initial-scale=1">. Helps mobile agents render the page correctly.
  https://axrush.com/guides/seo-basics#no-viewport

### Accès — 85/100

#### TLS / HTTPS — 100/100

- **PASS** Site is served over HTTPS
- **PASS** HTTP requests redirect to HTTPS
- **PASS** HSTS max-age=47474747
- **PASS** HSTS includes subdomains
- **PASS** HSTS preload-eligible

#### Agent Access — 80/100

- **WARN** GPTBot probe failed: Server error (HTTP 503)
  status 503
  The request did not complete, so access for this crawler is unknown. Re-run the audit; if it persists, check origin health for this user agent.
  https://axrush.com/guides/agent-access#probe-failed
- **WARN** ClaudeBot probe failed: Server error (HTTP 503)
  status 503
  The request did not complete, so access for this crawler is unknown. Re-run the audit; if it persists, check origin health for this user agent.
  https://axrush.com/guides/agent-access#probe-failed
- **WARN** Bytespider probe failed: Server error (HTTP 503)
  status 503
  The request did not complete, so access for this crawler is unknown. Re-run the audit; if it persists, check origin health for this user agent.
  https://axrush.com/guides/agent-access#probe-failed
- **WARN** CCBot probe failed: Server error (HTTP 503)
  status 503
  The request did not complete, so access for this crawler is unknown. Re-run the audit; if it persists, check origin health for this user agent.
  https://axrush.com/guides/agent-access#probe-failed
- **WARN** OAI-SearchBot probe failed: Server error (HTTP 503)
  status 503
  The request did not complete, so access for this crawler is unknown. Re-run the audit; if it persists, check origin health for this user agent.
  https://axrush.com/guides/agent-access#probe-failed
- **WARN** Claude-SearchBot probe failed: Server error (HTTP 503)
  status 503
  The request did not complete, so access for this crawler is unknown. Re-run the audit; if it persists, check origin health for this user agent.
  https://axrush.com/guides/agent-access#probe-failed
- **WARN** PerplexityBot probe failed: Server error (HTTP 503)
  status 503
  The request did not complete, so access for this crawler is unknown. Re-run the audit; if it persists, check origin health for this user agent.
  https://axrush.com/guides/agent-access#probe-failed
- **WARN** ChatGPT-User probe failed: Server error (HTTP 503)
  status 503
  The request did not complete, so access for this crawler is unknown. Re-run the audit; if it persists, check origin health for this user agent.
  https://axrush.com/guides/agent-access#probe-failed
- **WARN** 8 crawler probe(s) could not be settled from outside
  GPTBot, ClaudeBot, Bytespider, CCBot, OAI-SearchBot, Claude-SearchBot, PerplexityBot, ChatGPT-User
  ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
  https://axrush.com/guides/agent-access#inconclusive-probe

#### Directives IA — 100/100

- **PASS** Homepage is indexable
- **WARN** Google-Extended is disallowed, but this page is still eligible for AI Overviews
  robots.txt disallows Google-Extended; no nosnippet or max-snippet directive is set on the page.
  Google-Extended governs Gemini training and grounding in Gemini Apps and Vertex AI. AI Overviews and AI Mode follow Googlebot and the snippet directives instead. If the intent was to stay out of AI Overviews, use nosnippet or max-snippet. If the intent was to opt out of training, this is already correct.
  https://axrush.com/guides/ai-directives#google-extended-mismatch

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

- **WARN** A missing page redirects (301) instead of returning 404
  Location: https://www.amazon.com/ax-audit-probe-sde9lwyu
  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.amazon.com/
- **WARN** HEAD requests are refused (405)
  HEAD lets a client confirm a URL exists, or check Last-Modified, without downloading the page. Refusing it turns every existence check into a full transfer.
  https://axrush.com/guides/http-hygiene#head-refused
- **PASS** Content-Type: text/html with charset

#### Crawl Efficiency — 65/100

- **PASS** Response compressed with gzip
  Brotli (br) typically compresses text 10–20% smaller — consider enabling it.
- **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 on the large side (897.4 KB decompressed)
  Consider trimming inlined payloads to reduce crawl cost.
  https://axrush.com/guides/crawl-efficiency#large-page
- **WARN** Roughly 1,246 tokens of content in 218,683 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 684ms

### Découverte — 18/100

#### LLMs.txt — 0/100

- **FAIL** /llms.txt not found
  HTTP 404
  Create a /llms.txt file at your site root following the llmstxt.org specification. It should be a Markdown file starting with "# Your Site Name" and include a description, sections, and links.
  https://axrush.com/guides/llms-txt#not-found

#### Robots.txt — 0/100

- **PASS** /robots.txt exists
- **WARN** 10/12 core AI crawlers configured
  Applebot-Extended — Opts your content out of Apple foundation-model training without affecting Siri or Spotlight.
Amazonbot — General crawler whose content may be used to train Amazon AI models.
  Add explicit User-agent entries for the missing crawlers with Allow: / for each one.
  https://axrush.com/guides/robots-txt#missing-crawlers
- **WARN** 33 AI crawler(s) explicitly blocked
  GPTBot, CCBot, PerplexityBot, Google-Extended, ClaudeBot, meta-externalagent, Bytespider, PetalBot, Devin, omgili, AI2Bot, PanguBot, MistralAI-User, Diffbot, DuckAssistBot, Ai2Bot-Dolma, Google-CloudVertexBot, meta-externalfetcher, YouBot, Claude-User, Claude-SearchBot, Perplexity-User, ChatGPT-User, OAI-SearchBot, Timpibot, DeepSeekBot, ImagesiftBot, Kangaroo Bot, Manus-User, meta-webindexer, PhindBot, TavilyBot, webzio-extended
  These crawlers have "Disallow: /" rules. If you want AI agents to access your site, change to "Allow: /" for each blocked crawler.
  https://axrush.com/guides/robots-txt#explicitly-blocked
- **WARN** 8 assistant search crawler(s) blocked — your site cannot be cited by those assistants
  PerplexityBot — Blocking it removes your site from Perplexity answers and citations. Not used for model training.
PetalBot — search index crawler
DuckAssistBot — Fetches pages in real time for DuckDuckGo AI answers. No training use.
YouBot — Indexes pages for You.com search and its LLM answers.
Claude-SearchBot — Blocking it removes your site from the index Claude cites when it searches the web.
OAI-SearchBot — Blocking it removes your site from ChatGPT search answers and citations.
meta-webindexer — Blocking it removes your site from Meta AI search results and citations.
PhindBot — search index crawler
  Search crawlers build the index an assistant cites from; they are separate from the training crawlers. If the intent was to opt out of training only, allow these and block the training tokens instead.
  https://axrush.com/guides/robots-txt#blocked-search-crawlers
- **PASS** 17 training crawler(s) blocked — recorded as a deliberate policy choice
  GPTBot, CCBot, Google-Extended, ClaudeBot, meta-externalagent, Bytespider, omgili, AI2Bot, PanguBot, Diffbot, Ai2Bot-Dolma, Google-CloudVertexBot, Timpibot, DeepSeekBot, ImagesiftBot, Kangaroo Bot, webzio-extended
- **WARN** 3 user-triggered fetcher(s) blocked in robots.txt that may ignore it
  meta-externalfetcher — documented as possibly ignoring robots.txt
Perplexity-User — documented as possibly ignoring robots.txt
ChatGPT-User — Since December 2025 OpenAI documents that robots.txt rules may not apply to this user-triggered fetcher.
  These clients fetch a page because a person asked for that URL, and their vendors document that robots.txt may not apply. Enforce at the edge if the block must hold.
  https://axrush.com/guides/robots-txt#blocked-user-fetchers
- **WARN** 5 robots.txt rule(s) target a retired or non-existent crawler token
  GoogleAgent-Mariner — Project Mariner was discontinued on 2026-05-04; superseded by Google-Agent.
Google-NotebookLM — Renamed to Google-GeminiNotebook on 2026-07-17.
cohere-ai — Cohere states it operates no web crawlers.
Claude-Web — Never documented by Anthropic and absent from its current crawler page. Use ClaudeBot.
cohere-training-data-crawler — Cohere states it operates no web crawlers.
  These rules have no effect. Remove them so the file reflects your actual policy.
  https://axrush.com/guides/robots-txt#legacy-tokens
- **WARN** No Sitemap directive found
  Add a Sitemap directive to your robots.txt: Sitemap: https://your-site.com/sitemap.xml
  https://axrush.com/guides/robots-txt#missing-sitemap
- **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
- **PASS** 33/57 known AI crawlers have explicit rules

#### Meta Tags — 41/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
- **WARN** OpenGraph required tags missing: og:title, og:url, og:type
  Add these meta tags: <meta property="og:title" content="...">, <meta property="og:url" content="...">, <meta property="og:type" content="...">.
  https://axrush.com/guides/meta-tags#og-required-missing
- **WARN** Twitter Card required tags missing: twitter:card, twitter:title, twitter:description
  Add these meta tags: <meta name="twitter:card" content="...">, <meta name="twitter:title" content="...">, <meta name="twitter:description" content="...">.
  https://axrush.com/guides/meta-tags#twitter-required-missing

#### Sitemap — 0/100

- **FAIL** No sitemap found
  Tried robots.txt Sitemap: directive and /sitemap.xml
  Publish an XML sitemap at /sitemap.xml and reference it from robots.txt with: Sitemap: https://your-site.com/sitemap.xml
  https://axrush.com/guides/sitemap#not-found

#### HTTP Headers — 85/100

- **PASS** 6/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 — 100/100 (informe, ne note pas)

- **WARN** 2 form(s) on the page, none declared as agent tools
  WebMCP is a W3C Community Group draft in a Chrome origin trial. It is not a standard and adoption is minimal, so this is a forward-looking note, not a defect.
  A declared form is called by an agent rather than driven pixel by pixel. Add toolname and tooldescription to the forms worth automating — search, filter, subscribe — and toolparamdescription to each field.
  https://axrush.com/guides/webmcp#no-annotations

#### Découverte commerce — 0/100 (informe, ne note pas)

- **WARN** Site sells something but publishes no agent-readable commerce profile
  Commerce signals found: links to a cart or checkout. Checked /.well-known/ucp, /.well-known/ucp.json.
  Publish a Universal Commerce Protocol profile at /.well-known/ucp so an agent can find your catalog, cart and checkout without a human. Note that the alternatives are not discoverable by design: the OpenAI and Stripe Agentic Commerce Protocol defines no manifest, and AP2 advertises itself through an A2A card extension.
  https://axrush.com/guides/commerce-discovery#not-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 — 43/100

#### Security.txt — 75/100

- **PASS** /.well-known/security.txt exists
- **PASS** Required field "Contact" present
- **FAIL** Required field "Expires" missing (RFC 9116)
  Add "Expires:" to your security.txt. Use an ISO 8601 date, e.g., Expires: 2026-12-31T23:59:59.000Z
  https://axrush.com/guides/security-txt#missing-field
- **PASS** 2/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/amazon.com
