Is getmaxim.ai agent ready?

getmaxim.ai is not yet agent ready: it scores 39/100 (grade D) on the w2agent rubric. Weakest areas: Structured Data (10), Content Quality (24), Agent Auth (33), Agent Discovery (38), Agent Protocols (42).

39/ 100
Grade: D

Last checked · Platform: nextjs

Scored Oct 14, 2026 · Rubric v3.0

Changed since last check

+3 points since the previous check (2026-09-16)

Regressed: Response time, Content negotiation (Markdown)

Changed: Answer-first content (partial → fail), Semantic HTML elements (fail → partial), Security headers (partial → fail), Heading hierarchy (fail → partial), Author attribution (fail → partial), Schema.org JSON-LD present (fail → partial)

Category scores

Technical
53
Agent Auth
33
Agent Discovery
38
Agent Protocols
42
Content Quality
24
Structured Data
10
Bot Accessibility
79

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 timefail
  • ✓XML sitemap existspass
  • ✓AI agent accesspass
  • ?Edge treatment of agent user-agentstracked, not scorederror
  • ✓robots.txt existspass
  • ✗Content negotiation (Markdown)fail
  • —Declared AI usage preferencestracked, not scoredskip

Structured Data

  • ~OpenGraph meta tagspartial
  • ~Semantic HTML elementspartial
  • ✗Appropriate Schema.org typefail
  • ✗JSON-LD validfail
  • ~Heading hierarchypartial
  • ~Schema.org JSON-LD presentpartial
  • ✗Schema.org completenessfail

Content Quality

  • ✓FAQ contentpass
  • ✗Answer-first contentfail
  • ~Content lengthpartial
  • ✓Token efficiency (HTML-to-text ratio)pass
  • ✗Freshness signalsfail
  • ~Author attributionpartial
  • ~Citation readinesspartial
  • ✗Lists and tables for structured infofail

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 endpointspass
  • ✗MCP endpointfail
  • ✗Action schemasfail
  • —/.well-known/ucpskip
  • ✗Structured formsfail
  • —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 charsetfail
  • ~Canonical URLspartial
  • ✗Mobile viewportfail
  • ~Content accessible without JSpartial
  • ✗Security headersfail

Other

  • ✗nextjs-metadata-apifail
  • ✓nextjs-static-generationpass
  • ✗nextjs-well-known-servedfail
  • —local-business-hours-jsonldskip
  • —local-business-nap-structuredskip
  • —local-business-booking-accessibleskip

Score history

  • 39/100 · rubric v3.0
  • 36/100 · rubric v3.0
  • 34/100 · rubric v3.0
  • 46/100 · rubric v2.0
  • 46/100 · rubric v2.0
  • 46/100 · rubric v2.0
  • 45/100 · rubric v2.0
  • 45/100 · rubric v2.0
  • 46/100 · rubric v2.0

Related websites

Is your own site agent ready?

Check your own site →

Re-audit getmaxim.ai