Is brandefense.io agent ready?
brandefense.io is largely agent ready: it scores 61/100 (grade B) on the w2agent rubric. Weakest areas: Agent Protocols (25), Agent Auth (33), Agent Discovery (47).
Changed since last check
+4 points since the previous check (2026-09-16)
Fixed: OpenGraph meta tags, XML sitemap exists
Regressed: MCP endpoint
Changed: Appropriate Schema.org type (fail → partial), JSON-LD valid (fail → partial)
Files added: sitemap.xml
Category scores
Technical
100
Agent Auth
33
Agent Discovery
47
Agent Protocols
25
Content Quality
86
Structured Data
54
Bot Accessibility
97
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 scorederror
- ✓robots.txt existspass
- ✓Content negotiation (Markdown)pass
- ✓Declared AI usage preferencestracked, not scoredpass
Structured Data
- ✓OpenGraph meta tagspass
- ~Semantic HTML elementspartial
- ~Appropriate Schema.org typepartial
- ~JSON-LD validpartial
- ✗Heading hierarchyfail
- ✓Schema.org JSON-LD presentpass
- ✗Schema.org completenessfail
Content Quality
- ✓FAQ contentpass
- ✓Answer-first contentpass
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ✓Freshness signalspass
- ✗Author attributionfail
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
Agent Discovery
- ✓llms.txt follows specpass
- ✓llms.txt existspass
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- ✓llms.txt links resolvepass
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 supportfail
- ✗Public API surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- ~Agent/bot auth documentationpartial
- —OAuth discovery chain (RFC 9728 → RFC 8414)skip
- ✓Developer portalpass
- ✗Scoped API permissionsfail
- —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 headerspass
Other
- ✓wp-page-builder-souppass
- ✗wp-rest-api-accessiblefail
- ✓wp-security-blocking-botspass
- ✓wp-robots-default-blockingpass
Score history
- 61/100 · rubric v3.0
- 57/100 · rubric v3.0
- 57/100 · rubric v3.0
- 53/100 · rubric v2.0
- 53/100 · rubric v2.0
- 53/100 · rubric v2.0
- 52/100 · rubric v2.0
- 52/100 · rubric v2.0
- 53/100 · rubric v2.0