# Préparation de mercadona.es à l'IA

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

Score 60/100, note Moyen. Mesuré 2026-09-08T16:13:10.957+00:00, moteur ax-audit@4.2.1.

## Vérifications

### Contenu — 47/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

#### 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 — 35/100

- **WARN** Sparse server-rendered content (1 words, 9 chars)
  Below thresholds: 80 words, 500 chars
  Render at least the main page content server-side. Many AI crawlers (GPTBot, ClaudeBot, CCBot) do not execute JavaScript and will see only the static HTML.
  https://axrush.com/guides/html-rendering#sparse-content
- **WARN** Low text-to-markup ratio (1.6%)
  Recommended minimum: 5% of structural markup (script/style bodies and svg interiors excluded)
  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
- **FAIL** Empty SPA mount point detected: #root
  The static HTML contains an empty SPA mount node, which means content is rendered only client-side. Enable SSR/SSG so the initial HTML response includes meaningful content.
  https://axrush.com/guides/html-rendering#empty-spa
- **PASS** Semantic landmarks present (section, footer, nav)
- **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

#### SEO Basics — 90/100

- **WARN** <title> is too short (9 chars): "Mercadona"
  Lengthen the title to 20-70 characters with a clear topic indicator.
  https://axrush.com/guides/seo-basics#short-title
- **PASS** Meta description length 122 chars
- **PASS** Canonical URL: https://www.mercadona.es/
- **PASS** <html lang="es">
- **PASS** UTF-8 charset declared
- **PASS** Viewport meta present: "width=device-width,initial-scale=1,shrink-to-fit=no"

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

- **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.

### Accès — 93/100

#### TLS / HTTPS — 87/100

- **PASS** Site is served over HTTPS
- **PASS** HTTP requests redirect to HTTPS
- **WARN** HSTS max-age is short (86400s = ~1 days)
  Use at least max-age=15768000 (~6 months); preload list submission requires max-age=31536000 (1 year).
  https://axrush.com/guides/tls-https#hsts-short
- **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 lacks the preload directive
  Add preload (and ensure max-age >= 31536000 + includeSubDomains) and submit the domain at https://hstspreload.org for browser-built-in HTTPS enforcement.
  https://axrush.com/guides/tls-https#hsts-no-preload

#### Agent Access — 100/100

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

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

- **WARN** A missing page redirects (302) instead of returning 404
  Location: https://www.mercadona.es/
  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
  302 → https://www.mercadona.es/
- **PASS** HEAD requests are supported
- **PASS** Character encoding declared in the document (not in the Content-Type header)

#### Crawl Efficiency — 70/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
- **PASS** Homepage size is reasonable (2.2 KB decompressed)
- **WARN** Roughly 2 tokens of content in 556 tokens of response (100% 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 254ms

#### Directives IA — 100/100

- **PASS** Homepage is indexable
- **PASS** notranslate declared — assistants should not offer a translated version
- **PASS** No directive restricts how AI assistants may use this page

### Découverte — 56/100

#### LLMs.txt — 60/100

- **PASS** /llms.txt exists
- **WARN** /llms.txt Content-Type is "text/html"
  Expected one of: text/plain, text/markdown
  Configure your server to serve /llms.txt as text/plain so AI agents parse it correctly.
  https://axrush.com/guides/llms-txt#wrong-content-type
- **WARN** Missing H1 heading (first line should start with "# ")
  Add an H1 heading as the first line of your llms.txt file, e.g.: # Your Site Name
  https://axrush.com/guides/llms-txt#missing-h1
- **WARN** No blockquote description found ("> ...")
  Add a blockquote description after the H1 heading, e.g.: > A brief summary of your site for AI agents.
  https://axrush.com/guides/llms-txt#missing-blockquote
- **WARN** No section headings found (## ...)
  Organize your llms.txt content with ## section headings (e.g., ## About, ## API, ## Documentation).
  https://axrush.com/guides/llms-txt#missing-sections
- **WARN** No Markdown links found
  Add Markdown links to relevant pages: [Page Title](https://example.com/page). This helps AI agents navigate your site.
  https://axrush.com/guides/llms-txt#no-links
- **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** 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 — 55/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
- **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
- **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

#### Sitemap — 20/100

- **PASS** Sitemap located: https://mercadona.es/sitemap.xml
- **FAIL** Sitemap response does not look like XML
  <!doctype html><html lang="es"><head><meta charset="UTF-8"><link rel="manifest" 
  Serve the sitemap with valid XML and Content-Type: application/xml. Confirm the file starts with <?xml ...?> and contains <urlset> or <sitemapindex>.
  https://axrush.com/guides/sitemap#not-xml

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

#### HTTP Headers — 75/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 CORS headers on .well-known resources
  Add Access-Control-Allow-Origin: * to responses from /.well-known/* so AI agents from other domains can fetch your discovery files.
  https://axrush.com/guides/http-headers#no-cors
- **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) — N/A

- **PASS** No agent-facing surface — an Agent Card does not apply to this site
  No API, MCP server or existing card was found. An Agent Card advertises capabilities another agent can invoke; a site that offers none has nothing to put in it. Run with --profile agent to audit as though it did.

#### OpenAPI Spec — N/A

- **WARN** /.well-known/api-catalog served as "text/html"
  RFC 9727 requires support for application/linkset+json.
  Serve the catalog as application/linkset+json.
  https://axrush.com/guides/api-discovery#catalog-content-type
- **PASS** No API surface — API discovery does not apply to this site
  No description, catalog, service-desc relation or developer area was found. Run with --profile api to audit as though the site offered one.

#### 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 — N/A

- **PASS** No developer-facing surface — skills do not apply to this site
  No documentation links, llms.txt, or API description found. Skills describe procedures an agent follows; a site with no procedures to teach has nothing to publish.

#### 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.

#### WebMCP — N/A

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

### Politique — 33/100

#### Security.txt — 45/100

- **PASS** /.well-known/security.txt exists
- **FAIL** Required field "Contact" missing (RFC 9116)
  Add "Contact:" to your security.txt. Use a mailto: or https: URI, e.g., Contact: mailto:security@example.com
  https://axrush.com/guides/security-txt#missing-field
- **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
- **WARN** No optional fields (Canonical, Preferred-Languages, Policy, etc.)
  Consider adding Canonical: (canonical URL), Preferred-Languages: (e.g., en), and Policy: (link to your security policy).
  https://axrush.com/guides/security-txt#missing-optional

#### 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/mercadona.es
