Rescan Report
Share Report
Copy Report Link
Rescan Report
Share Report
Copy Report Link
Export Report
45/100

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability31%Agent Easeof Use4%Security& Trust40%GEO, AIO, AEO77%SEO100%Performance& Accessibility60%
  • AI Discoverability 31 out of 100
  • Agent Ease of Use 4 out of 100
  • Security & Trust 40 out of 100
  • GEO, AIO and AEO 77 out of 100
  • SEO 100 out of 100
  • Performance and Accessibility 60 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

BuyrSide | Property Sourcer For Buyers

BuyrSide is a property sourcer that works in favor of property buyers. Source, filter, verify, and secure better property opportunities.

Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
31
Priority fix6170View details
Discoverability
67
Needs work540View details
Content Readiness
17
Priority fix190View details
Bot Access Control
0
Priority fix040View details
Agent Ease of Use
4
Priority fix11202View details
API
0
Priority fix060View details
Auth
Not Applicable
Not Applicable700
MCP
13
Priority fix062View details
Skill Discovery
0
Priority fix080View details
Agent Commerce
Not Applicable
Not Applicable400
GEO, AIO and AEO
77
Mostly ready5212View details
GEO Readiness
88
Mostly ready104
AIO Readiness
79
Mostly ready313View details
AEO Readiness
64
Needs work115View details
SEO
100
Strong1100
SEO
100
Strong1100
Security & Trust
40
Priority fix630View details
Security & Trust
40
Priority fix230View details
AI Training Exposure
Not Applicable
Not Applicable400
Performance and Accessibility
60
Needs work2240View details
Performance
42
Priority fix1130View details
Accessibility
92
Strong1110View details

Prioritized recommendations

Issues ranked by score impact

42 items need attention

Agent Ease of UseAPIEstablished

API Catalog

API Catalog failed at "Fetch API catalog".

50 Fail

Needs attention

API Catalog

Failed check
01

Issue

The API catalog endpoint did not return HTTP 2xx.

02

Why it matters

API catalogs help agents find service descriptions, documentation, and status resources without guessing API entry points.

Check name

API Catalog

Score

0/100

Status

fail

Category

API

Maturity

Established

Goal

Publish an API catalog for automated API discovery using RFC 9727.

Result

API Catalog failed at "Fetch API catalog".

Validation steps

  1. Fetch API catalog

    The API catalog endpoint did not return HTTP 2xx.

  2. Validate RFC 9727 linkset

    Response is not valid JSON.

  3. Fetch advertised API catalog targets

    API Catalog did not expose any same-origin hrefs to validate.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch API catalog",
      "status": "fail",
      "evidence": {
        "statusCode": 404,
        "contentType": "text/html; charset=utf-8"
      },
      "issue": "The API catalog endpoint did not return HTTP 2xx.",
      "howToFix": "Publish /.well-known/api-catalog."
    },
    {
      "id": "validate",
      "title": "Validate RFC 9727 linkset",
      "status": "fail",
      "evidence": {
        "valid": false,
        "compatibleContentType": false,
        "issue": "Response is not valid JSON.",
        "rawExcerpt": "<!DOCTYPE html><html lang=\"en\" class=\"inter_7e838cde-module__DzEfXW__variable manrope_c74ae919-module__GlRqrq__variable\"><head><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><link rel=\"stylesheet\" href=\"/_next/static/chunks/0ddz_nathaknr.css\" data-precedence=\"next\"/><link rel=\"preload\" as=\"script\" fetchPriority=\"low\" href=\"/_next/static/chunks/0lclmgfn-n7l1.js\"/><script src=\"/_next/static/chunks/0pqt~8bl3ukh4.js\" async=\"\"></script><script src=\"/_next/static/chunks/10~x95jhs6ns3.js\" async=\"\"></script><script src=\"/_next/static/chunks/062hzijh369a_.js\" async=\"\"></script><script src=\"/_next/static/chunks/turbopack-09ycf6y7jk0qn.js\" async=\"\"></script><script src=\"/_next/static/chunks/0m6_ecmhgjm_j.js\" async=\"\"></script><script src=\"/_next/static/chu"
      },
      "issue": "Response is not valid JSON.",
      "howToFix": "Use application/linkset+json with service-desc, service-doc, and status relations that each include href."
    },
    {
      "id": "target-validation",
      "title": "Fetch advertised API catalog targets",
      "status": "fail",
      "evidence": {
        "checked": [],
        "failures": [
          {
            "reason": "No same-origin API catalog hrefs were available to fetch."
          }
        ]
      },
      "issue": "API Catalog did not expose any same-origin hrefs to validate.",
      "howToFix": "Make each same-origin API catalog href reachable and serve the advertised media type."
    }
  ]
}

AI DiscoverabilityDiscoverabilityEstablished

High-value schema types

High-value schema types is missing or incomplete.

50 Fail

Needs attention

High-value schema types

Failed check
01

Issue

No high-value schema types (e.g. Article, Product, Service) were found.

02

Why it matters

High-value schema types tell agents whether a page is an article, product, event, service, or other actionable content type.

Check name

High-value schema types

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Use schema types that describe the page's primary content or offering.

Result

High-value schema types is missing or incomplete.

Evidence
{
  "found": [],
  "expected": [
    "Article",
    "BlogPosting",
    "NewsArticle",
    "Product",
    "SoftwareApplication",
    "FAQPage",
    "LocalBusiness",
    "VideoObject",
    "HowTo",
    "Event",
    "Course",
    "Review",
    "Service"
  ],
  "allTypes": [
    "Organization"
  ]
}

AI DiscoverabilityDiscoverabilityEstablished

Link headers

Link headers failed at "Find useful Link headers".

50 Fail

Needs attention

Link headers

Failed check
01

Issue

No useful agent discovery Link headers were found.

02

Why it matters

Link headers let automated clients discover API catalogs, documentation, and machine-readable alternates without parsing page markup first.

Check name

Link headers

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Include Link response headers for agent discovery using RFC 8288.

Result

Link headers failed at "Find useful Link headers".

Validation steps

  1. Find useful Link headers

    No useful agent discovery Link headers were found.

  2. Fetch same-origin Link header targets

    Link headers did not expose any same-origin targets to validate.

Evidence
{
  "failedStep": "presence",
  "steps": [
    {
      "id": "presence",
      "title": "Find useful Link headers",
      "status": "fail",
      "evidence": {
        "links": []
      },
      "issue": "No useful agent discovery Link headers were found.",
      "howToFix": "Expose useful Link headers such as rel=\"api-catalog\", rel=\"service-doc\", and rel=\"service-desc\"."
    },
    {
      "id": "target-validation",
      "title": "Fetch same-origin Link header targets",
      "status": "fail",
      "evidence": {
        "checked": [],
        "failures": [
          {
            "reason": "No same-origin Link header targets were available to fetch."
          }
        ]
      },
      "issue": "Link headers did not expose any same-origin targets to validate.",
      "howToFix": "Make each same-origin Link href reachable and serve the advertised media type."
    }
  ]
}

Agent Ease of UseAPIEstablished

OpenAPI discovery

OpenAPI discovery failed at "Find valid OpenAPI document".

50 Fail

Needs attention

OpenAPI discovery

Failed check
01

Issue

OpenAPI YAML document did not match the expected shape. Content-Type "text/html; charset=utf-8" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.

02

Why it matters

OpenAPI documents let agents understand available operations, schemas, authentication, and request formats before calling an API.

Check name

OpenAPI discovery

Score

0/100

Status

fail

Category

API

Maturity

Established

Goal

Publish a valid OpenAPI or Swagger document for API discovery.

Result

OpenAPI discovery failed at "Find valid OpenAPI document".

Validation steps

  1. Find valid OpenAPI document

    OpenAPI YAML document did not match the expected shape. Content-Type "text/html; charset=utf-8" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Find valid OpenAPI document",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/openapi.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en\" class=\"inter_7e838cde-module__DzEfXW__variable manrope_c74ae919-module__GlRqrq__variable\"><head><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><link rel=\"stylesheet\" href=\"/_next/static/chunks/0ddz_nathaknr.css\" data-precedence=\"next\"/><link rel=\"preload\" as=\"script\" fetchPriority=\"low\" href=\"/_next/static/chunks/0lclmgfn-n7l1.js\"/><script src=\"/_next/static/chunks/0pqt~8bl3ukh4.js\" async=\"\"></script><script src=\"/_next/static/chunks/10~x95jhs6ns3.js\" async=\"\"></script><script src=\"/_next/static/chunks/062hzijh369a_.js\" async=\"\"></script><script src=\"/_next/static/chunks/turbopack-09ycf6y7jk0qn.js\" async=\"\"></script><script src=\"/_next/static/chunks/0m6_ecmhgjm_j.js\" async=\"\"></script><script src=\"/_next/static/chu"
          },
          {
            "path": "/openapi.yaml",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en\" class=\"inter_7e838cde-module__DzEfXW__variable manrope_c74ae919-module__GlRqrq__variable\"><head><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><link rel=\"stylesheet\" href=\"/_next/static/chunks/0ddz_nathaknr.css\" data-precedence=\"next\"/><link rel=\"preload\" as=\"script\" fetchPriority=\"low\" href=\"/_next/static/chunks/0lclmgfn-n7l1.js\"/><script src=\"/_next/static/chunks/0pqt~8bl3ukh4.js\" async=\"\"></script><script src=\"/_next/static/chunks/10~x95jhs6ns3.js\" async=\"\"></script><script src=\"/_next/static/chunks/062hzijh369a_.js\" async=\"\"></script><script src=\"/_next/static/chunks/turbopack-09ycf6y7jk0qn.js\" async=\"\"></script><script src=\"/_next/static/chunks/0m6_ecmhgjm_j.js\" async=\"\"></script><script src=\"/_next/static/chu"
          },
          {
            "path": "/swagger.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en\" class=\"inter_7e838cde-module__DzEfXW__variable manrope_c74ae919-module__GlRqrq__variable\"><head><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><link rel=\"stylesheet\" href=\"/_next/static/chunks/0ddz_nathaknr.css\" data-precedence=\"next\"/><link rel=\"preload\" as=\"script\" fetchPriority=\"low\" href=\"/_next/static/chunks/0lclmgfn-n7l1.js\"/><script src=\"/_next/static/chunks/0pqt~8bl3ukh4.js\" async=\"\"></script><script src=\"/_next/static/chunks/10~x95jhs6ns3.js\" async=\"\"></script><script src=\"/_next/static/chunks/062hzijh369a_.js\" async=\"\"></script><script src=\"/_next/static/chunks/turbopack-09ycf6y7jk0qn.js\" async=\"\"></script><script src=\"/_next/static/chunks/0m6_ecmhgjm_j.js\" async=\"\"></script><script src=\"/_next/static/chu"
          },
          {
            "path": "/swagger.yaml",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en\" class=\"inter_7e838cde-module__DzEfXW__variable manrope_c74ae919-module__GlRqrq__variable\"><head><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><link rel=\"stylesheet\" href=\"/_next/static/chunks/0ddz_nathaknr.css\" data-precedence=\"next\"/><link rel=\"preload\" as=\"script\" fetchPriority=\"low\" href=\"/_next/static/chunks/0lclmgfn-n7l1.js\"/><script src=\"/_next/static/chunks/0pqt~8bl3ukh4.js\" async=\"\"></script><script src=\"/_next/static/chunks/10~x95jhs6ns3.js\" async=\"\"></script><script src=\"/_next/static/chunks/062hzijh369a_.js\" async=\"\"></script><script src=\"/_next/static/chunks/turbopack-09ycf6y7jk0qn.js\" async=\"\"></script><script src=\"/_next/static/chunks/0m6_ecmhgjm_j.js\" async=\"\"></script><script src=\"/_next/static/chu"
          },
          {
            "path": "/api/openapi.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en\" class=\"inter_7e838cde-module__DzEfXW__variable manrope_c74ae919-module__GlRqrq__variable\"><head><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><link rel=\"stylesheet\" href=\"/_next/static/chunks/0ddz_nathaknr.css\" data-precedence=\"next\"/><link rel=\"preload\" as=\"script\" fetchPriority=\"low\" href=\"/_next/static/chunks/0lclmgfn-n7l1.js\"/><script src=\"/_next/static/chunks/0pqt~8bl3ukh4.js\" async=\"\"></script><script src=\"/_next/static/chunks/10~x95jhs6ns3.js\" async=\"\"></script><script src=\"/_next/static/chunks/062hzijh369a_.js\" async=\"\"></script><script src=\"/_next/static/chunks/turbopack-09ycf6y7jk0qn.js\" async=\"\"></script><script src=\"/_next/static/chunks/0m6_ecmhgjm_j.js\" async=\"\"></script><script src=\"/_next/static/chu"
          },
          {
            "path": "/api/swagger.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en\" class=\"inter_7e838cde-module__DzEfXW__variable manrope_c74ae919-module__GlRqrq__variable\"><head><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><link rel=\"stylesheet\" href=\"/_next/static/chunks/0ddz_nathaknr.css\" data-precedence=\"next\"/><link rel=\"preload\" as=\"script\" fetchPriority=\"low\" href=\"/_next/static/chunks/0lclmgfn-n7l1.js\"/><script src=\"/_next/static/chunks/0pqt~8bl3ukh4.js\" async=\"\"></script><script src=\"/_next/static/chunks/10~x95jhs6ns3.js\" async=\"\"></script><script src=\"/_next/static/chunks/062hzijh369a_.js\" async=\"\"></script><script src=\"/_next/static/chunks/turbopack-09ycf6y7jk0qn.js\" async=\"\"></script><script src=\"/_next/static/chunks/0m6_ecmhgjm_j.js\" async=\"\"></script><script src=\"/_next/static/chu"
          },
          {
            "path": "/docs/openapi.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en\" class=\"inter_7e838cde-module__DzEfXW__variable manrope_c74ae919-module__GlRqrq__variable\"><head><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><link rel=\"stylesheet\" href=\"/_next/static/chunks/0ddz_nathaknr.css\" data-precedence=\"next\"/><link rel=\"preload\" as=\"script\" fetchPriority=\"low\" href=\"/_next/static/chunks/0lclmgfn-n7l1.js\"/><script src=\"/_next/static/chunks/0pqt~8bl3ukh4.js\" async=\"\"></script><script src=\"/_next/static/chunks/10~x95jhs6ns3.js\" async=\"\"></script><script src=\"/_next/static/chunks/062hzijh369a_.js\" async=\"\"></script><script src=\"/_next/static/chunks/turbopack-09ycf6y7jk0qn.js\" async=\"\"></script><script src=\"/_next/static/chunks/0m6_ecmhgjm_j.js\" async=\"\"></script><script src=\"/_next/static/chu"
          }
        ]
      },
      "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
      "howToFix": "Publish a valid OpenAPI 3.x or Swagger 2.0 JSON/YAML document with info, paths, operations, and responses."
    }
  ]
}

AI DiscoverabilityBot Access ControlEstablished

AI bot rules in robots.txt

AI bot rules in robots.txt is missing or incomplete.

33 Fail

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

No specific User-agent rules found for major AI crawlers (GPTBot, ClaudeBot, etc.) in robots.txt.

02

Why it matters

Explicit AI bot rules reduce ambiguity for crawler operators and make training, indexing, or retrieval access policy auditable.

Check name

AI bot rules in robots.txt

Score

0/100

Status

fail

Category

Bot Access Control

Maturity

Established

Goal

Add User-agent rules for AI crawlers like GPTBot, Claude-Web, and others.

Result

AI bot rules in robots.txt is missing or incomplete.

Evidence
{
  "expectedBots": [
    "GPTBot",
    "ChatGPT-User",
    "ClaudeBot",
    "Claude-Web",
    "Anthropic-AI",
    "Google-Extended",
    "PerplexityBot",
    "CCBot",
    "Applebot-Extended",
    "Meta-ExternalAgent",
    "Bytespider",
    "Amazonbot",
    "Cohere-AI"
  ],
  "configuredBots": []
}

AI DiscoverabilityBot Access ControlInformational

Content Signal

Content Signal is missing or incomplete.

33 Fail

Needs attention

Content Signal

Failed check
01

Issue

No Content Signal found in robots.txt

02

Why it matters

Content Signal provides a machine-readable way to communicate AI usage preferences where participating crawlers look for policy.

Check name

Content Signal

Score

0/100

Status

fail

Category

Bot Access Control

Maturity

Informational

Goal

Declare AI content usage preferences with Content Signal in robots.txt.

Result

Content Signal is missing or incomplete.

Evidence
{
  "signals": [],
  "ai-train": false,
  "search": false,
  "ai-input": false
}

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy is missing or incomplete.

33 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

Content-Security-Policy is missing or incomplete.

02

Why it matters

Content Security Policy limits where scripts, styles, frames, and connections can load from, reducing the impact of injection bugs.

Check name

Content-Security-Policy

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Constrain script, style, frame, and resource loading with a Content-Security-Policy header.

Result

Content-Security-Policy is missing or incomplete.

Evidence
{
  "header": "content-security-policy",
  "value": null
}

Security & TrustSecurity & TrustEstablished

Frame protection

Frame protection is missing or incomplete.

33 Fail

Needs attention

Frame protection

Failed check
01

Issue

Frame protection is missing or incomplete.

02

Why it matters

Frame protection blocks hostile sites from embedding pages in deceptive frames, reducing clickjacking risk.

Check name

Frame protection

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Prevent unwanted framing with X-Frame-Options or CSP frame-ancestors.

Result

Frame protection is missing or incomplete.

Evidence
{
  "xFrameOptions": null,
  "validXFrame": false,
  "contentSecurityPolicy": null,
  "cspFrameAncestors": false
}

Security & TrustSecurity & TrustEstablished

Referrer-Policy

Referrer-Policy is missing or incomplete.

33 Fail

Needs attention

Referrer-Policy

Failed check
01

Issue

Referrer-Policy is missing or incomplete.

02

Why it matters

Referrer-Policy controls how much URL context is sent to other origins, limiting accidental leakage of paths, queries, and identifiers.

Check name

Referrer-Policy

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Limit how much referrer data leaves the site.

Result

Referrer-Policy is missing or incomplete.

Evidence
{
  "header": "referrer-policy",
  "value": null
}

AI DiscoverabilityBot Access ControlInformational

Web Bot Auth request signing

Web Bot Auth request signing failed at "Fetch to find resource".

33 Fail

Needs attention

Web Bot Auth request signing

Failed check
01

Issue

Web Bot Auth request signing was not found at the expected path.

02

Why it matters

Web Bot Auth discovery lets servers and clients find signing keys for bot identity workflows based on HTTP Message Signatures.

Check name

Web Bot Auth request signing

Score

0/100

Status

fail

Category

Bot Access Control

Maturity

Informational

Goal

Advertise HTTP Message Signatures keys when this site operates signed bot clients or supports Web Bot Auth workflows.

Result

Web Bot Auth request signing failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    Web Bot Auth request signing was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/http-message-signatures-directory",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          }
        ]
      },
      "issue": "Web Bot Auth request signing was not found at the expected path.",
      "howToFix": "If publishing Web Bot Auth keys, return a JSON key directory with a non-empty keys array and the draft media type."
    }
  ]
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

A2A Agent Card failed at "Fetch to find resource".

25 Fail

Needs attention

A2A Agent Card

Failed check
01

Issue

A2A Agent Card was not found at the expected path.

02

Why it matters

A2A Agent Cards let compatible clients discover agent skills, input and output modes, and the endpoint used to invoke those skills.

Check name

A2A Agent Card

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an agent card so A2A-compatible clients can discover capabilities.

Result

A2A Agent Card failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    A2A Agent Card was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/agent-card.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          },
          {
            "path": "/.well-known/a2a/agent-card.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          },
          {
            "path": "/agent-card.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          }
        ]
      },
      "issue": "A2A Agent Card was not found at the expected path.",
      "howToFix": "Publish an A2A Agent Card with required skill details and make the advertised url answer A2A JSON-RPC requests."
    }
  ]
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

Agent Skills index failed at "Fetch to find resource".

25 Fail

Needs attention

Agent Skills index

Failed check
01

Issue

Agent Skills index was not found at the expected path.

02

Why it matters

An Agent Skills index lets clients find task-specific SKILL.md documents that describe how to use site capabilities correctly.

Check name

Agent Skills index

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an agent skills discovery index.

Result

Agent Skills index failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    Agent Skills index was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/agent-skills/index.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          },
          {
            "path": "/.well-known/skills/index.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          }
        ]
      },
      "issue": "Agent Skills index was not found at the expected path.",
      "howToFix": "Publish an index with a non-empty skills array and reachable SKILL.md URLs."
    }
  ]
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

agent.json

agent.json failed at "Fetch to find resource".

25 Fail

Needs attention

agent.json

Failed check
01

Issue

agent.json was not found at the expected path.

02

Why it matters

agent.json is an emerging machine-readable manifest for declaring what a website does, how agents authenticate, and which actions or protocols are available.

Check name

agent.json

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish the singular Agent Web Protocol agent.json manifest without confusing it with the separate agents.json directory convention.

Result

agent.json failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    agent.json was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/agent.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          },
          {
            "path": "/agent.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          }
        ]
      },
      "issue": "agent.json was not found at the expected path.",
      "howToFix": "Publish agent.json with awp_version, domain, intent, and typed actions that point to real same-origin API or protocol endpoints."
    }
  ]
}

Agent Ease of UseSkill DiscoveryInformational

agents.json

agents.json failed at "Fetch to find resource".

25 Fail

Needs attention

agents.json

Failed check
01

Issue

agents.json was not found at the expected path.

02

Why it matters

agents.json gives clients a simple directory of agent-facing capabilities and contacts when a site chooses to advertise them.

Check name

agents.json

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Informational

Goal

Publish an agents.json directory for agent-facing capabilities and contacts when using this convention.

Result

agents.json failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    agents.json was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/agents.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          },
          {
            "path": "/agents.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          }
        ]
      },
      "issue": "agents.json was not found at the expected path.",
      "howToFix": "If this site uses agents.json, publish JSON with an agents array containing name and url for each agent."
    }
  ]
}

Agent Ease of UseMCPEmerging recommendation

MCP Server Card

MCP Server Card failed at "Fetch to find resource".

25 Fail

Needs attention

MCP Server Card

Failed check
01

Issue

MCP Server Card was not found at the expected path.

02

Why it matters

MCP Server Cards help agents discover server transports, capabilities, and protocol details before opening an MCP session.

Check name

MCP Server Card

Score

0/100

Status

fail

Category

MCP

Maturity

Emerging recommendation

Goal

Publish an MCP Server Card for agent discovery.

Result

MCP Server Card failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    MCP Server Card was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/mcp/server-card.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          },
          {
            "path": "/.well-known/mcp/server-cards.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          },
          {
            "path": "/.well-known/mcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          }
        ]
      },
      "issue": "MCP Server Card was not found at the expected path.",
      "howToFix": "Publish an MCP server card with valid transports and make each advertised local endpoint answer an MCP initialize request."
    }
  ]
}

Agent Ease of UseMCPEmerging recommendation

mcp.json

mcp.json failed at "Fetch to find resource".

25 Fail

Needs attention

mcp.json

Failed check
01

Issue

mcp.json was not found at the expected path.

02

Why it matters

MCP clients need trustworthy server metadata, protocol version, transport details, and capability hints before connecting to a remote MCP server.

Check name

mcp.json

Score

0/100

Status

fail

Category

MCP

Maturity

Emerging recommendation

Goal

Expose a stable MCP server metadata document that points agents to the site's MCP endpoint.

Result

mcp.json failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    mcp.json was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/mcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          },
          {
            "path": "/.well-known/mcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          },
          {
            "path": "/.well-known/mcp/server-card.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          }
        ]
      },
      "issue": "mcp.json was not found at the expected path.",
      "howToFix": "Publish mcp.json or an MCP server card with serverInfo, protocolVersion, transport endpoint, and capabilities."
    }
  ]
}

Agent Ease of UseMCPInformational

WebMCP manifest

WebMCP manifest failed at "Fetch to find resource".

25 Fail

Needs attention

WebMCP manifest

Failed check
01

Issue

WebMCP manifest was not found at the expected path.

02

Why it matters

A WebMCP manifest advertises browser-exposed tools declaratively so agents can understand available site actions before invoking them.

Check name

WebMCP manifest

Score

0/100

Status

fail

Category

MCP

Maturity

Informational

Goal

Publish a WebMCP manifest for declarative browser tool discovery when using the draft manifest convention.

Result

WebMCP manifest failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    WebMCP manifest was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/webmcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          },
          {
            "path": "/webmcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          },
          {
            "path": "/mcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          }
        ]
      },
      "issue": "WebMCP manifest was not found at the expected path.",
      "howToFix": "Keep declarative WebMCP manifest discovery informational until the manifest shape stabilizes; validate tools if you publish one."
    }
  ]
}

AI DiscoverabilityContent ReadinessEstablished

Author attribution

Author attribution is missing or incomplete.

20 Fail

Needs attention

Author attribution

Failed check
01

Issue

Author attribution is missing: no schema.org author/publisher; no author meta tags; no rel=author links; no visible byline detected.

02

Why it matters

Author attribution helps agents cite content responsibly, assess source credibility, and distinguish editorial pages from anonymous marketing copy.

Check name

Author attribution

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Identify content authors or publishers for trust and attribution.

Result

Author attribution is missing or incomplete.

Evidence
{
  "editorial": true,
  "schemaAuthor": false,
  "metaAuthor": false,
  "relAuthor": false,
  "visibleByline": false
}

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

20 Fail

Needs attention

Content freshness signals

Failed check
01

Issue

Content freshness signals are incomplete: missing Last-Modified HTTP header; missing dateModified/datePublished in JSON-LD; missing meta or <time> freshness tags.

02

Why it matters

Freshness signals help agents decide whether content is current enough to cite, summarize, or compare against newer sources.

Check name

Content freshness signals

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose modified and published dates for freshness-aware retrieval and ranking.

Result

Content freshness signals is missing or incomplete.

Evidence
{
  "lastModified": null,
  "schemaDates": [],
  "metaDateCount": 0,
  "timeDateCount": 0
}

AI DiscoverabilityContent ReadinessEmerging recommendation

llms.txt

llms.txt failed at "Fetch to find resource".

20 Fail

Needs attention

llms.txt

Failed check
01

Issue

llms.txt was not found at the expected path.

02

Why it matters

llms.txt gives language-model clients a concise, curated summary of important site context and links before they crawl broadly.

Check name

llms.txt

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Emerging recommendation

Goal

Publish llms.txt to summarize agent-readable site guidance.

Result

llms.txt failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    llms.txt was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/llms.txt",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          },
          {
            "path": "/llms-full.txt",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          }
        ]
      },
      "issue": "llms.txt was not found at the expected path.",
      "howToFix": "Publish /llms.txt as Markdown with a clear title, concise site summary, and useful links for agents."
    }
  ]
}

AI DiscoverabilityContent ReadinessEstablished

Markdown negotiation

Markdown negotiation failed at "Markdown content type".

20 Fail

Needs attention

Markdown negotiation

Failed check
01

Issue

Content-Type "text/html; charset=utf-8" does not indicate Markdown when requested with Accept: text/markdown.

02

Why it matters

Markdown negotiation gives agents a cleaner representation of page content while preserving normal HTML for browsers.

Check name

Markdown negotiation

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Return HTML responses as markdown when agents request it.

Result

Markdown negotiation failed at "Markdown content type".

Validation steps

  1. Markdown content type

    Content-Type "text/html; charset=utf-8" does not indicate Markdown when requested with Accept: text/markdown.

  2. Vary: Accept header

    Markdown negotiation is missing Vary: Accept; current Vary header is "rsc,next-router-state-tree,next-router-prefetch,next-router-segment-prefetch,Accept-Encoding".

  3. Structured Markdown body

    Markdown response is missing a heading.

Evidence
{
  "failedStep": "content-type",
  "steps": [
    {
      "id": "content-type",
      "title": "Markdown content type",
      "status": "fail",
      "evidence": {
        "statusCode": 200,
        "contentType": "text/html; charset=utf-8"
      },
      "issue": "Content-Type \"text/html; charset=utf-8\" does not indicate Markdown when requested with Accept: text/markdown.",
      "howToFix": "Return Content-Type: text/markdown; charset=utf-8 for requests with Accept: text/markdown."
    },
    {
      "id": "vary-accept",
      "title": "Vary: Accept header",
      "status": "fail",
      "evidence": {
        "vary": "rsc,next-router-state-tree,next-router-prefetch,next-router-segment-prefetch,Accept-Encoding"
      },
      "issue": "Markdown negotiation is missing Vary: Accept; current Vary header is \"rsc,next-router-state-tree,next-router-prefetch,next-router-segment-prefetch,Accept-Encoding\".",
      "howToFix": "Add Vary: Accept on negotiated Markdown responses so shared caches keep HTML and Markdown variants separate."
    },
    {
      "id": "markdown-content",
      "title": "Structured Markdown body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "hasHeading": false,
        "wordCount": 15927,
        "excerpt": "<!DOCTYPE html><html lang=\"en\" class=\"inter_7e838cde-module__DzEfXW__variable manrope_c74ae919-module__GlRqrq__variable\"><head><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><link rel=\"preload\" h",
        "issue": "Markdown response is missing a heading."
      },
      "issue": "Markdown response is missing a heading.",
      "howToFix": "Return Markdown with at least one heading and substantive page content, including useful links or instructions for agents."
    }
  ]
}

AI DiscoverabilityContent ReadinessEstablished

Semantic HTML

Semantic HTML is missing or incomplete.

20 Fail

Needs attention

Semantic HTML

Failed check
01

Issue

Semantic HTML is incomplete: 0/2 applicable form inputs have autocomplete attributes (2 missing).

Details

02

Why it matters

Semantic HTML gives browsers, assistive technology, search systems, and agents reliable landmarks, headings, controls, form semantics, and image context.

Check name

Semantic HTML

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose readable page structure through semantic HTML and accessible controls.

Result

Semantic HTML is missing or incomplete.

Evidence
{
  "main": true,
  "nav": true,
  "footer": true,
  "meaningfulH1": true,
  "headingOrder": true,
  "accessibleLinks": true,
  "accessibleButtons": true,
  "imageAltCoverage": true,
  "formAutocompleteCoverage": false,
  "details": {
    "inaccessibleLinks": [],
    "inaccessibleButtons": [],
    "missingAutocompleteInputs": [
      "<input type=\"text\" placeholder=\"Full Name\">",
      "<input type=\"text\" placeholder=\"WhatsApp Number\">"
    ],
    "imagesMissingAlt": [],
    "skippedHeadingLevels": []
  },
  "counts": {
    "h1": 1,
    "headings": 32,
    "links": 29,
    "inaccessibleLinks": 0,
    "buttons": 2,
    "inaccessibleButtons": 0,
    "images": 2,
    "imagesWithAlt": 2,
    "autocompleteInputs": 2,
    "inputsWithAutocomplete": 0,
    "missingAutocompleteInputs": 2
  }
}

Agent Ease of UseMCPInformational

WebMCP

WebMCP has a validation warning at "Validate WebMCP declarative annotation quality".

13 Warning

Needs attention

WebMCP

Warning
01

Issue

WebMCP declarative annotations need fixes.

Details

02

Why it matters

WebMCP can expose page context and actions directly through the browser, giving agents safer structured hooks than screen scraping alone.

Check name

WebMCP

Score

50/100

Status

warning

Category

MCP

Maturity

Informational

Goal

Support WebMCP to expose site tools to AI agents via the browser.

Result

WebMCP has a validation warning at "Validate WebMCP declarative annotation quality".

Validation steps

  1. Detect data-mcp-tool annotations

    No data-mcp-tool attributes were found on interactive elements.

  2. Detect WebMCP declarative tags

    No elements found with tool-name or tool-description attributes.

  3. Validate WebMCP declarative annotation quality

    WebMCP declarative annotations need fixes.

    WebMCP declarative annotation issues
    • <input> is missing a name attribute.
    • <input> is missing a label.
    • <input> is missing tool-param-description.
    • <input> is missing a name attribute.
    • <input> is missing a label.
    • <input> is missing tool-param-description.
    • <select> is missing a name attribute.
    • <select> is missing a label.
    • <select> is missing tool-param-description.
  4. Detect WebMCP imperative API usage

    navigator.modelContext.provideContext(), navigator.modelContext.registerTool(), or other imperative signals were not detected in rendered browser state.

  5. Detect WebMCP browser navigator injection

    navigator.modelContext was not detected in the rendered browser page.

  6. Interactive surface coverage

    Only 0% of interactive surfaces are annotated.

Evidence
{
  "failedStep": "declarative-annotation-quality",
  "steps": [
    {
      "id": "data-mcp-tool-attributes",
      "title": "Detect data-mcp-tool annotations",
      "status": "informational",
      "evidence": {
        "dataMcpToolCount": 0,
        "dataMcpTools": []
      },
      "issue": "No data-mcp-tool attributes were found on interactive elements.",
      "howToFix": "Add data-mcp-tool attributes to high-value forms, buttons, and links so generic MCP-aware tooling can identify intended actions."
    },
    {
      "id": "declarative-tags",
      "title": "Detect WebMCP declarative tags",
      "status": "informational",
      "evidence": {
        "totalForms": 1,
        "formsWithTags": 0,
        "totalInteractive": 34,
        "interactiveWithTags": 0,
        "totalCount": 35,
        "taggedCount": 0,
        "dataMcpToolCount": 0,
        "dataMcpTools": [],
        "coverage": 0,
        "annotationIssues": [
          "<input> is missing a name attribute.",
          "<input> is missing a label.",
          "<input> is missing tool-param-description.",
          "<input> is missing a name attribute.",
          "<input> is missing a label.",
          "<input> is missing tool-param-description.",
          "<select> is missing a name attribute.",
          "<select> is missing a label.",
          "<select> is missing tool-param-description."
        ]
      },
      "issue": "No elements found with tool-name or tool-description attributes.",
      "howToFix": "Add tool-name and tool-description attributes to forms and interactive elements."
    },
    {
      "id": "declarative-annotation-quality",
      "title": "Validate WebMCP declarative annotation quality",
      "status": "warning",
      "evidence": {
        "issueCount": 9,
        "issues": [
          "<input> is missing a name attribute.",
          "<input> is missing a label.",
          "<input> is missing tool-param-description.",
          "<input> is missing a name attribute.",
          "<input> is missing a label.",
          "<input> is missing tool-param-description.",
          "<select> is missing a name attribute.",
          "<select> is missing a label.",
          "<select> is missing tool-param-description."
        ]
      },
      "issue": "WebMCP declarative annotations need fixes.",
      "issueDetails": [
        {
          "title": "WebMCP declarative annotation issues",
          "items": [
            {
              "type": "code",
              "value": "<input> is missing a name attribute."
            },
            {
              "type": "code",
              "value": "<input> is missing a label."
            },
            {
              "type": "code",
              "value": "<input> is missing tool-param-description."
            },
            {
              "type": "code",
              "value": "<input> is missing a name attribute."
            },
            {
              "type": "code",
              "value": "<input> is missing a label."
            },
            {
              "type": "code",
              "value": "<input> is missing tool-param-description."
            },
            {
              "type": "code",
              "value": "<select> is missing a name attribute."
            },
            {
              "type": "code",
              "value": "<select> is missing a label."
            },
            {
              "type": "code",
              "value": "<select> is missing tool-param-description."
            }
          ]
        }
      ],
      "howToFix": "Use snake_case tool-name values, descriptive tool-description values, named and labeled fields, and tool-param-description on inputs."
    },
    {
      "id": "imperative-api",
      "title": "Detect WebMCP imperative API usage",
      "status": "informational",
      "evidence": {
        "staticSignals": {
          "detected": false,
          "matched": []
        },
        "browser": {
          "checked": true,
          "detected": false,
          "hasNavigatorModelContext": false,
          "modelContextType": "undefined",
          "hasProvideContext": false,
          "hasRegisterTool": false
        }
      },
      "issue": "navigator.modelContext.provideContext(), navigator.modelContext.registerTool(), or other imperative signals were not detected in rendered browser state.",
      "howToFix": "Use navigator.modelContext.provideContext() to register tools programmatically."
    },
    {
      "id": "browser-navigator-injection",
      "title": "Detect WebMCP browser navigator injection",
      "status": "informational",
      "evidence": {
        "browser": {
          "checked": true,
          "detected": false,
          "hasNavigatorModelContext": false,
          "modelContextType": "undefined",
          "hasProvideContext": false,
          "hasRegisterTool": false
        }
      },
      "issue": "navigator.modelContext was not detected in the rendered browser page.",
      "howToFix": "Expose WebMCP through navigator.modelContext in the browser runtime when the page is intended to provide in-page tools."
    },
    {
      "id": "surface-coverage",
      "title": "Interactive surface coverage",
      "status": "informational",
      "evidence": {
        "totalForms": 1,
        "formsWithTags": 0,
        "totalInteractive": 34,
        "interactiveWithTags": 0,
        "totalCount": 35,
        "taggedCount": 0,
        "dataMcpToolCount": 0,
        "dataMcpTools": [],
        "coverage": 0,
        "annotationIssues": [
          "<input> is missing a name attribute.",
          "<input> is missing a label.",
          "<input> is missing tool-param-description.",
          "<input> is missing a name attribute.",
          "<input> is missing a label.",
          "<input> is missing tool-param-description.",
          "<select> is missing a name attribute.",
          "<select> is missing a label.",
          "<select> is missing tool-param-description."
        ]
      },
      "issue": "Only 0% of interactive surfaces are annotated.",
      "howToFix": "Add WebMCP annotations to all forms and interactive elements to increase agent coverage."
    }
  ],
  "staticSignals": {
    "detected": false,
    "matched": []
  },
  "coverage": {
    "totalForms": 1,
    "formsWithTags": 0,
    "totalInteractive": 34,
    "interactiveWithTags": 0,
    "totalCount": 35,
    "taggedCount": 0,
    "dataMcpToolCount": 0,
    "dataMcpTools": [],
    "coverage": 0,
    "annotationIssues": [
      "<input> is missing a name attribute.",
      "<input> is missing a label.",
      "<input> is missing tool-param-description.",
      "<input> is missing a name attribute.",
      "<input> is missing a label.",
      "<input> is missing tool-param-description.",
      "<select> is missing a name attribute.",
      "<select> is missing a label.",
      "<select> is missing tool-param-description."
    ]
  },
  "browserWebMcp": {
    "checked": true,
    "detected": false,
    "hasNavigatorModelContext": false,
    "modelContextType": "undefined",
    "hasProvideContext": false,
    "hasRegisterTool": false
  }
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Source and trust signals

AIO: Source and trust signals scored 40/100 and needs a fix.

8 Fail

Needs attention

AIO: Source and trust signals

Failed check
01

Issue

Missing AIO trust signals: author, publisher, freshnessDate.

Details

02

Why it matters

AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.

Check name

AIO: Source and trust signals

Score

40/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible and useful for Google AI Overviews and AI Mode extraction.

Result

AIO: Source and trust signals scored 40/100 and needs a fix.

Evidence
{
  "signals": {
    "author": false,
    "publisher": false,
    "freshnessDate": false,
    "aboutOrContact": true,
    "policyLinks": true
  },
  "missing": [
    "author",
    "publisher",
    "freshnessDate"
  ],
  "authorMeta": "",
  "schemaAuthors": [],
  "schemaPublishers": [],
  "schemaDates": [],
  "visibleDates": [],
  "aboutLinks": [
    {
      "href": "/about",
      "text": "About",
      "html": "<a class href=\"/about\">About</a>"
    },
    {
      "href": "/about",
      "text": "About",
      "html": "<a href=\"/about\">About</a>"
    }
  ],
  "contactLinks": [
    {
      "href": "/contact",
      "text": "Talk on WhatsApp",
      "html": "<a class=\"nav-cta\" href=\"/contact\">Talk on WhatsApp</a>"
    },
    {
      "href": "/contact",
      "text": "Talk on WhatsApp",
      "html": "<a class=\"button button-primary\" href=\"/contact\">Talk on WhatsApp</a>"
    },
    {
      "href": "/negotiation-support",
      "text": "Negotiation Support",
      "html": "<a class=\"button button-white\" href=\"/negotiation-support\">Negotiation Support</a>"
    },
    {
      "href": "/contact",
      "text": "Talk on WhatsApp",
      "html": "<a class=\"button button-primary\" href=\"/contact\">Talk on WhatsApp</a>"
    },
    {
      "href": "/contact",
      "text": "Talk on WhatsApp",
      "html": "<a href=\"/contact\">Talk on WhatsApp</a>"
    }
  ],
  "privacyLinks": [
    {
      "href": "/privacy-policy",
      "text": "Privacy Policy",
      "html": "<a href=\"/privacy-policy\">Privacy Policy</a>"
    },
    {
      "href": "/terms-and-conditions",
      "text": "Terms and Conditions",
      "html": "<a href=\"/terms-and-conditions\">Terms and Conditions</a>"
    }
  ],
  "score": 40,
  "weight": 20
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer evidence and trust

AEO: Answer evidence and trust scored 40/100 and needs a fix.

5 Fail

Needs attention

AEO: Answer evidence and trust

Failed check
01

Issue

Missing AIO trust signals: author, publisher, freshnessDate.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Answer evidence and trust

Score

40/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Answer evidence and trust scored 40/100 and needs a fix.

Evidence
{
  "signals": {
    "author": false,
    "publisher": false,
    "freshnessDate": false,
    "aboutOrContact": true,
    "policyLinks": true
  },
  "missing": [
    "author",
    "publisher",
    "freshnessDate"
  ],
  "authorMeta": "",
  "schemaAuthors": [],
  "schemaPublishers": [],
  "schemaDates": [],
  "visibleDates": [],
  "aboutLinks": [
    {
      "href": "/about",
      "text": "About",
      "html": "<a class href=\"/about\">About</a>"
    },
    {
      "href": "/about",
      "text": "About",
      "html": "<a href=\"/about\">About</a>"
    }
  ],
  "contactLinks": [
    {
      "href": "/contact",
      "text": "Talk on WhatsApp",
      "html": "<a class=\"nav-cta\" href=\"/contact\">Talk on WhatsApp</a>"
    },
    {
      "href": "/contact",
      "text": "Talk on WhatsApp",
      "html": "<a class=\"button button-primary\" href=\"/contact\">Talk on WhatsApp</a>"
    },
    {
      "href": "/negotiation-support",
      "text": "Negotiation Support",
      "html": "<a class=\"button button-white\" href=\"/negotiation-support\">Negotiation Support</a>"
    },
    {
      "href": "/contact",
      "text": "Talk on WhatsApp",
      "html": "<a class=\"button button-primary\" href=\"/contact\">Talk on WhatsApp</a>"
    },
    {
      "href": "/contact",
      "text": "Talk on WhatsApp",
      "html": "<a href=\"/contact\">Talk on WhatsApp</a>"
    }
  ],
  "privacyLinks": [
    {
      "href": "/privacy-policy",
      "text": "Privacy Policy",
      "html": "<a href=\"/privacy-policy\">Privacy Policy</a>"
    },
    {
      "href": "/terms-and-conditions",
      "text": "Terms and Conditions",
      "html": "<a href=\"/terms-and-conditions\">Terms and Conditions</a>"
    }
  ],
  "score": 40,
  "weight": 22
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first sections

AEO: Answer-first sections scored 65/100 and needs improvement.

4 Warning

Needs attention

AEO: Answer-first sections

Warning
01

Issue

27 section(s) may benefit from a clearer opening answer; this is optional for feature/card sections.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Answer-first sections

Score

65/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Answer-first sections scored 65/100 and needs improvement.

Evidence
{
  "sectionCount": 31,
  "passing": 4,
  "failing": [
    {
      "heading": "Too many listings",
      "headingHtml": "<h3>Too many listings</h3>",
      "firstParagraph": "Buyers spend time looking at volume instead of quality.",
      "paragraphHtml": "<p>Buyers spend time looking at volume instead of quality.</p>",
      "words": 9,
      "direct": false,
      "issue": "First paragraph is 9 words and does not look like a concise direct answer."
    },
    {
      "heading": "Seller-led advice",
      "headingHtml": "<h3>Seller-led advice</h3>",
      "firstParagraph": "Most advice in the market is built to close inventory, not protect the buyer.",
      "paragraphHtml": "<p>Most advice in the market is built to close inventory, not protect the buyer.</p>",
      "words": 14,
      "direct": false,
      "issue": "First paragraph is 14 words and does not look like a concise direct answer."
    },
    {
      "heading": "Unclear pricing",
      "headingHtml": "<h3>Unclear pricing</h3>",
      "firstParagraph": "A property can look attractive and still be the wrong entry.",
      "paragraphHtml": "<p>A property can look attractive and still be the wrong entry.</p>",
      "words": 11,
      "direct": false,
      "issue": "First paragraph is 11 words and does not look like a concise direct answer."
    },
    {
      "heading": "Hidden risk",
      "headingHtml": "<h3>Hidden risk</h3>",
      "firstParagraph": "Legal, technical, and market issues often stay invisible until it is too late.",
      "paragraphHtml": "<p>Legal, technical, and market issues often stay invisible until it is too late.</p>",
      "words": 13,
      "direct": false,
      "issue": "First paragraph is 13 words and does not look like a concise direct answer."
    },
    {
      "heading": "A better buying decision starts before the site visit.",
      "headingHtml": "<h2>A better buying decision starts before the site visit.</h2>",
      "firstParagraph": "We help buyers move through the market with a structured process, from sourcing and filtering to verification and negotiation.",
      "paragraphHtml": "<p>We help buyers move through the market with a structured process, from sourcing and filtering to verification and negotiation.</p>",
      "words": 19,
      "direct": false,
      "issue": "First paragraph is 19 words and does not look like a concise direct answer."
    },
    {
      "heading": "Source",
      "headingHtml": "<h3>Source</h3>",
      "firstParagraph": "We understand your budget, purpose, and objective, then identify opportunities that fit.",
      "paragraphHtml": "<p>We understand your budget, purpose, and objective, then identify opportunities that fit.</p>",
      "words": 12,
      "direct": false,
      "issue": "First paragraph is 12 words and does not look like a concise direct answer."
    },
    {
      "heading": "Filter",
      "headingHtml": "<h3>Filter</h3>",
      "firstParagraph": "We remove noise, compare options, and narrow the field to what actually makes sense.",
      "paragraphHtml": "<p>We remove noise, compare options, and narrow the field to what actually makes sense.</p>",
      "words": 14,
      "direct": false,
      "issue": "First paragraph is 14 words and does not look like a concise direct answer."
    },
    {
      "heading": "Verify",
      "headingHtml": "<h3>Verify</h3>",
      "firstParagraph": "We assess legal, technical, and market risk before you move forward.",
      "paragraphHtml": "<p>We assess legal, technical, and market risk before you move forward.</p>",
      "words": 11,
      "direct": false,
      "issue": "First paragraph is 11 words and does not look like a concise direct answer."
    },
    {
      "heading": "Negotiate",
      "headingHtml": "<h3>Negotiate</h3>",
      "firstParagraph": "We help you move with better leverage, more clarity, and fewer blind spots.",
      "paragraphHtml": "<p>We help you move with better leverage, more clarity, and fewer blind spots.</p>",
      "words": 13,
      "direct": false,
      "issue": "First paragraph is 13 words and does not look like a concise direct answer."
    },
    {
      "heading": "Everything serious buyers need.",
      "headingHtml": "<h2>Everything serious buyers need.</h2>",
      "firstParagraph": "BuyrSide is a complete property sourcing engine built to find, judge, and secure better opportunities.",
      "paragraphHtml": "<p class=\"lead\">BuyrSide is a complete property sourcing engine built to find, judge, and secure better opportunities.</p>",
      "words": 15,
      "direct": false,
      "issue": "First paragraph is 15 words and does not look like a concise direct answer."
    },
    {
      "heading": "Find Better Opportunities",
      "headingHtml": "<h3>Find Better Opportunities</h3>",
      "firstParagraph": "Curated below-market and off-market deals.",
      "paragraphHtml": "<p class=\"lead-small\">Curated below-market and off-market deals.</p>",
      "words": 5,
      "direct": false,
      "issue": "First paragraph is 5 words and does not look like a concise direct answer."
    },
    {
      "heading": "Deal Score System",
      "headingHtml": "<h3>Deal Score System</h3>",
      "firstParagraph": "A structured way to compare pricing, upside, and risk.",
      "paragraphHtml": "<p>A structured way to compare pricing, upside, and risk.</p>",
      "words": 9,
      "direct": false,
      "issue": "First paragraph is 9 words and does not look like a concise direct answer."
    },
    {
      "heading": "Property Verification",
      "headingHtml": "<h3>Property Verification</h3>",
      "firstParagraph": "Checks across legal, technical, and market factors.",
      "paragraphHtml": "<p>Checks across legal, technical, and market factors.</p>",
      "words": 7,
      "direct": false,
      "issue": "First paragraph is 7 words and does not look like a concise direct answer."
    },
    {
      "heading": "Secure Better Outcomes",
      "headingHtml": "<h3>Secure Better Outcomes</h3>",
      "firstParagraph": "Negotiation support and clarity before you commit.",
      "paragraphHtml": "<p>Negotiation support and clarity before you commit.</p>",
      "words": 7,
      "direct": false,
      "issue": "First paragraph is 7 words and does not look like a concise direct answer."
    },
    {
      "heading": "Buyer-Loyal",
      "headingHtml": "<h3>Buyer-Loyal</h3>",
      "firstParagraph": "We work in favor of the buyer's decision, not the seller's pipeline.",
      "paragraphHtml": "<p>We work in favor of the buyer&apos;s decision, not the seller&apos;s pipeline.</p>",
      "words": 12,
      "direct": false,
      "issue": "First paragraph is 12 words and does not look like a concise direct answer."
    },
    {
      "heading": "Filtered, Not Flooded",
      "headingHtml": "<h3>Filtered, Not Flooded</h3>",
      "firstParagraph": "We do not overwhelm you with options. We help you focus on what is worth attention.",
      "paragraphHtml": "<p>We do not overwhelm you with options. We help you focus on what is worth attention.</p>",
      "words": 16,
      "direct": false,
      "issue": "First paragraph is 16 words and does not look like a concise direct answer."
    },
    {
      "heading": "Decision-Led",
      "headingHtml": "<h3>Decision-Led</h3>",
      "firstParagraph": "We combine sourcing, scoring, verification, and judgment in one process.",
      "paragraphHtml": "<p>We combine sourcing, scoring, verification, and judgment in one process.</p>",
      "words": 10,
      "direct": false,
      "issue": "First paragraph is 10 words and does not look like a concise direct answer."
    },
    {
      "heading": "Serious-Buyer Focused",
      "headingHtml": "<h3>Serious-Buyer Focused</h3>",
      "firstParagraph": "This experience is built for buyers who want signal, clarity, and action.",
      "paragraphHtml": "<p>This experience is built for buyers who want signal, clarity, and action.</p>",
      "words": 12,
      "direct": false,
      "issue": "First paragraph is 12 words and does not look like a concise direct answer."
    },
    {
      "heading": "Proof matters when the decision does.",
      "headingHtml": "<h2>Proof matters when the decision does.</h2>",
      "firstParagraph": "Claims are not enough. We provide evidence, structure, and outcomes you can trust.",
      "paragraphHtml": "<p class=\"lead\">Claims are not enough. We provide evidence, structure, and outcomes you can trust.</p>",
      "words": 13,
      "direct": false,
      "issue": "First paragraph is 13 words and does not look like a concise direct answer."
    },
    {
      "heading": "Request Access",
      "headingHtml": "<h3>Request Access</h3>",
      "firstParagraph": "Our team will review and reach out.",
      "paragraphHtml": "<p class=\"form-note\" style=\"text-align:center\">Our team will review and reach out.</p>",
      "words": 7,
      "direct": false,
      "issue": "First paragraph is 7 words and does not look like a concise direct answer."
    },
    {
      "heading": "Better sourcing. Better judgment. Better outcomes.",
      "headingHtml": "<h2>Better sourcing. Better judgment. Better outcomes.</h2>",
      "firstParagraph": "When buyers get better filtering and better clarity, they make stronger moves.",
      "paragraphHtml": "<p>When buyers get better filtering and better clarity, they make stronger moves.</p>",
      "words": 12,
      "direct": false,
      "issue": "First paragraph is 12 words and does not look like a concise direct answer."
    },
    {
      "heading": "End-use buyer found a stronger entry in a high-demand micro-market.",
      "headingHtml": "<h3>End-use buyer found a stronger entry in a high-demand micro-market.</h3>",
      "firstParagraph": "Better fit, stronger entry, less wasted time comparing weak options.",
      "paragraphHtml": "<p>Better fit, stronger entry, less wasted time comparing weak options.</p>",
      "words": 10,
      "direct": false,
      "issue": "First paragraph is 10 words and does not look like a concise direct answer."
    },
    {
      "heading": "Investor avoided a weaker asset and focused on the right micro-market.",
      "headingHtml": "<h3>Investor avoided a weaker asset and focused on the right micro-market.</h3>",
      "firstParagraph": "More clarity on rental demand, upside, and long-term decision quality.",
      "paragraphHtml": "<p>More clarity on rental demand, upside, and long-term decision quality.</p>",
      "words": 10,
      "direct": false,
      "issue": "First paragraph is 10 words and does not look like a concise direct answer."
    },
    {
      "heading": "Buyer paused a property that looked attractive but did not hold up under scrutiny.",
      "headingHtml": "<h3>Buyer paused a property that looked attractive but did not hold up under scrutiny.</h3>",
      "firstParagraph": "Verification and judgment prevented a costly move based on surface-level appeal.",
      "paragraphHtml": "<p>Verification and judgment prevented a costly move based on surface-level appeal.</p>",
      "words": 11,
      "direct": false,
      "issue": "First paragraph is 11 words and does not look like a concise direct answer."
    },
    {
      "heading": "Explore",
      "headingHtml": "<h3>Explore</h3>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Services",
      "headingHtml": "<h3>Services</h3>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Contact",
      "headingHtml": "<h3>Contact</h3>",
      "firstParagraph": "© 2026 BuyrSide. All rights reserved.",
      "paragraphHtml": "<p>&#xa9; <!-- -->2026<!-- --> BuyrSide. All rights reserved.</p>",
      "words": 5,
      "direct": false,
      "issue": "First paragraph is 5 words and does not look like a concise direct answer."
    }
  ],
  "score": 65,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question-led structure

AEO: Question-led structure scored 50/100 and needs improvement.

3 Warning

Needs attention

AEO: Question-led structure

Warning
01

Issue

No question-led h2 sections or FAQ pattern was detected.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Question-led structure

Score

50/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Question-led structure scored 50/100 and needs improvement.

Evidence
{
  "h2Count": 8,
  "questionH2s": [],
  "hasFaq": false,
  "score": 50,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Google eligibility and indexability

AIO: Google eligibility and indexability scored 80/100 and needs improvement.

2 Warning

Needs attention

AIO: Google eligibility and indexability

Warning
01

Issue

Canonical does not self-reference the scanned page.

Details

02

Why it matters

AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.

Check name

AIO: Google eligibility and indexability

Score

80/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible and useful for Google AI Overviews and AI Mode extraction.

Result

AIO: Google eligibility and indexability scored 80/100 and needs improvement.

Evidence
{
  "status": 200,
  "googlebotBlocked": false,
  "metaRobotsTags": [],
  "xRobotsTag": "",
  "canonical": "https://buyrside.in",
  "finalUrl": "https://buyrside.com/",
  "canonicalScore": 60,
  "score": 80,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Explanatory content depth

GEO: Explanatory content depth scored 75/100 and needs improvement.

2 Warning

Needs attention

GEO: Explanatory content depth

Warning
01

Issue

No substantial explanatory paragraphs were found.

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: Explanatory content depth

Score

75/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

GEO: Explanatory content depth scored 75/100 and needs improvement.

Evidence
{
  "candidatePassages": 1,
  "citablePassages": 0,
  "failingCandidateParagraphs": [],
  "citableParagraphs": [],
  "score": 75,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Answer block readiness

AIO: Answer block readiness scored 65/100 and needs improvement.

2 Warning

Needs attention

AIO: Answer block readiness

Warning
01

Issue

27 section(s) may benefit from a clearer opening answer; this is optional for feature/card sections.

Details

02

Why it matters

AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.

Check name

AIO: Answer block readiness

Score

65/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible and useful for Google AI Overviews and AI Mode extraction.

Result

AIO: Answer block readiness scored 65/100 and needs improvement.

Evidence
{
  "sectionCount": 31,
  "passing": 4,
  "failing": [
    {
      "heading": "Too many listings",
      "headingHtml": "<h3>Too many listings</h3>",
      "firstParagraph": "Buyers spend time looking at volume instead of quality.",
      "paragraphHtml": "<p>Buyers spend time looking at volume instead of quality.</p>",
      "words": 9,
      "direct": false,
      "issue": "First paragraph is 9 words and does not look like a concise direct answer."
    },
    {
      "heading": "Seller-led advice",
      "headingHtml": "<h3>Seller-led advice</h3>",
      "firstParagraph": "Most advice in the market is built to close inventory, not protect the buyer.",
      "paragraphHtml": "<p>Most advice in the market is built to close inventory, not protect the buyer.</p>",
      "words": 14,
      "direct": false,
      "issue": "First paragraph is 14 words and does not look like a concise direct answer."
    },
    {
      "heading": "Unclear pricing",
      "headingHtml": "<h3>Unclear pricing</h3>",
      "firstParagraph": "A property can look attractive and still be the wrong entry.",
      "paragraphHtml": "<p>A property can look attractive and still be the wrong entry.</p>",
      "words": 11,
      "direct": false,
      "issue": "First paragraph is 11 words and does not look like a concise direct answer."
    },
    {
      "heading": "Hidden risk",
      "headingHtml": "<h3>Hidden risk</h3>",
      "firstParagraph": "Legal, technical, and market issues often stay invisible until it is too late.",
      "paragraphHtml": "<p>Legal, technical, and market issues often stay invisible until it is too late.</p>",
      "words": 13,
      "direct": false,
      "issue": "First paragraph is 13 words and does not look like a concise direct answer."
    },
    {
      "heading": "A better buying decision starts before the site visit.",
      "headingHtml": "<h2>A better buying decision starts before the site visit.</h2>",
      "firstParagraph": "We help buyers move through the market with a structured process, from sourcing and filtering to verification and negotiation.",
      "paragraphHtml": "<p>We help buyers move through the market with a structured process, from sourcing and filtering to verification and negotiation.</p>",
      "words": 19,
      "direct": false,
      "issue": "First paragraph is 19 words and does not look like a concise direct answer."
    },
    {
      "heading": "Source",
      "headingHtml": "<h3>Source</h3>",
      "firstParagraph": "We understand your budget, purpose, and objective, then identify opportunities that fit.",
      "paragraphHtml": "<p>We understand your budget, purpose, and objective, then identify opportunities that fit.</p>",
      "words": 12,
      "direct": false,
      "issue": "First paragraph is 12 words and does not look like a concise direct answer."
    },
    {
      "heading": "Filter",
      "headingHtml": "<h3>Filter</h3>",
      "firstParagraph": "We remove noise, compare options, and narrow the field to what actually makes sense.",
      "paragraphHtml": "<p>We remove noise, compare options, and narrow the field to what actually makes sense.</p>",
      "words": 14,
      "direct": false,
      "issue": "First paragraph is 14 words and does not look like a concise direct answer."
    },
    {
      "heading": "Verify",
      "headingHtml": "<h3>Verify</h3>",
      "firstParagraph": "We assess legal, technical, and market risk before you move forward.",
      "paragraphHtml": "<p>We assess legal, technical, and market risk before you move forward.</p>",
      "words": 11,
      "direct": false,
      "issue": "First paragraph is 11 words and does not look like a concise direct answer."
    },
    {
      "heading": "Negotiate",
      "headingHtml": "<h3>Negotiate</h3>",
      "firstParagraph": "We help you move with better leverage, more clarity, and fewer blind spots.",
      "paragraphHtml": "<p>We help you move with better leverage, more clarity, and fewer blind spots.</p>",
      "words": 13,
      "direct": false,
      "issue": "First paragraph is 13 words and does not look like a concise direct answer."
    },
    {
      "heading": "Everything serious buyers need.",
      "headingHtml": "<h2>Everything serious buyers need.</h2>",
      "firstParagraph": "BuyrSide is a complete property sourcing engine built to find, judge, and secure better opportunities.",
      "paragraphHtml": "<p class=\"lead\">BuyrSide is a complete property sourcing engine built to find, judge, and secure better opportunities.</p>",
      "words": 15,
      "direct": false,
      "issue": "First paragraph is 15 words and does not look like a concise direct answer."
    },
    {
      "heading": "Find Better Opportunities",
      "headingHtml": "<h3>Find Better Opportunities</h3>",
      "firstParagraph": "Curated below-market and off-market deals.",
      "paragraphHtml": "<p class=\"lead-small\">Curated below-market and off-market deals.</p>",
      "words": 5,
      "direct": false,
      "issue": "First paragraph is 5 words and does not look like a concise direct answer."
    },
    {
      "heading": "Deal Score System",
      "headingHtml": "<h3>Deal Score System</h3>",
      "firstParagraph": "A structured way to compare pricing, upside, and risk.",
      "paragraphHtml": "<p>A structured way to compare pricing, upside, and risk.</p>",
      "words": 9,
      "direct": false,
      "issue": "First paragraph is 9 words and does not look like a concise direct answer."
    },
    {
      "heading": "Property Verification",
      "headingHtml": "<h3>Property Verification</h3>",
      "firstParagraph": "Checks across legal, technical, and market factors.",
      "paragraphHtml": "<p>Checks across legal, technical, and market factors.</p>",
      "words": 7,
      "direct": false,
      "issue": "First paragraph is 7 words and does not look like a concise direct answer."
    },
    {
      "heading": "Secure Better Outcomes",
      "headingHtml": "<h3>Secure Better Outcomes</h3>",
      "firstParagraph": "Negotiation support and clarity before you commit.",
      "paragraphHtml": "<p>Negotiation support and clarity before you commit.</p>",
      "words": 7,
      "direct": false,
      "issue": "First paragraph is 7 words and does not look like a concise direct answer."
    },
    {
      "heading": "Buyer-Loyal",
      "headingHtml": "<h3>Buyer-Loyal</h3>",
      "firstParagraph": "We work in favor of the buyer's decision, not the seller's pipeline.",
      "paragraphHtml": "<p>We work in favor of the buyer&apos;s decision, not the seller&apos;s pipeline.</p>",
      "words": 12,
      "direct": false,
      "issue": "First paragraph is 12 words and does not look like a concise direct answer."
    },
    {
      "heading": "Filtered, Not Flooded",
      "headingHtml": "<h3>Filtered, Not Flooded</h3>",
      "firstParagraph": "We do not overwhelm you with options. We help you focus on what is worth attention.",
      "paragraphHtml": "<p>We do not overwhelm you with options. We help you focus on what is worth attention.</p>",
      "words": 16,
      "direct": false,
      "issue": "First paragraph is 16 words and does not look like a concise direct answer."
    },
    {
      "heading": "Decision-Led",
      "headingHtml": "<h3>Decision-Led</h3>",
      "firstParagraph": "We combine sourcing, scoring, verification, and judgment in one process.",
      "paragraphHtml": "<p>We combine sourcing, scoring, verification, and judgment in one process.</p>",
      "words": 10,
      "direct": false,
      "issue": "First paragraph is 10 words and does not look like a concise direct answer."
    },
    {
      "heading": "Serious-Buyer Focused",
      "headingHtml": "<h3>Serious-Buyer Focused</h3>",
      "firstParagraph": "This experience is built for buyers who want signal, clarity, and action.",
      "paragraphHtml": "<p>This experience is built for buyers who want signal, clarity, and action.</p>",
      "words": 12,
      "direct": false,
      "issue": "First paragraph is 12 words and does not look like a concise direct answer."
    },
    {
      "heading": "Proof matters when the decision does.",
      "headingHtml": "<h2>Proof matters when the decision does.</h2>",
      "firstParagraph": "Claims are not enough. We provide evidence, structure, and outcomes you can trust.",
      "paragraphHtml": "<p class=\"lead\">Claims are not enough. We provide evidence, structure, and outcomes you can trust.</p>",
      "words": 13,
      "direct": false,
      "issue": "First paragraph is 13 words and does not look like a concise direct answer."
    },
    {
      "heading": "Request Access",
      "headingHtml": "<h3>Request Access</h3>",
      "firstParagraph": "Our team will review and reach out.",
      "paragraphHtml": "<p class=\"form-note\" style=\"text-align:center\">Our team will review and reach out.</p>",
      "words": 7,
      "direct": false,
      "issue": "First paragraph is 7 words and does not look like a concise direct answer."
    },
    {
      "heading": "Better sourcing. Better judgment. Better outcomes.",
      "headingHtml": "<h2>Better sourcing. Better judgment. Better outcomes.</h2>",
      "firstParagraph": "When buyers get better filtering and better clarity, they make stronger moves.",
      "paragraphHtml": "<p>When buyers get better filtering and better clarity, they make stronger moves.</p>",
      "words": 12,
      "direct": false,
      "issue": "First paragraph is 12 words and does not look like a concise direct answer."
    },
    {
      "heading": "End-use buyer found a stronger entry in a high-demand micro-market.",
      "headingHtml": "<h3>End-use buyer found a stronger entry in a high-demand micro-market.</h3>",
      "firstParagraph": "Better fit, stronger entry, less wasted time comparing weak options.",
      "paragraphHtml": "<p>Better fit, stronger entry, less wasted time comparing weak options.</p>",
      "words": 10,
      "direct": false,
      "issue": "First paragraph is 10 words and does not look like a concise direct answer."
    },
    {
      "heading": "Investor avoided a weaker asset and focused on the right micro-market.",
      "headingHtml": "<h3>Investor avoided a weaker asset and focused on the right micro-market.</h3>",
      "firstParagraph": "More clarity on rental demand, upside, and long-term decision quality.",
      "paragraphHtml": "<p>More clarity on rental demand, upside, and long-term decision quality.</p>",
      "words": 10,
      "direct": false,
      "issue": "First paragraph is 10 words and does not look like a concise direct answer."
    },
    {
      "heading": "Buyer paused a property that looked attractive but did not hold up under scrutiny.",
      "headingHtml": "<h3>Buyer paused a property that looked attractive but did not hold up under scrutiny.</h3>",
      "firstParagraph": "Verification and judgment prevented a costly move based on surface-level appeal.",
      "paragraphHtml": "<p>Verification and judgment prevented a costly move based on surface-level appeal.</p>",
      "words": 11,
      "direct": false,
      "issue": "First paragraph is 11 words and does not look like a concise direct answer."
    },
    {
      "heading": "Explore",
      "headingHtml": "<h3>Explore</h3>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Services",
      "headingHtml": "<h3>Services</h3>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Contact",
      "headingHtml": "<h3>Contact</h3>",
      "firstParagraph": "© 2026 BuyrSide. All rights reserved.",
      "paragraphHtml": "<p>&#xa9; <!-- -->2026<!-- --> BuyrSide. All rights reserved.</p>",
      "words": 5,
      "direct": false,
      "issue": "First paragraph is 5 words and does not look like a concise direct answer."
    }
  ],
  "score": 65,
  "weight": 8
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Entity clarity

GEO: Entity clarity scored 87/100 and needs improvement.

2 Warning

Needs attention

GEO: Entity clarity

Warning
01

Issue

Title/H1 terms missing from description: buyer, first, sourcing.

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: Entity clarity

Score

87/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

GEO: Entity clarity scored 87/100 and needs improvement.

Evidence
{
  "title": "BuyrSide | Property Sourcer For Buyers",
  "h1": "Buyer-first property sourcing.",
  "description": "BuyrSide is a property sourcer that works in favor of property buyers. Source, filter, verify, and secure better property opportunities.",
  "topicOverlap": 0.5714285714285714,
  "topicTerms": [
    "buyrside",
    "property",
    "sourcer",
    "buyers",
    "buyer",
    "first",
    "sourcing"
  ],
  "descriptionTerms": [
    "buyrside",
    "property",
    "sourcer",
    "works",
    "favor",
    "buyers",
    "source",
    "filter",
    "verify",
    "secure",
    "better",
    "opportunities"
  ],
  "missingFromDescription": [
    "buyer",
    "first",
    "sourcing"
  ],
  "score": 87,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Extraction-friendly structure

GEO: Extraction-friendly structure scored 85/100 and needs improvement.

2 Warning

Needs attention

GEO: Extraction-friendly structure

Warning
01

Issue

Missing extraction signals: optional top summary / TL;DR / key takeaways block, table with <thead> only if the page already has tabular/comparative data, ordered list only if the page explains a workflow/process, optional visible FAQ or FAQPage schema.

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: Extraction-friendly structure

Score

85/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

GEO: Extraction-friendly structure scored 85/100 and needs improvement.

Evidence
{
  "hasSummary": false,
  "tableCount": 0,
  "tablesWithHead": 0,
  "tablesMissingThead": [],
  "orderedLists": 0,
  "hasFaq": false,
  "definitionPatterns": 10,
  "schemaBlocks": 1,
  "missingSignals": [
    "optional top summary / TL;DR / key takeaways block",
    "table with <thead> only if the page already has tabular/comparative data",
    "ordered list only if the page explains a workflow/process",
    "optional visible FAQ or FAQPage schema"
  ],
  "score": 85,
  "weight": 24
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer intent coverage

AEO: Answer intent coverage scored 70/100 and needs improvement.

1 Warning

Needs attention

AEO: Answer intent coverage

Warning
01

Issue

Missing likely AI Overview intent sections: what, how, benefits, cost, compare.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Answer intent coverage

Score

70/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Answer intent coverage scored 70/100 and needs improvement.

Evidence
{
  "headings": [
    {
      "text": "Most property buyers do not lack options. They lack signal.",
      "html": "<h2>Most property buyers do not lack options. They lack signal.</h2>"
    },
    {
      "text": "A better buying decision starts before the site visit.",
      "html": "<h2>A better buying decision starts before the site visit.</h2>"
    },
    {
      "text": "Everything serious buyers need.",
      "html": "<h2>Everything serious buyers need.</h2>"
    },
    {
      "text": "Built for buyers, not for pushing inventory.",
      "html": "<h2 class=\"text-gradient\">Built for buyers, not for pushing inventory.</h2>"
    },
    {
      "text": "Proof matters when the decision does.",
      "html": "<h2>Proof matters when the decision does.</h2>"
    },
    {
      "text": "Private Access For Serious Buyers.",
      "html": "<h2>Private Access For Serious Buyers.</h2>"
    },
    {
      "text": "Better sourcing. Better judgment. Better outcomes.",
      "html": "<h2>Better sourcing. Better judgment. Better outcomes.</h2>"
    },
    {
      "text": "If you're serious about buying right, start with better sourcing.",
      "html": "<h2>If you&apos;re serious about buying right, start with better sourcing.</h2>"
    }
  ],
  "expected": [
    {
      "id": "what",
      "label": "What is BuyrSide?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does BuyrSide work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use BuyrSide?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is BuyrSide free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does BuyrSide compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is BuyrSide?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does BuyrSide work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use BuyrSide?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is BuyrSide free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does BuyrSide compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 8
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

AEO: Entity and definition clarity scored 89/100 and needs improvement.

1 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

Entity or definition gaps: buyer, first, sourcing.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Entity and definition clarity

Score

89/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Entity and definition clarity scored 89/100 and needs improvement.

Evidence
{
  "title": "BuyrSide | Property Sourcer For Buyers",
  "h1": "Buyer-first property sourcing.",
  "description": "BuyrSide is a property sourcer that works in favor of property buyers. Source, filter, verify, and secure better property opportunities.",
  "topicOverlap": 0.5714285714285714,
  "definitionCount": 10,
  "topicTerms": [
    "buyrside",
    "property",
    "sourcer",
    "buyers",
    "buyer",
    "first",
    "sourcing"
  ],
  "descriptionTerms": [
    "buyrside",
    "property",
    "sourcer",
    "works",
    "favor",
    "buyers",
    "source",
    "filter",
    "verify",
    "secure",
    "better",
    "opportunities"
  ],
  "missingFromDescription": [
    "buyer",
    "first",
    "sourcing"
  ],
  "score": 89,
  "weight": 18
}

Agent Ease of UseAPIEmerging recommendation

AI context endpoint

AI context endpoint is informational for this page.

Informational

Needs attention

AI context endpoint

Informational
01

Issue

AI context endpoint is informational for this page.

02

Why it matters

A context endpoint gives agents a small, low-latency summary of product purpose, safe actions, and canonical machine-readable resources without scraping the whole site.

Check name

AI context endpoint

Score

100/100

Status

informational

Category

API

Maturity

Emerging recommendation

Goal

Expose a compact API context endpoint agents can fetch before deciding which public API or discovery resource to use.

Result

AI context endpoint is informational for this page.

Validation steps

  1. Fetch to find resource

    AI context endpoint was not found at the expected path.

Evidence
{
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "informational",
      "evidence": {
        "checked": [
          {
            "path": "/api/ai/context",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          },
          {
            "path": "/api/context",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          },
          {
            "path": "/context",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 98790
          }
        ]
      },
      "issue": "AI context endpoint was not found at the expected path.",
      "howToFix": "Publish a concise JSON or Markdown AI context endpoint describing the product, public actions, and machine-readable resources."
    }
  ]
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Query intent coverage

AIO: Query intent coverage is informational for this page.

Informational

Needs attention

AIO: Query intent coverage

Informational
01

Issue

Missing likely AI Overview intent sections: what, how, benefits, cost, compare.

Details

02

Why it matters

AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.

Check name

AIO: Query intent coverage

Score

70/100

Status

informational

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible and useful for Google AI Overviews and AI Mode extraction.

Result

AIO: Query intent coverage is informational for this page.

Evidence
{
  "headings": [
    {
      "text": "Most property buyers do not lack options. They lack signal.",
      "html": "<h2>Most property buyers do not lack options. They lack signal.</h2>"
    },
    {
      "text": "A better buying decision starts before the site visit.",
      "html": "<h2>A better buying decision starts before the site visit.</h2>"
    },
    {
      "text": "Everything serious buyers need.",
      "html": "<h2>Everything serious buyers need.</h2>"
    },
    {
      "text": "Built for buyers, not for pushing inventory.",
      "html": "<h2 class=\"text-gradient\">Built for buyers, not for pushing inventory.</h2>"
    },
    {
      "text": "Proof matters when the decision does.",
      "html": "<h2>Proof matters when the decision does.</h2>"
    },
    {
      "text": "Private Access For Serious Buyers.",
      "html": "<h2>Private Access For Serious Buyers.</h2>"
    },
    {
      "text": "Better sourcing. Better judgment. Better outcomes.",
      "html": "<h2>Better sourcing. Better judgment. Better outcomes.</h2>"
    },
    {
      "text": "If you're serious about buying right, start with better sourcing.",
      "html": "<h2>If you&apos;re serious about buying right, start with better sourcing.</h2>"
    }
  ],
  "expected": [
    {
      "id": "what",
      "label": "What is BuyrSide?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does BuyrSide work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use BuyrSide?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is BuyrSide free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does BuyrSide compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is BuyrSide?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does BuyrSide work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use BuyrSide?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is BuyrSide free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does BuyrSide compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 4
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Q&A and FAQ opportunities

GEO: Q&A and FAQ opportunities is informational for this page.

Informational

Needs attention

GEO: Q&A and FAQ opportunities

Informational
01

Issue

8 h2 heading(s) are not phrased as questions; this is optional and only useful where Q&A wording is natural. No visible FAQ or FAQPage schema was detected; this is optional unless the page answers common questions.

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: Q&A and FAQ opportunities

Score

75/100

Status

informational

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

GEO: Q&A and FAQ opportunities is informational for this page.

Evidence
{
  "h2Count": 8,
  "questionH2s": 0,
  "hasFaq": false,
  "nonQuestionH2s": [
    {
      "index": 1,
      "text": "Most property buyers do not lack options. They lack signal.",
      "isQuestion": false,
      "html": "<h2>Most property buyers do not lack options. They lack signal.</h2>"
    },
    {
      "index": 2,
      "text": "A better buying decision starts before the site visit.",
      "isQuestion": false,
      "html": "<h2>A better buying decision starts before the site visit.</h2>"
    },
    {
      "index": 3,
      "text": "Everything serious buyers need.",
      "isQuestion": false,
      "html": "<h2>Everything serious buyers need.</h2>"
    },
    {
      "index": 4,
      "text": "Built for buyers, not for pushing inventory.",
      "isQuestion": false,
      "html": "<h2 class=\"text-gradient\">Built for buyers, not for pushing inventory.</h2>"
    },
    {
      "index": 5,
      "text": "Proof matters when the decision does.",
      "isQuestion": false,
      "html": "<h2>Proof matters when the decision does.</h2>"
    },
    {
      "index": 6,
      "text": "Private Access For Serious Buyers.",
      "isQuestion": false,
      "html": "<h2>Private Access For Serious Buyers.</h2>"
    },
    {
      "index": 7,
      "text": "Better sourcing. Better judgment. Better outcomes.",
      "isQuestion": false,
      "html": "<h2>Better sourcing. Better judgment. Better outcomes.</h2>"
    },
    {
      "index": 8,
      "text": "If you're serious about buying right, start with better sourcing.",
      "isQuestion": false,
      "html": "<h2>If you&apos;re serious about buying right, start with better sourcing.</h2>"
    }
  ],
  "score": 75,
  "weight": 4
}

AI DiscoverabilityDiscoverabilityEstablished

IndexNow key

IndexNow key is informational for this page.

Informational

Needs attention

IndexNow key

Informational
01

Issue

IndexNow key is informational for this page.

02

Why it matters

IndexNow lets sites notify participating search engines about changed URLs, but ownership verification requires a UTF-8 key file whose filename matches the key.

Check name

IndexNow key

Score

100/100

Status

informational

Category

Discoverability

Maturity

Established

Goal

Verify that IndexNow ownership key placement is detectable when the site advertises it.

Result

IndexNow key is informational for this page.

Validation steps

  1. Find advertised IndexNow key location

    No IndexNow key location was advertised in HTML or Link headers.

  2. Fetch and validate IndexNow key file

    No discoverable IndexNow key file was found.

Evidence
{
  "steps": [
    {
      "id": "advertised-location",
      "title": "Find advertised IndexNow key location",
      "status": "informational",
      "evidence": {
        "advertised": []
      },
      "issue": "No IndexNow key location was advertised in HTML or Link headers.",
      "howToFix": "Advertise the key location with rel=\"indexnow-key\" or meta name=\"indexnow-key-location\" if you want scanners to verify it."
    },
    {
      "id": "fetch-key",
      "title": "Fetch and validate IndexNow key file",
      "status": "informational",
      "evidence": {
        "advertised": [],
        "checked": []
      },
      "issue": "No discoverable IndexNow key file was found.",
      "howToFix": "Host a UTF-8 text file named {key}.txt whose body exactly matches the key."
    }
  ]
}

Performance and AccessibilityAccessibilityBrowser audit

Background and foreground colors do not have a sufficient contrast ratio.

100 Fail

Check name

Background and foreground colors do not have a sufficient contrast ratio.

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast](https://dequeuniversity.com/rules/axe/4.10/color-contrast).

Evidence
{
  "description": "Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast](https://dequeuniversity.com/rules/axe/4.10/color-contrast)."
}

Performance and AccessibilityPerformanceBrowser audit

Reduce JavaScript execution time

33 Fail

Check name

Reduce JavaScript execution time

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

2.7 s

Fix guidance

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to reduce Javascript execution time](https://developer.chrome.com/docs/lighthouse/performance/bootup-time/).

Evidence
{
  "displayValue": "2.7 s",
  "description": "Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to reduce Javascript execution time](https://developer.chrome.com/docs/lighthouse/performance/bootup-time/).",
  "numericValue": 2662.191999999998
}

Performance and AccessibilityPerformanceBrowser audit

Loading performance

17 Fail

Check name

Loading performance

Score

48/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

Review the grouped loading performance checks and improve the failing sub-checks listed in evidence.

Evidence
{
  "checks": [
    {
      "id": "first-contentful-paint",
      "title": "First Contentful Paint",
      "score": 61,
      "displayValue": "1.4 s",
      "numericValue": 1409.4823000000001
    },
    {
      "id": "largest-contentful-paint",
      "title": "Largest Contentful Paint",
      "score": 18,
      "displayValue": "3.9 s",
      "numericValue": 3871.4823
    },
    {
      "id": "speed-index",
      "title": "Speed Index",
      "score": 63,
      "displayValue": "2.0 s",
      "numericValue": 1968.0720714632553
    },
    {
      "id": "total-blocking-time",
      "title": "Total Blocking Time",
      "score": 0,
      "displayValue": "2,160 ms",
      "numericValue": 2159.4999999999995
    },
    {
      "id": "max-potential-fid",
      "title": "Max Potential First Input Delay",
      "score": 0,
      "displayValue": "1,110 ms",
      "numericValue": 1109
    },
    {
      "id": "server-response-time",
      "title": "Initial server response time was short",
      "score": 100,
      "displayValue": "Root document took 40 ms",
      "numericValue": 42.324
    },
    {
      "id": "interactive",
      "title": "Time to Interactive",
      "score": 42,
      "displayValue": "4.9 s",
      "numericValue": 4930.4323
    },
    {
      "id": "uses-rel-preconnect",
      "title": "Preconnect to required origins",
      "score": 100,
      "displayValue": "",
      "numericValue": 0
    },
    {
      "id": "network-rtt",
      "title": "Network Round Trip Times",
      "score": 100,
      "displayValue": "0 ms",
      "numericValue": 0.0317
    },
    {
      "id": "largest-contentful-paint-element",
      "title": "Largest Contentful Paint element",
      "score": 0,
      "displayValue": "3,870 ms"
    }
  ]
}

Performance and AccessibilityPerformanceBrowser audit

Image optimization

17 Fail

Check name

Image optimization

Score

50/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

Review the grouped image optimization checks and improve the failing sub-checks listed in evidence.

Evidence
{
  "checks": [
    {
      "id": "image-aspect-ratio",
      "title": "Displays images with correct aspect ratio",
      "score": 100
    },
    {
      "id": "uses-responsive-images",
      "title": "Properly size images",
      "score": 0,
      "displayValue": "Est savings of 75 KiB",
      "numericValue": 370
    }
  ]
}

Improve Your Score

Send the scan details to a professional with the required report context attached.

Score history

Public scan score over time

Public reports for this website origin. Select any point or report link to open that canonical report.

1 reports
Public score history report links
Scan dateScoreReadinessReport
45/100Level 2, Agent-LimitedCurrent report
Report ID 785dccc5-7279-49c8-ac19-20a1a41c1976. Scanned Jun 4, 2026, 12:27 AM.
buyrside.com AI SEO Report: 45/100 (Level 2, Agent-Limited)