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

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability41%Agent Easeof Use6%Security& Trust40%GEO, AIO, AEO57%SEO100%Performance& Accessibility70%
  • AI Discoverability 41 out of 100
  • Agent Ease of Use 6 out of 100
  • Security & Trust 40 out of 100
  • GEO, AIO and AEO 57 out of 100
  • SEO 100 out of 100
  • Performance and Accessibility 70 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Vivun — AI Teammates Built on Structured Reasoning favicon

Vivun — AI Teammates Built on Structured Reasoning

Vivun is an AI research organization that builds AI Teammates by codifying expert knowledge into structured systems. Where most AI generates language, Vivun builds agents that generate reasoning.

Next step

Turn this report into a fix workflow

26 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
41
Priority fix9141View details
Discoverability
33
Priority fix360View details
Content Readiness
54
Needs work551View details
Bot Access Control
33
Priority fix130View details
Agent Ease of Use
6
Priority fix4293View details
API
0
Priority fix060View details
Auth
Not Applicable
Not Applicable070View details
MCP
13
Priority fix062View details
Skill Discovery
5
Priority fix0101View details
Agent Commerce
Not Applicable
Not Applicable400
GEO, AIO and AEO
57
Needs work3412View details
GEO Readiness
61
Needs work014View details
AIO Readiness
52
Needs work223View details
AEO Readiness
57
Needs work115View details
SEO
100
Strong1100
SEO
100
Strong1100
Security & Trust
40
Priority fix630View details
Security & Trust
40
Priority fix230View details
AI Training Exposure
Not Applicable
Not Applicable400
Performance and Accessibility
70
Needs work2053View details
Performance
57
Needs work1053View details
Accessibility
95
Strong1000

Prioritized recommendations

Issues ranked by score impact

51 items need attention

Agent Ease of UseAPIEstablished

API Catalog

API Catalog failed at "Fetch API catalog".

50 Fail

Needs attention

API Catalog

Failed check
01

Issue

The API catalog endpoint did not return HTTP 2xx.

02

Why it matters

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

Check name

API Catalog

Score

0/100

Status

fail

Category

API

Maturity

Established

Goal

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

Result

API Catalog failed at "Fetch API catalog".

Validation steps

  1. Fetch API catalog

    The API catalog endpoint did not return HTTP 2xx.

  2. Validate RFC 9727 linkset

    Response is not valid JSON.

  3. Fetch advertised API catalog targets

    API Catalog did not expose any same-origin hrefs to validate.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch API catalog",
      "status": "fail",
      "evidence": {
        "statusCode": 404,
        "contentType": "text/html; charset=utf-8"
      },
      "issue": "The API catalog endpoint did not return HTTP 2xx.",
      "howToFix": "Publish /.well-known/api-catalog."
    },
    {
      "id": "validate",
      "title": "Validate RFC 9727 linkset",
      "status": "fail",
      "evidence": {
        "valid": false,
        "compatibleContentType": false,
        "issue": "Response is not valid JSON.",
        "rawExcerpt": "<!DOCTYPE html>\n<html>\n  <body>\n    <p>Invalid .well-known request</p>\n  </body>\n</html>"
      },
      "issue": "Response is not valid JSON.",
      "howToFix": "Use application/linkset+json with service-desc, service-doc, and status relations that each include href."
    },
    {
      "id": "target-validation",
      "title": "Fetch advertised API catalog targets",
      "status": "fail",
      "evidence": {
        "checked": [],
        "failures": [
          {
            "reason": "No same-origin API catalog hrefs were available to fetch."
          }
        ]
      },
      "issue": "API Catalog did not expose any same-origin hrefs to validate.",
      "howToFix": "Make each same-origin API catalog href reachable and serve the advertised media type."
    }
  ]
}

AI DiscoverabilityBot Access ControlInformational

Content Signal

Content Signal is missing or incomplete.

50 Fail

Needs attention

Content Signal

Failed check
01

Issue

No Content Signal found in robots.txt

02

Why it matters

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

Check name

Content Signal

Score

0/100

Status

fail

Category

Bot Access Control

Maturity

Informational

Goal

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

Result

Content Signal is missing or incomplete.

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

Agent Ease of UseAPIEstablished

OpenAPI discovery

OpenAPI discovery failed at "Find valid OpenAPI document".

50 Fail

Needs attention

OpenAPI discovery

Failed check
01

Issue

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

02

Why it matters

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

Check name

OpenAPI discovery

Score

0/100

Status

fail

Category

API

Maturity

Established

Goal

Publish a valid OpenAPI or Swagger document for API discovery.

Result

OpenAPI discovery failed at "Find valid OpenAPI document".

Validation steps

  1. Find valid OpenAPI document

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

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Find valid OpenAPI document",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/openapi.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><!-- This site was created in Webflow. https://webflow.com --><!-- Last Published: Wed Jun 10 2026 14:29:48 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"www.vivun.com\" data-wf-page=\"68c0b333272bed3cd2f94fa9\" data-wf-site=\"68424a45023d688185720fd0\" lang=\"en\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><meta content=\"Not Found\" property=\"og:title\"/><meta content=\"Not Found\" name=\"twitter:title\"/><meta content=\"width=device-width, initial-scale=1\" name=\"viewport\"/><meta content=\"google-site-verification=j6X4NU3RdZbkFomKC4AI1pJRdCXMV2FFyy1ZDCJaxL8\" name=\"google-site-verification\"/><meta content=\"Webflow\" name=\"generator\"/><link href=\"https://cdn.prod.website-files"
          },
          {
            "path": "/openapi.yaml",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><!-- This site was created in Webflow. https://webflow.com --><!-- Last Published: Wed Jun 10 2026 14:29:48 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"www.vivun.com\" data-wf-page=\"68c0b333272bed3cd2f94fa9\" data-wf-site=\"68424a45023d688185720fd0\" lang=\"en\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><meta content=\"Not Found\" property=\"og:title\"/><meta content=\"Not Found\" name=\"twitter:title\"/><meta content=\"width=device-width, initial-scale=1\" name=\"viewport\"/><meta content=\"google-site-verification=j6X4NU3RdZbkFomKC4AI1pJRdCXMV2FFyy1ZDCJaxL8\" name=\"google-site-verification\"/><meta content=\"Webflow\" name=\"generator\"/><link href=\"https://cdn.prod.website-files"
          },
          {
            "path": "/swagger.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><!-- This site was created in Webflow. https://webflow.com --><!-- Last Published: Wed Jun 10 2026 14:29:48 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"www.vivun.com\" data-wf-page=\"68c0b333272bed3cd2f94fa9\" data-wf-site=\"68424a45023d688185720fd0\" lang=\"en\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><meta content=\"Not Found\" property=\"og:title\"/><meta content=\"Not Found\" name=\"twitter:title\"/><meta content=\"width=device-width, initial-scale=1\" name=\"viewport\"/><meta content=\"google-site-verification=j6X4NU3RdZbkFomKC4AI1pJRdCXMV2FFyy1ZDCJaxL8\" name=\"google-site-verification\"/><meta content=\"Webflow\" name=\"generator\"/><link href=\"https://cdn.prod.website-files"
          },
          {
            "path": "/swagger.yaml",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><!-- This site was created in Webflow. https://webflow.com --><!-- Last Published: Wed Jun 10 2026 14:29:48 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"www.vivun.com\" data-wf-page=\"68c0b333272bed3cd2f94fa9\" data-wf-site=\"68424a45023d688185720fd0\" lang=\"en\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><meta content=\"Not Found\" property=\"og:title\"/><meta content=\"Not Found\" name=\"twitter:title\"/><meta content=\"width=device-width, initial-scale=1\" name=\"viewport\"/><meta content=\"google-site-verification=j6X4NU3RdZbkFomKC4AI1pJRdCXMV2FFyy1ZDCJaxL8\" name=\"google-site-verification\"/><meta content=\"Webflow\" name=\"generator\"/><link href=\"https://cdn.prod.website-files"
          },
          {
            "path": "/api/openapi.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><!-- This site was created in Webflow. https://webflow.com --><!-- Last Published: Wed Jun 10 2026 14:29:48 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"www.vivun.com\" data-wf-page=\"68c0b333272bed3cd2f94fa9\" data-wf-site=\"68424a45023d688185720fd0\" lang=\"en\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><meta content=\"Not Found\" property=\"og:title\"/><meta content=\"Not Found\" name=\"twitter:title\"/><meta content=\"width=device-width, initial-scale=1\" name=\"viewport\"/><meta content=\"google-site-verification=j6X4NU3RdZbkFomKC4AI1pJRdCXMV2FFyy1ZDCJaxL8\" name=\"google-site-verification\"/><meta content=\"Webflow\" name=\"generator\"/><link href=\"https://cdn.prod.website-files"
          },
          {
            "path": "/api/swagger.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><!-- This site was created in Webflow. https://webflow.com --><!-- Last Published: Wed Jun 10 2026 14:29:48 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"www.vivun.com\" data-wf-page=\"68c0b333272bed3cd2f94fa9\" data-wf-site=\"68424a45023d688185720fd0\" lang=\"en\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><meta content=\"Not Found\" property=\"og:title\"/><meta content=\"Not Found\" name=\"twitter:title\"/><meta content=\"width=device-width, initial-scale=1\" name=\"viewport\"/><meta content=\"google-site-verification=j6X4NU3RdZbkFomKC4AI1pJRdCXMV2FFyy1ZDCJaxL8\" name=\"google-site-verification\"/><meta content=\"Webflow\" name=\"generator\"/><link href=\"https://cdn.prod.website-files"
          },
          {
            "path": "/docs/openapi.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><!-- This site was created in Webflow. https://webflow.com --><!-- Last Published: Wed Jun 10 2026 14:29:48 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"www.vivun.com\" data-wf-page=\"68c0b333272bed3cd2f94fa9\" data-wf-site=\"68424a45023d688185720fd0\" lang=\"en\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><meta content=\"Not Found\" property=\"og:title\"/><meta content=\"Not Found\" name=\"twitter:title\"/><meta content=\"width=device-width, initial-scale=1\" name=\"viewport\"/><meta content=\"google-site-verification=j6X4NU3RdZbkFomKC4AI1pJRdCXMV2FFyy1ZDCJaxL8\" name=\"google-site-verification\"/><meta content=\"Webflow\" name=\"generator\"/><link href=\"https://cdn.prod.website-files"
          }
        ]
      },
      "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=utf-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
      "howToFix": "Publish a valid OpenAPI 3.x or Swagger 2.0 JSON/YAML document with info, paths, operations, and responses."
    }
  ]
}

AI DiscoverabilityBot Access ControlInformational

Web Bot Auth request signing

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

50 Fail

Needs attention

Web Bot Auth request signing

Failed check
01

Issue

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

02

Why it matters

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

Check name

Web Bot Auth request signing

Score

0/100

Status

fail

Category

Bot Access Control

Maturity

Informational

Goal

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

Result

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

Validation steps

  1. Fetch to find resource

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

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/http-message-signatures-directory",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 88
          }
        ]
      },
      "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."
    }
  ]
}

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy is missing or incomplete.

33 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'"
}

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; charset=utf-8" does not indicate Markdown when requested with Accept: text/markdown.

02

Why it matters

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

Check name

Markdown negotiation

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Return HTML responses as markdown when agents request it.

Result

Markdown negotiation failed at "Markdown content type".

Validation steps

  1. Markdown content type

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

  2. Vary: Accept header

    Markdown negotiation is missing Vary: Accept; current Vary header is "accept-encoding".

  3. Structured Markdown body

    Markdown response is missing a heading.

Evidence
{
  "failedStep": "content-type",
  "steps": [
    {
      "id": "content-type",
      "title": "Markdown content type",
      "status": "fail",
      "evidence": {
        "statusCode": 200,
        "contentType": "text/html; charset=utf-8"
      },
      "issue": "Content-Type \"text/html; charset=utf-8\" does not indicate Markdown when requested with Accept: text/markdown.",
      "howToFix": "Return Content-Type: text/markdown; charset=utf-8 for requests with Accept: text/markdown."
    },
    {
      "id": "vary-accept",
      "title": "Vary: Accept header",
      "status": "fail",
      "evidence": {
        "vary": "accept-encoding"
      },
      "issue": "Markdown negotiation is missing Vary: Accept; current Vary header is \"accept-encoding\".",
      "howToFix": "Add Vary: Accept on negotiated Markdown responses so shared caches keep HTML and Markdown variants separate."
    },
    {
      "id": "markdown-content",
      "title": "Structured Markdown body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "hasHeading": false,
        "wordCount": 9408,
        "excerpt": "<!DOCTYPE html><!-- This site was created in Webflow. https://webflow.com --><!-- Last Published: Wed Jun 10 2026 14:29:48 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"www.vivun.com\" data-wf-page=\"69bacb56b377ff74ac066c85\"",
        "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."
    }
  ]
}

Security & TrustSecurity & TrustEstablished

Referrer-Policy

Referrer-Policy is missing or incomplete.

33 Fail

Needs attention

Referrer-Policy

Failed check
01

Issue

Referrer-Policy is missing or incomplete.

02

Why it matters

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

Check name

Referrer-Policy

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Limit how much referrer data leaves the site.

Result

Referrer-Policy is missing or incomplete.

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

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: missing <main> landmark; missing <footer> landmark; invalid h1 (found 0); 0/1 applicable form inputs have autocomplete attributes (1 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": false,
  "nav": true,
  "footer": false,
  "meaningfulH1": false,
  "headingOrder": true,
  "accessibleLinks": true,
  "accessibleButtons": true,
  "imageAltCoverage": true,
  "formAutocompleteCoverage": false,
  "details": {
    "inaccessibleLinks": [],
    "inaccessibleButtons": [],
    "missingAutocompleteInputs": [
      "<input id=\"vendor-search-handler\" type=\"text\" name=\"vendor-search-handler\" placeholder=\"Search&#x2026;\" aria-label=\"Cookie list search\">"
    ],
    "imagesMissingAlt": [],
    "skippedHeadingLevels": []
  },
  "counts": {
    "h1": 0,
    "headings": 13,
    "links": 24,
    "inaccessibleLinks": 0,
    "buttons": 16,
    "inaccessibleButtons": 0,
    "images": 6,
    "imagesWithAlt": 6,
    "autocompleteInputs": 1,
    "inputsWithAutocomplete": 0,
    "missingAutocompleteInputs": 1
  }
}

Security & TrustSecurity & TrustEstablished

X-Content-Type-Options

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

33 Fail

Needs attention

X-Content-Type-Options

Failed check
01

Issue

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

02

Why it matters

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

Check name

X-Content-Type-Options

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Prevent MIME sniffing for browser-loaded resources.

Result

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

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

AI DiscoverabilityDiscoverabilityEstablished

High-value schema types

High-value schema types is missing or incomplete.

25 Fail

Needs attention

High-value schema types

Failed check
01

Issue

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

02

Why it matters

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

Check name

High-value schema types

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

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

Result

High-value schema types is missing or incomplete.

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

AI DiscoverabilityDiscoverabilityEstablished

JSON-LD present

JSON-LD present is missing or incomplete.

25 Fail

Needs attention

JSON-LD present

Failed check
01

Issue

No JSON-LD blocks found.

02

Why it matters

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

Check name

JSON-LD present

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

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

Result

JSON-LD present is missing or incomplete.

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

AI DiscoverabilityDiscoverabilityEstablished

Link headers

Link headers failed at "Find useful Link headers".

25 Fail

Needs attention

Link headers

Failed check
01

Issue

No useful agent discovery Link headers were found.

02

Why it matters

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

Check name

Link headers

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Include Link response headers for agent discovery using RFC 8288.

Result

Link headers failed at "Find useful Link headers".

Validation steps

  1. Find useful Link headers

    No useful agent discovery Link headers were found.

  2. Fetch same-origin Link header targets

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

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

Agent Ease of UseMCPEmerging recommendation

MCP Server Card

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

25 Fail

Needs attention

MCP Server Card

Failed check
01

Issue

MCP Server Card was not found at the expected path.

02

Why it matters

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

Check name

MCP Server Card

Score

0/100

Status

fail

Category

MCP

Maturity

Emerging recommendation

Goal

Publish an MCP Server Card for agent discovery.

Result

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

Validation steps

  1. Fetch to find resource

    MCP Server Card was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/mcp/server-card.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 88
          },
          {
            "path": "/.well-known/mcp/server-cards.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 88
          },
          {
            "path": "/.well-known/mcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 88
          }
        ]
      },
      "issue": "MCP Server Card was not found at the expected path.",
      "howToFix": "Publish an MCP server card with valid transports and make each advertised local endpoint answer an MCP initialize request."
    }
  ]
}

Agent Ease of UseMCPEmerging recommendation

mcp.json

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

25 Fail

Needs attention

mcp.json

Failed check
01

Issue

mcp.json was not found at the expected path.

02

Why it matters

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

Check name

mcp.json

Score

0/100

Status

fail

Category

MCP

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Fetch to find resource

    mcp.json was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/mcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 25509
          },
          {
            "path": "/.well-known/mcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 88
          },
          {
            "path": "/.well-known/mcp/server-card.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 88
          }
        ]
      },
      "issue": "mcp.json was not found at the expected path.",
      "howToFix": "Publish mcp.json or an MCP server card with serverInfo, protocolVersion, transport endpoint, and capabilities."
    }
  ]
}

AI DiscoverabilityDiscoverabilityEstablished

Organization / WebSite schema

Organization / WebSite schema is missing or incomplete.

25 Fail

Needs attention

Organization / WebSite schema

Failed check
01

Issue

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

02

Why it matters

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

Check name

Organization / WebSite schema

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Identify the site owner and website entity in structured data.

Result

Organization / WebSite schema is missing or incomplete.

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

Agent Ease of UseMCPInformational

WebMCP manifest

WebMCP manifest failed at "Fetch to find resource".

25 Fail

Needs attention

WebMCP manifest

Failed check
01

Issue

WebMCP manifest was not found at the expected path.

02

Why it matters

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

Check name

WebMCP manifest

Score

0/100

Status

fail

Category

MCP

Maturity

Informational

Goal

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

Result

WebMCP manifest failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    WebMCP manifest was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/webmcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 88
          },
          {
            "path": "/webmcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 25509
          },
          {
            "path": "/mcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 25509
          }
        ]
      },
      "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 DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is partially implemented.

25 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": "Thu, 11 Jun 2026 14:58:23 GMT",
  "schemaDates": [],
  "metaDateCount": 0,
  "timeDateCount": 0
}

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

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

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

20 Fail

Needs attention

Agent Skills index

Failed check
01

Issue

Agent Skills index was not found at the expected path.

02

Why it matters

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

Check name

Agent Skills index

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an agent skills discovery index.

Result

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

Validation steps

  1. Fetch to find resource

    Agent Skills index was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/agent-skills/index.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 88
          },
          {
            "path": "/.well-known/skills/index.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 88
          }
        ]
      },
      "issue": "Agent Skills index was not found at the expected path.",
      "howToFix": "Publish an index with a non-empty skills array and reachable SKILL.md URLs."
    }
  ]
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

agent.json

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

20 Fail

Needs attention

agent.json

Failed check
01

Issue

agent.json was not found at the expected path.

02

Why it matters

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

Check name

agent.json

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Fetch to find resource

    agent.json was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/agent.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 88
          },
          {
            "path": "/agent.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 25509
          }
        ]
      },
      "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; charset=utf-8",
            "length": 88
          },
          {
            "path": "/agents.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 25509
          }
        ]
      },
      "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 UseSkill DiscoveryEmerging recommendation

DNS-AID Agent Discovery

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

15 Fail

Needs attention

DNS-AID Agent Discovery

Failed check
01

Issue

No DNS-AID entrypoint records were found under _agents.

02

Why it matters

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

Check name

DNS-AID Agent Discovery

Score

25/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

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

Result

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

Validation steps

  1. Resolve DNS-AID SVCB/HTTPS records

    No DNS-AID entrypoint records were found under _agents.

  2. Validate alpn and endpoint parameters

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

  3. Check DNSSEC material

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

Evidence
{
  "failedStep": "svcb-https-records",
  "steps": [
    {
      "id": "svcb-https-records",
      "title": "Resolve DNS-AID SVCB/HTTPS records",
      "status": "fail",
      "evidence": {
        "hostname": "www.vivun.com",
        "probes": [
          {
            "name": "_index._agents.www.vivun.com",
            "found": false,
            "recordCount": 1,
            "records": [],
            "hasAlpn": false,
            "hasEndpoint": false
          },
          {
            "name": "_a2a._agents.www.vivun.com",
            "found": false,
            "recordCount": 1,
            "records": [],
            "hasAlpn": false,
            "hasEndpoint": false
          }
        ]
      },
      "issue": "No DNS-AID entrypoint records were found under _agents.",
      "howToFix": "Publish ServiceMode SVCB/HTTPS records such as _index._agents.example.com or _a2a._agents.example.com."
    },
    {
      "id": "service-params",
      "title": "Validate alpn and endpoint parameters",
      "status": "informational",
      "evidence": {
        "discovered": []
      },
      "howToFix": "Include alpn and endpoint service parameters in each DNS-AID record so agents know the protocol and target entrypoint."
    },
    {
      "id": "dnssec",
      "title": "Check DNSSEC material",
      "status": "warning",
      "evidence": {
        "hasDnssecMaterial": false,
        "checked": [
          {
            "name": "www.vivun.com",
            "dnssecTypes": [],
            "dnssecRecordCount": 0
          },
          {
            "name": "vivun.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 name="ot-group-id-C0004"> is missing tool-param-description.
    • <input name="ot-group-id-C0002"> is missing tool-param-description.
    • <input name="ot-group-id-C0003"> is missing tool-param-description.
    • <input name="vendor-search-handler"> 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 tool-param-description.
    • <input> is missing a name attribute.
    • <input> is missing tool-param-description.
    • <input> is missing a name attribute.
    • <input> is missing tool-param-description.
  4. Detect WebMCP imperative API usage

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

  5. Detect WebMCP browser navigator injection

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

  6. Interactive surface coverage

    Only 0% of interactive surfaces are annotated.

Evidence
{
  "failedStep": "declarative-annotation-quality",
  "steps": [
    {
      "id": "data-mcp-tool-attributes",
      "title": "Detect data-mcp-tool annotations",
      "status": "informational",
      "evidence": {
        "dataMcpToolCount": 0,
        "dataMcpTools": []
      },
      "issue": "No data-mcp-tool attributes were found on interactive elements.",
      "howToFix": "Add data-mcp-tool attributes to high-value forms, buttons, and links so generic MCP-aware tooling can identify intended actions."
    },
    {
      "id": "declarative-tags",
      "title": "Detect WebMCP declarative tags",
      "status": "informational",
      "evidence": {
        "totalForms": 0,
        "formsWithTags": 0,
        "totalInteractive": 48,
        "interactiveWithTags": 0,
        "totalCount": 48,
        "taggedCount": 0,
        "dataMcpToolCount": 0,
        "dataMcpTools": [],
        "coverage": 0,
        "annotationIssues": [
          "<input name=\"ot-group-id-C0004\"> is missing tool-param-description.",
          "<input name=\"ot-group-id-C0002\"> is missing tool-param-description.",
          "<input name=\"ot-group-id-C0003\"> is missing tool-param-description.",
          "<input name=\"vendor-search-handler\"> 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 tool-param-description.",
          "<input> is missing a name attribute.",
          "<input> is missing tool-param-description.",
          "<input> is missing a name attribute.",
          "<input> is missing tool-param-description."
        ]
      },
      "issue": "No elements found with tool-name or tool-description attributes.",
      "howToFix": "Add tool-name and tool-description attributes to forms and interactive elements."
    },
    {
      "id": "declarative-annotation-quality",
      "title": "Validate WebMCP declarative annotation quality",
      "status": "warning",
      "evidence": {
        "issueCount": 12,
        "issues": [
          "<input name=\"ot-group-id-C0004\"> is missing tool-param-description.",
          "<input name=\"ot-group-id-C0002\"> is missing tool-param-description.",
          "<input name=\"ot-group-id-C0003\"> is missing tool-param-description.",
          "<input name=\"vendor-search-handler\"> 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 tool-param-description.",
          "<input> is missing a name attribute.",
          "<input> is missing tool-param-description.",
          "<input> is missing a name attribute.",
          "<input> is missing tool-param-description."
        ]
      },
      "issue": "WebMCP declarative annotations need fixes.",
      "issueDetails": [
        {
          "title": "WebMCP declarative annotation issues",
          "items": [
            {
              "type": "code",
              "value": "<input name=\"ot-group-id-C0004\"> is missing tool-param-description."
            },
            {
              "type": "code",
              "value": "<input name=\"ot-group-id-C0002\"> is missing tool-param-description."
            },
            {
              "type": "code",
              "value": "<input name=\"ot-group-id-C0003\"> is missing tool-param-description."
            },
            {
              "type": "code",
              "value": "<input name=\"vendor-search-handler\"> 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 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 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": 0,
        "formsWithTags": 0,
        "totalInteractive": 48,
        "interactiveWithTags": 0,
        "totalCount": 48,
        "taggedCount": 0,
        "dataMcpToolCount": 0,
        "dataMcpTools": [],
        "coverage": 0,
        "annotationIssues": [
          "<input name=\"ot-group-id-C0004\"> is missing tool-param-description.",
          "<input name=\"ot-group-id-C0002\"> is missing tool-param-description.",
          "<input name=\"ot-group-id-C0003\"> is missing tool-param-description.",
          "<input name=\"vendor-search-handler\"> 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 tool-param-description.",
          "<input> is missing a name attribute.",
          "<input> is missing tool-param-description.",
          "<input> is missing a name attribute.",
          "<input> is missing tool-param-description."
        ]
      },
      "issue": "Only 0% of interactive surfaces are annotated.",
      "howToFix": "Add WebMCP annotations to all forms and interactive elements to increase agent coverage."
    }
  ],
  "staticSignals": {
    "detected": false,
    "matched": []
  },
  "coverage": {
    "totalForms": 0,
    "formsWithTags": 0,
    "totalInteractive": 48,
    "interactiveWithTags": 0,
    "totalCount": 48,
    "taggedCount": 0,
    "dataMcpToolCount": 0,
    "dataMcpTools": [],
    "coverage": 0,
    "annotationIssues": [
      "<input name=\"ot-group-id-C0004\"> is missing tool-param-description.",
      "<input name=\"ot-group-id-C0002\"> is missing tool-param-description.",
      "<input name=\"ot-group-id-C0003\"> is missing tool-param-description.",
      "<input name=\"vendor-search-handler\"> 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 tool-param-description.",
      "<input> is missing a name attribute.",
      "<input> is missing tool-param-description.",
      "<input> is missing a name attribute.",
      "<input> is missing tool-param-description."
    ]
  },
  "browserWebMcp": {
    "checked": true,
    "detected": false,
    "hasNavigatorModelContext": false,
    "modelContextType": "undefined",
    "hasProvideContext": false,
    "hasRegisterTool": false
  }
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Visible structured data match

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

10 Fail

Needs attention

AIO: Visible structured data match

Failed check
01

Issue

No JSON-LD structured data was detected.

Details

02

Why it matters

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

Check name

AIO: Visible structured data match

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Source and trust signals

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

9 Fail

Needs attention

AIO: Source and trust signals

Failed check
01

Issue

Missing AIO trust signals: author, publisher, freshnessDate, 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

20/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

Evidence
{
  "signals": {
    "author": false,
    "publisher": false,
    "freshnessDate": false,
    "aboutOrContact": true,
    "policyLinks": false
  },
  "missing": [
    "author",
    "publisher",
    "freshnessDate",
    "policyLinks"
  ],
  "authorMeta": "",
  "schemaAuthors": [],
  "schemaPublishers": [],
  "schemaDates": [],
  "visibleDates": [],
  "aboutLinks": [
    {
      "href": "#",
      "text": "Company",
      "html": "<a href=\"#\" aria-haspopup=\"true\" aria-expanded=\"false\" id=\"vvw-ct\">Company <span class=\"vvw-cv\"></span></a>"
    },
    {
      "href": "/about",
      "text": "About",
      "html": "<a href=\"/about\">About</a>"
    },
    {
      "href": "/about",
      "text": "About",
      "html": "<a href=\"/about\">About</a>"
    }
  ],
  "contactLinks": [],
  "privacyLinks": [],
  "score": 20,
  "weight": 20
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer evidence and trust

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

7 Fail

Needs attention

AEO: Answer evidence and trust

Failed check
01

Issue

Missing AIO trust signals: author, publisher, freshnessDate, 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

20/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

Evidence
{
  "signals": {
    "author": false,
    "publisher": false,
    "freshnessDate": false,
    "aboutOrContact": true,
    "policyLinks": false
  },
  "missing": [
    "author",
    "publisher",
    "freshnessDate",
    "policyLinks"
  ],
  "authorMeta": "",
  "schemaAuthors": [],
  "schemaPublishers": [],
  "schemaDates": [],
  "visibleDates": [],
  "aboutLinks": [
    {
      "href": "#",
      "text": "Company",
      "html": "<a href=\"#\" aria-haspopup=\"true\" aria-expanded=\"false\" id=\"vvw-ct\">Company <span class=\"vvw-cv\"></span></a>"
    },
    {
      "href": "/about",
      "text": "About",
      "html": "<a href=\"/about\">About</a>"
    },
    {
      "href": "/about",
      "text": "About",
      "html": "<a href=\"/about\">About</a>"
    }
  ],
  "contactLinks": [],
  "privacyLinks": [],
  "score": 20,
  "weight": 22
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: AI crawler accessibility

GEO: AI crawler accessibility scored 45/100 and needs a fix.

5 Fail

Needs attention

GEO: AI crawler accessibility

Failed check
01

Issue

robots.txt blocks these AI crawlers: gptbot, chatgpt-user, google-extended. No rendered JSON-LD schema block was detected.

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: AI crawler accessibility

Score

45/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

GEO: AI crawler accessibility scored 45/100 and needs a fix.

Evidence
{
  "textWords": 558,
  "htmlBytes": 225307,
  "robots": {
    "checkedCrawlers": [
      "gptbot",
      "chatgpt-user",
      "claudebot",
      "perplexitybot",
      "google-extended"
    ],
    "blocked": [
      "gptbot",
      "chatgpt-user",
      "google-extended"
    ],
    "allows": false
  },
  "schemaBlocks": 0,
  "finalUrl": "https://www.vivun.com/",
  "robotsExcerpt": "# robots.txt for vivun.com\n# https://www.vivun.com/robots.txt\n\n# Allow all major search engine crawlers\nUser-agent: Googlebot\nAllow: /\n\nUser-agent: Bingbot\nAllow: /\n\nUser-agent: Slurp\nAllow: /\n\nUser-agent: DuckDuckBot\nAllow: /\n\n# Block AI training crawlers\nUser-agent: GPTBot\nDisallow: /\n\nUser-agent: ChatGPT-User\nDisallow: /\n\nUser-agent: CCBot\nDisallow: /\n\nUser-agent: anthropic-ai\nDisallow: /\n\nUser-agent: Claude-Web\nDisallow: /\n\nUser-agent: Google-Extended\nDisallow: /\n\nUser-agent: Omgilibot\nDisallow: /\n\nUser-agent: FacebookBot\nDisallow: /\n\n# Default rule for all other bots\nUser-agent: *\nAllow: /\n\n# Disallow admin, auth, and internal paths\nDisallow: /admin/\nDisallow: /api/\nDisallow: /auth/\nDisallow: /dashboard/\nDisallow: /account/\nDisallow: /settings/\nDisallow: /private/\nDisallow: /_next/\nDi",
  "score": 45,
  "weight": 26
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first sections

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

4 Warning

Needs attention

AEO: Answer-first sections

Warning
01

Issue

7 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": 8,
  "passing": 1,
  "failing": [
    {
      "heading": "Privacy Preference Center",
      "headingHtml": "<h2 id=\"ot-pc-title\" aria-hidden=\"false\">Privacy Preference Center</h2>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Privacy Preference Center",
      "headingHtml": "<h2 id=\"ot-pc-title-mobile\" aria-hidden=\"true\">Privacy Preference Center</h2>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Your Privacy",
      "headingHtml": "<h3 id=\"ot-pvcy-txt\">Your Privacy</h3>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Strictly Necessary Cookies",
      "headingHtml": "<h3 id=\"ot-header-id-C0001\">Strictly Necessary Cookies</h3>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Targeting Cookies",
      "headingHtml": "<h3 id=\"ot-header-id-C0004\">Targeting Cookies</h3>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Performance Cookies",
      "headingHtml": "<h3 id=\"ot-header-id-C0002\">Performance Cookies</h3>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Cookie List",
      "headingHtml": "<h3>Cookie List</h3>",
      "firstParagraph": "",
      "paragraphHtml": "<p role=\"status\" class=\"ot-scrn-rdr\"></p>",
      "words": 0,
      "direct": false,
      "issue": "First paragraph is 0 words and does not look like a concise direct answer."
    }
  ],
  "score": 65,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Extraction-friendly structure

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

4 Warning

Needs attention

GEO: Extraction-friendly structure

Warning
01

Issue

Missing extraction signals: optional top summary / TL;DR / key takeaways block, table with <thead> only if the page already has tabular/comparative data, ordered list only if the page explains a workflow/process, optional visible FAQ or FAQPage schema, JSON-LD structured data.

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: Extraction-friendly structure

Score

60/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

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

Evidence
{
  "hasSummary": false,
  "tableCount": 0,
  "tablesWithHead": 0,
  "tablesMissingThead": [],
  "orderedLists": 0,
  "hasFaq": false,
  "definitionPatterns": 4,
  "schemaBlocks": 0,
  "missingSignals": [
    "optional top summary / TL;DR / key takeaways block",
    "table with <thead> only if the page already has tabular/comparative data",
    "ordered list only if the page explains a workflow/process",
    "optional visible FAQ or FAQPage schema",
    "JSON-LD structured data"
  ],
  "score": 60,
  "weight": 24
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question-led structure

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

3 Warning

Needs attention

AEO: Question-led structure

Warning
01

Issue

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

Details

02

Why it matters

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

Check name

AEO: Question-led structure

Score

50/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Entity clarity

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

3 Warning

Needs attention

GEO: Entity clarity

Warning
01

Issue

Title/H1 terms missing from description: built.

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: Entity clarity

Score

69/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

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

Evidence
{
  "title": "Vivun — AI Teammates Built on Structured Reasoning",
  "h1": "",
  "description": "Vivun is an AI research organization that builds AI Teammates by codifying expert knowledge into structured systems. Where most AI generates language, Vivun builds agents that generate reasoning.",
  "topicOverlap": 0.8,
  "topicTerms": [
    "vivun",
    "teammates",
    "built",
    "structured",
    "reasoning"
  ],
  "descriptionTerms": [
    "vivun",
    "research",
    "organization",
    "builds",
    "teammates",
    "codifying",
    "expert",
    "knowledge",
    "into",
    "structured",
    "systems",
    "where",
    "most",
    "generates",
    "language",
    "agents",
    "generate",
    "reasoning"
  ],
  "missingFromDescription": [
    "built"
  ],
  "score": 69,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

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

2 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

Entity or definition gaps: built.

Details

02

Why it matters

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

Check name

AEO: Entity and definition clarity

Score

75/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

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

Evidence
{
  "title": "Vivun — AI Teammates Built on Structured Reasoning",
  "h1": "",
  "description": "Vivun is an AI research organization that builds AI Teammates by codifying expert knowledge into structured systems. Where most AI generates language, Vivun builds agents that generate reasoning.",
  "topicOverlap": 0.8,
  "definitionCount": 4,
  "topicTerms": [
    "vivun",
    "teammates",
    "built",
    "structured",
    "reasoning"
  ],
  "descriptionTerms": [
    "vivun",
    "research",
    "organization",
    "builds",
    "teammates",
    "codifying",
    "expert",
    "knowledge",
    "into",
    "structured",
    "systems",
    "where",
    "most",
    "generates",
    "language",
    "agents",
    "generate",
    "reasoning"
  ],
  "missingFromDescription": [
    "built"
  ],
  "score": 75,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Explanatory content depth

GEO: Explanatory content depth scored 75/100 and needs improvement.

2 Warning

Needs attention

GEO: Explanatory content depth

Warning
01

Issue

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

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: Explanatory content depth

Score

75/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

GEO: Explanatory content depth scored 75/100 and needs improvement.

Evidence
{
  "candidatePassages": 5,
  "citablePassages": 0,
  "failingCandidateParagraphs": [
    {
      "index": 1,
      "heading": "H4: Your Privacy",
      "text": "When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences, or your device, and is mostly used to make the site work as you expect. The information does not usually identify you directly, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to a...",
      "words": 114,
      "hasEvidence": false,
      "reasons": [
        "Missing a named source, statistic, date, percentage, report, or other evidence signal."
      ],
      "html": "<p id=\"ot-pc-desc\" class=\"ot-grp-desc\">When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences, or your device, and is mostly used to make the site work as you expect. The information does not usually identify you directly, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the..."
    },
    {
      "index": 2,
      "heading": "H4: Strictly Necessary Cookies",
      "text": "These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store a...",
      "words": 80,
      "hasEvidence": false,
      "reasons": [
        "Missing a named source, statistic, date, percentage, report, or other evidence signal."
      ],
      "html": "<p class=\"ot-grp-desc ot-category-desc\">These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.</p>"
    },
    {
      "index": 3,
      "heading": "H4: Targeting Cookies",
      "text": "These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.",
      "words": 65,
      "hasEvidence": false,
      "reasons": [
        "Too short for a citation-ready passage (65 words; target 80-220).",
        "Missing a named source, statistic, date, percentage, report, or other evidence signal."
      ],
      "html": "<p class=\"ot-grp-desc ot-category-desc\">These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.</p>"
    },
    {
      "index": 4,
      "heading": "H4: Performance Cookies",
      "text": "These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor...",
      "words": 78,
      "hasEvidence": false,
      "reasons": [
        "Too short for a citation-ready passage (78 words; target 80-220).",
        "Missing a named source, statistic, date, percentage, report, or other evidence signal."
      ],
      "html": "<p class=\"ot-grp-desc ot-category-desc\">These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.</p>"
    },
    {
      "index": 5,
      "heading": "H4: Functional Cookies",
      "text": "These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.",
      "words": 48,
      "hasEvidence": false,
      "reasons": [
        "Too short for a citation-ready passage (48 words; target 80-220).",
        "Missing a named source, statistic, date, percentage, report, or other evidence signal."
      ],
      "html": "<p class=\"ot-grp-desc ot-category-desc\">These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.</p>"
    }
  ],
  "citableParagraphs": [],
  "score": 75,
  "weight": 18
}

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

5 image(s) are missing width/height attributes. 3 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, initial-scale=1",
  "visibleWords": 558,
  "htmlBytes": 225307,
  "imagesMissingDimensions": [
    {
      "src": "https://acuteintuitive52.com/810633.png",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img alt src=\"https://acuteintuitive52.com/810633.png\" style=\"display:none;\">"
    },
    {
      "src": "https://cdn.prod.website-files.com/68424a45023d688185720fd0/69bc0033285062a2fe5b79f5_Property%201%3DVariant3.png",
      "width": "",
      "height": "17",
      "loading": "",
      "html": "<img src=\"https://cdn.prod.website-files.com/68424a45023d688185720fd0/69bc0033285062a2fe5b79f5_Property%201%3DVariant3.png\" alt=\"Vivun\" height=\"17\">"
    },
    {
      "src": "https://cdn.cookielaw.org/logos/72eaac4e-8116-4ff9-a9af-6cacee83445d/019d496d-e87b-7cd3-b3e4-562ea3a6b9c0/ca62a761-452a-4b54-9851-9aeaa1c9c447/69bc0033285062a2fe5b79f5_Property_1=Variant3_(1).png",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img class=\"ot-bnr-logo\" src=\"https://cdn.cookielaw.org/logos/72eaac4e-8116-4ff9-a9af-6cacee83445d/019d496d-e87b-7cd3-b3e4-562ea3a6b9c0/ca62a761-452a-4b54-9851-9aeaa1c9c447/69bc0033285062a2fe5b79f5_Property_1=Variant3_(1).png\" title=\"Vivun Logo\" alt=\"Vivun Logo\">"
    },
    {
      "src": "https://cdn.cookielaw.org/logos/72eaac4e-8116-4ff9-a9af-6cacee83445d/019d6a85-8dc6-7d36-a165-3e390611990b/38cb517f-7e20-4830-8b46-d1df1f1a79cd/69bc0033ceca59a735ff39af_Property_1=Variant3_(1).png",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img alt=\"Vivun Logo\" src=\"https://cdn.cookielaw.org/logos/72eaac4e-8116-4ff9-a9af-6cacee83445d/019d6a85-8dc6-7d36-a165-3e390611990b/38cb517f-7e20-4830-8b46-d1df1f1a79cd/69bc0033ceca59a735ff39af_Property_1=Variant3_(1).png\">"
    },
    {
      "src": "https://cdn.cookielaw.org/logos/static/powered_by_logo.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img alt=\"Powered by Onetrust\" src=\"https://cdn.cookielaw.org/logos/static/powered_by_logo.svg\" title=\"Powered by OneTrust Opens in a new Tab\">"
    }
  ],
  "possibleDialogs": [
    "<div class=\"ot-sdk-container\" role=\"dialog\" aria-label=\"Privacy\"><div class=\"ot-sdk-row\"><div id=\"onetrust-group-container\" class=\"ot-sdk-twelve ot-sdk-columns\"><div id=\"onetrust-policy\"><div class=\"banner-header\"><div class=\"banner_logo\"></div><img class=\"ot-bnr-logo\" src=\"https://cdn.cookielaw.org/logos/72eaac4e-8116-4ff9-a9af-6cacee83445d/019d496d-e87b-7cd3-b3e4-562ea3a6b9c0/ca62a761-452a-4b54-9851-9aeaa1c9c447/69bc0033285062a2fe5b79f5_Property_1=Variant3_(1).png\" title=\"Vivun Logo\" alt=\"V...",
    "<div role=\"dialog\" aria-modal=\"true\" style=\"height: 100%;\" aria-label=\"Privacy Preference Center\"><!-- pc header --><div class=\"ot-pc-header\" role=\"presentation\"><!-- Header logo --><div class=\"ot-pc-logo\" role=\"img\" aria-label=\"Vivun Logo\"><img alt=\"Vivun Logo\" src=\"https://cdn.cookielaw.org/logos/72eaac4e-8116-4ff9-a9af-6cacee83445d/019d6a85-8dc6-7d36-a165-3e390611990b/38cb517f-7e20-4830-8b46-d1df1f1a79cd/69bc0033ceca59a735ff39af_Property_1=Variant3_(1).png\"></div><div class=\"ot-title-cntr\"...",
    "<section id=\"ot-fltr-modal\"><div id=\"ot-fltr-cnt\"><div id=\"ot-filter-list-header\"></div><button id=\"clear-filters-handler\">Clear</button><div class=\"ot-fltr-scrlcnt ot-pc-scrollbar\" role=\"group\" aria-labelledby=\"ot-filter-list-header\"><ul class=\"ot-fltr-opts\"><li class=\"ot-fltr-opt\"><div class=\"ot-chkbox\"><input id=\"chkbox-id\" type=\"checkbox\" class=\"category-filter-handler\"> <label for=\"chkbox-id\"><span class=\"ot-label-txt\">checkbox label</span></label> <span class=\"ot-label-status\">label</sp..."
  ],
  "score": 70,
  "weight": 10
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Answer block readiness

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

2 Warning

Needs attention

AIO: Answer block readiness

Warning
01

Issue

7 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": 8,
  "passing": 1,
  "failing": [
    {
      "heading": "Privacy Preference Center",
      "headingHtml": "<h2 id=\"ot-pc-title\" aria-hidden=\"false\">Privacy Preference Center</h2>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Privacy Preference Center",
      "headingHtml": "<h2 id=\"ot-pc-title-mobile\" aria-hidden=\"true\">Privacy Preference Center</h2>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Your Privacy",
      "headingHtml": "<h3 id=\"ot-pvcy-txt\">Your Privacy</h3>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Strictly Necessary Cookies",
      "headingHtml": "<h3 id=\"ot-header-id-C0001\">Strictly Necessary Cookies</h3>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Targeting Cookies",
      "headingHtml": "<h3 id=\"ot-header-id-C0004\">Targeting Cookies</h3>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Performance Cookies",
      "headingHtml": "<h3 id=\"ot-header-id-C0002\">Performance Cookies</h3>",
      "firstParagraph": "",
      "paragraphHtml": "",
      "words": 0,
      "direct": false,
      "issue": "No paragraph follows this heading."
    },
    {
      "heading": "Cookie List",
      "headingHtml": "<h3>Cookie List</h3>",
      "firstParagraph": "",
      "paragraphHtml": "<p role=\"status\" class=\"ot-scrn-rdr\"></p>",
      "words": 0,
      "direct": false,
      "issue": "First paragraph is 0 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, 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": [
    {
      "text": "Privacy Preference Center",
      "html": "<h2 id=\"ot-pc-title\" aria-hidden=\"false\">Privacy Preference Center</h2>"
    },
    {
      "text": "Privacy Preference Center",
      "html": "<h2 id=\"ot-pc-title-mobile\" aria-hidden=\"true\">Privacy Preference Center</h2>"
    }
  ],
  "expected": [
    {
      "id": "what",
      "label": "What is Vivun — AI Teammates Built on Structured Reas...?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Vivun — AI Teammates Built on Structured Reas... work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Vivun — AI Teammates Built on Structured Reas...?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Vivun — AI Teammates Built on Structured Reas... free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Vivun — AI Teammates Built on Structured Reas... compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is Vivun — AI Teammates Built on Structured Reas...?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Vivun — AI Teammates Built on Structured Reas... work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Vivun — AI Teammates Built on Structured Reas...?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Vivun — AI Teammates Built on Structured Reas... free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Vivun — AI Teammates Built on Structured Reas... compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 8
}

Agent Ease of UseAPIEmerging recommendation

AI context endpoint

AI context endpoint is informational for this page.

Informational

Needs attention

AI context endpoint

Informational
01

Issue

AI context endpoint is informational for this page.

02

Why it matters

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

Check name

AI context endpoint

Score

100/100

Status

informational

Category

API

Maturity

Emerging recommendation

Goal

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

Result

AI context endpoint is informational for this page.

Validation steps

  1. Fetch to find resource

    AI context endpoint was not found at the expected path.

Evidence
{
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "informational",
      "evidence": {
        "checked": [
          {
            "path": "/api/ai/context",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 25509
          },
          {
            "path": "/api/context",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 25509
          },
          {
            "path": "/context",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 25509
          }
        ]
      },
      "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": [
    {
      "text": "Privacy Preference Center",
      "html": "<h2 id=\"ot-pc-title\" aria-hidden=\"false\">Privacy Preference Center</h2>"
    },
    {
      "text": "Privacy Preference Center",
      "html": "<h2 id=\"ot-pc-title-mobile\" aria-hidden=\"true\">Privacy Preference Center</h2>"
    }
  ],
  "expected": [
    {
      "id": "what",
      "label": "What is Vivun — AI Teammates Built on Structured Reas...?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Vivun — AI Teammates Built on Structured Reas... work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Vivun — AI Teammates Built on Structured Reas...?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Vivun — AI Teammates Built on Structured Reas... free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Vivun — AI Teammates Built on Structured Reas... compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is Vivun — AI Teammates Built on Structured Reas...?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Vivun — AI Teammates Built on Structured Reas... work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Vivun — AI Teammates Built on Structured Reas...?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Vivun — AI Teammates Built on Structured Reas... free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Vivun — AI Teammates Built on Structured Reas... compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 4
}

Agent Ease of UseAuthEmerging recommendation

Auth.md Agent Registration

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

Informational

Needs attention

Auth.md Agent Registration

Informational
01

Issue

auth.md response did not match the expected agent registration shape. Content-Type "text/html; charset=utf-8" is not Markdown or text/plain; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; 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; charset=utf-8" 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; charset=utf-8",
        "length": 25509,
        "validation": {
          "valid": false,
          "issue": "auth.md response did not match the expected agent registration shape. Content-Type \"text/html; charset=utf-8\" is not Markdown or text/plain; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; missing supported identity type language; missing credential type language.",
          "compatibleContentType": false,
          "contentLength": 23219,
          "hasRegisterInstructions": true,
          "hasProtectedResourceLink": false,
          "hasAuthorizationServerLink": false,
          "mentionsIdentity": false,
          "mentionsCredential": false,
          "links": [
            "https://webflow.com",
            "https://cdn.prod.website-files.com\"",
            "/title",
            "https://cdn.prod.website-files.com/68424a45023d688185720fd0/css/vivun-79bc1c-06bf2c351ecd-68e8df42bf396.webflow.shared.b3424035b.css\"",
            "/css",
            "/fwKyuwTU/m",
            "https://fonts.googleapis.com\"",
            "https://fonts.gstatic.com\"",
            "https://ajax.googleapis.com/ajax/libs/webfont/1.6.26/webfont.js\"",
            "/javascript"
          ],
          "rawExcerpt": "<!DOCTYPE html><!-- This site was created in Webflow. https://webflow.com --><!-- Last Published: Wed Jun 10 2026 14:29:48 GMT+0000 (Coordinated Universal Time) --><html data-wf-domain=\"www.vivun.com\" data-wf-page=\"68c0b333272bed3cd2f94fa9\" data-wf-site=\"68424a45023d688185720fd0\" lang=\"en\"><head><meta charset=\"utf-8\"/><link href=\"https://cdn.prod.website-files.com\" rel=\"preconnect\" crossorigin=\"anonymous\"/><title>Not Found</title><meta content=\"Not Found\" property=\"og:title\"/><meta content=\"Not Found\" name=\"twitter:title\"/><meta content=\"width=device-width, initial-scale=1\" name=\"viewport\"/><meta content=\"google-site-verification=j6X4NU3RdZbkFomKC4AI1pJRdCXMV2FFyy1ZDCJaxL8\" name=\"google-site-verification\"/><meta content=\"Webflow\" name=\"generator\"/><link href=\"https://cdn.prod.website-files"
        }
      },
      "issue": "auth.md response did not match the expected agent registration shape. Content-Type \"text/html; charset=utf-8\" is not Markdown or text/plain; missing /.well-known/oauth-protected-resource link; missing /.well-known/oauth-authorization-server link; 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; charset=utf-8",
        "length": 88,
        "text": "<!DOCTYPE html>\n<html>\n  <body>\n    <p>Invalid .well-known request</p>\n  </body>\n</html>"
      },
      "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; charset=utf-8",
          "length": 88,
          "text": "<!DOCTYPE html>\n<html>\n  <body>\n    <p>Invalid .well-known request</p>\n  </body>\n</html>"
        }
      },
      "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": 3,
    "signals": [
      {
        "source": "link:href",
        "weight": 3,
        "match": "auth link"
      }
    ]
  },
  "resourceFetchSucceeded": false
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Q&A and FAQ opportunities

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

Informational

Needs attention

GEO: Q&A and FAQ opportunities

Informational
01

Issue

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

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: Q&A and FAQ opportunities

Score

75/100

Status

informational

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

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

Evidence
{
  "h2Count": 2,
  "questionH2s": 0,
  "hasFaq": false,
  "nonQuestionH2s": [
    {
      "index": 1,
      "text": "Privacy Preference Center",
      "isQuestion": false,
      "html": "<h2 id=\"ot-pc-title\" aria-hidden=\"false\">Privacy Preference Center</h2>"
    },
    {
      "index": 2,
      "text": "Privacy Preference Center",
      "isQuestion": false,
      "html": "<h2 id=\"ot-pc-title-mobile\" aria-hidden=\"true\">Privacy Preference Center</h2>"
    }
  ],
  "score": 75,
  "weight": 4
}

AI DiscoverabilityDiscoverabilityEstablished

IndexNow key

IndexNow key is informational for this page.

Informational

Needs attention

IndexNow key

Informational
01

Issue

IndexNow key is informational for this page.

02

Why it matters

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

Check name

IndexNow key

Score

100/100

Status

informational

Category

Discoverability

Maturity

Established

Goal

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

Result

IndexNow key is informational for this page.

Validation steps

  1. Find advertised IndexNow key location

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

  2. Fetch and validate IndexNow key file

    No discoverable IndexNow key file was found.

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

Agent Ease of UseAuthEstablished

OAuth / OIDC discovery

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

Informational

Needs attention

OAuth / OIDC discovery

Informational
01

Issue

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

02

Why it matters

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

Check name

OAuth / OIDC discovery

Score

0/100

Status

informational

Category

Auth

Maturity

Established

Goal

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

Result

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

Validation steps

  1. Fetch to find resource

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

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/openid-configuration",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 88
          },
          {
            "path": "/.well-known/oauth-authorization-server",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 88
          }
        ]
      },
      "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": 3,
    "signals": [
      {
        "source": "link:href",
        "weight": 3,
        "match": "auth link"
      }
    ]
  },
  "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; charset=utf-8"
      },
      "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>\n<html>\n  <body>\n    <p>Invalid .well-known request</p>\n  </body>\n</html>"
      },
      "issue": "Response is not valid JSON.",
      "howToFix": "Publish resource and authorization_servers as absolute URLs."
    },
    {
      "id": "resource-identity",
      "title": "Validate protected resource identity",
      "status": "fail",
      "evidence": {
        "expectedResource": "https://www.vivun.com"
      },
      "issue": "Protected resource metadata `resource` did not match the resource identifier used to retrieve it.",
      "howToFix": "Set `resource` to the origin/resource identifier represented by /.well-known/oauth-protected-resource."
    },
    {
      "id": "protected-route-challenge",
      "title": "Probe protected API Bearer challenge",
      "status": "informational",
      "evidence": {
        "checked": [
          {
            "path": "/api/admin/scans",
            "statusCode": 404,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://www.vivun.com/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "resourceMatchesRequestContext": true
          },
          {
            "path": "/api/admin/summary",
            "statusCode": 404,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://www.vivun.com/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "resourceMatchesRequestContext": true
          },
          {
            "path": "/api/scans",
            "statusCode": 404,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://www.vivun.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": 3,
    "signals": [
      {
        "source": "link:href",
        "weight": 3,
        "match": "auth link"
      }
    ]
  },
  "resourceFetchSucceeded": false
}

Performance and AccessibilityPerformanceBrowser audit

Image optimization

13 Fail

Check name

Image optimization

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

Review the grouped image optimization checks and improve the failing sub-checks listed in evidence.

Evidence
{
  "checks": [
    {
      "id": "image-aspect-ratio",
      "title": "Displays images with incorrect aspect ratio",
      "score": 0
    }
  ]
}

Performance and AccessibilityPerformanceBrowser audit

Legacy JavaScript

13 Fail

Check name

Legacy JavaScript

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 39 KiB

Fix guidance

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers. [Learn why most sites can deploy ES6+ code without transpiling](https://developer.chrome.com/docs/performance/insights/legacy-javascript)

Evidence
{
  "displayValue": "Est savings of 39 KiB",
  "description": "Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers. [Learn why most sites can deploy ES6+ code without transpiling](https://developer.chrome.com/docs/performance/insights/legacy-javascript)"
}

Performance and AccessibilityPerformanceBrowser audit

Reduce unused JavaScript

13 Fail

Check name

Reduce unused JavaScript

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 789 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 789 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": 290
}

Performance and AccessibilityPerformanceBrowser audit

Render-blocking requests

13 Fail

Check name

Render-blocking requests

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 1,630 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 1,630 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

Font display

6 Warning

Check name

Font display

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 10 ms

Fix guidance

Consider setting [font-display](https://developer.chrome.com/docs/performance/insights/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).

Evidence
{
  "displayValue": "Est savings of 10 ms",
  "description": "Consider setting [font-display](https://developer.chrome.com/docs/performance/insights/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks)."
}

Performance and AccessibilityPerformanceBrowser audit

Minify JavaScript

6 Warning

Check name

Minify JavaScript

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 76 KiB

Fix guidance

Minifying JavaScript files can reduce payload sizes and script parse time. [Learn how to minify JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unminified-javascript/).

Evidence
{
  "displayValue": "Est savings of 76 KiB",
  "description": "Minifying JavaScript files can reduce payload sizes and script parse time. [Learn how to minify JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unminified-javascript/).",
  "numericValue": 0
}

Performance and AccessibilityPerformanceBrowser audit

Use efficient cache lifetimes

6 Warning

Check name

Use efficient cache lifetimes

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 367 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 367 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)."
}

Performance and AccessibilityPerformanceBrowser audit

Loading performance

5 Fail

Check name

Loading performance

Score

62/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

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

Evidence
{
  "checks": [
    {
      "id": "interactive",
      "title": "Time to Interactive",
      "score": 47,
      "displayValue": "4.6 s",
      "numericValue": 4634.10475409579
    },
    {
      "id": "network-rtt",
      "title": "Network Round Trip Times",
      "score": 100,
      "displayValue": "40 ms",
      "numericValue": 37.67796
    },
    {
      "id": "max-potential-fid",
      "title": "Max Potential First Input Delay",
      "score": 86,
      "displayValue": "140 ms",
      "numericValue": 141
    },
    {
      "id": "total-blocking-time",
      "title": "Total Blocking Time",
      "score": 35,
      "displayValue": "440 ms",
      "numericValue": 444.5
    },
    {
      "id": "first-contentful-paint",
      "title": "First Contentful Paint",
      "score": 64,
      "displayValue": "1.4 s",
      "numericValue": 1362.6960141578886
    },
    {
      "id": "largest-contentful-paint",
      "title": "Largest Contentful Paint",
      "score": 53,
      "displayValue": "2.3 s",
      "numericValue": 2282.9374642186367
    },
    {
      "id": "speed-index",
      "title": "Speed Index",
      "score": 14,
      "displayValue": "3.6 s",
      "numericValue": 3624.2209520651104
    },
    {
      "id": "server-response-time",
      "title": "Initial server response time was short",
      "score": 100,
      "displayValue": "Root document took 20 ms",
      "numericValue": 20
    }
  ]
}

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