Is birkenstock.com ready for AI agents?

AI agent readiness report · platform: Salesforce · checked 2026-10-23 · log in to re-run
22%
Readiness
2/9
Verified
Salesforce
Platform
22%2/9
Not agent-ready
Mcp
Webmcp
A2a
Anp
Ucp
Ap2
Openapi
Llms Txt
Wikidata
2/18 AI crawlers reached the homepage16 blocked
Ranks above 36% of 138 sites checkedcorpus avg 24/100

Not agent-ready

birkenstock.com has 2 of 9 readable agent standards in place; missing Mcp, Webmcp, A2a, Anp, Ap2, Openapi, Llms Txt.

Assessment

2 of 9 readable agent-readiness checks verified. Detected platform: Salesforce. Our request with an ordinary browser user-agent was refused too, so the crawler results describe our checker being blocked, not rules about AI crawlers. See per-protocol drawers for evidence and fix-it files.

Per-protocol verdicts

Mcpno MCP endpoint declared in /.well-known/ucp, and none at the draft discovery addresses /.well-known/mcp.json, /.well-known/mcp or /mcp (MCP has no agreed discovery address yet)Not found
Webmcpno navigator.modelContext.register, <script type="webmcp">, or <link rel="modelcontext"> in HTMLNot found
A2ano /.well-known/agent.json or /.well-known/agent-card.jsonNot found
Anpno /.well-known/agent-descriptions and no did:wba identity at /.well-known/did.jsonNot found
Ucp/.well-known/ucp present, UCP version 2026-04-08Verified
Ap2/.well-known/ucp does not declare dev.ucp.shopping.ap2_mandateNot found
Openapino /openapi.json, /api/openapi.json, or /.well-known/openapi.jsonNot found
Llms Txtno /llms.txtNot found
WikidataWikidata entity Q648458 (Birkenstock)Verified

.well-known files

.well-known/mcp.json625886 bytes200
Mcp Well Known Alt625886 bytes200
/mcp endpoint625886 bytes200
Ai Plugin Legacy625886 bytes200
.well-known/agent.json625885 bytes200
.well-known/agent-card.json625886 bytes200
Anp Discovery625886 bytes200
Anp Did625886 bytes200
Openapi Well Known625886 bytes200
Openapi Root625886 bytes200
Openapi Api625886 bytes200
Ucp Profile722 bytes200
Llms Txt625886 bytes200
Llms Full Txt625886 bytes200
robots.txt1970 bytes200
sitemap.xmlnot found404

AI crawler audit

2 of 18 AI user-agents reached the homepage.
Our request with an ordinary browser user-agent was refused as well (HTTP 200 before, 0 after). This site was blocking our checker, so read these counts as "could not check", not as rules about AI crawlers.
9 of 18 were tested with the operator's published user-agent string and the rest with the bare token, since no published string was found. A request that only names a user-agent does not prove the real crawler would be treated the same.

What this means for birkenstock.com

On birkenstock.com (Salesforce), 2 of 9 readable agent standards are in place: Ucp, Wikidata. Missing: Mcp, Webmcp, A2a, Anp, Ap2, Openapi, Llms Txt.

Without JavaScript, your brand name still appears in the raw HTML, so crawlers that do not run JS can read it.

birkenstock.com scores higher than 36% of the 138 sites checked here so far; the average readiness score is 24/100.

Make birkenstock.com agent-ready

Start with the highest-impact gap: Mcp. Publish a working MCP endpoint at /.well-known/mcp.json (the initialize handshake must succeed, not just return 200), add an A2A agent card, and keep the crawler path clean.

Frequently asked questions

Are these real probes or AI guesses?

Real probes. We fetch the actual files, run a real MCP initialize handshake, and validate A2A cards against their schema. No model decides a verdict.

Does birkenstock.com need every standard to pass?

No. Start with the highest-impact gap above, then add the rest. Most sites win the most by shipping a working MCP endpoint and keeping the crawler path clean.

Check your own site free

Run the same protocol probes on any URL, then sign up free for the copy-paste fix-it files and the full 20-crawler audit.

Run a free check