CanAgentUse

Saved report

https://www.zendesk.com/

SCANNED

Jun 4, 2026, 3:16 AM

VISIBILITY

Public

Rescan Report

Share Report

Copy Report Link

New Scan

https://www.zendesk.com/

SCANNED

Jun 4, 2026, 3:16:28 AMJun 4, 2026, 3:16 AM

VISIBILITY

Public

Rescan Report

Share Report

Copy Report Link

Export Report

14/100

OVERALL SCORE

Level 1, Not Agent-Ready

Priority improvements needed for AI agents

CAPTURED SCREENSHOT

Screenshot unavailable

What AI sees of your website

Just a moment...

Just a moment... www.zendesk.com Performing security verification This website uses a security service to protect against malicious bots. This page is displayed while the website verifies you are not a bot. Verification successful. Waiting for www.zendesk.com...

Detailed report scores grouped by capability area
Metric	Score	Status	Passed	Failed	Warning	Evidence
AI Discoverability	6	Priority fix	2	21	0	View details
Discoverability	0	Priority fix	1	8	0	View details
Content Readiness	17	Priority fix	1	9	0	View details
Bot Access Control	0	Priority fix	0	4	0	View details
Agent Ease of Use	8	Priority fix	13	20	0	View details
API	0	Priority fix	0	6	0	View details
Auth	Not Applicable	Not Applicable	7	0	0
MCP	25	Priority fix	2	6	0	View details
Skill Discovery	0	Priority fix	0	8	0	View details
Agent Commerce	Not Applicable	Not Applicable	4	0	0
GEO, AIO and AEO	45	Priority fix	1	9	9	View details
GEO Readiness	49	Priority fix	0	2	3	View details
AIO Readiness	35	Priority fix	1	4	2	View details
AEO Readiness	49	Priority fix	0	3	4	View details
SEO	0	Priority fix	11	0	0
SEO	0	Priority fix	11	0	0
Security & Trust	80	Mostly ready	8	1	0	View details
Security & Trust	80	Mostly ready	4	1	0	View details
AI Training Exposure	Not Applicable	Not Applicable	4	0	0
Performance and Accessibility	0	Priority fix	0	0	0
Performance	0	Priority fix	0	0	0
Accessibility	0	Priority fix	0	0	0

Prioritized recommendations

Issues ranked by score impact

43 items need attention

Security & TrustSecurity & TrustEstablished

HSTS header

HSTS header is missing or incomplete.

100 Fail

Needs attention

HSTS header

Failed check

Issue

HSTS header is missing or incomplete.

Why it matters

HSTS tells browsers to keep using HTTPS after the first secure visit, reducing downgrade and mixed-transport risk for repeat users.

Check name

HSTS header

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Require HTTPS for repeat visits with Strict-Transport-Security.

Result

HSTS header is missing or incomplete.

Evidence

{
  "header": "strict-transport-security",
  "value": "max-age=0; preload"
}

Agent Ease of UseAPIEstablished

API Catalog

API Catalog failed at "Fetch API catalog".

50 Fail

Needs attention

API Catalog

Failed check

Issue

The API catalog endpoint did not return HTTP 2xx.

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

Fetch API catalog
The API catalog endpoint did not return HTTP 2xx.
Validate RFC 9727 linkset
Response is not valid JSON.
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": 403,
        "contentType": "text/html; charset=UTF-8"
      },
      "issue": "The API catalog endpoint did not return HTTP 2xx.",
      "howToFix": "Publish /.well-known/api-catalog."
    },
    {
      "id": "validate",
      "title": "Validate RFC 9727 linkset",
      "status": "fail",
      "evidence": {
        "valid": false,
        "compatibleContentType": false,
        "issue": "Response is not valid JSON.",
        "rawExcerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src 'none'; script-src 'nonce-VMA2alYj49fkyKvXXGuBFo' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare.com blob:; worker-src blob:; form-action http: https:; base-uri 'self'\">"
      },
      "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."
    }
  ]
}

Agent Ease of UseAPIEstablished

OpenAPI discovery

OpenAPI discovery failed at "Find valid OpenAPI document".

50 Fail

Needs attention

OpenAPI discovery

Failed check

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.

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

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": 403,
            "contentType": "text/html; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src 'none'; script-src 'nonce-kKa428SJDFa7gt8OZgFE8Y' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare.com blob:; worker-src blob:; form-action http: https:; base-uri 'self'\">"
          },
          {
            "path": "/openapi.yaml",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src 'none'; script-src 'nonce-rNvA54V1Xlk1zGfCyzONXp' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare.com blob:; worker-src blob:; form-action http: https:; base-uri 'self'\">"
          },
          {
            "path": "/swagger.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src 'none'; script-src 'nonce-X9y07cmQvuVw7W5Ww6dSfZ' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare.com blob:; worker-src blob:; form-action http: https:; base-uri 'self'\">"
          },
          {
            "path": "/swagger.yaml",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src 'none'; script-src 'nonce-MJaUNSjYI44fHLJoAE8Phe' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare.com blob:; worker-src blob:; form-action http: https:; base-uri 'self'\">"
          },
          {
            "path": "/api/openapi.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src 'none'; script-src 'nonce-RRVL1NeNUk2suz9us5xczJ' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare.com blob:; worker-src blob:; form-action http: https:; base-uri 'self'\">"
          },
          {
            "path": "/api/swagger.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src 'none'; script-src 'nonce-rx2VWlQIJuzlsHFT6IQ7n0' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare.com blob:; worker-src blob:; form-action http: https:; base-uri 'self'\">"
          },
          {
            "path": "/docs/openapi.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src 'none'; script-src 'nonce-Opb8q5fkkE70Eycx5sSXxb' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare.com blob:; worker-src blob:; form-action http: https:; base-uri 'self'\">"
          }
        ]
      },
      "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
      "howToFix": "Publish a valid OpenAPI 3.x or Swagger 2.0 JSON/YAML document with info, paths, operations, and responses."
    }
  ]
}

AI DiscoverabilityBot Access ControlEstablished

AI bot rules in robots.txt

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

33 Fail

Needs attention

AI bot rules in robots.txt

Failed check

Issue

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

Why it matters

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

Check name

AI bot rules in robots.txt

Score

0/100

Status

fail

Category

Bot Access Control

Maturity

Established

Goal

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

Result

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

Evidence

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

AI DiscoverabilityBot Access ControlInformational

Content Signal

Content Signal is missing or incomplete.

33 Fail

Needs attention

Content Signal

Failed check

Issue

No Content Signal found in robots.txt

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 UseMCPEmerging recommendation

MCP Server Card

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

33 Fail

Needs attention

MCP Server Card

Failed check

Issue

MCP Server Card was not found at the expected path.

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

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": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 10103
          },
          {
            "path": "/.well-known/mcp/server-cards.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 10127
          },
          {
            "path": "/.well-known/mcp.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 10043
          }
        ]
      },
      "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".

33 Fail

Needs attention

mcp.json

Failed check

Issue

mcp.json was not found at the expected path.

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

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": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 9982
          },
          {
            "path": "/.well-known/mcp.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 10043
          },
          {
            "path": "/.well-known/mcp/server-card.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 10124
          }
        ]
      },
      "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 DiscoverabilityBot Access ControlInformational

Web Bot Auth request signing

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

33 Fail

Needs attention

Web Bot Auth request signing

Failed check

Issue

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

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

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": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 10181
          }
        ]
      },
      "issue": "Web Bot Auth request signing was not found at the expected path.",
      "howToFix": "If publishing Web Bot Auth keys, return a JSON key directory with a non-empty keys array and the draft media type."
    }
  ]
}

Agent Ease of UseMCPInformational

WebMCP manifest

WebMCP manifest failed at "Fetch to find resource".

33 Fail

Needs attention

WebMCP manifest

Failed check

Issue

WebMCP manifest was not found at the expected path.

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

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": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 10052
          },
          {
            "path": "/webmcp.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 9948
          },
          {
            "path": "/mcp.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 10003
          }
        ]
      },
      "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".

25 Fail

Needs attention

A2A Agent Card

Failed check

Issue

A2A Agent Card was not found at the expected path.

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

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": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 10064
          },
          {
            "path": "/.well-known/a2a/agent-card.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 10100
          },
          {
            "path": "/agent-card.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 10003
          }
        ]
      },
      "issue": "A2A Agent Card was not found at the expected path.",
      "howToFix": "Publish an A2A Agent Card with required skill details and make the advertised url answer A2A JSON-RPC requests."
    }
  ]
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

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

25 Fail

Needs attention

Agent Skills index

Failed check

Issue

Agent Skills index was not found at the expected path.

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

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": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 10133
          },
          {
            "path": "/.well-known/skills/index.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 10094
          }
        ]
      },
      "issue": "Agent Skills index was not found at the expected path.",
      "howToFix": "Publish an index with a non-empty skills array and reachable SKILL.md URLs."
    }
  ]
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

agent.json

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

25 Fail

Needs attention

agent.json

Failed check

Issue

agent.json was not found at the expected path.

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

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": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 10049
          },
          {
            "path": "/agent.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 10009
          }
        ]
      },
      "issue": "agent.json was not found at the expected path.",
      "howToFix": "Publish agent.json with awp_version, domain, intent, and typed actions that point to real same-origin API or protocol endpoints."
    }
  ]
}

Agent Ease of UseSkill DiscoveryInformational

agents.json

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

25 Fail

Needs attention

agents.json

Failed check

Issue

agents.json was not found at the expected path.

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

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": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 10073
          },
          {
            "path": "/agents.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 10012
          }
        ]
      },
      "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 missing or incomplete.

20 Fail

Needs attention

Content freshness signals

Failed check

Issue

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

Why it matters

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

Check name

Content freshness signals

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

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

Result

Content freshness signals is missing or incomplete.

Evidence

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

AI DiscoverabilityContent ReadinessEmerging recommendation

llms.txt

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

20 Fail

Needs attention

llms.txt

Failed check

Issue

llms.txt was not found at the expected path.

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

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": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 10003
          },
          {
            "path": "/llms-full.txt",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 9997
          }
        ]
      },
      "issue": "llms.txt was not found at the expected path.",
      "howToFix": "Publish /llms.txt as Markdown with a clear title, concise site summary, and useful links for agents."
    }
  ]
}

AI DiscoverabilityContent ReadinessEstablished

Markdown negotiation

Markdown negotiation failed at "Markdown content type".

20 Fail

Needs attention

Markdown negotiation

Failed check

Issue

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

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

Markdown content type
Content-Type "text/html; charset=UTF-8" does not indicate Markdown when requested with Accept: text/markdown.
Vary: Accept header
Markdown negotiation is missing Vary: Accept; current Vary header is "Accept-Encoding".
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": 403,
        "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": 413,
        "excerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><m",
        "issue": "Markdown response is missing a heading."
      },
      "issue": "Markdown response is missing a heading.",
      "howToFix": "Return Markdown with at least one heading and substantive page content, including useful links or instructions for agents."
    }
  ]
}

AI DiscoverabilityContent ReadinessEstablished

Semantic HTML

Semantic HTML is missing or incomplete.

20 Fail

Needs attention

Semantic HTML

Failed check

Issue

Semantic HTML is incomplete: missing <main> landmark; missing <nav> landmark; missing <footer> landmark.

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": false,
  "footer": false,
  "meaningfulH1": true,
  "headingOrder": true,
  "accessibleLinks": true,
  "accessibleButtons": true,
  "imageAltCoverage": true,
  "formAutocompleteCoverage": true,
  "details": {
    "inaccessibleLinks": [],
    "inaccessibleButtons": [],
    "missingAutocompleteInputs": [],
    "imagesMissingAlt": [],
    "skippedHeadingLevels": []
  },
  "counts": {
    "h1": 1,
    "headings": 3,
    "links": 2,
    "inaccessibleLinks": 0,
    "buttons": 0,
    "inaccessibleButtons": 0,
    "images": 1,
    "imagesWithAlt": 1,
    "autocompleteInputs": 0,
    "inputsWithAutocomplete": 0,
    "missingAutocompleteInputs": 0
  }
}

AI DiscoverabilityContent ReadinessEstablished

Structured data

Structured data is missing or incomplete.

20 Fail

Needs attention

Structured data

Failed check

Issue

No structured data (JSON-LD, Microdata, or RDFa) found on page.

Why it matters

Structured data gives agents explicit entities, relationships, and page meaning that are harder to infer reliably from visual layout alone.

Check name

Structured data

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose machine-readable page entities and relationships.

Result

Structured data is missing or incomplete.

Evidence

{
  "jsonLdBlocks": 0,
  "microdata": false,
  "rdfa": false
}

AI DiscoverabilityDiscoverabilityEstablished

High-value schema types

High-value schema types is missing or incomplete.

17 Fail

Needs attention

High-value schema types

Failed check

Issue

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

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.

17 Fail

Needs attention

JSON-LD present

Failed check

Issue

No JSON-LD blocks found.

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".

17 Fail

Needs attention

Link headers

Failed check

Issue

No useful agent discovery Link headers were found.

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

Find useful Link headers
No useful agent discovery Link headers were found.
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 DiscoverabilityDiscoverabilityEstablished

Organization / WebSite schema

Organization / WebSite schema is missing or incomplete.

17 Fail

Needs attention

Organization / WebSite schema

Failed check

Issue

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

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 DiscoverabilityDiscoverabilityEstablished

robots.txt

robots.txt is missing or incomplete.

17 Fail

Needs attention

robots.txt

Failed check

Issue

Failed to fetch /robots.txt (Status: 403).

Why it matters

robots.txt gives crawlers and agents a standard place to read crawl permissions, disallowed paths, and sitemap locations before requesting site content.

Check name

robots.txt

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Publish /robots.txt with clear crawl rules.

Result

robots.txt is missing or incomplete.

Evidence

{
  "statusCode": 403,
  "contentType": "text/html; charset=UTF-8",
  "parsedUserAgents": [],
  "sitemapDirectives": [],
  "rawExcerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src 'none'; script-src 'nonce-QsXsUTf9BduaK0TdTU6b62' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare.com blob:; worker-src blob:; form-action http: https:; base-uri 'self'\">"
}

AI DiscoverabilityDiscoverabilityEstablished

Sitemap

Sitemap is missing or incomplete.

17 Fail

Needs attention

Sitemap

Failed check

Issue

No valid XML sitemap found at checked locations: https://www.zendesk.com/sitemap.xml, https://www.zendesk.com/sitemap_index.xml, https://www.zendesk.com/sitemap-index.xml.

Why it matters

Sitemaps help crawlers and agents discover canonical URLs, updated pages, and deeper content that may not be obvious from the homepage navigation.

Check name

Sitemap

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Publish a sitemap and reference it from robots.txt.

Result

Sitemap is missing or incomplete.

Evidence

{
  "checked": [
    "https://www.zendesk.com/sitemap.xml",
    "https://www.zendesk.com/sitemap_index.xml",
    "https://www.zendesk.com/sitemap-index.xml"
  ]
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Visible structured data match

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

7 Fail

Needs attention

AIO: Visible structured data match

Failed check

Issue

No JSON-LD structured data was detected.

Details

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: Google eligibility and indexability

AIO: Google eligibility and indexability scored 10/100 and needs a fix.

7 Fail

Needs attention

AIO: Google eligibility and indexability

Failed check

Issue

HTTP status is 403; Google AI features need an indexable 2xx page. Noindex directive found: noindex,nofollow. Canonical tag is missing.

Details

Why it matters

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

Check name

AIO: Google eligibility and indexability

Score

10/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: Google eligibility and indexability scored 10/100 and needs a fix.

Evidence

{
  "status": 403,
  "googlebotBlocked": false,
  "metaRobotsTags": [
    "noindex,nofollow"
  ],
  "xRobotsTag": "",
  "canonical": "",
  "finalUrl": "https://www.zendesk.com/",
  "canonicalScore": 0,
  "score": 10,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Source and trust signals

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

6 Fail

Needs attention

AIO: Source and trust signals

Failed check

Issue

Missing AIO trust signals: author, publisher, freshnessDate, aboutOrContact.

Details

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

20/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 20/100 and needs a fix.

Evidence

{
  "signals": {
    "author": false,
    "publisher": false,
    "freshnessDate": false,
    "aboutOrContact": false,
    "policyLinks": true
  },
  "missing": [
    "author",
    "publisher",
    "freshnessDate",
    "aboutOrContact"
  ],
  "authorMeta": "",
  "schemaAuthors": [],
  "schemaPublishers": [],
  "schemaDates": [],
  "visibleDates": [],
  "aboutLinks": [],
  "contactLinks": [],
  "privacyLinks": [
    {
      "href": "https://www.cloudflare.com/privacypolicy/",
      "text": "Privacy",
      "html": "<a id=\"privacy-link\" target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://www.cloudflare.com/privacypolicy/\" class=\"footer-text\">Privacy</a>"
    }
  ],
  "score": 20,
  "weight": 20
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer evidence and trust

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

6 Fail

Needs attention

AEO: Answer evidence and trust

Failed check

Issue

Missing AIO trust signals: author, publisher, freshnessDate, aboutOrContact.

Details

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

20/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 20/100 and needs a fix.

Evidence

{
  "signals": {
    "author": false,
    "publisher": false,
    "freshnessDate": false,
    "aboutOrContact": false,
    "policyLinks": true
  },
  "missing": [
    "author",
    "publisher",
    "freshnessDate",
    "aboutOrContact"
  ],
  "authorMeta": "",
  "schemaAuthors": [],
  "schemaPublishers": [],
  "schemaDates": [],
  "visibleDates": [],
  "aboutLinks": [],
  "contactLinks": [],
  "privacyLinks": [
    {
      "href": "https://www.cloudflare.com/privacypolicy/",
      "text": "Privacy",
      "html": "<a id=\"privacy-link\" target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://www.cloudflare.com/privacypolicy/\" class=\"footer-text\">Privacy</a>"
    }
  ],
  "score": 20,
  "weight": 22
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Entity clarity

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

5 Warning

Needs attention

GEO: Entity clarity

Warning

Issue

Title/H1 terms missing from description: just, moment, www, zendesk, com.

Details

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

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

Evidence

{
  "title": "Just a moment...",
  "h1": "www.zendesk.com",
  "description": "",
  "topicOverlap": 0,
  "topicTerms": [
    "just",
    "moment",
    "www",
    "zendesk",
    "com"
  ],
  "descriptionTerms": [],
  "missingFromDescription": [
    "just",
    "moment",
    "www",
    "zendesk",
    "com"
  ],
  "score": 50,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Explanatory content depth

GEO: Explanatory content depth scored 25/100 and needs a fix.

5 Fail

Needs attention

GEO: Explanatory content depth

Failed check

Issue

No substantial explanatory paragraphs were found.

Details

Why it matters

Check name

GEO: Explanatory content depth

Score

25/100

Status

fail

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 25/100 and needs a fix.

Evidence

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: AI crawler accessibility

GEO: AI crawler accessibility scored 55/100 and needs improvement.

4 Warning

Needs attention

GEO: AI crawler accessibility

Warning

Issue

Only 57 words of Chrome-rendered body text were detected. No rendered JSON-LD schema block was detected.

Details

Why it matters

Check name

GEO: AI crawler accessibility

Score

55/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: AI crawler accessibility scored 55/100 and needs improvement.

Evidence

{
  "textWords": 57,
  "htmlBytes": 36338,
  "robots": {
    "checkedCrawlers": [
      "gptbot",
      "chatgpt-user",
      "claudebot",
      "perplexitybot",
      "google-extended"
    ],
    "blocked": [],
    "allows": true
  },
  "schemaBlocks": 0,
  "finalUrl": "https://www.zendesk.com/",
  "robotsExcerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src 'none'; script-src 'nonce-QsXsUTf9BduaK0TdTU6b62' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare.com blob:; worker-src blob:; form-action http: https:; base-uri 'self'\">",
  "score": 55,
  "weight": 26
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Extraction-friendly structure

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

4 Warning

Needs attention

GEO: Extraction-friendly structure

Warning

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

Why it matters

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": 1,
  "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: Answer-first sections

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

3 Warning

Needs attention

AEO: Answer-first sections

Warning

Issue

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

Details

Why it matters

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

Check name

AEO: Answer-first sections

Score

65/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

Evidence

{
  "sectionCount": 2,
  "passing": 1,
  "failing": [
    {
      "heading": "Verification successful. Waiting for www.zendesk.com to respond",
      "headingHtml": "<h2 id=\"challenge-success-text\" class=\"spacer-top\">Verification successful. Waiting for www.zendesk.com to respond</h2>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    }
  ],
  "score": 65,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question-led structure

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

3 Warning

Needs attention

AEO: Question-led structure

Warning

Issue

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

Details

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

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

3 Warning

Needs attention

AEO: Entity and definition clarity

Warning

Issue

Entity or definition gaps: just, moment, www, zendesk, com.

Details

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

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

Evidence

{
  "title": "Just a moment...",
  "h1": "www.zendesk.com",
  "description": "",
  "topicOverlap": 0,
  "definitionCount": 1,
  "topicTerms": [
    "just",
    "moment",
    "www",
    "zendesk",
    "com"
  ],
  "descriptionTerms": [],
  "missingFromDescription": [
    "just",
    "moment",
    "www",
    "zendesk",
    "com"
  ],
  "score": 55,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Extractable visible copy

AEO: Extractable visible copy scored 35/100 and needs a fix.

1 Fail

Needs attention

AEO: Extractable visible copy

Failed check

Issue

Only 57 visible words were detected for answer extraction.

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: Extractable visible copy

Score

35/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: Extractable visible copy scored 35/100 and needs a fix.

Evidence

{
  "visibleWords": 57,
  "schemaCount": 0,
  "score": 35,
  "weight": 6
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Page experience for AIO

AIO: Page experience for AIO scored 70/100 and needs improvement.

1 Warning

Needs attention

AIO: Page experience for AIO

Warning

Issue

Only 57 words of visible rendered text were detected. 1 image(s) are missing width/height attributes.

Details

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: Page experience for AIO

Score

70/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: Page experience for AIO scored 70/100 and needs improvement.

Evidence

{
  "viewportContent": "width=device-width,initial-scale=1",
  "visibleWords": 57,
  "htmlBytes": 36338,
  "imagesMissingDimensions": [
    {
      "src": "/favicon.ico",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/favicon.ico\" class=\"heading-favicon heading-favicon-hidden\" alt=\"Icon for www.zendesk.com\">"
    }
  ],
  "possibleDialogs": [],
  "score": 70,
  "weight": 10
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Answer block readiness

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

1 Warning

Needs attention

AIO: Answer block readiness

Warning

Issue

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

Details

Why it matters

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

Check name

AIO: Answer block readiness

Score

65/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

Evidence

{
  "sectionCount": 2,
  "passing": 1,
  "failing": [
    {
      "heading": "Verification successful. Waiting for www.zendesk.com to respond",
      "headingHtml": "<h2 id=\"challenge-success-text\" class=\"spacer-top\">Verification successful. Waiting for www.zendesk.com to respond</h2>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    }
  ],
  "score": 65,
  "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

Issue

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

Details

Why it matters

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

Check name

AEO: Answer intent coverage

Score

70/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

Evidence

{
  "headings": [
    {
      "text": "Performing security verification",
      "html": "<h2 id=\"FbRG5\" class=\"ch-title spacer-bottom\">Performing security verification</h2>"
    },
    {
      "text": "Verification successful. Waiting for www.zendesk.com to respond",
      "html": "<h2 id=\"challenge-success-text\" class=\"spacer-top\">Verification successful. Waiting for www.zendesk.com to respond</h2>"
    }
  ],
  "expected": [
    {
      "id": "what",
      "label": "What is Just a moment...?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Just a moment... work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Just a moment...?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Just a moment... free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Just a moment... compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is Just a moment...?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Just a moment... work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Just a moment...?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Just a moment... free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Just a moment... 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

Issue

AI context endpoint is informational for this page.

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

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": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 10006
          },
          {
            "path": "/api/context",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 9994
          },
          {
            "path": "/context",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 9979
          }
        ]
      },
      "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

Issue

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

Details

Why it matters

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

Check name

AIO: Query intent coverage

Score

70/100

Status

informational

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

AIO: Query intent coverage is informational for this page.

Evidence

{
  "headings": [
    {
      "text": "Performing security verification",
      "html": "<h2 id=\"FbRG5\" class=\"ch-title spacer-bottom\">Performing security verification</h2>"
    },
    {
      "text": "Verification successful. Waiting for www.zendesk.com to respond",
      "html": "<h2 id=\"challenge-success-text\" class=\"spacer-top\">Verification successful. Waiting for www.zendesk.com to respond</h2>"
    }
  ],
  "expected": [
    {
      "id": "what",
      "label": "What is Just a moment...?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Just a moment... work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Just a moment...?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Just a moment... free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Just a moment... compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is Just a moment...?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Just a moment... work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Just a moment...?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Just a moment... free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Just a moment... compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 4
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Q&A and FAQ opportunities

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

Informational

Needs attention

GEO: Q&A and FAQ opportunities

Informational

Issue

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

Details

Why it matters

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": 2,
  "questionH2s": 0,
  "hasFaq": false,
  "nonQuestionH2s": [
    {
      "index": 1,
      "text": "Performing security verification",
      "isQuestion": false,
      "html": "<h2 id=\"FbRG5\" class=\"ch-title spacer-bottom\">Performing security verification</h2>"
    },
    {
      "index": 2,
      "text": "Verification successful. Waiting for www.zendesk.com to respond",
      "isQuestion": false,
      "html": "<h2 id=\"challenge-success-text\" class=\"spacer-top\">Verification successful. Waiting for www.zendesk.com to respond</h2>"
    }
  ],
  "score": 75,
  "weight": 4
}

AI DiscoverabilityDiscoverabilityEstablished

IndexNow key

IndexNow key is informational for this page.

Informational

Needs attention

IndexNow key

Informational

Issue

IndexNow key is informational for this page.

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

Find advertised IndexNow key location
No IndexNow key location was advertised in HTML, Link headers, or robots.txt.
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."
    }
  ]
}

Improve Your Score

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

Score history

Public scan score over time

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

1 reports

Public score history report links
Scan date	Score	Readiness	Report
Jun 4, 2026	14/100	Level 1, Not Agent-Ready	Current report