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

OVERALL SCORE

Level 4, Mostly Ready

Good readiness for AI agents
AIDiscoverability54%Agent Easeof Use36%Security& Trust100%GEO, AIO, AEO80%SEO92%Performance& Accessibility96%
  • AI Discoverability 54 out of 100
  • Agent Ease of Use 36 out of 100
  • Security & Trust 100 out of 100
  • GEO, AIO and AEO 80 out of 100
  • SEO 92 out of 100
  • Performance and Accessibility 96 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

PlanetScale - the world’s fastest and most scalable cloud hosting for Vitess and Postgres favicon

PlanetScale - the world’s fastest and most scalable cloud hosting for Vitess and Postgres

PlanetScale offers the world’s fastest and most scalable cloud hosting for Vitess and Postgres.

Next step

Turn this report into a fix workflow

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

Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
54
Needs work12120View details
Discoverability
75
Mostly ready630View details
Content Readiness
50
Needs work560View details
Bot Access Control
33
Priority fix130View details
Agent Ease of Use
36
Priority fix13272View details
API
50
Needs work420View details
Auth
Not Applicable
Not Applicable070View details
MCP
47
Priority fix471View details
Skill Discovery
12
Priority fix1111View details
Agent Commerce
Not Applicable
Not Applicable400
GEO, AIO and AEO
80
Mostly ready926View details
GEO Readiness
Not Applicable
Not Applicable300
AIO Readiness
83
Mostly ready412View details
AEO Readiness
65
Needs work214View details
SEO
92
Strong1010View details
SEO
92
Strong1010View details
Security & Trust
100
Strong900
Security & Trust
100
Strong500
AI Training Exposure
Not Applicable
Not Applicable400
Performance and Accessibility
96
Strong1942View details
Performance
99
Strong1142View details
Accessibility
90
Strong800

Prioritized recommendations

Issues ranked by score impact

35 items need attention

Agent Ease of UseAPIEstablished

OpenAPI discovery

OpenAPI discovery failed at "Find valid OpenAPI document".

100 Fail

Needs attention

OpenAPI discovery

Failed check
01

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.

02

Why it matters

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

Check name

OpenAPI discovery

Score

0/100

Status

fail

Category

API

Maturity

Established

Goal

Publish a valid OpenAPI or Swagger document for API discovery.

Result

OpenAPI discovery failed at "Find valid OpenAPI document".

Validation steps

  1. Find valid OpenAPI document

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

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Find valid OpenAPI document",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/openapi.json",
            "statusCode": 404,
            "contentType": "text/html",
            "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 lang=\"en\"><head><title>404 Page not found - PlanetScale</title><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><meta name=\"theme-color\" content=\"#111111\"/><link rel=\"stylesheet\" href=\"/assets/styles-Bq4K_D9A.css\"/><link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\" sizes=\"16x16\"/><link rel=\"icon\" href=\"/icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"apple-touch-icon\" href=\"/apple-touch-icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"manifest\" href=\"/manifest.webmanifest\"/></head><body><div class=\"flex flex-col items-center gap-1 bg-gray-900 px-3 py-1.5 text-center font-medium text-white sm:flex-row sm:justify-center sm:gap-1.5 sm:py-1 dark:bg-gray-50 dark:text-gray-900\"><svg width=\"5\" height=\"23\" viewBox=\"0 0 "
          },
          {
            "path": "/openapi.yaml",
            "statusCode": 404,
            "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 lang=\"en\"><head><title>404 Page not found - PlanetScale</title><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><meta name=\"theme-color\" content=\"#111111\"/><link rel=\"stylesheet\" href=\"/assets/styles-Bq4K_D9A.css\"/><link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\" sizes=\"16x16\"/><link rel=\"icon\" href=\"/icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"apple-touch-icon\" href=\"/apple-touch-icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"manifest\" href=\"/manifest.webmanifest\"/></head><body><div class=\"flex flex-col items-center gap-1 bg-gray-900 px-3 py-1.5 text-center font-medium text-white sm:flex-row sm:justify-center sm:gap-1.5 sm:py-1 dark:bg-gray-50 dark:text-gray-900\"><svg width=\"5\" height=\"23\" viewBox=\"0 0 "
          },
          {
            "path": "/swagger.json",
            "statusCode": 404,
            "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 lang=\"en\"><head><title>404 Page not found - PlanetScale</title><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><meta name=\"theme-color\" content=\"#111111\"/><link rel=\"stylesheet\" href=\"/assets/styles-Bq4K_D9A.css\"/><link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\" sizes=\"16x16\"/><link rel=\"icon\" href=\"/icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"apple-touch-icon\" href=\"/apple-touch-icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"manifest\" href=\"/manifest.webmanifest\"/></head><body><div class=\"flex flex-col items-center gap-1 bg-gray-900 px-3 py-1.5 text-center font-medium text-white sm:flex-row sm:justify-center sm:gap-1.5 sm:py-1 dark:bg-gray-50 dark:text-gray-900\"><svg width=\"5\" height=\"23\" viewBox=\"0 0 "
          },
          {
            "path": "/swagger.yaml",
            "statusCode": 404,
            "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 lang=\"en\"><head><title>404 Page not found - PlanetScale</title><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><meta name=\"theme-color\" content=\"#111111\"/><link rel=\"stylesheet\" href=\"/assets/styles-Bq4K_D9A.css\"/><link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\" sizes=\"16x16\"/><link rel=\"icon\" href=\"/icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"apple-touch-icon\" href=\"/apple-touch-icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"manifest\" href=\"/manifest.webmanifest\"/></head><body><div class=\"flex flex-col items-center gap-1 bg-gray-900 px-3 py-1.5 text-center font-medium text-white sm:flex-row sm:justify-center sm:gap-1.5 sm:py-1 dark:bg-gray-50 dark:text-gray-900\"><svg width=\"5\" height=\"23\" viewBox=\"0 0 "
          },
          {
            "path": "/api/openapi.json",
            "statusCode": 404,
            "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 lang=\"en\"><head><title>404 Page not found - PlanetScale</title><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><meta name=\"theme-color\" content=\"#111111\"/><link rel=\"stylesheet\" href=\"/assets/styles-Bq4K_D9A.css\"/><link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\" sizes=\"16x16\"/><link rel=\"icon\" href=\"/icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"apple-touch-icon\" href=\"/apple-touch-icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"manifest\" href=\"/manifest.webmanifest\"/></head><body><div class=\"flex flex-col items-center gap-1 bg-gray-900 px-3 py-1.5 text-center font-medium text-white sm:flex-row sm:justify-center sm:gap-1.5 sm:py-1 dark:bg-gray-50 dark:text-gray-900\"><svg width=\"5\" height=\"23\" viewBox=\"0 0 "
          },
          {
            "path": "/api/swagger.json",
            "statusCode": 404,
            "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 lang=\"en\"><head><title>404 Page not found - PlanetScale</title><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><meta name=\"theme-color\" content=\"#111111\"/><link rel=\"stylesheet\" href=\"/assets/styles-Bq4K_D9A.css\"/><link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\" sizes=\"16x16\"/><link rel=\"icon\" href=\"/icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"apple-touch-icon\" href=\"/apple-touch-icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"manifest\" href=\"/manifest.webmanifest\"/></head><body><div class=\"flex flex-col items-center gap-1 bg-gray-900 px-3 py-1.5 text-center font-medium text-white sm:flex-row sm:justify-center sm:gap-1.5 sm:py-1 dark:bg-gray-50 dark:text-gray-900\"><svg width=\"5\" height=\"23\" viewBox=\"0 0 "
          },
          {
            "path": "/docs/openapi.json",
            "statusCode": 404,
            "contentType": "text/plain;charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": true,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "Asset not found"
          }
        ]
      },
      "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 DiscoverabilityBot Access ControlEstablished

AI bot rules in robots.txt

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

50 Fail

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

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

02

Why it matters

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

Check name

AI bot rules in robots.txt

Score

0/100

Status

fail

Category

Bot Access Control

Maturity

Established

Goal

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

Result

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

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

AI DiscoverabilityDiscoverabilityEstablished

High-value schema types

High-value schema types is missing or incomplete.

50 Fail

Needs attention

High-value schema types

Failed check
01

Issue

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

02

Why it matters

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

Check name

High-value schema types

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

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

Result

High-value schema types is missing or incomplete.

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

AI DiscoverabilityBot Access ControlInformational

Web Bot Auth request signing

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

50 Fail

Needs attention

Web Bot Auth request signing

Failed check
01

Issue

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

02

Why it matters

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

Check name

Web Bot Auth request signing

Score

0/100

Status

fail

Category

Bot Access Control

Maturity

Informational

Goal

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

Result

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

Validation steps

  1. Fetch to find resource

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

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

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

33 Fail

Needs attention

Content freshness signals

Failed check
01

Issue

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

02

Why it matters

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

Check name

Content freshness signals

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

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

Result

Content freshness signals is missing or incomplete.

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

AI DiscoverabilityContent ReadinessEstablished

Markdown negotiation

Markdown negotiation failed at "Markdown content type".

33 Fail

Needs attention

Markdown negotiation

Failed check
01

Issue

Content-Type "text/html" does not indicate Markdown when requested with Accept: text/markdown.

02

Why it matters

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

Check name

Markdown negotiation

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Return HTML responses as markdown when agents request it.

Result

Markdown negotiation failed at "Markdown content type".

Validation steps

  1. Markdown content type

    Content-Type "text/html" does not indicate Markdown when requested with Accept: text/markdown.

  2. Vary: Accept header

    Markdown negotiation is missing Vary: Accept; current Vary header is "(none)".

  3. Structured Markdown body

    Markdown response is missing a heading.

Evidence
{
  "failedStep": "content-type",
  "steps": [
    {
      "id": "content-type",
      "title": "Markdown content type",
      "status": "fail",
      "evidence": {
        "statusCode": 200,
        "contentType": "text/html"
      },
      "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": 7832,
        "excerpt": "<!DOCTYPE html><html lang=\"en\"><head><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><meta name=\"theme-color\" content=\"#111111\"/><meta name=\"user-signed-in\" content=\"false\"/><title>PlanetScale - t",
        "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.

33 Fail

Needs attention

Semantic HTML

Failed check
01

Issue

Semantic HTML is incomplete: 1 buttons missing accessible names.

Details

02

Why it matters

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

Check name

Semantic HTML

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose readable page structure through semantic HTML and accessible controls.

Result

Semantic HTML is missing or incomplete.

Evidence
{
  "main": true,
  "nav": true,
  "footer": true,
  "meaningfulH1": true,
  "headingOrder": true,
  "accessibleLinks": true,
  "accessibleButtons": false,
  "imageAltCoverage": true,
  "formAutocompleteCoverage": true,
  "details": {
    "inaccessibleLinks": [],
    "inaccessibleButtons": [
      "<button type=\"button\" aria-hidden=\"true\" style=\"position:fixed;top:1px;left:1px;width:1px;height:0;padding:0;margin:-1px;overflow:hidden;clip:rect(0, 0, 0, 0);white-space:nowrap;border-width:0\"></button>"
    ],
    "missingAutocompleteInputs": [],
    "imagesMissingAlt": [],
    "skippedHeadingLevels": []
  },
  "counts": {
    "h1": 1,
    "headings": 11,
    "links": 96,
    "inaccessibleLinks": 0,
    "buttons": 8,
    "inaccessibleButtons": 1,
    "images": 1,
    "imagesWithAlt": 1,
    "autocompleteInputs": 0,
    "inputsWithAutocomplete": 0,
    "missingAutocompleteInputs": 0
  }
}

Agent Ease of UseMCPInformational

WebMCP manifest

WebMCP manifest failed at "Fetch to find resource".

33 Fail

Needs attention

WebMCP manifest

Failed check
01

Issue

WebMCP manifest was not found at the expected path.

02

Why it matters

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

Check name

WebMCP manifest

Score

0/100

Status

fail

Category

MCP

Maturity

Informational

Goal

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

Result

WebMCP manifest failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    WebMCP manifest was not found at the expected path.

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

AI DiscoverabilityDiscoverabilityEstablished

Link headers

Link headers failed at "Fetch same-origin Link header targets".

25 Fail

Needs attention

Link headers

Failed check
01

Issue

Link header target /docs/openapi.yaml (service-desc) advertised application/yaml but returned text/yaml.

02

Why it matters

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

Check name

Link headers

Score

50/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Include Link response headers for agent discovery using RFC 8288.

Result

Link headers failed at "Fetch same-origin Link header targets".

Validation steps

  1. Fetch same-origin Link header targets

    Link header target /docs/openapi.yaml (service-desc) advertised application/yaml but returned text/yaml.

Evidence
{
  "failedStep": "target-validation",
  "steps": [
    {
      "id": "presence",
      "title": "Find useful Link headers",
      "status": "pass",
      "evidence": {
        "links": [
          {
            "url": "/docs/openapi.yaml",
            "rel": "service-desc",
            "type": "application/yaml"
          },
          {
            "url": "/docs",
            "rel": "service-doc"
          },
          {
            "url": "/llms.txt",
            "rel": "describedby",
            "type": "text/plain"
          }
        ]
      },
      "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": [
          {
            "rel": "service-desc",
            "url": "/docs/openapi.yaml",
            "type": "application/yaml",
            "statusCode": 200,
            "contentType": "text/yaml",
            "typeMatches": false
          },
          {
            "rel": "service-doc",
            "url": "/docs",
            "statusCode": 200,
            "contentType": "text/html; charset=utf-8",
            "typeMatches": true
          }
        ],
        "failures": [
          {
            "rel": "service-desc",
            "url": "/docs/openapi.yaml",
            "expectedType": "application/yaml",
            "actualContentType": "text/yaml",
            "reason": "Content-Type did not match advertised type."
          }
        ]
      },
      "issue": "Link header target /docs/openapi.yaml (service-desc) advertised application/yaml but returned text/yaml.",
      "howToFix": "Make each same-origin Link 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
01

Issue

MCP Server Card response is missing required fields or has invalid transports.

Details

02

Why it matters

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

Check name

MCP Server Card

Score

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

  1. Validate resource body

    MCP Server Card response is missing required fields or has invalid transports.

    Missing required fields
    • protocolVersion
    • transports array
  2. 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.

  3. 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": "application/json"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "validJson": true,
        "compatibleContentType": true,
        "document": {
          "serverInfo": {
            "name": "PlanetScale",
            "version": "1.0.0"
          },
          "remotes": [
            {
              "transportType": "streamable-http",
              "url": "https://mcp.pscale.dev/mcp/planetscale"
            }
          ],
          "capabilities": {
            "tools": true,
            "resources": true,
            "prompts": false
          }
        },
        "rawExcerpt": "{\n  \"serverInfo\": {\n    \"name\": \"PlanetScale\",\n    \"version\": \"1.0.0\"\n  },\n  \"remotes\": [\n    {\n      \"transportType\": \"streamable-http\",\n      \"url\": \"https://mcp.pscale.dev/mcp/planetscale\"\n    }\n  ],\n  \"capabilities\": {\n    \"tools\": true,\n    \"resources\": true,\n    \"prompts\": false\n  }\n}",
        "issue": "MCP Server Card response is missing required fields or has invalid transports.",
        "issueDetails": [
          {
            "title": "Missing required fields",
            "items": [
              "protocolVersion",
              "transports array"
            ]
          }
        ],
        "missing": [
          "protocolVersion",
          "transports array"
        ],
        "protocolVersion": "",
        "transportCount": 0,
        "transports": [],
        "invalidTransports": [],
        "capabilityKeys": [
          "tools",
          "resources",
          "prompts"
        ]
      },
      "issue": "MCP Server Card response is missing required fields or has invalid transports.",
      "howToFix": "Publish an MCP server card with valid transports and make each advertised local endpoint answer an MCP initialize request.",
      "issueDetails": [
        {
          "title": "Missing required fields",
          "items": [
            "protocolVersion",
            "transports array"
          ]
        }
      ]
    },
    {
      "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."
    }
  ]
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

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

20 Fail

Needs attention

A2A Agent Card

Failed check
01

Issue

A2A Agent Card was not found at the expected path.

02

Why it matters

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

Check name

A2A Agent Card

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Fetch to find resource

    A2A Agent Card was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/agent-card.json",
            "statusCode": 404,
            "contentType": "text/html",
            "length": 7973
          },
          {
            "path": "/.well-known/a2a/agent-card.json",
            "statusCode": 404,
            "contentType": "text/html",
            "length": 7973
          },
          {
            "path": "/agent-card.json",
            "statusCode": 404,
            "contentType": "text/html",
            "length": 7973
          }
        ]
      },
      "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.json

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

20 Fail

Needs attention

agent.json

Failed check
01

Issue

agent.json was not found at the expected path.

02

Why it matters

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

Check name

agent.json

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Fetch to find resource

    agent.json was not found at the expected path.

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

Agent Ease of UseSkill DiscoveryInformational

agents.json

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

20 Fail

Needs attention

agents.json

Failed check
01

Issue

agents.json was not found at the expected path.

02

Why it matters

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

Check name

agents.json

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Informational

Goal

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

Result

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

Validation steps

  1. Fetch to find resource

    agents.json was not found at the expected path.

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

Agent Ease of UseMCPEmerging recommendation

mcp.json

mcp.json failed at "Validate resource body".

17 Fail

Needs attention

mcp.json

Failed check
01

Issue

mcp.json response did not match the expected MCP server metadata shape. missing: protocolVersion, transport or transports.

Details

02

Why it matters

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

Check name

mcp.json

Score

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

  1. Validate resource body

    mcp.json response did not match the expected MCP server metadata shape. missing: protocolVersion, transport or transports.

    Missing required fields
    • protocolVersion
    • transport or transports
Evidence
{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/mcp/server-card.json",
        "statusCode": 200,
        "contentType": "application/json"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "validJson": true,
        "compatibleContentType": true,
        "document": {
          "serverInfo": {
            "name": "PlanetScale",
            "version": "1.0.0"
          },
          "remotes": [
            {
              "transportType": "streamable-http",
              "url": "https://mcp.pscale.dev/mcp/planetscale"
            }
          ],
          "capabilities": {
            "tools": true,
            "resources": true,
            "prompts": false
          }
        },
        "rawExcerpt": "{\n  \"serverInfo\": {\n    \"name\": \"PlanetScale\",\n    \"version\": \"1.0.0\"\n  },\n  \"remotes\": [\n    {\n      \"transportType\": \"streamable-http\",\n      \"url\": \"https://mcp.pscale.dev/mcp/planetscale\"\n    }\n  ],\n  \"capabilities\": {\n    \"tools\": true,\n    \"resources\": true,\n    \"prompts\": false\n  }\n}",
        "issue": "mcp.json response did not match the expected MCP server metadata shape. missing: protocolVersion, transport or transports.",
        "issueDetails": [
          {
            "title": "Missing required fields",
            "items": [
              "protocolVersion",
              "transport or transports"
            ]
          }
        ],
        "missing": [
          "protocolVersion",
          "transport or transports"
        ],
        "protocolVersion": "",
        "transportCount": 0,
        "transports": [],
        "invalidTransports": [],
        "toolCount": 0,
        "capabilityKeys": [
          "tools",
          "resources",
          "prompts"
        ]
      },
      "issue": "mcp.json response did not match the expected MCP server metadata shape. missing: protocolVersion, transport or transports.",
      "howToFix": "Publish mcp.json or an MCP server card with serverInfo, protocolVersion, transport endpoint, and capabilities.",
      "issueDetails": [
        {
          "title": "Missing required fields",
          "items": [
            "protocolVersion",
            "transport or transports"
          ]
        }
      ]
    }
  ]
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

DNS-AID Agent Discovery

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

15 Fail

Needs attention

DNS-AID Agent Discovery

Failed check
01

Issue

No DNS-AID entrypoint records were found under _agents.

02

Why it matters

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

Check name

DNS-AID Agent Discovery

Score

25/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Resolve DNS-AID SVCB/HTTPS records

    No DNS-AID entrypoint records were found under _agents.

  2. Validate alpn and endpoint parameters

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

  3. Check DNSSEC material

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

Evidence
{
  "failedStep": "svcb-https-records",
  "steps": [
    {
      "id": "svcb-https-records",
      "title": "Resolve DNS-AID SVCB/HTTPS records",
      "status": "fail",
      "evidence": {
        "hostname": "planetscale.com",
        "probes": [
          {
            "name": "_index._agents.planetscale.com",
            "found": false,
            "recordCount": 1,
            "records": [],
            "hasAlpn": false,
            "hasEndpoint": false
          },
          {
            "name": "_a2a._agents.planetscale.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": "planetscale.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
01

Issue

Agent Skills Index response did not match the expected shape. missing or invalid top-level fields: $schema, version=0.2.0; invalid skills: [{"index":0,"name":"planetscale","missing":["type","url","digest"],"invalid":[]}].

02

Why it matters

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

Check name

Agent Skills index

Score

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

  1. Validate resource body

    Agent Skills Index response did not match the expected shape. missing or invalid top-level fields: $schema, version=0.2.0; invalid skills: [{"index":0,"name":"planetscale","missing":["type","url","digest"],"invalid":[]}].

  2. 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/skills/index.json",
        "statusCode": 200,
        "contentType": "application/json"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "validJson": true,
        "compatibleContentType": true,
        "document": {
          "skills": [
            {
              "name": "planetscale",
              "description": "Use when managing MySQL (Vitess) or PostgreSQL databases, creating and deploying schema changes, managing database branches, automating database operations via API or CLI, or integrating databases with applications and CI/CD pipelines.",
              "files": [
                "SKILL.md"
              ]
            }
          ]
        },
        "rawExcerpt": "{\"skills\":[{\"name\":\"planetscale\",\"description\":\"Use when managing MySQL (Vitess) or PostgreSQL databases, creating and deploying schema changes, managing database branches, automating database operations via API or CLI, or integrating databases with applications and CI/CD pipelines.\",\"files\":[\"SKILL.md\"]}]}",
        "issue": "Agent Skills Index response did not match the expected shape. missing or invalid top-level fields: $schema, version=0.2.0; invalid skills: [{\"index\":0,\"name\":\"planetscale\",\"missing\":[\"type\",\"url\",\"digest\"],\"invalid\":[]}].",
        "skillCount": 1,
        "validSkillCount": 0,
        "invalidSkills": [
          {
            "index": 0,
            "name": "planetscale",
            "missing": [
              "type",
              "url",
              "digest"
            ],
            "invalid": []
          }
        ],
        "skills": [
          {
            "name": "planetscale",
            "description": "Use when managing MySQL (Vitess) or PostgreSQL databases, creating and deploying schema changes, managing database branches, automating database operations via API or CLI, or integrating databases with applications and CI/CD pipelines.",
            "files": [
              "SKILL.md"
            ]
          }
        ]
      },
      "issue": "Agent Skills Index response did not match the expected shape. missing or invalid top-level fields: $schema, version=0.2.0; invalid skills: [{\"index\":0,\"name\":\"planetscale\",\"missing\":[\"type\",\"url\",\"digest\"],\"invalid\":[]}].",
      "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": 1,
        "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

AIO: Source and trust signals

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

13 Fail

Needs attention

AIO: Source and trust signals

Failed check
01

Issue

Missing AIO trust signals: author, publisher, freshnessDate.

Details

02

Why it matters

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

Check name

AIO: Source and trust signals

Score

40/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

Evidence
{
  "signals": {
    "author": false,
    "publisher": false,
    "freshnessDate": false,
    "aboutOrContact": true,
    "policyLinks": true
  },
  "missing": [
    "author",
    "publisher",
    "freshnessDate"
  ],
  "authorMeta": "",
  "schemaAuthors": [],
  "schemaPublishers": [],
  "schemaDates": [],
  "visibleDates": [],
  "aboutLinks": [
    {
      "href": "/about",
      "text": "and more",
      "html": "<a href=\"/about\" data-discover=\"true\">and more</a>"
    },
    {
      "href": "/about",
      "text": "About",
      "html": "<a class=\"block pl-1ch -indent-1ch text-primary hover:text-contrast\" href=\"/about\" data-discover=\"true\">About</a>"
    },
    {
      "href": "https://www.linkedin.com/company/planetscale",
      "text": "LinkedIn",
      "html": "<a aria-label=\"LinkedIn\" class=\"text-primary\" href=\"https://www.linkedin.com/company/planetscale\" target=\"_blank\" rel=\"noreferrer\">LinkedIn</a>"
    }
  ],
  "contactLinks": [
    {
      "href": "/contact",
      "text": "Get in touch",
      "html": "<a class=\"btn !h-[32px] !px-1 font-semibold\" href=\"/contact\" data-discover=\"true\">Get in touch</a>"
    },
    {
      "href": "/contact",
      "text": "Contact",
      "html": "<a class=\"font-semibold text-primary hover:text-contrast\" href=\"/contact\" data-discover=\"true\">Contact</a>"
    },
    {
      "href": "/contact",
      "text": "Contact",
      "html": "<a class=\"font-semibold text-primary hover:text-contrast\" href=\"/contact\" data-discover=\"true\">Contact</a>"
    },
    {
      "href": "/contact",
      "text": "reach out to us",
      "html": "<a href=\"/contact\" data-discover=\"true\">reach out to us</a>"
    },
    {
      "href": "/docs/support",
      "text": "best-in-class support",
      "html": "<a href=\"/docs/support\">best-in-class support</a>"
    },
    {
      "href": "https://support.planetscale.com/hc/en-us",
      "text": "Support",
      "html": "<a class=\"block pl-1ch -indent-1ch text-primary hover:text-contrast\" href=\"https://support.planetscale.com/hc/en-us\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Support</a>"
    }
  ],
  "privacyLinks": [
    {
      "href": "/legal/privacy",
      "text": "Privacy",
      "html": "<a class=\"text-primary\" rel=\"nofollow\" href=\"/legal/privacy\" data-discover=\"true\">Privacy</a>"
    },
    {
      "href": "/legal/siteterms",
      "text": "Terms",
      "html": "<a class=\"text-primary\" rel=\"nofollow\" href=\"/legal/siteterms\" data-discover=\"true\">Terms</a>"
    },
    {
      "href": "/legal/privacy#privacy-rights-and-choices",
      "text": "Do Not Share My Personal Information",
      "html": "<a class=\"text-primary\" rel=\"nofollow\" href=\"/legal/privacy#privacy-rights-and-choices\" data-discover=\"true\">Do Not Share My Personal Information</a>"
    }
  ],
  "score": 40,
  "weight": 20
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer evidence and trust

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

6 Fail

Needs attention

AEO: Answer evidence and trust

Failed check
01

Issue

Missing AIO trust signals: author, publisher, freshnessDate.

Details

02

Why it matters

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

Check name

AEO: Answer evidence and trust

Score

40/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

Evidence
{
  "signals": {
    "author": false,
    "publisher": false,
    "freshnessDate": false,
    "aboutOrContact": true,
    "policyLinks": true
  },
  "missing": [
    "author",
    "publisher",
    "freshnessDate"
  ],
  "authorMeta": "",
  "schemaAuthors": [],
  "schemaPublishers": [],
  "schemaDates": [],
  "visibleDates": [],
  "aboutLinks": [
    {
      "href": "/about",
      "text": "and more",
      "html": "<a href=\"/about\" data-discover=\"true\">and more</a>"
    },
    {
      "href": "/about",
      "text": "About",
      "html": "<a class=\"block pl-1ch -indent-1ch text-primary hover:text-contrast\" href=\"/about\" data-discover=\"true\">About</a>"
    },
    {
      "href": "https://www.linkedin.com/company/planetscale",
      "text": "LinkedIn",
      "html": "<a aria-label=\"LinkedIn\" class=\"text-primary\" href=\"https://www.linkedin.com/company/planetscale\" target=\"_blank\" rel=\"noreferrer\">LinkedIn</a>"
    }
  ],
  "contactLinks": [
    {
      "href": "/contact",
      "text": "Get in touch",
      "html": "<a class=\"btn !h-[32px] !px-1 font-semibold\" href=\"/contact\" data-discover=\"true\">Get in touch</a>"
    },
    {
      "href": "/contact",
      "text": "Contact",
      "html": "<a class=\"font-semibold text-primary hover:text-contrast\" href=\"/contact\" data-discover=\"true\">Contact</a>"
    },
    {
      "href": "/contact",
      "text": "Contact",
      "html": "<a class=\"font-semibold text-primary hover:text-contrast\" href=\"/contact\" data-discover=\"true\">Contact</a>"
    },
    {
      "href": "/contact",
      "text": "reach out to us",
      "html": "<a href=\"/contact\" data-discover=\"true\">reach out to us</a>"
    },
    {
      "href": "/docs/support",
      "text": "best-in-class support",
      "html": "<a href=\"/docs/support\">best-in-class support</a>"
    },
    {
      "href": "https://support.planetscale.com/hc/en-us",
      "text": "Support",
      "html": "<a class=\"block pl-1ch -indent-1ch text-primary hover:text-contrast\" href=\"https://support.planetscale.com/hc/en-us\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Support</a>"
    }
  ],
  "privacyLinks": [
    {
      "href": "/legal/privacy",
      "text": "Privacy",
      "html": "<a class=\"text-primary\" rel=\"nofollow\" href=\"/legal/privacy\" data-discover=\"true\">Privacy</a>"
    },
    {
      "href": "/legal/siteterms",
      "text": "Terms",
      "html": "<a class=\"text-primary\" rel=\"nofollow\" href=\"/legal/siteterms\" data-discover=\"true\">Terms</a>"
    },
    {
      "href": "/legal/privacy#privacy-rights-and-choices",
      "text": "Do Not Share My Personal Information",
      "html": "<a class=\"text-primary\" rel=\"nofollow\" href=\"/legal/privacy#privacy-rights-and-choices\" data-discover=\"true\">Do Not Share My Personal Information</a>"
    }
  ],
  "score": 40,
  "weight": 22
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first sections

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

5 Warning

Needs attention

AEO: Answer-first sections

Warning
01

Issue

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

Details

02

Why it matters

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

Check name

AEO: Answer-first sections

Score

65/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

Evidence
{
  "sectionCount": 10,
  "passing": 5,
  "failing": [
    {
      "heading": "Company",
      "headingHtml": "<h2 class=\"font-semibold\">Company</h2>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Product",
      "headingHtml": "<h2 class=\"font-semibold\">Product</h2>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Resources",
      "headingHtml": "<h2 class=\"font-semibold\">Resources</h2>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Courses",
      "headingHtml": "<h2 class=\"font-semibold\">Courses</h2>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Open source",
      "headingHtml": "<h2 class=\"font-semibold text-primary hover:text-contrast\">Open source</h2>",
      "firstParagraph": "Privacy | Terms | Cookies | Patents | Do Not Share My Personal Information",
      "paragraphHtml": "<p class=\"mb-3 md:mb-0\"><a class=\"text-primary\" rel=\"nofollow\" href=\"/legal/privacy\" data-discover=\"true\">Privacy</a><span class=\"text-decoration\" role=\"presentation\"> <!-- -->|<!-- --> </span><a class=\"text-primary\" rel=\"nofollow\" href=\"/legal/siteterms\" data-discover=\"true\">Terms</a><span class=\"text-decoration\" role=\"presentation\"> <!-- -->|<!-- --> </span><a class=\"text-primary\" rel=\"nofollow\" href=\"/legal/cookies\" data-discover=\"true\">Cookies</a><span class=\"text-decoration\" role=\"presen...",
      "words": 10,
      "direct": false,
      "issue": "First paragraph is 10 words and does not look like a concise direct answer."
    }
  ],
  "score": 65,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question-led structure

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

4 Warning

Needs attention

AEO: Question-led structure

Warning
01

Issue

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

Details

02

Why it matters

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

Check name

AEO: Question-led structure

Score

50/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Answer block readiness

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

3 Warning

Needs attention

AIO: Answer block readiness

Warning
01

Issue

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

Details

02

Why it matters

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

Check name

AIO: Answer block readiness

Score

65/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

Evidence
{
  "sectionCount": 10,
  "passing": 5,
  "failing": [
    {
      "heading": "Company",
      "headingHtml": "<h2 class=\"font-semibold\">Company</h2>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Product",
      "headingHtml": "<h2 class=\"font-semibold\">Product</h2>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Resources",
      "headingHtml": "<h2 class=\"font-semibold\">Resources</h2>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Courses",
      "headingHtml": "<h2 class=\"font-semibold\">Courses</h2>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Open source",
      "headingHtml": "<h2 class=\"font-semibold text-primary hover:text-contrast\">Open source</h2>",
      "firstParagraph": "Privacy | Terms | Cookies | Patents | Do Not Share My Personal Information",
      "paragraphHtml": "<p class=\"mb-3 md:mb-0\"><a class=\"text-primary\" rel=\"nofollow\" href=\"/legal/privacy\" data-discover=\"true\">Privacy</a><span class=\"text-decoration\" role=\"presentation\"> <!-- -->|<!-- --> </span><a class=\"text-primary\" rel=\"nofollow\" href=\"/legal/siteterms\" data-discover=\"true\">Terms</a><span class=\"text-decoration\" role=\"presentation\"> <!-- -->|<!-- --> </span><a class=\"text-primary\" rel=\"nofollow\" href=\"/legal/cookies\" data-discover=\"true\">Cookies</a><span class=\"text-decoration\" role=\"presen...",
      "words": 10,
      "direct": false,
      "issue": "First paragraph is 10 words and does not look like a concise direct answer."
    }
  ],
  "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
01

Issue

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

Details

02

Why it matters

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

Check name

AEO: Answer intent coverage

Score

70/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

Evidence
{
  "headings": [
    {
      "text": "Performance",
      "html": "<h2 id=\"performance\"><a href=\"/#performance\" data-discover=\"true\">Performance</a></h2>"
    },
    {
      "text": "Uptime",
      "html": "<h2 id=\"uptime\"><a href=\"/#uptime\" data-discover=\"true\">Uptime</a></h2>"
    },
    {
      "text": "Cost",
      "html": "<h2 id=\"cost\"><a href=\"/#cost\" data-discover=\"true\">Cost</a></h2>"
    },
    {
      "text": "Security",
      "html": "<h2 id=\"security\"><a href=\"/#security\" data-discover=\"true\">Security</a></h2>"
    },
    {
      "text": "Features",
      "html": "<h2 id=\"platform\"><a href=\"/#platform\" data-discover=\"true\">Features</a></h2>"
    },
    {
      "text": "Company",
      "html": "<h2 class=\"font-semibold\">Company</h2>"
    },
    {
      "text": "Product",
      "html": "<h2 class=\"font-semibold\">Product</h2>"
    },
    {
      "text": "Resources",
      "html": "<h2 class=\"font-semibold\">Resources</h2>"
    },
    {
      "text": "Courses",
      "html": "<h2 class=\"font-semibold\">Courses</h2>"
    },
    {
      "text": "Open source",
      "html": "<h2 class=\"font-semibold text-primary hover:text-contrast\">Open source</h2>"
    }
  ],
  "expected": [
    {
      "id": "what",
      "label": "What is PlanetScale - the world’s fastest and most sc...?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does PlanetScale - the world’s fastest and most sc... work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use PlanetScale - the world’s fastest and most sc...?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is PlanetScale - the world’s fastest and most sc... free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does PlanetScale - the world’s fastest and most sc... compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is PlanetScale - the world’s fastest and most sc...?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does PlanetScale - the world’s fastest and most sc... work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use PlanetScale - the world’s fastest and most sc...?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does PlanetScale - the world’s fastest and most sc... compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 8
}

Agent Ease of UseAPIEmerging recommendation

AI context endpoint

AI context endpoint is informational for this page.

Informational

Needs attention

AI context endpoint

Informational
01

Issue

AI context endpoint is informational for this page.

02

Why it matters

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

Check name

AI context endpoint

Score

100/100

Status

informational

Category

API

Maturity

Emerging recommendation

Goal

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

Result

AI context endpoint is informational for this page.

Validation steps

  1. Fetch to find resource

    AI context endpoint was not found at the expected path.

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Query intent coverage

AIO: Query intent coverage is informational for this page.

Informational

Needs attention

AIO: Query intent coverage

Informational
01

Issue

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

Details

02

Why it matters

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

Check name

AIO: Query intent coverage

Score

70/100

Status

informational

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

AIO: Query intent coverage is informational for this page.

Evidence
{
  "headings": [
    {
      "text": "Performance",
      "html": "<h2 id=\"performance\"><a href=\"/#performance\" data-discover=\"true\">Performance</a></h2>"
    },
    {
      "text": "Uptime",
      "html": "<h2 id=\"uptime\"><a href=\"/#uptime\" data-discover=\"true\">Uptime</a></h2>"
    },
    {
      "text": "Cost",
      "html": "<h2 id=\"cost\"><a href=\"/#cost\" data-discover=\"true\">Cost</a></h2>"
    },
    {
      "text": "Security",
      "html": "<h2 id=\"security\"><a href=\"/#security\" data-discover=\"true\">Security</a></h2>"
    },
    {
      "text": "Features",
      "html": "<h2 id=\"platform\"><a href=\"/#platform\" data-discover=\"true\">Features</a></h2>"
    },
    {
      "text": "Company",
      "html": "<h2 class=\"font-semibold\">Company</h2>"
    },
    {
      "text": "Product",
      "html": "<h2 class=\"font-semibold\">Product</h2>"
    },
    {
      "text": "Resources",
      "html": "<h2 class=\"font-semibold\">Resources</h2>"
    },
    {
      "text": "Courses",
      "html": "<h2 class=\"font-semibold\">Courses</h2>"
    },
    {
      "text": "Open source",
      "html": "<h2 class=\"font-semibold text-primary hover:text-contrast\">Open source</h2>"
    }
  ],
  "expected": [
    {
      "id": "what",
      "label": "What is PlanetScale - the world’s fastest and most sc...?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does PlanetScale - the world’s fastest and most sc... work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use PlanetScale - the world’s fastest and most sc...?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is PlanetScale - the world’s fastest and most sc... free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does PlanetScale - the world’s fastest and most sc... compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is PlanetScale - the world’s fastest and most sc...?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does PlanetScale - the world’s fastest and most sc... work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use PlanetScale - the world’s fastest and most sc...?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does PlanetScale - the world’s fastest and most sc... compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 4
}

Agent Ease of UseAuthEmerging recommendation

Auth.md Agent Registration

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

Informational

Needs attention

Auth.md Agent Registration

Informational
01

Issue

auth.md response did not match the expected agent registration shape. Content-Type "text/html" is not Markdown or text/plain; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; missing supported identity type language; missing credential type language.

02

Why it matters

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

Check name

Auth.md Agent Registration

Score

0/100

Status

informational

Category

Auth

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Fetch and validate /auth.md

    auth.md response did not match the expected agent registration shape. Content-Type "text/html" is not Markdown or text/plain; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; missing supported identity type language; missing credential type language.

  2. Publish protected resource metadata

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

  3. Validate agent_auth authorization metadata

    OAuth authorization server metadata could not be fetched.

Evidence
{
  "failedStep": "auth-md",
  "steps": [
    {
      "id": "auth-md",
      "title": "Fetch and validate /auth.md",
      "status": "fail",
      "evidence": {
        "path": "/auth.md",
        "ok": false,
        "statusCode": 404,
        "contentType": "text/html",
        "length": 7973,
        "validation": {
          "valid": false,
          "issue": "auth.md response did not match the expected agent registration shape. Content-Type \"text/html\" is not Markdown or text/plain; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; missing supported identity type language; missing credential type language.",
          "compatibleContentType": false,
          "contentLength": 7723,
          "hasRegisterInstructions": true,
          "hasProtectedResourceLink": false,
          "hasAuthorizationServerLink": false,
          "mentionsIdentity": false,
          "mentionsCredential": false,
          "links": [
            "/title",
            "/assets/styles-Bq4K_D9A.css",
            "/favicon.ico",
            "/x-icon",
            "/icon.png",
            "/png",
            "/apple-touch-icon.png",
            "/png",
            "/manifest.webmanifest",
            "/head"
          ],
          "rawExcerpt": "<!DOCTYPE html><html lang=\"en\"><head><title>404 Page not found - PlanetScale</title><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><meta name=\"theme-color\" content=\"#111111\"/><link rel=\"stylesheet\" href=\"/assets/styles-Bq4K_D9A.css\"/><link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\" sizes=\"16x16\"/><link rel=\"icon\" href=\"/icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"apple-touch-icon\" href=\"/apple-touch-icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"manifest\" href=\"/manifest.webmanifest\"/></head><body><div class=\"flex flex-col items-center gap-1 bg-gray-900 px-3 py-1.5 text-center font-medium text-white sm:flex-row sm:justify-center sm:gap-1.5 sm:py-1 dark:bg-gray-50 dark:text-gray-900\"><svg width=\"5\" height=\"23\" viewBox=\"0 0 "
        }
      },
      "issue": "auth.md response did not match the expected agent registration shape. Content-Type \"text/html\" is not Markdown or text/plain; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; missing supported identity type language; missing credential type language.",
      "howToFix": "Serve /auth.md at the site root as Markdown with agent registration instructions and links to OAuth metadata."
    },
    {
      "id": "oauth-protected-resource",
      "title": "Publish protected resource metadata",
      "status": "fail",
      "evidence": {
        "path": "/.well-known/oauth-protected-resource",
        "ok": false,
        "statusCode": 404,
        "contentType": "text/html",
        "length": 7973,
        "text": "<!DOCTYPE html><html lang=\"en\"><head><title>404 Page not found - PlanetScale</title><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><meta name=\"theme-color\" content=\"#111111\"/><link rel=\"stylesheet\" href=\"/assets/styles-Bq4K_D9A.css\"/><link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\" sizes=\"16x16\"/><link rel=\"icon\" href=\"/icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"apple-touch-icon\" href=\"/apple-touch-icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"manifest\" href=\"/manifest.webmanifest\"/></head><body><div class=\"flex flex-col items-center gap-1 bg-gray-900 px-3 py-1.5 text-center font-medium text-white sm:flex-row sm:justify-center sm:gap-1.5 sm:py-1 dark:bg-gray-50 dark:text-gray-900\"><svg width=\"5\" height=\"23\" viewBox=\"0 0 5 23\" fill=\"none\" xmlns=\"http://www.w3.org/2000/svg\" class=\"hidden sm:block\"><style>\n              @keyframes banner-red-light {\n                0%, 66% { fill: currentColor; opacity: 0.3; }\n                67%, 100% { fill: #C11027; opacity: 1; }\n              }\n              @keyframes banner-yellow-light {\n                0%, 33% { fill: currentColor; opacity: 0.3; }\n                34%, 66% { fill: #F5A623; opacity: 1; }\n                67%, 100% { fill: currentColor; opacity: 0.3; }\n              }\n              @keyframes banner-green-light {\n                0%, 33% { fill: #22A652; opacity: 1; }\n                34%, 100% { fill: currentColor; opacity: 0.3; }\n              }\n            </style><rect width=\"5\" height=\"5\" style=\"animation:banner-red-light 7s infinite\"></rect><rect y=\"9\" width=\"5\" height=\"5\" style=\"animation:banner-yellow-light 7s infinite\"></rect><rect y=\"18\" width=\"5\" height=\"5\" style=\"animation:banner-green-light 7s infinite\"></rect></svg><span class=\"text-sm sm:text-base\">Introducing Database Traffic Controlâ„¢: resource budgets for your Postgres query traffic.</span><a class=\"whitespace-nowrap bg-yellow-300 px-1 py-px text-sm font-semibold text-gray-900 sm:px-sm sm:py-0 sm:text-base\" href=\"/blog/introducing-database-traffic-control\" data-discover=\"true\">Learn more</a></div><header class=\"relative mb-6 mt-4 bg-primary\"><div class=\"flex flex-col gap-y-3 px-3 sm:px-5 container max-w-7xl\"><div class=\"grid w-full grid-cols-[auto_1fr] grid-rows-1 @container lg:gap-3 lg:grid-rows-2 xl:grid-rows-1\"><a aria-label=\"Go to homepage\" class=\"col-start-1 col-end-2 h-4 w-4 rounded-full text-primary lg:hidden\" href=\"/\" data-discover=\"true\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"32\" height=\"32\" fill=\"none\" viewBox=\"0 0 40 40\"><path fill=\"currentColor\" d=\"M0 20C0 8.954 8.954 0 20 0c8.121 0 15.112 4.84 18.245 11.794l-26.45 26.45a20 20 0 0 1-3.225-1.83L24.984 20H20L5.858 34.142A19.94 19.94 0 0 1 0 20M39.999 20.007 20.006 40c11.04-.004 19.99-8.953 19.993-19.993\"></path></svg></a><div class=\"group col-start-2 col-end-3 flex items-center justify-end gap-1.5 xl:row-start-1 xl:gap-3\"><div class=\"flex items-center gap-1\"><a href=\"https://auth.planetscale.com/sign-in\" class=\"font-semibold text-primary hover:text-orange\">Log in</a><div class=\"hidden gap-1 @lg:inline-flex\"><span class=\"text-decoration\">|</span><a href=\"https://auth.planetscale.com/sign-up\" class=\"font-semibold text-primary hover:text-orange\">Get started</a></div><span class=\"text-decoration\">|</span><a class=\"btn !h-[32px] !px-1 font-semibold\" href=\"/contact\" data-discover=\"true\">Get in touch</a></div></div><div class=\"col-start-1 col-end-3 flex items-center gap-x-3 xl:col-end-2 xl:row-start-1\"><a aria-label=\"Go to homepage\" class=\"col-start-1 col-end-2 hidden h-4 w-4 rounded-full text-primary lg:block\" href=\"/\" data-discover=\"true\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"32\" height=\"32\" fill=\"none\" viewBox=\"0 0 40 40\"><path fill=\"currentColor\" d=\"M0 20C0 8.954 8.954 0 20 0c8.121 0 15.112 4.84 18.245 11.794l-26.45 26.45a20 20 0 0 1-3.225-1.83L24.984 20H20L5.858 34.142A19.94 19.94 0 0 1 0 20M39.999 20.007 20.006 40c11.04-.004 19.99-8.953 19.993-19.993\"></path></svg></"
      },
      "issue": "The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.",
      "howToFix": "Publish /.well-known/oauth-protected-resource with resource and authorization_servers fields."
    },
    {
      "id": "agent-auth-block",
      "title": "Validate agent_auth authorization metadata",
      "status": "fail",
      "evidence": {
        "valid": false,
        "issue": "OAuth authorization server metadata could not be fetched.",
        "fetch": {
          "ok": false,
          "statusCode": 404,
          "contentType": "text/html",
          "length": 7973,
          "text": "<!DOCTYPE html><html lang=\"en\"><head><title>404 Page not found - PlanetScale</title><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><meta name=\"theme-color\" content=\"#111111\"/><link rel=\"stylesheet\" href=\"/assets/styles-Bq4K_D9A.css\"/><link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\" sizes=\"16x16\"/><link rel=\"icon\" href=\"/icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"apple-touch-icon\" href=\"/apple-touch-icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"manifest\" href=\"/manifest.webmanifest\"/></head><body><div class=\"flex flex-col items-center gap-1 bg-gray-900 px-3 py-1.5 text-center font-medium text-white sm:flex-row sm:justify-center sm:gap-1.5 sm:py-1 dark:bg-gray-50 dark:text-gray-900\"><svg width=\"5\" height=\"23\" viewBox=\"0 0 5 23\" fill=\"none\" xmlns=\"http://www.w3.org/2000/svg\" class=\"hidden sm:block\"><style>\n              @keyframes banner-red-light {\n                0%, 66% { fill: currentColor; opacity: 0.3; }\n                67%, 100% { fill: #C11027; opacity: 1; }\n              }\n              @keyframes banner-yellow-light {\n                0%, 33% { fill: currentColor; opacity: 0.3; }\n                34%, 66% { fill: #F5A623; opacity: 1; }\n                67%, 100% { fill: currentColor; opacity: 0.3; }\n              }\n              @keyframes banner-green-light {\n                0%, 33% { fill: #22A652; opacity: 1; }\n                34%, 100% { fill: currentColor; opacity: 0.3; }\n              }\n            </style><rect width=\"5\" height=\"5\" style=\"animation:banner-red-light 7s infinite\"></rect><rect y=\"9\" width=\"5\" height=\"5\" style=\"animation:banner-yellow-light 7s infinite\"></rect><rect y=\"18\" width=\"5\" height=\"5\" style=\"animation:banner-green-light 7s infinite\"></rect></svg><span class=\"text-sm sm:text-base\">Introducing Database Traffic Controlâ„¢: resource budgets for your Postgres query traffic.</span><a class=\"whitespace-nowrap bg-yellow-300 px-1 py-px text-sm font-semibold text-gray-900 sm:px-sm sm:py-0 sm:text-base\" href=\"/blog/introducing-database-traffic-control\" data-discover=\"true\">Learn more</a></div><header class=\"relative mb-6 mt-4 bg-primary\"><div class=\"flex flex-col gap-y-3 px-3 sm:px-5 container max-w-7xl\"><div class=\"grid w-full grid-cols-[auto_1fr] grid-rows-1 @container lg:gap-3 lg:grid-rows-2 xl:grid-rows-1\"><a aria-label=\"Go to homepage\" class=\"col-start-1 col-end-2 h-4 w-4 rounded-full text-primary lg:hidden\" href=\"/\" data-discover=\"true\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"32\" height=\"32\" fill=\"none\" viewBox=\"0 0 40 40\"><path fill=\"currentColor\" d=\"M0 20C0 8.954 8.954 0 20 0c8.121 0 15.112 4.84 18.245 11.794l-26.45 26.45a20 20 0 0 1-3.225-1.83L24.984 20H20L5.858 34.142A19.94 19.94 0 0 1 0 20M39.999 20.007 20.006 40c11.04-.004 19.99-8.953 19.993-19.993\"></path></svg></a><div class=\"group col-start-2 col-end-3 flex items-center justify-end gap-1.5 xl:row-start-1 xl:gap-3\"><div class=\"flex items-center gap-1\"><a href=\"https://auth.planetscale.com/sign-in\" class=\"font-semibold text-primary hover:text-orange\">Log in</a><div class=\"hidden gap-1 @lg:inline-flex\"><span class=\"text-decoration\">|</span><a href=\"https://auth.planetscale.com/sign-up\" class=\"font-semibold text-primary hover:text-orange\">Get started</a></div><span class=\"text-decoration\">|</span><a class=\"btn !h-[32px] !px-1 font-semibold\" href=\"/contact\" data-discover=\"true\">Get in touch</a></div></div><div class=\"col-start-1 col-end-3 flex items-center gap-x-3 xl:col-end-2 xl:row-start-1\"><a aria-label=\"Go to homepage\" class=\"col-start-1 col-end-2 hidden h-4 w-4 rounded-full text-primary lg:block\" href=\"/\" data-discover=\"true\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"32\" height=\"32\" fill=\"none\" viewBox=\"0 0 40 40\"><path fill=\"currentColor\" d=\"M0 20C0 8.954 8.954 0 20 0c8.121 0 15.112 4.84 18.245 11.794l-26.45 26.45a20 20 0 0 1-3.225-1.83L24.984 20H20L5.858 34.142A19.94 19.94 0 0 1 0 20M39.999 20.007 20.006 40c11.04-.004 19.99-8.953 19.993-19.993\"></path></svg></"
        }
      },
      "issue": "OAuth authorization server metadata could not be fetched.",
      "howToFix": "Add agent_auth to /.well-known/oauth-authorization-server with register_uri, supported identity types, credential types, and claim or revocation URLs where applicable."
    }
  ],
  "authApplicability": {
    "supportsAuth": true,
    "score": 6,
    "signals": [
      {
        "source": "link:href",
        "weight": 3,
        "match": "auth link"
      },
      {
        "source": "visible-text",
        "weight": 3,
        "match": "log in"
      }
    ]
  },
  "resourceFetchSucceeded": false
}

AI DiscoverabilityDiscoverabilityEstablished

IndexNow key

IndexNow key is informational for this page.

Informational

Needs attention

IndexNow key

Informational
01

Issue

IndexNow key is informational for this page.

02

Why it matters

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

Check name

IndexNow key

Score

100/100

Status

informational

Category

Discoverability

Maturity

Established

Goal

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

Result

IndexNow key is informational for this page.

Validation steps

  1. Find advertised IndexNow key location

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

  2. Fetch and validate IndexNow key file

    No discoverable IndexNow key file was found.

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

Agent Ease of UseAuthEstablished

OAuth / OIDC discovery

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

Informational

Needs attention

OAuth / OIDC discovery

Informational
01

Issue

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

02

Why it matters

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

Check name

OAuth / OIDC discovery

Score

0/100

Status

informational

Category

Auth

Maturity

Established

Goal

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

Result

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

Validation steps

  1. Fetch to find resource

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

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/openid-configuration",
            "statusCode": 404,
            "contentType": "text/html",
            "length": 7973
          },
          {
            "path": "/.well-known/oauth-authorization-server",
            "statusCode": 404,
            "contentType": "text/html",
            "length": 7973
          }
        ]
      },
      "issue": "OAuth / OIDC discovery was not found at the expected path.",
      "howToFix": "Publish valid OAuth/OIDC metadata only when the site actually supports OAuth/OIDC. Otherwise omit provider discovery and document any unauthenticated public APIs separately."
    }
  ],
  "authApplicability": {
    "supportsAuth": true,
    "score": 6,
    "signals": [
      {
        "source": "link:href",
        "weight": 3,
        "match": "auth link"
      },
      {
        "source": "visible-text",
        "weight": 3,
        "match": "log in"
      }
    ]
  },
  "resourceFetchSucceeded": false
}

Agent Ease of UseAuthEmerging recommendation

OAuth Protected Resource

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

Informational

Needs attention

OAuth Protected Resource

Informational
01

Issue

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

02

Why it matters

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

Check name

OAuth Protected Resource

Score

0/100

Status

informational

Category

Auth

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Fetch protected resource metadata

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

  2. Validate protected resource metadata

    Response is not valid JSON.

  3. Validate protected resource identity

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

  4. Probe protected API Bearer challenge

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

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch protected resource metadata",
      "status": "fail",
      "evidence": {
        "path": "/.well-known/oauth-protected-resource",
        "statusCode": 404,
        "contentType": "text/html"
      },
      "issue": "The OAuth Protected Resource metadata endpoint did not return HTTP 2xx.",
      "howToFix": "Publish /.well-known/oauth-protected-resource JSON."
    },
    {
      "id": "metadata",
      "title": "Validate protected resource metadata",
      "status": "fail",
      "evidence": {
        "valid": false,
        "compatibleContentType": false,
        "issue": "Response is not valid JSON.",
        "rawExcerpt": "<!DOCTYPE html><html lang=\"en\"><head><title>404 Page not found - PlanetScale</title><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><meta name=\"theme-color\" content=\"#111111\"/><link rel=\"stylesheet\" href=\"/assets/styles-Bq4K_D9A.css\"/><link rel=\"icon\" href=\"/favicon.ico\" type=\"image/x-icon\" sizes=\"16x16\"/><link rel=\"icon\" href=\"/icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"apple-touch-icon\" href=\"/apple-touch-icon.png\" type=\"image/png\" sizes=\"32x32\"/><link rel=\"manifest\" href=\"/manifest.webmanifest\"/></head><body><div class=\"flex flex-col items-center gap-1 bg-gray-900 px-3 py-1.5 text-center font-medium text-white sm:flex-row sm:justify-center sm:gap-1.5 sm:py-1 dark:bg-gray-50 dark:text-gray-900\"><svg width=\"5\" height=\"23\" viewBox=\"0 0 "
      },
      "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://planetscale.com"
      },
      "issue": "Protected resource metadata `resource` did not match the resource identifier used to retrieve it.",
      "howToFix": "Set `resource` to the origin/resource identifier represented by /.well-known/oauth-protected-resource."
    },
    {
      "id": "protected-route-challenge",
      "title": "Probe protected API Bearer challenge",
      "status": "informational",
      "evidence": {
        "checked": [
          {
            "path": "/api/admin/scans",
            "statusCode": 404,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://planetscale.com/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "resourceMatchesRequestContext": true
          },
          {
            "path": "/api/admin/summary",
            "statusCode": 404,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://planetscale.com/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "resourceMatchesRequestContext": true
          },
          {
            "path": "/api/scans",
            "statusCode": 404,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://planetscale.com/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "resourceMatchesRequestContext": true
          }
        ]
      },
      "issue": "No protected route with a 401 Bearer challenge was detected; metadata alone does not prove a protected resource.",
      "howToFix": "When this site exposes bearer-protected APIs, return 401 with WWW-Authenticate: Bearer and link resource_metadata."
    }
  ],
  "authApplicability": {
    "supportsAuth": true,
    "score": 6,
    "signals": [
      {
        "source": "link:href",
        "weight": 3,
        "match": "auth link"
      },
      {
        "source": "visible-text",
        "weight": 3,
        "match": "log in"
      }
    ]
  },
  "resourceFetchSucceeded": false
}

SEOSEOBrowser audit

Links do not have descriptive text

100 Fail

Check name

Links do not have descriptive text

Score

0/100

Status

fail

Device

desktop

Category

SEO

Estimated savings

1 link found

Fix guidance

Descriptive link text helps search engines understand your content. [Learn how to make links more accessible](https://developer.chrome.com/docs/lighthouse/seo/link-text/).

Evidence
{
  "displayValue": "1 link found",
  "description": "Descriptive link text helps search engines understand your content. [Learn how to make links more accessible](https://developer.chrome.com/docs/lighthouse/seo/link-text/)."
}

Performance and AccessibilityPerformanceBrowser audit

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

17 Fail

Check name

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. [Learn more about proper list structure](https://dequeuniversity.com/rules/axe/4.11/list).

Evidence
{
  "description": "Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. [Learn more about proper list structure](https://dequeuniversity.com/rules/axe/4.11/list)."
}

Performance and AccessibilityPerformanceBrowser audit

Network dependency tree

17 Fail

Check name

Network dependency tree

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

[Avoid chaining critical requests](https://developer.chrome.com/docs/performance/insights/network-dependency-tree) by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Evidence
{
  "description": "[Avoid chaining critical requests](https://developer.chrome.com/docs/performance/insights/network-dependency-tree) by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load."
}

Performance and AccessibilityPerformanceBrowser audit

Reduce unused JavaScript

17 Fail

Check name

Reduce unused JavaScript

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 26 KiB

Fix guidance

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/).

Evidence
{
  "displayValue": "Est savings of 26 KiB",
  "description": "Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/).",
  "numericValue": 40
}

Performance and AccessibilityPerformanceBrowser audit

Render-blocking requests

17 Fail

Check name

Render-blocking requests

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 50 ms

Fix guidance

Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining](https://developer.chrome.com/docs/performance/insights/render-blocking) can move these network requests out of the critical path.

Evidence
{
  "displayValue": "Est savings of 50 ms",
  "description": "Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining](https://developer.chrome.com/docs/performance/insights/render-blocking) can move these network requests out of the critical path."
}

Performance and AccessibilityPerformanceBrowser audit

Improve image delivery

8 Warning

Check name

Improve image delivery

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 139 KiB

Fix guidance

Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery)

Evidence
{
  "displayValue": "Est savings of 139 KiB",
  "description": "Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery)"
}

Performance and AccessibilityPerformanceBrowser audit

Reduce unused CSS

8 Warning

Check name

Reduce unused CSS

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 11 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/).

Evidence
{
  "displayValue": "Est savings of 11 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
}

Fix with MCP or CLI

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

Score history

Public scan score over time

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

1 reports
Public score history report links
Scan dateScoreReadinessReport
76/100Level 4, Mostly ReadyCurrent report
Report ID 79fb3e24-b12d-4e4b-8b21-d40e0ec004e9. Scanned Jun 8, 2026, 7:37 PM.
planetscale.com AI SEO Report: 76/100 (Level 4, Mostly Ready)