Is dandomain.dk agent ready?
dandomain.dk is not yet agent ready: it scores 45/100 (grade D) on the w2agent rubric. Weakest areas: Agent Discovery (0), Agent Auth (10), Agent Protocols (37), Content Quality (45).
Changed since last check
+11 points since the previous check (2026-09-16)
Fixed: FAQ content, OpenGraph meta tags, Semantic HTML elements, Canonical URLs, Content length, Structured forms, Content accessible without JS, Citation readiness, Lists and tables for structured info
Regressed: Response time
Changed: Token efficiency (HTML-to-text ratio) (fail → partial)
Category scores
Technical
100
Agent Auth
10
Agent Discovery
0
Agent Protocols
37
Content Quality
45
Structured Data
85
Bot Accessibility
57
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot found
- MCP discoveryNot found
- llms.txt validityNot measured
Check results
Bot Accessibility
- ✓No error status codespass
- ✗Response timefail
- ✗XML sitemap existsfail
- ✓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 tagspass
- ✓Semantic HTML elementspass
- ✓Appropriate Schema.org typepass
- ✓JSON-LD validpass
- ~Heading hierarchypartial
- ✓Schema.org JSON-LD presentpass
- ~Schema.org completenesspartial
Content Quality
- ✓FAQ contentpass
- ✗Answer-first contentfail
- ✓Content lengthpass
- ~Token efficiency (HTML-to-text ratio)partial
- ✗Freshness signalsfail
- ✗Author attributionfail
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
Agent Discovery
- —llms.txt follows specskip
- ✗llms.txt existsfail
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- —llms.txt links resolveskip
Agent Protocols
- ✗Discoverable API endpointsfail
- ✗MCP endpointfail
- ✗Action schemasfail
- ✗/.well-known/ucpfail
- ✓Structured formspass
- —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 surfacepartial
- —Client ID Metadata Documents (bonus)skip
- ✗OpenAPI specificationfail
- —Agent/bot auth documentationskip
- ✗OAuth discovery chain (RFC 9728 → RFC 8414)fail
- ✗Developer portalfail
- —Scoped API permissionsskip
- ✗API catalog (RFC 9727)fail
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ✓Canonical URLspass
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ✓Security headerspass
Other
- —ecommerce-gtin-validskip
- —ecommerce-product-schemaskip
- —ecommerce-checkout-accessibleskip
Score history
- 45/100 · rubric v3.0
- 34/100 · rubric v3.0
- 34/100 · rubric v3.0
- 42/100 · rubric v2.0
- 42/100 · rubric v2.0
- 42/100 · rubric v2.0
- 42/100 · rubric v2.0