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

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability30%Agent Easeof Use6%Security& Trust80%GEO, AIO, AEO69%SEO92%Performance& Accessibility71%
  • AI Discoverability 30 out of 100
  • Agent Ease of Use 6 out of 100
  • Security & Trust 80 out of 100
  • GEO, AIO and AEO 69 out of 100
  • SEO 92 out of 100
  • Performance and Accessibility 71 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Zillow: Real Estate, Apartments, Mortgages & Home Values favicon

Zillow: Real Estate, Apartments, Mortgages & Home Values

The leading real estate marketplace. Search millions of for-sale and rental listings, compare Zestimate® home values and connect with local professionals.

Next step

Turn this report into a fix workflow

25 failed checks are ready to move into MCP or CLI remediation. Generate a repair prompt, connect the scanner to your coding agent, or open the integration docs before your next rescan.

Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
30
Priority fix6161View details
Discoverability
33
Priority fix360View details
Content Readiness
25
Priority fix271View details
Bot Access Control
33
Priority fix130View details
Agent Ease of Use
6
Priority fix4293View details
API
0
Priority fix060View details
Auth
Not Applicable
Not Applicable070View details
MCP
13
Priority fix062View details
Skill Discovery
5
Priority fix0101View details
Agent Commerce
Not Applicable
Not Applicable400
GEO, AIO and AEO
69
Needs work5311View details
GEO Readiness
77
Mostly ready104
AIO Readiness
62
Needs work322View details
AEO Readiness
67
Needs work115View details
SEO
92
Strong1010View details
SEO
92
Strong1010View details
Security & Trust
80
Mostly ready810View details
Security & Trust
80
Mostly ready410View details
AI Training Exposure
Not Applicable
Not Applicable400
Performance and Accessibility
71
Needs work2250View details
Performance
60
Needs work1250View details
Accessibility
90
Strong1000

Prioritized recommendations

Issues ranked by score impact

47 items need attention

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy is missing or incomplete.

100 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": "frame-ancestors none"
}

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": "application/xml"
      },
      "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": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message><Key>.well-known/api-catalog</Key><RequestId>G5MJQH8KPAR0DSXA</RequestId><HostId>vBWjqNaNt7WSSFgykT2dG24ZZaMh8lkIvxQ3ol0tum4riFT6uJ/o74uXjPVJI/axa8BnYGs06xA=</HostId></Error>"
      },
      "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 DiscoverabilityBot Access ControlInformational

Content Signal

Content Signal is missing or incomplete.

50 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
}

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><head><link id=\"zsg.core\" rel=\"stylesheet\" media=\"all\" href=\"https://www.zillowstatic.com/static-zsg/LATEST/static-zsg/zsg/zsg-core.css\"/><link id=\"zsg.opt\" rel=\"stylesheet\" media=\"all\" href=\"https://www.zillowstatic.com/static-zsg/LATEST/static-zsg/zsg/zsg-opt.css\"/><script id=\"scripts.pfs.appInfo\">\n        if (typeof Object.assign === 'function') {\n            window.appInfo = Object.assign(\n                typeof window.appInfo === 'object' ? window.appInfo : {},\n                {\"@zillow/page-frame-content\":\"master.5304.151b3ede\"}\n            );\n        }\n    </script><script id=\"scripts.ua\">(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){\n        (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),\n        m=s.getEle"
          },
          {
            "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><head><link id=\"zsg.core\" rel=\"stylesheet\" media=\"all\" href=\"https://www.zillowstatic.com/static-zsg/LATEST/static-zsg/zsg/zsg-core.css\"/><link id=\"zsg.opt\" rel=\"stylesheet\" media=\"all\" href=\"https://www.zillowstatic.com/static-zsg/LATEST/static-zsg/zsg/zsg-opt.css\"/><script id=\"scripts.pfs.appInfo\">\n        if (typeof Object.assign === 'function') {\n            window.appInfo = Object.assign(\n                typeof window.appInfo === 'object' ? window.appInfo : {},\n                {\"@zillow/page-frame-content\":\"master.5304.151b3ede\"}\n            );\n        }\n    </script><script id=\"scripts.ua\">(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){\n        (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),\n        m=s.getEle"
          },
          {
            "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><head><link id=\"zsg.core\" rel=\"stylesheet\" media=\"all\" href=\"https://www.zillowstatic.com/static-zsg/LATEST/static-zsg/zsg/zsg-core.css\"/><link id=\"zsg.opt\" rel=\"stylesheet\" media=\"all\" href=\"https://www.zillowstatic.com/static-zsg/LATEST/static-zsg/zsg/zsg-opt.css\"/><script id=\"scripts.pfs.appInfo\">\n        if (typeof Object.assign === 'function') {\n            window.appInfo = Object.assign(\n                typeof window.appInfo === 'object' ? window.appInfo : {},\n                {\"@zillow/page-frame-content\":\"master.5304.151b3ede\"}\n            );\n        }\n    </script><script id=\"scripts.ua\">(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){\n        (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),\n        m=s.getEle"
          },
          {
            "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><head><link id=\"zsg.core\" rel=\"stylesheet\" media=\"all\" href=\"https://www.zillowstatic.com/static-zsg/LATEST/static-zsg/zsg/zsg-core.css\"/><link id=\"zsg.opt\" rel=\"stylesheet\" media=\"all\" href=\"https://www.zillowstatic.com/static-zsg/LATEST/static-zsg/zsg/zsg-opt.css\"/><script id=\"scripts.pfs.appInfo\">\n        if (typeof Object.assign === 'function') {\n            window.appInfo = Object.assign(\n                typeof window.appInfo === 'object' ? window.appInfo : {},\n                {\"@zillow/page-frame-content\":\"master.5304.151b3ede\"}\n            );\n        }\n    </script><script id=\"scripts.ua\">(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){\n        (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),\n        m=s.getEle"
          },
          {
            "path": "/api/openapi.json",
            "statusCode": 404,
            "contentType": null,
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": true,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": ""
          },
          {
            "path": "/api/swagger.json",
            "statusCode": 404,
            "contentType": null,
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": true,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": ""
          },
          {
            "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><head><link id=\"zsg.core\" rel=\"stylesheet\" media=\"all\" href=\"https://www.zillowstatic.com/static-zsg/LATEST/static-zsg/zsg/zsg-core.css\"/><link id=\"zsg.opt\" rel=\"stylesheet\" media=\"all\" href=\"https://www.zillowstatic.com/static-zsg/LATEST/static-zsg/zsg/zsg-opt.css\"/><script id=\"scripts.pfs.appInfo\">\n        if (typeof Object.assign === 'function') {\n            window.appInfo = Object.assign(\n                typeof window.appInfo === 'object' ? window.appInfo : {},\n                {\"@zillow/page-frame-content\":\"master.5304.151b3ede\"}\n            );\n        }\n    </script><script id=\"scripts.ua\">(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){\n        (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),\n        m=s.getEle"
          }
        ]
      },
      "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 ControlInformational

Web Bot Auth request signing

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

50 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": "application/xml",
            "length": 336
          }
        ]
      },
      "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."
    }
  ]
}

AI DiscoverabilityDiscoverabilityEstablished

High-value schema types

High-value schema types is missing or incomplete.

25 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": []
}

AI DiscoverabilityDiscoverabilityEstablished

JSON-LD present

JSON-LD present is missing or incomplete.

25 Fail

Needs attention

JSON-LD present

Failed check
01

Issue

No JSON-LD blocks found.

02

Why it matters

JSON-LD is a low-friction structured data format that agents can extract without interpreting page presentation or microdata markup.

Check name

JSON-LD present

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Expose schema.org JSON-LD so AI search systems can parse page entities.

Result

JSON-LD present is missing or incomplete.

Evidence
{
  "blocks": 0,
  "validBlocks": 0,
  "schemaContextBlocks": 0,
  "errors": [],
  "documents": [],
  "nodes": []
}

AI DiscoverabilityDiscoverabilityEstablished

Link headers

Link headers failed at "Find useful Link headers".

25 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."
    }
  ]
}

AI DiscoverabilityContent ReadinessEmerging recommendation

llms.txt

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

25 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": 432692
          },
          {
            "path": "/llms-full.txt",
            "statusCode": 404,
            "contentType": "text/html;charset=utf-8",
            "length": 432692
          }
        ]
      },
      "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".

25 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 "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": "Accept-Encoding"
      },
      "issue": "Markdown negotiation is missing Vary: Accept; current Vary header is \"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": 50309,
        "excerpt": "<!DOCTYPE html><html lang=\"en\"><head><link rel=\"preconnect\" href=\"https://www.zillowstatic.com/\" crossorigin=\"anonymous\"/><link rel=\"preload\" href=\"//www.zillowstatic.com/s3/constellation-website/public/shared/fonts/open-sans/LATEST/open-sa",
        "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."
    }
  ]
}

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": "application/xml",
            "length": 323
          },
          {
            "path": "/.well-known/mcp/server-cards.json",
            "statusCode": 404,
            "contentType": "application/xml",
            "length": 324
          },
          {
            "path": "/.well-known/mcp.json",
            "statusCode": 404,
            "contentType": "application/xml",
            "length": 311
          }
        ]
      },
      "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": 432692
          },
          {
            "path": "/.well-known/mcp.json",
            "statusCode": 404,
            "contentType": "application/xml",
            "length": 311
          },
          {
            "path": "/.well-known/mcp/server-card.json",
            "statusCode": 404,
            "contentType": "application/xml",
            "length": 323
          }
        ]
      },
      "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."
    }
  ]
}

AI DiscoverabilityDiscoverabilityEstablished

Organization / WebSite schema

Organization / WebSite schema is missing or incomplete.

25 Fail

Needs attention

Organization / WebSite schema

Failed check
01

Issue

Neither Organization nor WebSite schema types were found in JSON-LD.

02

Why it matters

Organization and WebSite schema help agents identify the publisher, canonical site identity, logo, and related profiles for attribution.

Check name

Organization / WebSite schema

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Identify the site owner and website entity in structured data.

Result

Organization / WebSite schema is missing or incomplete.

Evidence
{
  "found": [],
  "allTypes": []
}

AI DiscoverabilityContent ReadinessEstablished

Semantic HTML

Semantic HTML is missing or incomplete.

25 Fail

Needs attention

Semantic HTML

Failed check
01

Issue

Semantic HTML is incomplete: missing <main> landmark; skipped heading levels.

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": false,
  "nav": true,
  "footer": true,
  "meaningfulH1": true,
  "headingOrder": false,
  "accessibleLinks": true,
  "accessibleButtons": true,
  "imageAltCoverage": true,
  "formAutocompleteCoverage": true,
  "details": {
    "inaccessibleLinks": [],
    "inaccessibleButtons": [],
    "missingAutocompleteInputs": [],
    "imagesMissingAlt": [],
    "skippedHeadingLevels": [
      "h1: Rentals. Homes. Agents. Loans.",
      "h6: About Zillow's Recommendations"
    ]
  },
  "counts": {
    "h1": 1,
    "headings": 2,
    "links": 271,
    "inaccessibleLinks": 0,
    "buttons": 17,
    "inaccessibleButtons": 0,
    "images": 7,
    "imagesWithAlt": 7,
    "autocompleteInputs": 1,
    "inputsWithAutocomplete": 1,
    "missingAutocompleteInputs": 0
  }
}

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": "application/xml",
            "length": 314
          },
          {
            "path": "/webmcp.json",
            "statusCode": 404,
            "contentType": "text/html;charset=utf-8",
            "length": 432692
          },
          {
            "path": "/mcp.json",
            "statusCode": 404,
            "contentType": "text/html;charset=utf-8",
            "length": 432692
          }
        ]
      },
      "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."
    }
  ]
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

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

20 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": "application/xml",
            "length": 298
          },
          {
            "path": "/.well-known/a2a/agent-card.json",
            "statusCode": 404,
            "contentType": "application/xml",
            "length": 302
          },
          {
            "path": "/agent-card.json",
            "statusCode": 404,
            "contentType": "text/html;charset=utf-8",
            "length": 432692
          }
        ]
      },
      "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".

20 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": "application/xml",
            "length": 306
          },
          {
            "path": "/.well-known/skills/index.json",
            "statusCode": 404,
            "contentType": "application/xml",
            "length": 320
          }
        ]
      },
      "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".

20 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": "application/xml",
            "length": 293
          },
          {
            "path": "/agent.json",
            "statusCode": 404,
            "contentType": "text/html;charset=utf-8",
            "length": 432692
          }
        ]
      },
      "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".

20 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": "application/xml",
            "length": 294
          },
          {
            "path": "/agents.json",
            "statusCode": 404,
            "contentType": "text/html;charset=utf-8",
            "length": 432692
          }
        ]
      },
      "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."
    }
  ]
}

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is partially implemented.

19 Warning

Needs attention

Content freshness signals

Warning
01

Issue

Content freshness signals are incomplete: missing Last-Modified HTTP header; missing dateModified/datePublished in JSON-LD.

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

25/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

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

Result

Content freshness signals is partially implemented.

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

Agent Ease of UseSkill DiscoveryEmerging recommendation

DNS-AID Agent Discovery

DNS-AID Agent Discovery failed at "Resolve DNS-AID SVCB/HTTPS records".

15 Fail

Needs attention

DNS-AID Agent Discovery

Failed check
01

Issue

No DNS-AID entrypoint records were found under _agents.

02

Why it matters

DNS-AID lets agents discover index, A2A, and other agent entrypoints before fetching HTTP metadata, while DNSSEC can authenticate the discovery zone.

Check name

DNS-AID Agent Discovery

Score

25/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish DNS for AI Discovery records under _agents for DNS-based agent entrypoint discovery.

Result

DNS-AID Agent Discovery failed at "Resolve DNS-AID SVCB/HTTPS records".

Validation steps

  1. Resolve DNS-AID SVCB/HTTPS records

    No DNS-AID entrypoint records were found under _agents.

  2. Validate alpn and endpoint parameters

    Include alpn and endpoint service parameters in each DNS-AID record so agents know the protocol and target entrypoint.

  3. Check DNSSEC material

    DNSSEC material was not visible for the hostname or parent zone from this resolver.

Evidence
{
  "failedStep": "svcb-https-records",
  "steps": [
    {
      "id": "svcb-https-records",
      "title": "Resolve DNS-AID SVCB/HTTPS records",
      "status": "fail",
      "evidence": {
        "hostname": "www.zillow.com",
        "probes": [
          {
            "name": "_index._agents.www.zillow.com",
            "found": false,
            "recordCount": 1,
            "records": [],
            "hasAlpn": false,
            "hasEndpoint": false
          },
          {
            "name": "_a2a._agents.www.zillow.com",
            "found": false,
            "recordCount": 1,
            "records": [],
            "hasAlpn": false,
            "hasEndpoint": false
          }
        ]
      },
      "issue": "No DNS-AID entrypoint records were found under _agents.",
      "howToFix": "Publish ServiceMode SVCB/HTTPS records such as _index._agents.example.com or _a2a._agents.example.com."
    },
    {
      "id": "service-params",
      "title": "Validate alpn and endpoint parameters",
      "status": "informational",
      "evidence": {
        "discovered": []
      },
      "howToFix": "Include alpn and endpoint service parameters in each DNS-AID record so agents know the protocol and target entrypoint."
    },
    {
      "id": "dnssec",
      "title": "Check DNSSEC material",
      "status": "warning",
      "evidence": {
        "hasDnssecMaterial": false,
        "checked": [
          {
            "name": "www.zillow.com",
            "dnssecTypes": [],
            "dnssecRecordCount": 0
          },
          {
            "name": "zillow.com",
            "dnssecTypes": [],
            "dnssecRecordCount": 0
          }
        ]
      },
      "issue": "DNSSEC material was not visible for the hostname or parent zone from this resolver.",
      "howToFix": "Sign the public discovery zone with DNSSEC so validating resolvers can return authenticated data."
    }
  ]
}

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 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": 289,
        "interactiveWithTags": 0,
        "totalCount": 290,
        "taggedCount": 0,
        "dataMcpToolCount": 0,
        "dataMcpTools": [],
        "coverage": 0,
        "annotationIssues": [
          "<input> is missing a name attribute.",
          "<input> 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": 2,
        "issues": [
          "<input> is missing a name attribute.",
          "<input> 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 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": 289,
        "interactiveWithTags": 0,
        "totalCount": 290,
        "taggedCount": 0,
        "dataMcpToolCount": 0,
        "dataMcpTools": [],
        "coverage": 0,
        "annotationIssues": [
          "<input> is missing a name attribute.",
          "<input> 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": 289,
    "interactiveWithTags": 0,
    "totalCount": 290,
    "taggedCount": 0,
    "dataMcpToolCount": 0,
    "dataMcpTools": [],
    "coverage": 0,
    "annotationIssues": [
      "<input> is missing a name attribute.",
      "<input> 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: Visible structured data match

AIO: Visible structured data match scored 0/100 and needs a fix.

12 Fail

Needs attention

AIO: Visible structured data match

Failed check
01

Issue

No JSON-LD structured data was detected.

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: Visible structured data match

Score

0/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: Visible structured data match scored 0/100 and needs a fix.

Evidence
{
  "schemaCount": 0,
  "mismatches": [],
  "score": 0,
  "weight": 18
}

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": "/z/corp/about/",
      "text": "About",
      "html": "<a href=\"/z/corp/about/\" class=\"StyledTextButton-c11n-8-112-0__sc-1nwmfqo-0 lcrsxX\" tabindex=\"0\" data-za-category=\"!inherit\" data-za-action=\"!inherit\" data-za-label=\"About\">About</a>"
    },
    {
      "href": "https://delivery.digitallibrary.zillowgroup.com/public/TRECNO.IABS1-1INFORMATIONABOUTBROKERAGESERVICES_pdf_Original.pdf",
      "text": "Information about brokerage services",
      "html": "<a href=\"https://delivery.digitallibrary.zillowgroup.com/public/TRECNO.IABS1-1INFORMATIONABOUTBROKERAGESERVICES_pdf_Original.pdf\" rel=\"nofollow\" class=\"Anchor-c11n-8-112-0__sc-hn4bge-0 ivHafp\">Information about brokerage services</a>"
    }
  ],
  "contactLinks": [
    {
      "href": "https://www.zillow.help/",
      "text": "Get help",
      "html": "<a class=\"Anchor-c11n-8-112-0__sc-hn4bge-0 pfs__sc-1dpbk03-0 ivHafp dGfGKQ\" href=\"https://www.zillow.help/\" data-za-action=\"Get help\" data-za-category=\"!inherit\" data-active=\"false\" data-zg-role=\"section-title\"><span>Get help<!-- --> </span></a>"
    },
    {
      "href": "https://www.zillow.help/",
      "text": "Help",
      "html": "<a href=\"https://www.zillow.help/\" class=\"StyledTextButton-c11n-8-112-0__sc-1nwmfqo-0 lcrsxX\" tabindex=\"0\" data-za-category=\"!inherit\" data-za-action=\"!inherit\" data-za-label=\"Help\">Help</a>"
    },
    {
      "href": "https://www.zillow.help/contact-us",
      "text": "let us know",
      "html": "<a href=\"https://www.zillow.help/contact-us\" rel=\"nofollow\" class=\"Anchor-c11n-8-112-0__sc-hn4bge-0 ivHafp\">let us know</a>"
    },
    {
      "href": "https://www.zillow.com/c/info/contact-us/",
      "text": "Contact Zillow, Inc. Brokerage",
      "html": "<a href=\"https://www.zillow.com/c/info/contact-us/\" class=\"Anchor-c11n-8-112-0__sc-hn4bge-0 pfs__chkjii-0 ivHafp eWHYiW\">Contact Zillow, Inc. Brokerage</a>"
    }
  ],
  "privacyLinks": [
    {
      "href": "/careers/global-applicant-privacy-notice/",
      "text": "Applicant Privacy Notice",
      "html": "<a href=\"/careers/global-applicant-privacy-notice/\" class=\"StyledTextButton-c11n-8-112-0__sc-1nwmfqo-0 lcrsxX\" tabindex=\"0\" data-za-category=\"!inherit\" data-za-action=\"!inherit\" data-za-label=\"Applicant Privacy Notice\">Applicant Privacy Notice</a>"
    },
    {
      "href": "https://www.zillow.com/corporate/terms-of-use/",
      "text": "Terms of use",
      "html": "<a href=\"https://www.zillow.com/corporate/terms-of-use/\" class=\"StyledTextButton-c11n-8-112-0__sc-1nwmfqo-0 lcrsxX\" tabindex=\"0\" data-za-category=\"!inherit\" data-za-action=\"!inherit\" data-za-label=\"Terms of use\">Terms of use</a>"
    },
    {
      "href": "https://www.zillow.com/corporate/zg-privacy-notice/",
      "text": "Privacy Notice",
      "html": "<a href=\"https://www.zillow.com/corporate/zg-privacy-notice/\" class=\"StyledTextButton-c11n-8-112-0__sc-1nwmfqo-0 lcrsxX\" tabindex=\"0\" data-za-category=\"!inherit\" data-za-action=\"!inherit\" data-za-label=\"Privacy Notice\">Privacy Notice</a>"
    },
    {
      "href": "https://www.zillowgroup.com/zg-privacy-policy/#third-party",
      "text": "Ad Choices",
      "html": "<a href=\"https://www.zillowgroup.com/zg-privacy-policy/#third-party\" class=\"StyledTextButton-c11n-8-112-0__sc-1nwmfqo-0 lcrsxX\" tabindex=\"0\" data-za-category=\"!inherit\" data-za-action=\"!inherit\" data-za-label=\"Ad Choices\">Ad Choices</a>"
    },
    {
      "href": "https://privacy.zillowgroup.com/cookie",
      "text": "Do Not Sell or Share My Personal Information →",
      "html": "<a id=\"doNotSell\" href=\"https://privacy.zillowgroup.com/cookie\" aria-label=\"Do not sell or share my personal information\" class=\"StyledTextButton-c11n-8-112-0__sc-1nwmfqo-0 iDsNNg\">Do Not Sell or Share My Personal Information<span aria-hidden=\"true\"> &#x2192;</span></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": "/z/corp/about/",
      "text": "About",
      "html": "<a href=\"/z/corp/about/\" class=\"StyledTextButton-c11n-8-112-0__sc-1nwmfqo-0 lcrsxX\" tabindex=\"0\" data-za-category=\"!inherit\" data-za-action=\"!inherit\" data-za-label=\"About\">About</a>"
    },
    {
      "href": "https://delivery.digitallibrary.zillowgroup.com/public/TRECNO.IABS1-1INFORMATIONABOUTBROKERAGESERVICES_pdf_Original.pdf",
      "text": "Information about brokerage services",
      "html": "<a href=\"https://delivery.digitallibrary.zillowgroup.com/public/TRECNO.IABS1-1INFORMATIONABOUTBROKERAGESERVICES_pdf_Original.pdf\" rel=\"nofollow\" class=\"Anchor-c11n-8-112-0__sc-hn4bge-0 ivHafp\">Information about brokerage services</a>"
    }
  ],
  "contactLinks": [
    {
      "href": "https://www.zillow.help/",
      "text": "Get help",
      "html": "<a class=\"Anchor-c11n-8-112-0__sc-hn4bge-0 pfs__sc-1dpbk03-0 ivHafp dGfGKQ\" href=\"https://www.zillow.help/\" data-za-action=\"Get help\" data-za-category=\"!inherit\" data-active=\"false\" data-zg-role=\"section-title\"><span>Get help<!-- --> </span></a>"
    },
    {
      "href": "https://www.zillow.help/",
      "text": "Help",
      "html": "<a href=\"https://www.zillow.help/\" class=\"StyledTextButton-c11n-8-112-0__sc-1nwmfqo-0 lcrsxX\" tabindex=\"0\" data-za-category=\"!inherit\" data-za-action=\"!inherit\" data-za-label=\"Help\">Help</a>"
    },
    {
      "href": "https://www.zillow.help/contact-us",
      "text": "let us know",
      "html": "<a href=\"https://www.zillow.help/contact-us\" rel=\"nofollow\" class=\"Anchor-c11n-8-112-0__sc-hn4bge-0 ivHafp\">let us know</a>"
    },
    {
      "href": "https://www.zillow.com/c/info/contact-us/",
      "text": "Contact Zillow, Inc. Brokerage",
      "html": "<a href=\"https://www.zillow.com/c/info/contact-us/\" class=\"Anchor-c11n-8-112-0__sc-hn4bge-0 pfs__chkjii-0 ivHafp eWHYiW\">Contact Zillow, Inc. Brokerage</a>"
    }
  ],
  "privacyLinks": [
    {
      "href": "/careers/global-applicant-privacy-notice/",
      "text": "Applicant Privacy Notice",
      "html": "<a href=\"/careers/global-applicant-privacy-notice/\" class=\"StyledTextButton-c11n-8-112-0__sc-1nwmfqo-0 lcrsxX\" tabindex=\"0\" data-za-category=\"!inherit\" data-za-action=\"!inherit\" data-za-label=\"Applicant Privacy Notice\">Applicant Privacy Notice</a>"
    },
    {
      "href": "https://www.zillow.com/corporate/terms-of-use/",
      "text": "Terms of use",
      "html": "<a href=\"https://www.zillow.com/corporate/terms-of-use/\" class=\"StyledTextButton-c11n-8-112-0__sc-1nwmfqo-0 lcrsxX\" tabindex=\"0\" data-za-category=\"!inherit\" data-za-action=\"!inherit\" data-za-label=\"Terms of use\">Terms of use</a>"
    },
    {
      "href": "https://www.zillow.com/corporate/zg-privacy-notice/",
      "text": "Privacy Notice",
      "html": "<a href=\"https://www.zillow.com/corporate/zg-privacy-notice/\" class=\"StyledTextButton-c11n-8-112-0__sc-1nwmfqo-0 lcrsxX\" tabindex=\"0\" data-za-category=\"!inherit\" data-za-action=\"!inherit\" data-za-label=\"Privacy Notice\">Privacy Notice</a>"
    },
    {
      "href": "https://www.zillowgroup.com/zg-privacy-policy/#third-party",
      "text": "Ad Choices",
      "html": "<a href=\"https://www.zillowgroup.com/zg-privacy-policy/#third-party\" class=\"StyledTextButton-c11n-8-112-0__sc-1nwmfqo-0 lcrsxX\" tabindex=\"0\" data-za-category=\"!inherit\" data-za-action=\"!inherit\" data-za-label=\"Ad Choices\">Ad Choices</a>"
    },
    {
      "href": "https://privacy.zillowgroup.com/cookie",
      "text": "Do Not Sell or Share My Personal Information →",
      "html": "<a id=\"doNotSell\" href=\"https://privacy.zillowgroup.com/cookie\" aria-label=\"Do not sell or share my personal information\" class=\"StyledTextButton-c11n-8-112-0__sc-1nwmfqo-0 iDsNNg\">Do Not Sell or Share My Personal Information<span aria-hidden=\"true\"> &#x2192;</span></a>"
    }
  ],
  "score": 40,
  "weight": 22
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Extraction-friendly structure

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

5 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, JSON-LD structured data.

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

60/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 60/100 and needs improvement.

Evidence
{
  "hasSummary": false,
  "tableCount": 0,
  "tablesWithHead": 0,
  "tablesMissingThead": [],
  "orderedLists": 0,
  "hasFaq": false,
  "definitionPatterns": 2,
  "schemaBlocks": 0,
  "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",
    "JSON-LD structured data"
  ],
  "score": 60,
  "weight": 24
}

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": 0,
  "questionH2s": [],
  "hasFaq": false,
  "score": 50,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Entity clarity

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

3 Warning

Needs attention

GEO: Entity clarity

Warning
01

Issue

Title/H1 terms missing from description: zillow, apartments, mortgages, rentals, homes, agents, loans.

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

81/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 81/100 and needs improvement.

Evidence
{
  "title": "Zillow: Real Estate, Apartments, Mortgages & Home Values",
  "h1": "Rentals. Homes. Agents. Loans.",
  "description": "The leading real estate marketplace. Search millions of for-sale and rental listings, compare Zestimate® home values and connect with local professionals.",
  "topicOverlap": 0.36363636363636365,
  "topicTerms": [
    "zillow",
    "real",
    "estate",
    "apartments",
    "mortgages",
    "home",
    "values",
    "rentals",
    "homes",
    "agents",
    "loans"
  ],
  "descriptionTerms": [
    "leading",
    "real",
    "estate",
    "marketplace",
    "search",
    "millions",
    "sale",
    "rental",
    "listings",
    "compare",
    "zestimate",
    "home",
    "values",
    "connect",
    "local",
    "professionals"
  ],
  "missingFromDescription": [
    "zillow",
    "apartments",
    "mortgages",
    "rentals",
    "homes",
    "agents",
    "loans"
  ],
  "score": 81,
  "weight": 28
}

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

2 explanatory paragraph(s) could be stronger for citation or AI extraction.

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": 3,
  "citablePassages": 1,
  "failingCandidateParagraphs": [
    {
      "index": 213,
      "heading": "H6: About Zillow's Recommendations",
      "text": "Zillow Group is committed to ensuring digital accessibility for individuals with disabilities. We are continuously working to improve the accessibility of our web experience for everyone, and we welcome feedback and accommodation requests. If you wish to report an issue or seek an accommodation, please let us know.",
      "words": 48,
      "hasEvidence": true,
      "reasons": [
        "Too short for a citation-ready passage (48 words; target 80-220)."
      ],
      "html": "<p class=\"Text-c11n-8-112-0__sc-aiai24-0 ezPwpO\">Zillow Group is committed to ensuring digital accessibility for individuals with disabilities. We are continuously working to improve the accessibility of our web experience for everyone, and we welcome feedback and accommodation requests. If you wish to report an issue or seek an accommodation, please <a href=\"https://www.zillow.help/contact-us\" rel=\"nofollow\" class=\"Anchor-c11n-8-112-0__sc-hn4bge-0 ivHafp\">let us know</a>.</p>"
    },
    {
      "index": 215,
      "heading": "H6: About Zillow's Recommendations",
      "text": "For listings in Canada, the trademarks REALTOR®, REALTORS®, and the REALTOR® logo are controlled by The Canadian Real Estate Association (CREA) and identify real estate professionals who are members of CREA. The trademarks MLS®, Multiple Listing Service® and the associated logos are owned by CREA and identify the quality of services provided by real estate professionals who are members of CREA. Used under license.",
      "words": 64,
      "hasEvidence": false,
      "reasons": [
        "Too short for a citation-ready passage (64 words; target 80-220).",
        "Missing a named source, statistic, date, percentage, report, or other evidence signal."
      ],
      "html": "<p class=\"Text-c11n-8-112-0__sc-aiai24-0 ezPwpO\">For listings in Canada, the trademarks REALTOR&#xae;, REALTORS&#xae;, and the REALTOR&#xae; logo are controlled by The Canadian Real Estate Association (CREA) and identify real estate professionals who are members of CREA. The trademarks MLS&#xae;, Multiple Listing Service&#xae; and the associated logos are owned by CREA and identify the quality of services provided by real estate professionals who are members of CREA. Used under license.</p>"
    }
  ],
  "citableParagraphs": [
    {
      "index": 214,
      "heading": "H6: About Zillow's Recommendations",
      "text": "Affiliated Business Arrangement DisclosureZillow, Inc. holds real estate brokerage licenses in multiple states. Zillow (Canada), Inc. holds real estate brokerage licenses in multiple provinces.All mortgage lending products and information provided by Zillow Home Loans, LLC, NMLS #10287. NMLS Consumer AccessLicensed Mortgage Banker, N.Y.S. Department of Financial Services2600 Michelson Drive, Suite 1201, Irvine, CA...",
      "words": 85,
      "hasEvidence": true,
      "reasons": [],
      "html": "<p class=\"Text-c11n-8-112-0__sc-aiai24-0 ezPwpO\"><a href=\"https://www.zillow.com/affiliated-business-arrangement-disclosure/\" rel=\"nofollow\" class=\"Anchor-c11n-8-112-0__sc-hn4bge-0 ivHafp\">Affiliated Business Arrangement Disclosure</a><br>Zillow, Inc. holds real estate brokerage <a href=\"/c/info/real-estate-licenses/\" class=\"Anchor-c11n-8-112-0__sc-hn4bge-0 ivHafp\">licenses</a> in multiple states. Zillow (Canada), Inc. holds real estate brokerage <a href=\"/c/info/real-estate-licenses/\" class=..."
    }
  ],
  "score": 75,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first sections

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

2 Warning

Needs attention

AEO: Answer-first sections

Warning
01

Issue

AEO readiness is incomplete.

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

80/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 80/100 and needs improvement.

Evidence
{
  "sectionCount": 0,
  "passing": 0,
  "failing": [],
  "score": 80,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

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

1 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

Entity or definition gaps: zillow, apartments, mortgages, rentals, homes, agents, loans.

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

84/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 84/100 and needs improvement.

Evidence
{
  "title": "Zillow: Real Estate, Apartments, Mortgages & Home Values",
  "h1": "Rentals. Homes. Agents. Loans.",
  "description": "The leading real estate marketplace. Search millions of for-sale and rental listings, compare Zestimate® home values and connect with local professionals.",
  "topicOverlap": 0.36363636363636365,
  "definitionCount": 2,
  "topicTerms": [
    "zillow",
    "real",
    "estate",
    "apartments",
    "mortgages",
    "home",
    "values",
    "rentals",
    "homes",
    "agents",
    "loans"
  ],
  "descriptionTerms": [
    "leading",
    "real",
    "estate",
    "marketplace",
    "search",
    "millions",
    "sale",
    "rental",
    "listings",
    "compare",
    "zestimate",
    "home",
    "values",
    "connect",
    "local",
    "professionals"
  ],
  "missingFromDescription": [
    "zillow",
    "apartments",
    "mortgages",
    "rentals",
    "homes",
    "agents",
    "loans"
  ],
  "score": 84,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Answer block readiness

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

1 Warning

Needs attention

AIO: Answer block readiness

Warning
01

Issue

No JSON-LD structured data was detected.

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

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: Answer block readiness scored 80/100 and needs improvement.

Evidence
{
  "sectionCount": 0,
  "passing": 0,
  "failing": [],
  "score": 80,
  "weight": 8
}

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": [],
  "expected": [
    {
      "id": "what",
      "label": "What is Zillow: Real Estate, Apartments, Mortgages &...?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Zillow: Real Estate, Apartments, Mortgages &... work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Zillow: Real Estate, Apartments, Mortgages &...?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Zillow: Real Estate, Apartments, Mortgages &... free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Zillow: Real Estate, Apartments, Mortgages &... compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is Zillow: Real Estate, Apartments, Mortgages &...?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Zillow: Real Estate, Apartments, Mortgages &... work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Zillow: Real Estate, Apartments, Mortgages &...?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Zillow: Real Estate, Apartments, Mortgages &... free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Zillow: Real Estate, Apartments, Mortgages &... compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 8
}

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": 432692
          },
          {
            "path": "/api/context",
            "statusCode": 404,
            "contentType": "text/html;charset=utf-8",
            "length": 432692
          },
          {
            "path": "/context",
            "statusCode": 404,
            "contentType": "text/html;charset=utf-8",
            "length": 432692
          }
        ]
      },
      "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": [],
  "expected": [
    {
      "id": "what",
      "label": "What is Zillow: Real Estate, Apartments, Mortgages &...?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Zillow: Real Estate, Apartments, Mortgages &... work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Zillow: Real Estate, Apartments, Mortgages &...?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Zillow: Real Estate, Apartments, Mortgages &... free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Zillow: Real Estate, Apartments, Mortgages &... compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is Zillow: Real Estate, Apartments, Mortgages &...?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Zillow: Real Estate, Apartments, Mortgages &... work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Zillow: Real Estate, Apartments, Mortgages &...?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Zillow: Real Estate, Apartments, Mortgages &... free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Zillow: Real Estate, Apartments, Mortgages &... compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 4
}

Agent Ease of UseAuthEmerging recommendation

Auth.md Agent Registration

Auth.md Agent Registration has an informational finding because the page appears to support authentication.

Informational

Needs attention

Auth.md Agent Registration

Informational
01

Issue

auth.md response did not match the expected agent registration shape. Content-Type "text/html;charset=utf-8" is not Markdown or text/plain; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link.

02

Why it matters

Agent registration metadata lets automated clients find the registration path, supported identity types, credential types, and related claim or revocation endpoints without scraping human docs.

Check name

Auth.md Agent Registration

Score

0/100

Status

informational

Category

Auth

Maturity

Emerging recommendation

Goal

Publish Auth.md and agent_auth metadata so agents can discover registration and credential requirements.

Result

Auth.md Agent Registration has an informational finding because the page appears to support authentication.

Validation steps

  1. Fetch and validate /auth.md

    auth.md response did not match the expected agent registration shape. Content-Type "text/html;charset=utf-8" is not Markdown or text/plain; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link.

  2. Publish protected resource metadata

    The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.

  3. Validate agent_auth authorization metadata

    OAuth authorization server metadata could not be fetched.

Evidence
{
  "failedStep": "auth-md",
  "steps": [
    {
      "id": "auth-md",
      "title": "Fetch and validate /auth.md",
      "status": "fail",
      "evidence": {
        "path": "/auth.md",
        "ok": false,
        "statusCode": 404,
        "contentType": "text/html;charset=utf-8",
        "length": 432692,
        "validation": {
          "valid": false,
          "issue": "auth.md response did not match the expected agent registration shape. Content-Type \"text/html;charset=utf-8\" is not Markdown or text/plain; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link.",
          "compatibleContentType": false,
          "contentLength": 423126,
          "hasRegisterInstructions": true,
          "hasProtectedResourceLink": false,
          "hasAuthorizationServerLink": false,
          "mentionsIdentity": true,
          "mentionsCredential": true,
          "links": [
            "https://www.zillowstatic.com/static-zsg/LATEST/static-zsg/zsg/zsg-core.css\"/><link",
            "https://www.zillowstatic.com/static-zsg/LATEST/static-zsg/zsg/zsg-opt.css\"/><script",
            "/page-frame-content",
            "/script",
            "https://www.google-analytics.com/analytics.js','ga'",
            "/script",
            "/*",
            "/script",
            "//",
            "//"
          ],
          "rawExcerpt": "<!DOCTYPE html><head><link id=\"zsg.core\" rel=\"stylesheet\" media=\"all\" href=\"https://www.zillowstatic.com/static-zsg/LATEST/static-zsg/zsg/zsg-core.css\"/><link id=\"zsg.opt\" rel=\"stylesheet\" media=\"all\" href=\"https://www.zillowstatic.com/static-zsg/LATEST/static-zsg/zsg/zsg-opt.css\"/><script id=\"scripts.pfs.appInfo\">\n        if (typeof Object.assign === 'function') {\n            window.appInfo = Object.assign(\n                typeof window.appInfo === 'object' ? window.appInfo : {},\n                {\"@zillow/page-frame-content\":\"master.5304.151b3ede\"}\n            );\n        }\n    </script><script id=\"scripts.ua\">(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){\n        (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),\n        m=s.getEle"
        }
      },
      "issue": "auth.md response did not match the expected agent registration shape. Content-Type \"text/html;charset=utf-8\" is not Markdown or text/plain; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link.",
      "howToFix": "Serve /auth.md at the site root as Markdown with agent registration instructions and links to OAuth metadata."
    },
    {
      "id": "oauth-protected-resource",
      "title": "Publish protected resource metadata",
      "status": "fail",
      "evidence": {
        "path": "/.well-known/oauth-protected-resource",
        "ok": false,
        "statusCode": 404,
        "contentType": "application/xml",
        "length": 327,
        "text": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message><Key>.well-known/oauth-protected-resource</Key><RequestId>EYA0T43PHE7AK7QE</RequestId><HostId>0YiE08So9KsG+ftK4hUPotb2sLMxzhKcPqNwcJI+QWV/SmMkX0FHVTSvlcqrPSqpTvoKwlXtDJFiyCIj4rF3dP4fbPePMMUA</HostId></Error>"
      },
      "issue": "The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.",
      "howToFix": "Publish /.well-known/oauth-protected-resource with resource and authorization_servers fields."
    },
    {
      "id": "agent-auth-block",
      "title": "Validate agent_auth authorization metadata",
      "status": "fail",
      "evidence": {
        "valid": false,
        "issue": "OAuth authorization server metadata could not be fetched.",
        "fetch": {
          "ok": false,
          "statusCode": 404,
          "contentType": "application/xml",
          "length": 329,
          "text": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message><Key>.well-known/oauth-authorization-server</Key><RequestId>EF75XF69DNEXVZJD</RequestId><HostId>v+fMbg9P39p//LxnvPUhRr3+8fZfkxNYBbFbjqSyPxqk23LoeaIGfCAkNmN/T4Jdsrw5wHTj/zU78XO6s+ecy1ASP5Q0E+98</HostId></Error>"
        }
      },
      "issue": "OAuth authorization server metadata could not be fetched.",
      "howToFix": "Add agent_auth to /.well-known/oauth-authorization-server with register_uri, supported identity types, credential types, and claim or revocation URLs where applicable."
    }
  ],
  "authApplicability": {
    "supportsAuth": true,
    "score": 6,
    "signals": [
      {
        "source": "link:href",
        "weight": 3,
        "match": "auth link"
      },
      {
        "source": "visible-text",
        "weight": 3,
        "match": "sign in"
      }
    ]
  },
  "resourceFetchSucceeded": false
}

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

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": 0,
  "questionH2s": 0,
  "hasFaq": false,
  "nonQuestionH2s": [],
  "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, Link headers, or robots.txt.

  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, Link headers, or robots.txt.",
      "howToFix": "Advertise the key location with robots.txt IndexNow-Key, 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 using a 32-character hexadecimal key whose body exactly matches the key."
    }
  ]
}

Agent Ease of UseAuthEstablished

OAuth / OIDC discovery

OAuth / OIDC discovery has an informational finding because the page appears to support authentication.

Informational

Needs attention

OAuth / OIDC discovery

Informational
01

Issue

OAuth / OIDC discovery was not found at the expected path.

02

Why it matters

OAuth and OIDC discovery let agents find authorization, token, and key endpoints programmatically instead of relying on human documentation.

Check name

OAuth / OIDC discovery

Score

0/100

Status

informational

Category

Auth

Maturity

Established

Goal

Publish OAuth/OIDC discovery metadata so agents can authenticate with your APIs.

Result

OAuth / OIDC discovery has an informational finding because the page appears to support authentication.

Validation steps

  1. Fetch to find resource

    OAuth / OIDC discovery 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/openid-configuration",
            "statusCode": 404,
            "contentType": "application/xml",
            "length": 323
          },
          {
            "path": "/.well-known/oauth-authorization-server",
            "statusCode": 404,
            "contentType": "application/xml",
            "length": 329
          }
        ]
      },
      "issue": "OAuth / OIDC discovery was not found at the expected path.",
      "howToFix": "Publish valid OAuth/OIDC metadata only when the site actually supports OAuth/OIDC. Otherwise omit provider discovery and document any unauthenticated public APIs separately."
    }
  ],
  "authApplicability": {
    "supportsAuth": true,
    "score": 6,
    "signals": [
      {
        "source": "link:href",
        "weight": 3,
        "match": "auth link"
      },
      {
        "source": "visible-text",
        "weight": 3,
        "match": "sign in"
      }
    ]
  },
  "resourceFetchSucceeded": false
}

Agent Ease of UseAuthEmerging recommendation

OAuth Protected Resource

OAuth Protected Resource has an informational finding because the page appears to support authentication.

Informational

Needs attention

OAuth Protected Resource

Informational
01

Issue

The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.

02

Why it matters

Protected Resource metadata tells agents which authorization servers protect an API and how to connect authentication challenges to the right resource.

Check name

OAuth Protected Resource

Score

0/100

Status

informational

Category

Auth

Maturity

Emerging recommendation

Goal

Publish OAuth Protected Resource Metadata so agents can discover how to authenticate.

Result

OAuth Protected Resource has an informational finding because the page appears to support authentication.

Validation steps

  1. Fetch protected resource metadata

    The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.

  2. Validate protected resource metadata

    Response is not valid JSON.

  3. Validate protected resource identity

    Protected resource metadata `resource` did not match the resource identifier used to retrieve it.

  4. Probe protected API Bearer challenge

    No protected route with a 401 Bearer challenge was detected; metadata alone does not prove a protected resource.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch protected resource metadata",
      "status": "fail",
      "evidence": {
        "path": "/.well-known/oauth-protected-resource",
        "statusCode": 404,
        "contentType": "application/xml"
      },
      "issue": "The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.",
      "howToFix": "Publish /.well-known/oauth-protected-resource JSON."
    },
    {
      "id": "metadata",
      "title": "Validate protected resource metadata",
      "status": "fail",
      "evidence": {
        "valid": false,
        "compatibleContentType": false,
        "issue": "Response is not valid JSON.",
        "rawExcerpt": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message><Key>.well-known/oauth-protected-resource</Key><RequestId>EYA0T43PHE7AK7QE</RequestId><HostId>0YiE08So9KsG+ftK4hUPotb2sLMxzhKcPqNwcJI+QWV/SmMkX0FHVTSvlcqrPSqpTvoKwlXtDJFiyCIj4rF3dP4fbPePMMUA</HostId></Error>"
      },
      "issue": "Response is not valid JSON.",
      "howToFix": "Publish resource and authorization_servers as absolute URLs."
    },
    {
      "id": "resource-identity",
      "title": "Validate protected resource identity",
      "status": "fail",
      "evidence": {
        "expectedResource": "https://www.zillow.com"
      },
      "issue": "Protected resource metadata `resource` did not match the resource identifier used to retrieve it.",
      "howToFix": "Set `resource` to the origin/resource identifier represented by /.well-known/oauth-protected-resource."
    },
    {
      "id": "protected-route-challenge",
      "title": "Probe protected API Bearer challenge",
      "status": "informational",
      "evidence": {
        "checked": [
          {
            "path": "/api/admin/scans",
            "statusCode": 404,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://www.zillow.com/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "resourceMatchesRequestContext": true
          },
          {
            "path": "/api/admin/summary",
            "statusCode": 404,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://www.zillow.com/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "resourceMatchesRequestContext": true
          },
          {
            "path": "/api/scans",
            "statusCode": 404,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://www.zillow.com/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "resourceMatchesRequestContext": true
          }
        ]
      },
      "issue": "No protected route with a 401 Bearer challenge was detected; metadata alone does not prove a protected resource.",
      "howToFix": "When this site exposes bearer-protected APIs, return 401 with WWW-Authenticate: Bearer and link resource_metadata."
    }
  ],
  "authApplicability": {
    "supportsAuth": true,
    "score": 6,
    "signals": [
      {
        "source": "link:href",
        "weight": 3,
        "match": "auth link"
      },
      {
        "source": "visible-text",
        "weight": 3,
        "match": "sign in"
      }
    ]
  },
  "resourceFetchSucceeded": false
}

SEOSEOBrowser audit

Image elements do not have `[alt]` attributes

100 Fail

Check name

Image elements do not have `[alt]` attributes

Score

0/100

Status

fail

Device

desktop

Category

SEO

Fix guidance

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. [Learn more about the `alt` attribute](https://dequeuniversity.com/rules/axe/4.11/image-alt).

Evidence
{
  "description": "Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. [Learn more about the `alt` attribute](https://dequeuniversity.com/rules/axe/4.11/image-alt)."
}

Performance and AccessibilityBest PracticesBrowser audit

Uses deprecated APIs

100 Fail

Check name

Uses deprecated APIs

Score

0/100

Status

fail

Device

desktop

Category

Best Practices

Estimated savings

1 warning found

Fix guidance

Deprecated APIs will eventually be removed from the browser. [Learn more about deprecated APIs](https://developer.chrome.com/docs/lighthouse/best-practices/deprecations/).

Evidence
{
  "displayValue": "1 warning found",
  "description": "Deprecated APIs will eventually be removed from the browser. [Learn more about deprecated APIs](https://developer.chrome.com/docs/lighthouse/best-practices/deprecations/)."
}

Performance and AccessibilityPerformanceBrowser audit

Document does not have a main landmark.

20 Fail

Check name

Document does not have a main landmark.

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

One main landmark helps screen reader users navigate a web page. [Learn more about landmarks](https://dequeuniversity.com/rules/axe/4.11/landmark-one-main).

Evidence
{
  "description": "One main landmark helps screen reader users navigate a web page. [Learn more about landmarks](https://dequeuniversity.com/rules/axe/4.11/landmark-one-main)."
}

Performance and AccessibilityPerformanceBrowser audit

Forced reflow

20 Fail

Check name

Forced reflow

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations.

Evidence
{
  "description": "A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations."
}

Performance and AccessibilityPerformanceBrowser audit

LCP request discovery

20 Fail

Check name

LCP request discovery

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

[Optimize LCP](https://developer.chrome.com/docs/performance/insights/lcp-discovery) by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Evidence
{
  "description": "[Optimize LCP](https://developer.chrome.com/docs/performance/insights/lcp-discovery) by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading"
}

Performance and AccessibilityPerformanceBrowser audit

Reduce JavaScript execution time

20 Fail

Check name

Reduce JavaScript execution time

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

5.5 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": "5.5 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": 5499.911999999976
}

Performance and AccessibilityPerformanceBrowser audit

Loading performance

9 Fail

Check name

Loading performance

Score

53/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": "network-rtt",
      "title": "Network Round Trip Times",
      "score": 100,
      "displayValue": "40 ms",
      "numericValue": 35.147925
    },
    {
      "id": "largest-contentful-paint",
      "title": "Largest Contentful Paint",
      "score": 98,
      "displayValue": "0.8 s",
      "numericValue": 763.0024029082675
    },
    {
      "id": "server-response-time",
      "title": "Initial server response time was short",
      "score": 100,
      "displayValue": "Root document took 10 ms",
      "numericValue": 8
    },
    {
      "id": "max-potential-fid",
      "title": "Max Potential First Input Delay",
      "score": 13,
      "displayValue": "440 ms",
      "numericValue": 441
    },
    {
      "id": "speed-index",
      "title": "Speed Index",
      "score": 5,
      "displayValue": "4.7 s",
      "numericValue": 4681.664427989382
    },
    {
      "id": "first-contentful-paint",
      "title": "First Contentful Paint",
      "score": 100,
      "displayValue": "0.5 s",
      "numericValue": 485.7011436194342
    },
    {
      "id": "interactive",
      "title": "Time to Interactive",
      "score": 9,
      "displayValue": "8.4 s",
      "numericValue": 8364.120275147234
    },
    {
      "id": "total-blocking-time",
      "title": "Total Blocking Time",
      "score": 0,
      "displayValue": "2,250 ms",
      "numericValue": 2253.000000000001
    }
  ]
}

Fix with MCP or CLI

Use this report as the handoff into remediation. Generate a coding-agent prompt with the failing checks attached, or jump to the MCP and CLI setup docs before your next rescan.

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
52/100Level 3, Bot-AwareCurrent report
zillow.com AI SEO Report: 52/100 (Level 3, Bot-Aware)