CanAgentUse

Saved report

https://pine-labs.com/

SCANNED

Jun 9, 2026, 1:55 AM

VISIBILITY

Public

Rescan Report

Share Report

Copy Report Link

New Scan

https://pine-labs.com/

SCANNED

Jun 9, 2026, 1:55:17 AMJun 9, 2026, 1:55 AM

VISIBILITY

Public

Rescan Report

Share Report

Copy Report Link

Export Report

46/100

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents

CAPTURED SCREENSHOT

What AI sees of your website

No page title captured

No page metadata or readable excerpt was captured.

Next step

Turn this report into a fix workflow

34 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
Metric	Score	Status	Passed	Failed	Warning	Evidence
AI Discoverability	24	Priority fix	8	17	0	View details
Discoverability	33	Priority fix	3	6	0	View details
Content Readiness	20	Priority fix	4	7	0	View details
Bot Access Control	17	Priority fix	1	4	0	View details
Agent Ease of Use	39	Priority fix	21	33	2	View details
API	28	Priority fix	2	7	0	View details
Auth	27	Priority fix	6	8	0	View details
MCP	60	Needs work	5	7	1	View details
Skill Discovery	42	Priority fix	4	11	1	View details
Agent Commerce	Not Applicable	Not Applicable	4	0	0
GEO, AIO and AEO	38	Priority fix	1	10	8	View details
GEO Readiness	32	Priority fix	0	3	2	View details
AIO Readiness	44	Priority fix	1	3	3	View details
AEO Readiness	39	Priority fix	0	4	3	View details
SEO	100	Strong	11	0	0
SEO	100	Strong	11	0	0
Security & Trust	20	Priority fix	3	7	0	View details
Security & Trust	0	Priority fix	0	5	0	View details
AI Training Exposure	50	Needs work	3	2	0	View details
Performance and Accessibility	74	Needs work	24	2	1	View details
Performance	63	Needs work	14	1	1	View details
Accessibility	94	Strong	10	1	0	View details

Prioritized recommendations

Issues ranked by score impact

51 items need attention

Security & TrustAI Training ExposureEmerging recommendation

TDMRep declaration

TDMRep declaration is missing or incomplete.

100 Fail

Needs attention

TDMRep declaration

Failed check

Issue

Response is not valid JSON.

Why it matters

TDMRep is a W3C Community Group protocol and IANA-registered well-known URI for declaring text and data mining reservation policy on applicable content.

Check name

TDMRep declaration

Score

0/100

Status

fail

Category

AI Training Exposure

Maturity

Emerging recommendation

Goal

Publish a machine-readable text and data mining reservation declaration when the site needs one.

Result

TDMRep declaration is missing or incomplete.

Validation steps

Validate TDMRep rules
Response is not valid JSON.

Evidence

{
  "statusCode": 200,
  "contentType": "text/html",
  "valid": false,
  "compatibleContentType": false,
  "issue": "Response is not valid JSON.",
  "rawExcerpt": "<!DOCTYPE html><html><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch /.well-known/tdmrep.json",
      "status": "pass",
      "evidence": {
        "statusCode": 200,
        "contentType": "text/html",
        "length": 114
      }
    },
    {
      "id": "validate",
      "title": "Validate TDMRep rules",
      "status": "fail",
      "evidence": {
        "valid": false,
        "compatibleContentType": false,
        "issue": "Response is not valid JSON.",
        "rawExcerpt": "<!DOCTYPE html><html><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
      },
      "issue": "Response is not valid JSON.",
      "howToFix": "Publish /.well-known/tdmrep.json as an array of TDMRep rule objects with location and tdm-reservation values of 0 or 1."
    }
  ]
}

Agent Ease of UseAuthEstablished

OAuth / OIDC discovery

OAuth / OIDC discovery failed at "Validate resource body".

40 Fail

Needs attention

OAuth / OIDC discovery

Failed check

Issue

Response is not valid JSON.

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

20/100

Status

fail

Category

Auth

Maturity

Established

Goal

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

Result

OAuth / OIDC discovery failed at "Validate resource body".

Validation steps

Validate resource body
Response is not valid JSON.
Probe authorization endpoint with an authorization-code request
authorization_endpoint is missing from discovery metadata.
Reject unregistered authorization redirects
authorization_endpoint is missing from discovery metadata.
Probe token endpoint with advertised grant type
token_endpoint is missing from discovery metadata.

Evidence

{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/openid-configuration",
        "statusCode": 200,
        "contentType": "text/html"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "compatibleContentType": false,
        "issue": "Response is not valid JSON.",
        "rawExcerpt": "<!DOCTYPE html><html><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
      },
      "issue": "Response is not valid JSON.",
      "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."
    },
    {
      "id": "authorization-endpoint",
      "title": "Probe authorization endpoint with an authorization-code request",
      "status": "fail",
      "evidence": {
        "url": ""
      },
      "issue": "authorization_endpoint is missing from discovery metadata.",
      "howToFix": "Advertise only implemented OAuth/OIDC endpoints."
    },
    {
      "id": "authorization-redirect-safety",
      "title": "Reject unregistered authorization redirects",
      "status": "fail",
      "evidence": {
        "url": ""
      },
      "issue": "authorization_endpoint is missing from discovery metadata.",
      "howToFix": "Validate clients and redirect_uri values before redirecting."
    },
    {
      "id": "token-endpoint",
      "title": "Probe token endpoint with advertised grant type",
      "status": "fail",
      "evidence": {
        "url": ""
      },
      "issue": "token_endpoint is missing from discovery metadata.",
      "howToFix": "Advertise only implemented OAuth/OIDC endpoints."
    }
  ],
  "authApplicability": {
    "supportsAuth": false,
    "score": 0,
    "signals": []
  },
  "resourceFetchSucceeded": true
}

Agent Ease of UseAuthEmerging recommendation

OAuth Protected Resource

OAuth Protected Resource failed at "Validate protected resource metadata".

34 Fail

Needs attention

OAuth Protected Resource

Failed check

Issue

Response is not valid JSON.

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

33/100

Status

fail

Category

Auth

Maturity

Emerging recommendation

Goal

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

Result

OAuth Protected Resource failed at "Validate protected resource metadata".

Validation steps

Validate protected resource metadata
Response is not valid JSON.
Validate protected resource identity
Protected resource metadata `resource` did not match the resource identifier used to retrieve it.
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": "metadata",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch protected resource metadata",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/oauth-protected-resource",
        "statusCode": 200,
        "contentType": "text/html"
      },
      "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": "<!DOCTYPE html><html><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
      },
      "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://pine-labs.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": 200,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://pine-labs.com/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "resourceMatchesRequestContext": true
          },
          {
            "path": "/api/admin/summary",
            "statusCode": 200,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://pine-labs.com/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "resourceMatchesRequestContext": true
          },
          {
            "path": "/api/scans",
            "statusCode": 200,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://pine-labs.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": false,
    "score": 0,
    "signals": []
  },
  "resourceFetchSucceeded": true
}

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 UseAPIEstablished

OpenAPI discovery

OpenAPI discovery failed at "Find valid OpenAPI document".

33 Fail

Needs attention

OpenAPI discovery

Failed check

Issue

OpenAPI YAML document did not match the expected shape. Content-Type "text/html" 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" 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": 200,
            "contentType": "text/html",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html\" 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><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
          },
          {
            "path": "/openapi.yaml",
            "statusCode": 200,
            "contentType": "text/html",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html\" 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><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
          },
          {
            "path": "/swagger.json",
            "statusCode": 200,
            "contentType": "text/html",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html\" 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><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
          },
          {
            "path": "/swagger.yaml",
            "statusCode": 200,
            "contentType": "text/html",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html\" 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><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
          },
          {
            "path": "/api/openapi.json",
            "statusCode": 200,
            "contentType": "text/html",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html\" 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><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
          },
          {
            "path": "/api/swagger.json",
            "statusCode": 200,
            "contentType": "text/html",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html\" 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><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
          },
          {
            "path": "/docs/openapi.json",
            "statusCode": 200,
            "contentType": "text/html",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html\" 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><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
          }
        ]
      },
      "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html\" 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 DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

25 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 DiscoverabilityDiscoverabilityEstablished

High-value schema types

High-value schema types is missing or incomplete.

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

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

25 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 DiscoverabilityContent ReadinessEstablished

Markdown negotiation

Markdown negotiation failed at "Markdown content type".

25 Fail

Needs attention

Markdown negotiation

Failed check

Issue

Content-Type "text/html" 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" does not indicate Markdown when requested with Accept: text/markdown.
Vary: Accept header
Markdown negotiation is missing Vary: Accept; current Vary header is "(none)".
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"
      },
      "issue": "Content-Type \"text/html\" 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": ""
      },
      "issue": "Markdown negotiation is missing Vary: Accept; current Vary header is \"(none)\".",
      "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": 10,
        "excerpt": "<!DOCTYPE html><html><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>",
        "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 DiscoverabilityDiscoverabilityEstablished

Organization / WebSite schema

Organization / WebSite schema is missing or incomplete.

25 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 DiscoverabilityContent ReadinessEstablished

Semantic HTML

Semantic HTML is missing or incomplete.

25 Fail

Needs attention

Semantic HTML

Failed check

Issue

Semantic HTML is incomplete: missing <main> landmark; missing <nav> landmark; missing <footer> landmark; invalid h1 (found 0).

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

AI DiscoverabilityContent ReadinessEstablished

Structured data

Structured data is missing or incomplete.

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

Agent Ease of UseAPIEstablished

API Catalog

API Catalog failed at "Validate RFC 9727 linkset".

22 Fail

Needs attention

API Catalog

Failed check

Issue

Response is not valid JSON.

Why it matters

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

Check name

API Catalog

Score

33/100

Status

fail

Category

API

Maturity

Established

Goal

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

Result

API Catalog failed at "Validate RFC 9727 linkset".

Validation steps

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": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch API catalog",
      "status": "pass",
      "evidence": {
        "statusCode": 200,
        "contentType": "text/html"
      },
      "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><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
      },
      "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 UseMCPEmerging recommendation

MCP Server Card

MCP Server Card failed at "Validate resource body".

21 Fail

Needs attention

MCP Server Card

Failed check

Issue

Response is not valid JSON.

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

38/100

Status

fail

Category

MCP

Maturity

Emerging recommendation

Goal

Publish an MCP Server Card for agent discovery.

Result

MCP Server Card failed at "Validate resource body".

Validation steps

Validate resource body
Response is not valid JSON.
Verify advertised MCP transport endpoints
At least one same-origin transport failed MCP initialize or advertised capability list probes. See probes[].capabilityProbes for the exact method, status, JSON-RPC error, and response excerpt.
Verify advertised MCP tool execution
MCP discovery passed, but no advertised tool could be safely executed by this scanner.

Evidence

{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/mcp/server-card.json",
        "statusCode": 200,
        "contentType": "text/html"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "validJson": false,
        "compatibleContentType": false,
        "issue": "Response is not valid JSON.",
        "rawExcerpt": "<!DOCTYPE html><html><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
      },
      "issue": "Response is not valid JSON.",
      "howToFix": "Publish an MCP server card with valid transports and make each advertised local endpoint answer an MCP initialize request."
    },
    {
      "id": "endpoint-verification",
      "title": "Verify advertised MCP transport endpoints",
      "status": "fail",
      "evidence": {
        "probes": []
      },
      "issue": "At least one same-origin transport failed MCP initialize or advertised capability list probes. See probes[].capabilityProbes for the exact method, status, JSON-RPC error, and response excerpt.",
      "howToFix": "Expose a real MCP endpoint for advertised transports, or remove transports that point to ordinary HTTP APIs."
    },
    {
      "id": "tool-execution",
      "title": "Verify advertised MCP tool execution",
      "status": "warning",
      "evidence": {
        "probes": []
      },
      "issue": "MCP discovery passed, but no advertised tool could be safely executed by this scanner.",
      "howToFix": "Implement tools/call for advertised tools, or report the MCP card as discovery-only until tools are executable."
    }
  ]
}

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy is missing or incomplete.

20 Fail

Needs attention

Content-Security-Policy

Failed check

Issue

Content-Security-Policy is missing or incomplete.

Why it matters

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

Check name

Content-Security-Policy

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

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

Result

Content-Security-Policy is missing or incomplete.

Evidence

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

Security & TrustSecurity & TrustEstablished

Frame protection

Frame protection is missing or incomplete.

20 Fail

Needs attention

Frame protection

Failed check

Issue

Frame protection is missing or incomplete.

Why it matters

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

Check name

Frame protection

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

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

Result

Frame protection is missing or incomplete.

Evidence

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

Security & TrustSecurity & TrustEstablished

HSTS header

HSTS header is missing or incomplete.

20 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": null
}

Security & TrustSecurity & TrustEstablished

Referrer-Policy

Referrer-Policy is missing or incomplete.

20 Fail

Needs attention

Referrer-Policy

Failed check

Issue

Referrer-Policy is missing or incomplete.

Why it matters

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

Check name

Referrer-Policy

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Limit how much referrer data leaves the site.

Result

Referrer-Policy is missing or incomplete.

Evidence

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

Security & TrustSecurity & TrustEstablished

X-Content-Type-Options

X-Content-Type-Options is missing or incomplete.

20 Fail

Needs attention

X-Content-Type-Options

Failed check

Issue

X-Content-Type-Options is missing or incomplete.

Why it matters

X-Content-Type-Options prevents browsers from treating mislabeled files as executable content, reducing content-sniffing attacks.

Check name

X-Content-Type-Options

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Prevent MIME sniffing for browser-loaded resources.

Result

X-Content-Type-Options is missing or incomplete.

Evidence

{
  "header": "x-content-type-options",
  "value": null
}

Agent Ease of UseAPIEmerging recommendation

AI context endpoint

AI context endpoint failed at "Validate resource body".

17 Fail

Needs attention

AI context endpoint

Failed check

Issue

Content-Type "text/html" is not JSON, Markdown, or text/plain.

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

50/100

Status

fail

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 failed at "Validate resource body".

Validation steps

Validate resource body
Content-Type "text/html" is not JSON, Markdown, or text/plain.

Evidence

{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/api/ai/context",
        "statusCode": 200,
        "contentType": "text/html"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "compatibleContentType": false,
        "issue": "Content-Type \"text/html\" is not JSON, Markdown, or text/plain.",
        "rawExcerpt": "<!DOCTYPE html><html><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
      },
      "issue": "Content-Type \"text/html\" is not JSON, Markdown, or text/plain.",
      "howToFix": "Publish a concise JSON or Markdown AI context endpoint describing the product, public actions, and machine-readable resources."
    }
  ]
}

Agent Ease of UseMCPEmerging recommendation

mcp.json

mcp.json failed at "Validate resource body".

17 Fail

Needs attention

mcp.json

Failed check

Issue

Response is not valid JSON.

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

50/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 "Validate resource body".

Validation steps

Validate resource body
Response is not valid JSON.

Evidence

{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/mcp.json",
        "statusCode": 200,
        "contentType": "text/html"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "validJson": false,
        "compatibleContentType": false,
        "issue": "Response is not valid JSON.",
        "rawExcerpt": "<!DOCTYPE html><html><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
      },
      "issue": "Response is not valid JSON.",
      "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 "Validate resource body".

17 Fail

Needs attention

Web Bot Auth request signing

Failed check

Issue

Response is not valid JSON.

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

50/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 "Validate resource body".

Validation steps

Validate resource body
Response is not valid JSON.

Evidence

{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/http-message-signatures-directory",
        "statusCode": 200,
        "contentType": "text/html"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "validJson": false,
        "compatibleContentType": false,
        "issue": "Response is not valid JSON.",
        "rawExcerpt": "<!DOCTYPE html><html><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
      },
      "issue": "Response is not valid JSON.",
      "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 "Validate resource body".

17 Fail

Needs attention

WebMCP manifest

Failed check

Issue

Response is not valid JSON.

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

50/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 "Validate resource body".

Validation steps

Validate resource body
Response is not valid JSON.

Evidence

{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/webmcp.json",
        "statusCode": 200,
        "contentType": "text/html"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "validJson": false,
        "compatibleContentType": false,
        "issue": "Response is not valid JSON.",
        "rawExcerpt": "<!DOCTYPE html><html><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
      },
      "issue": "Response is not valid JSON.",
      "howToFix": "Keep declarative WebMCP manifest discovery informational until the manifest shape stabilizes; validate tools if you publish one."
    }
  ]
}

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

Issue

No DNS-AID entrypoint records were found under _agents.

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

Resolve DNS-AID SVCB/HTTPS records
No DNS-AID entrypoint records were found under _agents.
Validate alpn and endpoint parameters
Include alpn and endpoint service parameters in each DNS-AID record so agents know the protocol and target entrypoint.
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": "pine-labs.com",
        "probes": [
          {
            "name": "_index._agents.pine-labs.com",
            "found": false,
            "recordCount": 1,
            "records": [],
            "hasAlpn": false,
            "hasEndpoint": false
          },
          {
            "name": "_a2a._agents.pine-labs.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": "pine-labs.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 UseSkill DiscoveryEmerging recommendation

Agent Skills index

Agent Skills index failed at "Validate resource body".

13 Fail

Needs attention

Agent Skills index

Failed check

Issue

Response is not valid JSON.

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

33/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an agent skills discovery index.

Result

Agent Skills index failed at "Validate resource body".

Validation steps

Validate resource body
Response is not valid JSON.
Fetch advertised SKILL.md files
One or more advertised skill URLs were missing, did not look like SKILL.md Markdown, or failed digest verification.

Evidence

{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/agent-skills/index.json",
        "statusCode": 200,
        "contentType": "text/html"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "validJson": false,
        "compatibleContentType": false,
        "issue": "Response is not valid JSON.",
        "rawExcerpt": "<!DOCTYPE html><html><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
      },
      "issue": "Response is not valid JSON.",
      "howToFix": "Publish an index with a non-empty skills array and reachable SKILL.md URLs."
    },
    {
      "id": "skill-documents",
      "title": "Fetch advertised SKILL.md files",
      "status": "fail",
      "evidence": {
        "checkedCount": 0,
        "totalCount": 0,
        "checked": []
      },
      "issue": "One or more advertised skill URLs were missing, did not look like SKILL.md Markdown, or failed digest verification.",
      "howToFix": "Make every advertised skill URL return Markdown with a top-level heading and a matching sha256 digest, or remove broken entries from the index."
    }
  ]
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Entity clarity

GEO: Entity clarity scored 0/100 and needs a fix.

10 Fail

Needs attention

GEO: Entity clarity

Failed check

Issue

Title/H1 terms missing from description: none.

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

0/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: Entity clarity scored 0/100 and needs a fix.

Evidence

{
  "title": "",
  "h1": "",
  "description": "",
  "topicOverlap": 0,
  "topicTerms": [],
  "descriptionTerms": [],
  "missingFromDescription": [],
  "score": 0,
  "weight": 28
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

A2A Agent Card failed at "Validate resource body".

10 Fail

Needs attention

A2A Agent Card

Failed check

Issue

Response is not valid JSON.

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

50/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 "Validate resource body".

Validation steps

Validate resource body
Response is not valid JSON.

Evidence

{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/agent-card.json",
        "statusCode": 200,
        "contentType": "text/html"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "validJson": false,
        "compatibleContentType": false,
        "issue": "Response is not valid JSON.",
        "rawExcerpt": "<!DOCTYPE html><html><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
      },
      "issue": "Response is not valid JSON.",
      "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.json

agent.json failed at "Validate resource body".

10 Fail

Needs attention

agent.json

Failed check

Issue

Response is not valid JSON.

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

50/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 "Validate resource body".

Validation steps

Validate resource body
Response is not valid JSON.

Evidence

{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/agent.json",
        "statusCode": 200,
        "contentType": "text/html"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "validJson": false,
        "compatibleContentType": false,
        "issue": "Response is not valid JSON.",
        "rawExcerpt": "<!DOCTYPE html><html><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
      },
      "issue": "Response is not valid JSON.",
      "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 "Validate resource body".

10 Fail

Needs attention

agents.json

Failed check

Issue

Response is not valid JSON.

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

50/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 "Validate resource body".

Validation steps

Validate resource body
Response is not valid JSON.

Evidence

{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/agents.json",
        "statusCode": 200,
        "contentType": "text/html"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "validJson": false,
        "compatibleContentType": false,
        "issue": "Response is not valid JSON.",
        "rawExcerpt": "<!DOCTYPE html><html><head><script>window.onload=function(){window.location.href=\"/lander\"}</script></head></html>"
      },
      "issue": "Response is not valid JSON.",
      "howToFix": "If this site uses agents.json, publish JSON with an agents array containing name and url for each agent."
    }
  ]
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Source and trust signals

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

8 Fail

Needs attention

AIO: Source and trust signals

Failed check

Issue

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

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

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: Source and trust signals scored 0/100 and needs a fix.

Evidence

{
  "signals": {
    "author": false,
    "publisher": false,
    "freshnessDate": false,
    "aboutOrContact": false,
    "policyLinks": false
  },
  "missing": [
    "author",
    "publisher",
    "freshnessDate",
    "aboutOrContact",
    "policyLinks"
  ],
  "authorMeta": "",
  "schemaAuthors": [],
  "schemaPublishers": [],
  "schemaDates": [],
  "visibleDates": [],
  "aboutLinks": [],
  "contactLinks": [],
  "privacyLinks": [],
  "score": 0,
  "weight": 20
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer evidence and trust

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

8 Fail

Needs attention

AEO: Answer evidence and trust

Failed check

Issue

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

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

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

Evidence

{
  "signals": {
    "author": false,
    "publisher": false,
    "freshnessDate": false,
    "aboutOrContact": false,
    "policyLinks": false
  },
  "missing": [
    "author",
    "publisher",
    "freshnessDate",
    "aboutOrContact",
    "policyLinks"
  ],
  "authorMeta": "",
  "schemaAuthors": [],
  "schemaPublishers": [],
  "schemaDates": [],
  "visibleDates": [],
  "aboutLinks": [],
  "contactLinks": [],
  "privacyLinks": [],
  "score": 0,
  "weight": 22
}

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

AEO: Entity and definition clarity

AEO: Entity and definition clarity scored 0/100 and needs a fix.

6 Fail

Needs attention

AEO: Entity and definition clarity

Failed check

Issue

Entity or definition gaps: no clear definition pattern found.

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

0/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: Entity and definition clarity scored 0/100 and needs a fix.

Evidence

{
  "title": "",
  "h1": "",
  "description": "",
  "topicOverlap": 0,
  "definitionCount": 0,
  "topicTerms": [],
  "descriptionTerms": [],
  "missingFromDescription": [],
  "score": 0,
  "weight": 18
}

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.

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: Extraction-friendly structure

GEO: Extraction-friendly structure scored 50/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, clear definition sentence using "is", "means", or "refers to" where natural, JSON-LD structured data.

Details

Why it matters

Check name

GEO: Extraction-friendly structure

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: Extraction-friendly structure scored 50/100 and needs improvement.

Evidence

{
  "hasSummary": false,
  "tableCount": 0,
  "tablesWithHead": 0,
  "tablesMissingThead": [],
  "orderedLists": 0,
  "hasFaq": false,
  "definitionPatterns": 0,
  "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",
    "clear definition sentence using \"is\", \"means\", or \"refers to\" where natural",
    "JSON-LD structured data"
  ],
  "score": 50,
  "weight": 24
}

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 0 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": 0,
  "htmlBytes": 127,
  "robots": {
    "checkedCrawlers": [
      "gptbot",
      "chatgpt-user",
      "claudebot",
      "perplexitybot",
      "google-extended"
    ],
    "blocked": [],
    "allows": true
  },
  "schemaBlocks": 0,
  "finalUrl": "https://pine-labs.com/",
  "robotsExcerpt": "User-agent: *\nAllow: /\nLLM-Policy: /llms.txt\nSitemap: /sitemap.xml",
  "score": 55,
  "weight": 26
}

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Page experience for AIO

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

2 Warning

Needs attention

AIO: Page experience for AIO

Warning

Issue

Missing viewport meta tag. Only 0 words of visible rendered text were 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: Page experience for AIO

Score

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

Evidence

{
  "viewportContent": "",
  "visibleWords": 0,
  "htmlBytes": 127,
  "imagesMissingDimensions": [],
  "possibleDialogs": [],
  "score": 50,
  "weight": 10
}

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

Issue

AEO readiness is incomplete.

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

AIO: Google eligibility and indexability

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

1 Warning

Needs attention

AIO: Google eligibility and indexability

Warning

Issue

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

80/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

Evidence

{
  "status": 200,
  "googlebotBlocked": false,
  "metaRobotsTags": [],
  "xRobotsTag": "",
  "canonical": "",
  "finalUrl": "https://pine-labs.com/",
  "canonicalScore": 0,
  "score": 80,
  "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 0 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": 0,
  "schemaCount": 0,
  "score": 35,
  "weight": 6
}

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

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

Issue

Canonical tag is missing.

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

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": [],
  "expected": [
    {
      "id": "what",
      "label": "What is this page?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does this page work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use this page?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is this page free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does this page compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is this page?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does this page work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use this page?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is this page free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does this page 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

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

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

Performance and AccessibilityAccessibilityBrowser audit

Heading elements are not in a sequentially-descending order

100 Fail

Check name

Heading elements are not in a sequentially-descending order

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. [Learn more about heading order](https://dequeuniversity.com/rules/axe/4.11/heading-order).

References

https://web.dev/learn/accessibility/

Evidence

{
  "description": "Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. [Learn more about heading order](https://dequeuniversity.com/rules/axe/4.11/heading-order)."
}

Performance and AccessibilityPerformanceBrowser audit

Reduce unused CSS

25 Warning

Check name

Reduce unused CSS

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 28 KiB

Fix guidance

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS](https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/).

References

https://web.dev/learn/performance/

Evidence

{
  "displayValue": "Est savings of 28 KiB",
  "description": "Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS](https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/).",
  "numericValue": 0
}

Performance and AccessibilityPerformanceBrowser audit

Loading performance

18 Fail

Check name

Loading performance

Score

64/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

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

References

https://web.dev/learn/performance/

Evidence

{
  "checks": [
    {
      "id": "max-potential-fid",
      "title": "Max Potential First Input Delay",
      "score": 31,
      "displayValue": "320 ms",
      "numericValue": 319.00000000000045
    },
    {
      "id": "speed-index",
      "title": "Speed Index",
      "score": 51,
      "displayValue": "2.3 s",
      "numericValue": 2263.4861686017884
    },
    {
      "id": "first-contentful-paint",
      "title": "First Contentful Paint",
      "score": 89,
      "displayValue": "0.9 s",
      "numericValue": 938.3024604122686
    },
    {
      "id": "server-response-time",
      "title": "Initial server response time was short",
      "score": 100,
      "displayValue": "Root document took 10 ms",
      "numericValue": 14
    },
    {
      "id": "network-rtt",
      "title": "Network Round Trip Times",
      "score": 100,
      "displayValue": "70 ms",
      "numericValue": 72.289305
    },
    {
      "id": "total-blocking-time",
      "title": "Total Blocking Time",
      "score": 0,
      "displayValue": "1,720 ms",
      "numericValue": 1718.000000000001
    },
    {
      "id": "interactive",
      "title": "Time to Interactive",
      "score": 48,
      "displayValue": "4.6 s",
      "numericValue": 4599.058165686944
    },
    {
      "id": "largest-contentful-paint",
      "title": "Largest Contentful Paint",
      "score": 94,
      "displayValue": "1.0 s",
      "numericValue": 1042.8899166799997
    }
  ]
}

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 date	Score	Readiness	Report
Jun 9, 2026	46/100	Level 2, Agent-Limited	Current report