Is ecuabet.com agent ready?
ecuabet.com is partly agent ready: it scores 45/100 (grade C) on the w2agent rubric. Weakest areas: Agent Auth (0), Agent Discovery (27), Agent Protocols (30), Structured Data (42).
Changed since last check
+27 points since the previous check (2026-09-15)
Fixed: FAQ content, Answer-first content, No error status codes, Canonical URLs, Content length, XML sitemap exists, llms.txt exists, robots.txt exists, Lists and tables for structured info, Reachable as Google-Agent, Reachable as ChatGPT-User, Reachable as Perplexity-User
Regressed: Security headers, Heading hierarchy
Changed: OpenGraph meta tags (fail → partial), Semantic HTML elements (partial → fail), Appropriate Schema.org type (fail → partial), Schema.org JSON-LD present (fail → partial)
Files added: robots.txt, sitemap.xml, llms.txt
Category scores
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot measured
- MCP discoveryNot found
- llms.txt validityPresent
Check results
Bot Accessibility
- ✓No error status codespass
- ✓Response timepass
- ✓XML sitemap existspass
- ✓AI agent accesspass
- ✓Edge treatment of agent user-agentstracked, not scoredpass
- ✓robots.txt existspass
- ✗Content negotiation (Markdown)fail
- —Declared AI usage preferencestracked, not scoredskip
Structured Data
- ~OpenGraph meta tagspartial
- ✗Semantic HTML elementsfail
- ~Appropriate Schema.org typepartial
- ✓JSON-LD validpass
- ~Heading hierarchypartial
- ~Schema.org JSON-LD presentpartial
- ✗Schema.org completenessfail
Content Quality
- ✓FAQ contentpass
- ✓Answer-first contentpass
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✗Author attributionfail
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
Agent Discovery
- ~llms.txt follows specpartial
- ✓llms.txt existspass
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- ~llms.txt links resolvepartial
Agent Protocols
- ✗Discoverable API endpointsfail
- ✗MCP endpointfail
- ✗Action schemasfail
- —/.well-known/ucpskip
- —Structured formsskip
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ✓Reachable as Google-Agentpass
- ✓Reachable as ChatGPT-Userpass
- ✓Reachable as Perplexity-Userpass
Agent Auth
- —MCP authorization (401 challenge → protected resource metadata)skip
- —PKCE S256 supportskip
- ✗Public API surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- —Agent/bot auth documentationskip
- —OAuth discovery chain (RFC 9728 → RFC 8414)skip
- —Developer portalskip
- —Scoped API permissionsskip
- —API catalog (RFC 9727)skip
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ✓Canonical URLspass
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ~Security headerspartial
Score history
- 45/100 · rubric v3.0
- 18/100 · rubric v3.0
- 48/100 · rubric v2.0
- 48/100 · rubric v2.0
- 47/100 · rubric v2.0
- 49/100 · rubric v2.0