Is examiner.com agent ready?

examiner.com is partly agent ready: it scores 49/100 (grade C) on the w2agent rubric. Weakest areas: Agent Discovery (0), Agent Auth (22), Agent Protocols (27), Structured Data (46).

49/ 100
Grade: C

Last checked · Platform: wordpress

Scored Oct 14, 2026 · Rubric v3.0

Changed since last check

−2 points since the previous check (2026-09-16)

Regressed: Response time

Category scores

Technical
90
Agent Auth
22
Agent Discovery
0
Agent Protocols
27
Content Quality
88
Structured Data
46
Bot Accessibility
83

Agent protocol panel

  • A2A agent cardNot found
  • OAuth discoveryNot measured
  • 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 scoredfail
  • ✓robots.txt existspass
  • ✗Content negotiation (Markdown)fail
  • —Declared AI usage preferencestracked, not scoredskip

Structured Data

  • ✓OpenGraph meta tagspass
  • ~Semantic HTML elementspartial
  • ✗Appropriate Schema.org typefail
  • ✗JSON-LD validfail
  • ~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 signalspass
  • ✗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 formsfail
  • —WebMCP imperative APItracked, not scoredskip
  • —WebMCP declarative APItracked, not scoredskip
  • ✗Reachable as Google-Agentfail
  • ✓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 documentationfail
  • —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 headerspartial

Other

  • —ecommerce-gtin-validskip
  • ✓wp-page-builder-souppass
  • ✓wp-rest-api-accessiblepass
  • —ecommerce-product-schemaskip
  • ✓wp-security-blocking-botspass
  • ✓wp-robots-default-blockingpass
  • —ecommerce-checkout-accessibleskip

Score history

  • 49/100 · rubric v3.0
  • 51/100 · rubric v3.0
  • 50/100 · rubric v3.0
  • 48/100 · rubric v2.0
  • 48/100 · rubric v2.0
  • 48/100 · rubric v2.0
  • 48/100 · rubric v2.0
  • 48/100 · rubric v2.0
  • 47/100 · rubric v2.0

Related websites