0
F

zara.com

This site is essentially invisible to AI agents.

Needs work (11)

agents.md Needs work

GET /agents.md returned 404

agents.md is the primary self-description file AI agents look for when deciding how to interact with a site.

Publish a markdown file at /agents.md describing your site, available actions, and machine-readable endpoints.
llms.txt Needs work

GET /llms.txt returned 404

llms.txt is the emerging convention for pointing LLMs at the most relevant content on a site.

Publish a markdown file at /llms.txt summarizing your site with links to key pages.
llms-full.txt Needs work

GET /llms-full.txt returned 404

llms-full.txt provides an extended, unabridged version of llms.txt for agents that can handle more context.

Publish a markdown file at /llms-full.txt with the full content llms.txt links to.
Content negotiation Needs work

homepage ignores Accept: text/markdown (content-type: text/html)

Agents that request text/markdown should receive a lightweight markdown response instead of full HTML.

Respond to `Accept: text/markdown` on / with a text/markdown content type and markdown body.
Structured data (JSON-LD) Needs work

no JSON-LD structured data found on homepage

JSON-LD structured data gives agents a machine-readable summary of what an organization or page is.

Add at least one valid <script type="application/ld+json"> block to your homepage describing your Organization or WebSite.
MCP server card Needs work

GET /.well-known/mcp.json returned 404

An MCP server card at a well-known location lets agents discover tool/action interfaces automatically.

Publish an MCP server descriptor at /.well-known/mcp.json describing available tools and endpoints.
.well-known/verified.md Needs work

GET /.well-known/verified.md returned 404

Publishing /.well-known/verified.md is the strongest first-party signal that a site actively participates in agent-readiness self-attestation.

Publish a markdown file at /.well-known/verified.md describing your entity for verified.md self-verification.
x402 payments (experimental) Needs work

no x402 signals detected (probed /api paths, headers, agents.md)

x402 is an emerging standard for agent-native micropayments over HTTP 402. Early support signals forward-looking infrastructure.

Consider returning 402 Payment Required with X-Payment headers on metered API routes, or mention x402 support in agents.md.
HTTPS + redirect Needs work

HTTPS reachable but HTTP does not redirect to HTTPS

Agents should reach the site over HTTPS, and plain HTTP should redirect there so credentials and payloads are never sent in the clear.

Serve the site over HTTPS and configure HTTP to redirect (301/308) to the HTTPS URL.
Meta hygiene Needs work

homepage missing: meta description, OG tags

Title, meta description, and Open Graph tags give agents (and the humans they act for) a reliable summary of the page.

Add a <title>, <meta name="description">, and og:title/og:description tags to your homepage.
Content readability Needs work

text-to-markup ratio 0.3% (threshold 2%)

If the homepage is almost entirely markup/script with little extractable text, agents that don't execute JS see an empty page.

Server-render meaningful text content, or provide a markdown/text alternative agents can read without executing JavaScript.

Passed (3)

robots.txt AI access Pass

robots.txt does not block crawlers; no explicit AI-crawler directives found

robots.txt controls whether AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) can access your site at all.

sitemap.xml Pass

sitemap referenced from robots.txt: https://www.zara.com/sitemaps/sitemap-index.xml.gz

A sitemap helps agents discover the full set of pages worth crawling or indexing.

Bot access Pass

homepage accessible to scanner user agent

If the homepage returns a 403 or a challenge page to a scanner-style user agent, real agents likely get blocked too.

What this means for zara.com

  • AI assistants answering questions in your category cannot read how zara.com wants to be used, so they cite competitors who declare themselves.
  • Assistants that look for a plain-language summary of zara.com find nothing, so what they say about you is guesswork assembled from third-party pages.
  • Agents that want your full content in one clean file have to crawl page by page instead, and most give up early.
  • Agents that ask for a clean text version of your pages get raw HTML instead, burning their limited attention on your navigation and scripts.
  • Agents cannot reliably extract what zara.com offers, so they describe you vaguely or not at all.
  • Agents can read zara.com but cannot interact with it. To them you are a brochure, not a service.
  • Nothing proves zara.com is who it says it is, so an agent has no way to tell you apart from an impersonator.
  • Agents that can pay for content and services have no way to pay you.
  • Without clean TLS, most agents will refuse the connection outright.
  • Assistants describing zara.com rely on your titles and descriptions. Right now those are missing or malformed, so they improvise.
  • Key content on zara.com only appears after JavaScript runs. Most agents do not run it. To them those pages are blank.

Make zara.com agent ready

Displace implements every failing check above and re-verifies monthly. Beta rate EUR 990 flat (list EUR 1,900), first 10 sites only, includes the first 3 months of certification.

Or email hello@verified.md.