Is vans.com ready for AI agents?

AI agent readiness report · platform: Custom · checked 2026-10-15 · log in to re-run
20%
Readiness
1/5
Verified (readable)
Custom
Platform
20%1/5
Not agent-ready
Mcp
Webmcp
A2a
Anp
Ucp
Ap2
Openapi
Llms Txt
Wikidata
0/20 AI crawlers reached the homepage20 blocked
Ranks above 29% of 116 sites checkedcorpus avg 25/100

Not agent-ready

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

Assessment

1 of 5 readable agent-readiness checks verified (4 could not be read: the site refused our request). 20 AI crawler(s) blocked at the edge despite robots.txt allowing them. 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/did.jsonNot found
Ucpno /.well-known/agentic-commerce.json (and platform is not a UCP-shipping host)Not found
Ap2no /.well-known/ap2.jsonNot found
Openapicould not read /openapi.json (403), /api/openapi.json (403) - the site refused our request, so this is not a findingCould not read
Llms Txtcould not read /llms.txt (403) - the site refused our request, so this is not a findingCould not read
WikidataWikidata entity Q1135366 (Vans)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 Didnot found404
Openapi Well Knownnot found404
Openapi Rootcould not read403
Openapi Apicould not read403
Ucp Well Knownnot found404
Ap2 Well Knownnot found404
Llms Txtcould not read403
Llms Full Txtcould not read403
robots.txt705 bytes200
sitemap.xmlcould not read403

AI crawler audit

0 of 20 AI user-agents reached the homepage; 20 returned an error to a request carrying their user-agent string although robots.txt allows it.
GPTBotHTTP 403Blocked
OAI-SearchBotHTTP 403Blocked
ChatGPT-UserHTTP 403Blocked
anthropic-aiHTTP 403Blocked
ClaudeBotHTTP 403Blocked
Claude-UserHTTP 403Blocked
Claude-SearchBotHTTP 403Blocked
PerplexityBotHTTP 403Blocked

What this means for vans.com

On vans.com (Custom), 1 of 5 readable agent standards are in place: Wikidata. Missing: A2a, Anp, Ucp, Ap2.

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

vans.com scores higher than 29% of the 116 sites checked here so far; the average readiness score is 25/100.

Make vans.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 vans.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

Agent readiness on Custom

We have checked 50 other sites on Custom. The Custom hub aggregates protocol verification rates and average readiness scores across every Custom site checked here.

Is Custom ready for AI agents?