Is salomon.com ready for AI agents?

AI agent readiness report · platform: Unknown · checked 2026-10-24 · log in to re-run
17%
Readiness
1/6
Verified (readable)
Unknown
Platform
17%1/6
Not agent-ready
Mcp
Webmcp
A2a
Anp
Ucp
Ap2
Openapi
Llms Txt
Wikidata
1/18 AI crawlers reached the homepage17 blocked
Ranks above 37% of 171 sites checkedcorpus avg 24/100

Not agent-ready

salomon.com has 1 of 6 readable agent standards in place; missing A2a, Anp, Ucp, Ap2, Openapi. 3 could not be read because the site refused our request (Mcp, Webmcp, Llms Txt), so they are not counted.

Assessment

1 of 6 readable agent-readiness checks verified (3 could not be read: the site refused our request). 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

Mcpcould not read /mcp (403) - the site refused our request, so this is not a findingCould not read
Webmcpcould not read the homepage HTML, so page-source markers could not be checkedCould not read
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
Ucpno /.well-known/ucpNot found
Ap2no /.well-known/ucp, so no AP2 declaration (AP2 is declared as a UCP capability)Not found
Openapino /openapi.json, /api/openapi.json, or /.well-known/openapi.jsonNot found
Llms Txtcould not read /llms.txt (403) - the site refused our request, so this is not a findingCould not read
WikidataWikidata entity Q2120822 (Salomon)Verified

.well-known files

.well-known/mcp.jsonnot found404
Mcp Well Known Altnot found404
/mcp endpointcould not read403
Ai Plugin Legacynot found404
.well-known/agent.jsonnot found404
.well-known/agent-card.jsonnot found404
Anp Discoverynot found404
Anp Didnot found404
Openapi Well Knownnot found404
Openapi Rootnot found404
Openapi Apinot found404
Ucp Profilenot found404
Llms Txtcould not read403
Llms Full Txtcould not read403
robots.txt2124 bytes200
sitemap.xml4044 bytes200

AI crawler audit

1 of 18 AI user-agents reached the homepage.
Our request with an ordinary browser user-agent was refused as well (HTTP 403 before, 403 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 salomon.com

On salomon.com (Unknown), 1 of 6 readable agent standards are in place: Wikidata. Missing: A2a, Anp, Ucp, Ap2, Openapi.

Without JavaScript, your brand name does not appear in the raw HTML, so crawlers that do not run JS see an empty shell.

salomon.com scores higher than 37% of the 171 sites checked here so far; the average readiness score is 24/100.

Make salomon.com agent-ready

Start with the highest-impact gap: A2a. 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 salomon.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