Is emlakjet.com agent ready?

emlakjet.com is partly agent ready: it scores 56/100 (grade C) on the w2agent rubric. Weakest areas: Agent Auth (20), Agent Protocols (25), Agent Discovery (38).

56/ 100
Grade: C

Last checked · Platform: nextjs

Scored Oct 14, 2026 · Rubric v3.0

Changed since last check

+38 points since the previous check (2026-09-15)

Fixed: Public API surface, FAQ content, Answer-first content, OpenGraph meta tags, No error status codes, Semantic HTML elements, Canonical URLs, Content length, llms.txt exists, Appropriate Schema.org type, Security headers, robots.txt exists, Lists and tables for structured info, Reachable as Google-Agent, Reachable as ChatGPT-User, Reachable as Perplexity-User

Regressed: Response time

Changed: Freshness signals (fail → partial), Schema.org JSON-LD present (fail → partial), Schema.org completeness (fail → partial)

Files added: robots.txt, llms.txt

Category scores

Technical
99
Agent Auth
20
Agent Discovery
38
Agent Protocols
25
Content Quality
81
Structured Data
83
Bot Accessibility
62

Agent protocol panel

  • A2A agent cardNot found
  • OAuth discoveryNot found
  • MCP discoveryNot found
  • llms.txt validityPresent

Check results

Bot Accessibility

  • ✓No error status codespass
  • ~Response timepartial
  • ✗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 hierarchypass
  • ~Schema.org JSON-LD presentpartial
  • ~Schema.org completenesspartial

Content Quality

  • ✓FAQ contentpass
  • ✓Answer-first contentpass
  • ✓Content lengthpass
  • ✓Token efficiency (HTML-to-text ratio)pass
  • ~Freshness signalspartial
  • ✗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 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 supportskip
  • ✓Public API surfacepass
  • —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

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

Score history

  • 56/100 · rubric v3.0
  • 18/100 · rubric v3.0
  • 44/100 · rubric v2.0
  • 44/100 · rubric v2.0
  • 44/100 · rubric v2.0

Related websites