Is ugg.com ready for AI agents?

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

Not agent-ready

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

Assessment

1 of 8 readable agent-readiness checks verified (1 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

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
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 Txtno /llms.txtNot found
WikidataWikidata entity Q1138480 (UGG)Verified

.well-known files

.well-known/mcp.jsonnot found410
Mcp Well Known Altnot found410
/mcp endpointnot found410
Ai Plugin Legacynot found410
.well-known/agent.jsonnot found410
.well-known/agent-card.jsonnot found410
Anp Discoverynot found410
Anp Didnot found410
Openapi Well Knownnot found410
Openapi Rootnot found410
Openapi Apinot found410
Ucp Profilenot found410
Llms Txtnot found410
Llms Full Txtnot found410
robots.txt12731 bytes200
sitemap.xmlcould not read403

AI crawler audit

0 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 ugg.com

On ugg.com (Unknown), 1 of 8 readable agent standards are in place: Wikidata. Missing: Mcp, A2a, Anp, Ucp, Ap2, Openapi, Llms Txt.

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

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

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

Related: Check another site · AI Crawler Access Checker · Structured Data Tester.