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

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability35%Agent Easeof Use6%Security& Trust80%GEO, AIO, AEO72%SEO100%Performance& Accessibility95%
  • AI Discoverability 35 out of 100
  • Agent Ease of Use 6 out of 100
  • Security & Trust 80 out of 100
  • GEO, AIO and AEO 72 out of 100
  • SEO 100 out of 100
  • Performance and Accessibility 95 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

wake.com for sale | Spaceship.com favicon

wake.com for sale | Spaceship.com

wake.com is for sale on Spaceship. Secure checkout and quick transfer. See all purchase options. No hidden fees.

Next step

Turn this report into a fix workflow

23 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
35
Priority fix6161View details
Discoverability
57
Needs work450View details
Content Readiness
38
Priority fix271View details
Bot Access Control
0
Priority fix040View details
Agent Ease of Use
6
Priority fix12203View details
API
0
Priority fix040View details
Auth
Not Applicable
Not Applicable800
MCP
13
Priority fix062View details
Skill Discovery
5
Priority fix0101View details
Agent Commerce
Not Applicable
Not Applicable400
GEO, AIO and AEO
72
Needs work828View details
GEO Readiness
Not Applicable
Not Applicable400
AIO Readiness
63
Needs work214View details
AEO Readiness
61
Needs work214View details
SEO
100
Strong1100
SEO
100
Strong1100
Security & Trust
80
Mostly ready510View details
Security & Trust
80
Mostly ready410View details
AI Training Exposure
Not Applicable
Not Applicable100
Performance and Accessibility
95
Strong1930View details
Performance
99
Strong1130View details
Accessibility
88
Mostly ready800

Prioritized recommendations

Issues ranked by score impact

38 items need attention

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy is missing or incomplete.

100 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

Content-Security-Policy is missing or incomplete.

02

Why it matters

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

Check name

Content-Security-Policy

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

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

Result

Content-Security-Policy is missing or incomplete.

Evidence
{
  "header": "content-security-policy",
  "value": "frame-ancestors 'self'"
}

Agent Ease of UseAPIEstablished

API Catalog

API Catalog failed at "Fetch API catalog".

50 Fail

Needs attention

API Catalog

Failed check
01

Issue

The API catalog endpoint could not be fetched.

02

Why it matters

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

Check name

API Catalog

Score

0/100

Status

fail

Category

API

Maturity

Established

Goal

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

Result

API Catalog failed at "Fetch API catalog".

Validation steps

  1. Fetch API catalog

    The API catalog endpoint could not be fetched.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch API catalog",
      "status": "fail",
      "evidence": {
        "error": "TypeError: fetch failed"
      },
      "issue": "The API catalog endpoint could not be fetched.",
      "howToFix": "Publish /.well-known/api-catalog as application/linkset+json."
    }
  ]
}

Agent Ease of UseAPIEstablished

OpenAPI discovery

OpenAPI discovery failed at "Find valid OpenAPI document".

50 Fail

Needs attention

OpenAPI discovery

Failed check
01

Issue

No valid OpenAPI or Swagger document was found at expected paths.

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

    No valid OpenAPI or Swagger document was found at expected paths.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Find valid OpenAPI document",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/openapi.json",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/openapi.yaml",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/swagger.json",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/swagger.yaml",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/api/openapi.json",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/api/swagger.json",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/docs/openapi.json",
            "error": "TypeError: fetch failed"
          }
        ]
      },
      "issue": "No valid OpenAPI or Swagger document was found at expected paths.",
      "howToFix": "Publish a valid OpenAPI 3.x or Swagger 2.0 JSON/YAML document with info, paths, operations, and responses."
    }
  ]
}

AI DiscoverabilityBot Access ControlEstablished

AI bot rules in robots.txt

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

33 Fail

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

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

02

Why it matters

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

Check name

AI bot rules in robots.txt

Score

0/100

Status

fail

Category

Bot Access Control

Maturity

Established

Goal

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

Result

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

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

AI DiscoverabilityBot Access ControlInformational

Content Signal

Content Signal is missing or incomplete.

33 Fail

Needs attention

Content Signal

Failed check
01

Issue

No Content Signal found in robots.txt

02

Why it matters

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

Check name

Content Signal

Score

0/100

Status

fail

Category

Bot Access Control

Maturity

Informational

Goal

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

Result

Content Signal is missing or incomplete.

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

AI DiscoverabilityDiscoverabilityEstablished

Link headers

Link headers failed at "Find useful Link headers".

33 Fail

Needs attention

Link headers

Failed check
01

Issue

No useful agent discovery Link headers were found.

02

Why it matters

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

Check name

Link headers

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Include Link response headers for agent discovery using RFC 8288.

Result

Link headers failed at "Find useful Link headers".

Validation steps

  1. Find useful Link headers

    No useful agent discovery Link headers were found.

  2. Fetch same-origin Link header targets

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

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

AI DiscoverabilityDiscoverabilityEstablished

Organization / WebSite schema

Organization / WebSite schema is missing or incomplete.

33 Fail

Needs attention

Organization / WebSite schema

Failed check
01

Issue

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

02

Why it matters

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

Check name

Organization / WebSite schema

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Identify the site owner and website entity in structured data.

Result

Organization / WebSite schema is missing or incomplete.

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

AI DiscoverabilityDiscoverabilityEstablished

Sitemap

Sitemap is missing or incomplete.

33 Fail

Needs attention

Sitemap

Failed check
01

Issue

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

02

Why it matters

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

Check name

Sitemap

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Publish a sitemap and reference it from robots.txt.

Result

Sitemap is missing or incomplete.

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

AI DiscoverabilityBot Access ControlInformational

Web Bot Auth request signing

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

33 Fail

Needs attention

Web Bot Auth request signing

Failed check
01

Issue

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

02

Why it matters

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

Check name

Web Bot Auth request signing

Score

0/100

Status

fail

Category

Bot Access Control

Maturity

Informational

Goal

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

Result

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

Validation steps

  1. Fetch to find resource

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

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/http-message-signatures-directory",
            "error": "TypeError: fetch failed"
          }
        ]
      },
      "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 ReadinessEmerging recommendation

llms.txt

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

25 Fail

Needs attention

llms.txt

Failed check
01

Issue

llms.txt was not found at the expected path.

02

Why it matters

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

Check name

llms.txt

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Fetch to find resource

    llms.txt was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/llms.txt",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/llms-full.txt",
            "error": "TypeError: fetch failed"
          }
        ]
      },
      "issue": "llms.txt was not found at the expected path.",
      "howToFix": "Publish /llms.txt as Markdown with a clear title, concise site summary, and useful links for agents."
    }
  ]
}

AI DiscoverabilityContent ReadinessEstablished

Markdown negotiation

Markdown negotiation failed at "Markdown content type".

25 Fail

Needs attention

Markdown negotiation

Failed check
01

Issue

Content-Type "text/html" 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 "Accept-Encoding".

  3. Structured Markdown body

    Markdown response is missing a heading.

Evidence
{
  "failedStep": "content-type",
  "steps": [
    {
      "id": "content-type",
      "title": "Markdown content type",
      "status": "fail",
      "evidence": {
        "statusCode": 200,
        "contentType": "text/html"
      },
      "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": "Accept-Encoding"
      },
      "issue": "Markdown negotiation is missing Vary: Accept; current Vary header is \"Accept-Encoding\".",
      "howToFix": "Add Vary: Accept on negotiated Markdown responses so shared caches keep HTML and Markdown variants separate."
    },
    {
      "id": "markdown-content",
      "title": "Structured Markdown body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "hasHeading": false,
        "wordCount": 1483,
        "excerpt": "<!doctype html>\n<html lang=\"en\">\n<head>\n    <meta charset=\"UTF-8\">\n    <meta name=\"viewport\"\n          content=\"width=device-width, user-scalable=no, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0\">\n    <meta http-equiv=\"X-UA-Compa",
        "issue": "Markdown response is missing a heading."
      },
      "issue": "Markdown response is missing a heading.",
      "howToFix": "Return Markdown with at least one heading and substantive page content, including useful links or instructions for agents."
    }
  ]
}

Agent Ease of UseMCPEmerging recommendation

MCP Server Card

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

25 Fail

Needs attention

MCP Server Card

Failed check
01

Issue

MCP Server Card was not found at the expected path.

02

Why it matters

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

Check name

MCP Server Card

Score

0/100

Status

fail

Category

MCP

Maturity

Emerging recommendation

Goal

Publish an MCP Server Card for agent discovery.

Result

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

Validation steps

  1. Fetch to find resource

    MCP Server Card was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/mcp/server-card.json",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/.well-known/mcp/server-cards.json",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/.well-known/mcp.json",
            "error": "TypeError: fetch failed"
          }
        ]
      },
      "issue": "MCP Server Card was not found at the expected path.",
      "howToFix": "Publish an MCP server card with valid transports and make each advertised local endpoint answer an MCP initialize request."
    }
  ]
}

Agent Ease of UseMCPEmerging recommendation

mcp.json

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

25 Fail

Needs attention

mcp.json

Failed check
01

Issue

mcp.json was not found at the expected path.

02

Why it matters

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

Check name

mcp.json

Score

0/100

Status

fail

Category

MCP

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Fetch to find resource

    mcp.json was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/mcp.json",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/.well-known/mcp.json",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/.well-known/mcp/server-card.json",
            "error": "TypeError: fetch failed"
          }
        ]
      },
      "issue": "mcp.json was not found at the expected path.",
      "howToFix": "Publish mcp.json or an MCP server card with serverInfo, protocolVersion, transport endpoint, and capabilities."
    }
  ]
}

AI DiscoverabilityContent ReadinessEstablished

Semantic HTML

Semantic HTML is missing or incomplete.

25 Fail

Needs attention

Semantic HTML

Failed check
01

Issue

Semantic HTML is incomplete: missing <nav> landmark; 0/6 applicable form inputs have autocomplete attributes (6 missing).

Details

02

Why it matters

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

Check name

Semantic HTML

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose readable page structure through semantic HTML and accessible controls.

Result

Semantic HTML is missing or incomplete.

Evidence
{
  "main": true,
  "nav": false,
  "footer": true,
  "meaningfulH1": true,
  "headingOrder": true,
  "accessibleLinks": true,
  "accessibleButtons": true,
  "imageAltCoverage": true,
  "formAutocompleteCoverage": false,
  "details": {
    "inaccessibleLinks": [],
    "inaccessibleButtons": [],
    "missingAutocompleteInputs": [
      "<input id=\"offer-price-input\" class=\"domain-card-with-offer-only__price--input gb-text-right\" data-zid=\"priceInputMakeOffer\" autofocus required type=\"text\" pattern=\"[0-9,]*\" inputmode=\"numeric\" oninput=\"this.parentNode.dataset.value = this.value\" placeholder=\"0\">",
      "<input id=\"first-name-field\" name=\"firstName\" placeholder=\"Enter your first name\" class=\"gb-textfield__input gb-input__input\" type=\"text\" value required>",
      "<input id=\"last-name-field\" name=\"lastName\" placeholder=\"Enter your last name\" class=\"gb-textfield__input gb-input__input\" type=\"text\" value required>",
      "<input id=\"email-field\" name=\"email\" placeholder=\"Enter your email address\" class=\"gb-textfield__input gb-input__input\" type=\"email\" title=\"Email should be in format: [email protected]\" value maxlength=\"128\" required>",
      "<input id=\"phone-input\" placeholder=\"000 000 000 000\" aria-label=\"phone number\" class=\"gb-textfield__input gb-input__input\" type=\"tel\" minlength=\"4\" maxlength=\"12\" required>",
      "<input id=\"select-search\" class=\"gb-textfield__input gb-input__input\" placeholder=\"Search here\" type=\"text\" value>"
    ],
    "imagesMissingAlt": [
      "<img width=\"20\" height=\"20\" class=\"gb-icon-img\" src=\"https://forsale.spaceship-cdn.com/static/latest/3.latest/assets/fonts/chevron-down.svg\">"
    ],
    "skippedHeadingLevels": []
  },
  "counts": {
    "h1": 1,
    "headings": 1,
    "links": 4,
    "inaccessibleLinks": 0,
    "buttons": 2,
    "inaccessibleButtons": 0,
    "images": 28,
    "imagesWithAlt": 27,
    "autocompleteInputs": 6,
    "inputsWithAutocomplete": 0,
    "missingAutocompleteInputs": 6
  }
}

Agent Ease of UseMCPInformational

WebMCP manifest

WebMCP manifest failed at "Fetch to find resource".

25 Fail

Needs attention

WebMCP manifest

Failed check
01

Issue

WebMCP manifest was not found at the expected path.

02

Why it matters

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

Check name

WebMCP manifest

Score

0/100

Status

fail

Category

MCP

Maturity

Informational

Goal

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

Result

WebMCP manifest failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    WebMCP manifest was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/webmcp.json",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/webmcp.json",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/mcp.json",
            "error": "TimeoutError: The operation was aborted due to timeout"
          }
        ]
      },
      "issue": "WebMCP manifest was not found at the expected path.",
      "howToFix": "Keep declarative WebMCP manifest discovery informational until the manifest shape stabilizes; validate tools if you publish one."
    }
  ]
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

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

20 Fail

Needs attention

A2A Agent Card

Failed check
01

Issue

A2A Agent Card was not found at the expected path.

02

Why it matters

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

Check name

A2A Agent Card

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Fetch to find resource

    A2A Agent Card was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/agent-card.json",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/.well-known/a2a/agent-card.json",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/agent-card.json",
            "error": "TypeError: fetch failed"
          }
        ]
      },
      "issue": "A2A Agent Card was not found at the expected path.",
      "howToFix": "Publish an A2A Agent Card with required skill details and make the advertised url answer A2A JSON-RPC requests."
    }
  ]
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

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

20 Fail

Needs attention

Agent Skills index

Failed check
01

Issue

Agent Skills index was not found at the expected path.

02

Why it matters

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

Check name

Agent Skills index

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an agent skills discovery index.

Result

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

Validation steps

  1. Fetch to find resource

    Agent Skills index was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/agent-skills/index.json",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/.well-known/skills/index.json",
            "error": "TypeError: fetch failed"
          }
        ]
      },
      "issue": "Agent Skills index was not found at the expected path.",
      "howToFix": "Publish an index with a non-empty skills array and reachable SKILL.md URLs."
    }
  ]
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

agent.json

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

20 Fail

Needs attention

agent.json

Failed check
01

Issue

agent.json was not found at the expected path.

02

Why it matters

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

Check name

agent.json

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Fetch to find resource

    agent.json was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/agent.json",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/agent.json",
            "error": "TypeError: fetch failed"
          }
        ]
      },
      "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",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/agents.json",
            "error": "TypeError: fetch failed"
          }
        ]
      },
      "issue": "agents.json was not found at the expected path.",
      "howToFix": "If this site uses agents.json, publish JSON with an agents array containing name and url for each agent."
    }
  ]
}

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is partially implemented.

19 Warning

Needs attention

Content freshness signals

Warning
01

Issue

Content freshness signals are incomplete: missing 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

25/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

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

Result

Content freshness signals is partially implemented.

Evidence
{
  "lastModified": "Mon, 23 Mar 2026 10:18:48 GMT",
  "schemaDates": [],
  "metaDateCount": 0,
  "timeDateCount": 0
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

DNS-AID Agent Discovery

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

15 Fail

Needs attention

DNS-AID Agent Discovery

Failed check
01

Issue

No DNS-AID entrypoint records were found under _agents.

02

Why it matters

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

Check name

DNS-AID Agent Discovery

Score

25/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Resolve DNS-AID SVCB/HTTPS records

    No DNS-AID entrypoint records were found under _agents.

  2. Validate alpn and endpoint parameters

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

  3. Check DNSSEC material

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

Evidence
{
  "failedStep": "svcb-https-records",
  "steps": [
    {
      "id": "svcb-https-records",
      "title": "Resolve DNS-AID SVCB/HTTPS records",
      "status": "fail",
      "evidence": {
        "hostname": "wake.com",
        "probes": [
          {
            "name": "_index._agents.wake.com",
            "found": false,
            "recordCount": 1,
            "records": [],
            "hasAlpn": false,
            "hasEndpoint": false
          },
          {
            "name": "_a2a._agents.wake.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": "wake.com",
            "dnssecTypes": [],
            "dnssecRecordCount": 0
          }
        ]
      },
      "issue": "DNSSEC material was not visible for the hostname or parent zone from this resolver.",
      "howToFix": "Sign the public discovery zone with DNSSEC so validating resolvers can return authenticated data."
    }
  ]
}

Agent Ease of UseMCPInformational

WebMCP

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

13 Warning

Needs attention

WebMCP

Warning
01

Issue

WebMCP declarative annotations need fixes.

Details

02

Why it matters

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

Check name

WebMCP

Score

50/100

Status

warning

Category

MCP

Maturity

Informational

Goal

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

Result

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

Validation steps

  1. Detect data-mcp-tool annotations

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

  2. Detect WebMCP declarative tags

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

  3. Validate WebMCP declarative annotation quality

    WebMCP declarative annotations need fixes.

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

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

  5. Detect WebMCP browser navigator injection

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

  6. Interactive surface coverage

    Only 0% of interactive surfaces are annotated.

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Source and trust signals

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

11 Fail

Needs attention

AIO: Source and trust signals

Failed check
01

Issue

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

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

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer evidence and trust

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

10 Fail

Needs attention

AEO: Answer evidence and trust

Failed check
01

Issue

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

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

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

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

AEO readiness is incomplete.

02

Why it matters

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

Check name

AEO: Question-led structure

Score

50/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

Evidence
{
  "h2Count": 0,
  "questionH2s": [],
  "hasFaq": true,
  "score": 50,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Visible structured data match

AIO: Visible structured data match scored 60/100 and needs improvement.

4 Warning

Needs attention

AIO: Visible structured data match

Warning
01

Issue

2 structured-data value(s) were not found in visible page text.

Details

02

Why it matters

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

Check name

AIO: Visible structured data match

Score

60/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: Visible structured data match scored 60/100 and needs improvement.

Evidence
{
  "schemaCount": 1,
  "checkedFields": [
    {
      "path": "$[0].mainEntity[0].name",
      "value": "How fast is the domain transfer?"
    },
    {
      "path": "$[0].mainEntity[1].name",
      "value": "Is the payment and domain transfer secure?"
    },
    {
      "path": "$[0].mainEntity[2].name",
      "value": "Can I make an offer?"
    },
    {
      "path": "$[0].mainEntity[3].name",
      "value": "Is Lease-to-Own (LTO) available for this domain?"
    },
    {
      "path": "$[0].mainEntity[4].name",
      "value": "Will I get an invoice or receipt?"
    }
  ],
  "mismatches": [
    {
      "path": "$[0].mainEntity[3].name",
      "value": "Is Lease-to-Own (LTO) available for this domain?"
    },
    {
      "path": "$[0].mainEntity[4].name",
      "value": "Will I get an invoice or receipt?"
    }
  ],
  "score": 60,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first sections

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

3 Warning

Needs attention

AEO: Answer-first sections

Warning
01

Issue

AEO readiness is incomplete.

02

Why it matters

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

Check name

AEO: Answer-first sections

Score

80/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Page experience for AIO

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

2 Warning

Needs attention

AIO: Page experience for AIO

Warning
01

Issue

4 image(s) are missing width/height attributes. 8 possible modal/interstitial element(s) detected.

Details

02

Why it matters

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

Check name

AIO: Page experience for AIO

Score

70/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

Evidence
{
  "viewportContent": "width=device-width, user-scalable=no, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0",
  "visibleWords": 154,
  "htmlBytes": 27160,
  "imagesMissingDimensions": [
    {
      "src": "https://forsale.spaceship-cdn.com/static/latest/3.latest/assets/fonts/arrow-right.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img class=\"gb-icon-img gb-button__icon gb-button__icon--trailing\" src=\"https://forsale.spaceship-cdn.com/static/latest/3.latest/assets/fonts/arrow-right.svg\" alt=\"Submit your offer\">"
    },
    {
      "src": "https://forsale.spaceship-cdn.com/static/latest/3.latest/assets/fonts/regular-cross.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img class=\"gb-icon-img gb-button__icon\" src=\"https://forsale.spaceship-cdn.com/static/latest/3.latest/assets/fonts/regular-cross.svg\" alt=\"Close\">"
    },
    {
      "src": "https://forsale.spaceship-cdn.com/static/latest/3.latest/assets/fonts/regular-cross.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img class=\"gb-icon-img gb-button__icon\" src=\"https://forsale.spaceship-cdn.com/static/latest/3.latest/assets/fonts/regular-cross.svg\" alt=\"Close\">"
    },
    {
      "src": "https://forsale.spaceship-cdn.com/static/latest/3.latest/assets/fonts/search.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img class=\"gb-icon-img\" src=\"https://forsale.spaceship-cdn.com/static/latest/3.latest/assets/fonts/search.svg\" alt=\"Search\">"
    }
  ],
  "possibleDialogs": [
    "<div id=\"contact-form-modal-container\"><div id=\"contact-form-modal\" class=\"gb-modal-base gb-modal--scrollable-body gb-modal gb-is-transition-leave-done gb-d-none\" tabindex=\"0\"> <div role=\"dialog\" class=\"gb-modal-base__surface\"> <div class=\"gb-modal-header\"> <div class=\"gb-modal-header__holder\"> Your personal information </div> <button class=\"gb-modal__close-button gb-modal-header__close gb-button gb-button--icon gb-button--gray-ghost\" type=\"button\"> <img class=\"gb-icon-img gb-button__icon\" sr...",
    "<div id=\"contact-form-modal\" class=\"gb-modal-base gb-modal--scrollable-body gb-modal gb-is-transition-leave-done gb-d-none\" tabindex=\"0\"> <div role=\"dialog\" class=\"gb-modal-base__surface\"> <div class=\"gb-modal-header\"> <div class=\"gb-modal-header__holder\"> Your personal information </div> <button class=\"gb-modal__close-button gb-modal-header__close gb-button gb-button--icon gb-button--gray-ghost\" type=\"button\"> <img class=\"gb-icon-img gb-button__icon\" src=\"https://forsale.spaceship-cdn.com/st...",
    "<div role=\"dialog\" class=\"gb-modal-base__surface\"> <div class=\"gb-modal-header\"> <div class=\"gb-modal-header__holder\"> Your personal information </div> <button class=\"gb-modal__close-button gb-modal-header__close gb-button gb-button--icon gb-button--gray-ghost\" type=\"button\"> <img class=\"gb-icon-img gb-button__icon\" src=\"https://forsale.spaceship-cdn.com/static/latest/3.latest/assets/fonts/regular-cross.svg\" alt=\"Close\"> <span class=\"gb-button__text\">Close</span> </button> </div> <div class=\"...",
    "<div class=\"gb-modal-header\"> <div class=\"gb-modal-header__holder\"> Your personal information </div> <button class=\"gb-modal__close-button gb-modal-header__close gb-button gb-button--icon gb-button--gray-ghost\" type=\"button\"> <img class=\"gb-icon-img gb-button__icon\" src=\"https://forsale.spaceship-cdn.com/static/latest/3.latest/assets/fonts/regular-cross.svg\" alt=\"Close\"> <span class=\"gb-button__text\">Close</span> </button> </div>",
    "<div class=\"gb-modal-header__holder\"> Your personal information </div>",
    "<button class=\"gb-modal__close-button gb-modal-header__close gb-button gb-button--icon gb-button--gray-ghost\" type=\"button\"> <img class=\"gb-icon-img gb-button__icon\" src=\"https://forsale.spaceship-cdn.com/static/latest/3.latest/assets/fonts/regular-cross.svg\" alt=\"Close\"> <span class=\"gb-button__text\">Close</span> </button>",
    "<div class=\"gb-modal-body\"> <p class=\"gb-mb-4\">Fill-in your basic information to submit the offer for <strong>wake.com</strong></p> <form id=\"contact-form\" novalidate> <div class=\"gb-row gb-mb-3\"> <div class=\"gb-col-12 gb-col-sm-6 gb-mb-3\"> <div class=\"gb-form-label\"> <label for=\"first-name-field\">First name *</label> </div> <div class=\"gb-input gb-textfield\"> <input id=\"first-name-field\" name=\"firstName\" placeholder=\"Enter your first name\" class=\"gb-textfield__input gb-input__input\" type=\"te...",
    "<div class=\"gb-modal-footer\"> <a id=\"submit-link\" class=\"gb-button gb-button--block gb-button--brand gb-is-disabled\" href=\"/\" disabled> <span class=\"gb-button__text\">Submit offer</span> </a> </div>"
  ],
  "score": 70,
  "weight": 10
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer intent coverage

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

1 Warning

Needs attention

AEO: Answer intent coverage

Warning
01

Issue

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

Details

02

Why it matters

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

Check name

AEO: Answer intent coverage

Score

70/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

Evidence
{
  "headings": [],
  "expected": [
    {
      "id": "what",
      "label": "What is wake.com for sale?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does wake.com for sale work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use wake.com for sale?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is wake.com for sale free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does wake.com for sale compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is wake.com for sale?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does wake.com for sale work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use wake.com for sale?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is wake.com for sale free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does wake.com for sale compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 8
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Answer block readiness

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

1 Warning

Needs attention

AIO: Answer block readiness

Warning
01

Issue

2 structured-data value(s) were not found in visible page text.

02

Why it matters

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

Check name

AIO: Answer block readiness

Score

80/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

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

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",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/api/context",
            "error": "TypeError: fetch failed"
          },
          {
            "path": "/context",
            "error": "TypeError: fetch failed"
          }
        ]
      },
      "issue": "AI context endpoint was not found at the expected path.",
      "howToFix": "Publish a concise JSON or Markdown AI context endpoint describing the product, public actions, and machine-readable resources."
    }
  ]
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Query intent coverage

AIO: Query intent coverage is informational for this page.

Informational

Needs attention

AIO: Query intent coverage

Informational
01

Issue

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

Details

02

Why it matters

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

Check name

AIO: Query intent coverage

Score

70/100

Status

informational

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

AIO: Query intent coverage is informational for this page.

Evidence
{
  "headings": [],
  "expected": [
    {
      "id": "what",
      "label": "What is wake.com for sale?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does wake.com for sale work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use wake.com for sale?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is wake.com for sale free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does wake.com for sale compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is wake.com for sale?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does wake.com for sale work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use wake.com for sale?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is wake.com for sale free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does wake.com for sale compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 4
}

AI DiscoverabilityDiscoverabilityEstablished

IndexNow key

IndexNow key is informational for this page.

Informational

Needs attention

IndexNow key

Informational
01

Issue

IndexNow key is informational for this page.

02

Why it matters

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

Check name

IndexNow key

Score

100/100

Status

informational

Category

Discoverability

Maturity

Established

Goal

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

Result

IndexNow key is informational for this page.

Validation steps

  1. Find advertised IndexNow key location

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

  2. Fetch and validate IndexNow key file

    No discoverable IndexNow key file was found.

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

Security & TrustAI Training ExposureEmerging recommendation

TDMRep declaration

The optional TDMRep check could not complete.

Informational

Needs attention

TDMRep declaration

Informational
01

Issue

The scanner could not fetch /.well-known/tdmrep.json: TypeError: fetch failed

02

Why it matters

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

Check name

TDMRep declaration

Score

0/100

Status

informational

Category

AI Training Exposure

Maturity

Emerging recommendation

Goal

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

Result

The optional TDMRep check could not complete.

Validation steps

  1. Fetch /.well-known/tdmrep.json

    The scanner could not fetch /.well-known/tdmrep.json: TypeError: fetch failed

Evidence
{
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch /.well-known/tdmrep.json",
      "status": "informational",
      "evidence": {
        "error": "TypeError: fetch failed"
      },
      "issue": "The scanner could not fetch /.well-known/tdmrep.json: TypeError: fetch failed",
      "howToFix": "Retry the scan, then publish /.well-known/tdmrep.json when the rightsholder needs to reserve or permit text and data mining with the W3C TDMRep signal."
    }
  ],
  "error": "TypeError: fetch failed"
}

Performance and AccessibilityBest PracticesBrowser audit

Browser errors were logged to the console

100 Fail

Check name

Browser errors were logged to the console

Score

0/100

Status

fail

Device

desktop

Category

Best Practices

Fix guidance

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. [Learn more about this errors in console diagnostic audit](https://developer.chrome.com/docs/lighthouse/best-practices/errors-in-console/)

Evidence
{
  "description": "Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. [Learn more about this errors in console diagnostic audit](https://developer.chrome.com/docs/lighthouse/best-practices/errors-in-console/)"
}

Performance and AccessibilityPerformanceBrowser audit

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.

33 Fail

Check name

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. [Learn more about the viewport meta tag](https://dequeuniversity.com/rules/axe/4.11/meta-viewport).

Evidence
{
  "description": "Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. [Learn more about the viewport meta tag](https://dequeuniversity.com/rules/axe/4.11/meta-viewport)."
}

Performance and AccessibilityPerformanceBrowser audit

Render-blocking requests

33 Fail

Check name

Render-blocking requests

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 210 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 210 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

Use efficient cache lifetimes

33 Fail

Check name

Use efficient cache lifetimes

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 324 KiB

Fix guidance

A long cache lifetime can speed up repeat visits to your page. [Learn more about caching](https://developer.chrome.com/docs/performance/insights/cache).

Evidence
{
  "displayValue": "Est savings of 324 KiB",
  "description": "A long cache lifetime can speed up repeat visits to your page. [Learn more about caching](https://developer.chrome.com/docs/performance/insights/cache)."
}

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