Is termly.io agent ready?
termly.io is partly agent ready: it scores 59/100 (grade C) on the w2agent rubric.
Changed since last check
−6 points since the previous check (2026-09-15)
Regressed: llms.txt exists
Changed: Response time (partial → fail)
Files removed: llms.txt
Category scores
Category breakdown not recorded for this audit.
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryPresent
- MCP discoveryNot found
- llms.txt validityNot measured
Check results
Bot Accessibility
- ✓No error status codespass
- ✗Response timefail
- ✓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 tagspass
- ✓Semantic HTML elementspass
- ✓Appropriate Schema.org typepass
- ~JSON-LD validpartial
- ~Heading hierarchypartial
- ✓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 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 supportpass
- ✓Public API surfacepass
- —Client ID Metadata Documents (bonus)skip
- ✗OpenAPI specificationfail
- ✗Agent/bot auth documentationfail
- ~OAuth discovery chain (RFC 9728 → RFC 8414)partial
- ✓Developer portalpass
- ✗Scoped API permissionsfail
- ✗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 headerspartial
Other
- —ecommerce-gtin-validskip
- ✓wp-page-builder-souppass
- ✗wp-rest-api-accessiblefail
- —ecommerce-product-schemaskip
- ✓wp-security-blocking-botspass
- ✓wp-robots-default-blockingpass
- ✓ecommerce-checkout-accessiblepass
Score history
- 59/100 · rubric v3.0
- 65/100 · rubric v3.0
- 61/100 · rubric v2.0
- 61/100 · rubric v2.0
- 60/100 · rubric v2.0
- 59/100 · rubric v2.0
- 54/100 · rubric v2.0
- 55/100 · rubric v2.0
- 55/100 · rubric v2.0
- 54/100 · rubric v2.0
- 54/100 · rubric v2.0
- 55/100 · rubric v2.0