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

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability47%Agent Easeof Use54%Security& Trust84%GEO, AIO, AEO46%SEO83%Performance& Accessibility56%
  • AI Discoverability 47 out of 100
  • Agent Ease of Use 54 out of 100
  • Security & Trust 84 out of 100
  • GEO, AIO and AEO 46 out of 100
  • SEO 83 out of 100
  • Performance and Accessibility 56 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Experiment favicon

Experiment

Experiment is an online platform for funding and sharing scientific discoveries. Push the boundaries of knowledge in biology, chemistry, medicine, physics, computer science, paleontology, economics, engineering, neuroscience, and more.

Next step

Turn this report into a fix workflow

10 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
47
Priority fix16286View details
Discoverability
48
Priority fix550View details
Content Readiness
20
Priority fix7233View details
Bot Access Control
69
Needs work403
Agent Ease of Use
54
Needs work1012
API
67
Needs work101
Auth
50
Needs work003
MCP
50
Needs work003
Skill Discovery
50
Needs work005
GEO, AIO and AEO
46
Priority fix567View details
GEO Readiness
36
Priority fix132View details
AIO Readiness
59
Needs work213View details
AEO Readiness
42
Priority fix222View details
SEO
83
Mostly ready720View details
SEO
83
Mostly ready720View details
Security & Trust
84
Mostly ready2011View details
Security & Trust
84
Mostly ready2011View details
Performance and Accessibility
56
Needs work1780View details
Performance
41
Priority fix1060View details
Accessibility
84
Mostly ready720View details

Prioritized recommendations

Issues ranked by score impact

48 items need attention

AI DiscoverabilityDiscoverabilityEstablished

Link headers

Link headers failed at "Find useful Link headers".

50 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 log2 steps · 9 lines
Find useful Link headers [fail]! No useful agent discovery Link headers were found.INFOFind useful Link headersINFOParse response Link header linkCount=0FAILCompare registered agent-useful relation count actual=0 expected="> 0"FAILCompare community relation count actual=0 expected="accepted as weaker evidence"FAILNo useful agent discovery Link headers were found.Fetch same-origin Link header targets [fail]! Link headers did not expose any same-origin targets to validate.INFOFetch same-origin Link header targetsINFOFetch same-origin Link header targets and record external skipsFAILCompare same-origin Link target failures actual=1 expected=0FAILLink headers did not expose any same-origin targets to validate.

Agent Ease of UseAPIEstablished

OpenAPI discovery

OpenAPI discovery has a validation warning at "Discover OpenAPI document".

33 Warning

Needs attention

OpenAPI discovery

Warning
01

Issue

The site appears to publish or document a public API, but no OpenAPI or Swagger document was found.

02

Why it matters

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

Check name

OpenAPI discovery

Score

67/100

Status

warning

Category

API

Maturity

Established

Goal

Publish a valid OpenAPI or Swagger document for public API discovery when this origin exposes public APIs.

Result

OpenAPI discovery has a validation warning at "Discover OpenAPI document".

Validation steps

  1. Discover OpenAPI document

    The site appears to publish or document a public API, but no OpenAPI or Swagger document was found.

Evidence log1 step · 16 lines
Discover OpenAPI document [warning]! The site appears to publish or document a public API, but no OpenAPI or Swagger document was found.INFODiscover OpenAPI document status="warning"INFOBuild OpenAPI candidate list conventionalPaths=19 candidateCount=19 sources={"conventional-path":19}INFOFetch OpenAPI candidate path="/openapi.json" source="conventional-path" statusCode=404 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/openapi.yaml" source="conventional-path" statusCode=404 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/swagger.json" source="conventional-path" statusCode=404 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/swagger.yaml" source="conventional-path" statusCode=404 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/api/openapi.json" source="conventional-path" statusCode=404 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/api/openapi.yaml" source="conventional-path" statusCode=404 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/api/swagger.json" source="conventional-path" statusCode=404 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/api/swagger.yaml" source="conventional-path" statusCode=404 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/docs/openapi.json" source="conventional-path" statusCode=404 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/docs/openapi.yaml" source="conventional-path" statusCode=404 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/api-docs" source="conventional-path" statusCode=404 contentType="text/html; charset=UTF-8"INFOFetch OpenAPI candidate path="/v3/api-docs" source="conventional-path" statusCode=404 contentType="text/html; charset=UTF-8"WARNSelect a usable OpenAPI candidate actual="none" expected="same-origin candidate with a parseable OpenAPI or Swagger document"WARNThe site appears to publish or document a public API, but no OpenAPI or Swagger document was found.

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Find enforcing CSP delivery".

30 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

Applicable HTML response is missing an enforcing Content-Security-Policy header.

02

Why it matters

Content Security Policy reduces the impact of injection bugs by limiting where scripts, styles, frames, forms, and other browser resources can load or execute.

Check name

Content-Security-Policy

Score

40/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Constrain browser resource loading and script execution with an enforcing Content-Security-Policy header.

Result

Content-Security-Policy failed at "Find enforcing CSP delivery".

Validation steps

  1. Find enforcing CSP delivery

    Applicable HTML response is missing an enforcing Content-Security-Policy header.

Evidence log1 step · 4 lines
Find enforcing CSP delivery [fail]! Applicable HTML response is missing an enforcing Content-Security-Policy header.INFOFind enforcing CSP deliveryINFORead CSP delivery headers enforcingHeader="missing" reportOnlyHeader="missing" metaPolicyCount=0 legacyHeadersPresent=[]FAILRequire enforcing Content-Security-Policy header actual="missing" expected="present" issue="Applicable HTML response is missing an enforcing Content-Security-Policy header."FAILApplicable HTML response is missing an enforcing Content-Security-Policy header.

AI DiscoverabilityDiscoverabilityEstablished

Sitemap

Sitemap failed at "Parse sitemap".

28 Fail

Needs attention

Sitemap

Failed check
01

Issue

Fetched sitemap content was not a valid sitemap with absolute HTTP(S) URL entries.

02

Why it matters

Sitemaps help crawlers and agents discover canonical URLs, update timestamps, and deeper content that may not be obvious from homepage navigation alone.

Check name

Sitemap

Score

45/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Publish a standards-aligned sitemap or sitemap index at a discoverable URL.

Result

Sitemap failed at "Parse sitemap".

Validation steps

  1. Parse sitemap

    Fetched sitemap content was not a valid sitemap with absolute HTTP(S) URL entries.

  2. Validate sitemap field quality

    No valid sitemap was available for field-quality validation.

  3. Validate URL scope

    No valid sitemap was available for URL scope validation.

Evidence log3 steps · 10 lines
Parse sitemap [fail]! Fetched sitemap content was not a valid sitemap with absolute HTTP(S) URL entries.INFOParse sitemapINFOInspecting fetched sitemap content url="http://sitemap.experiment.com/index.xml.gz" contentType="application/gzip" statusCode=200FAILCheck sitemap contains at least one URL entry or child sitemap entry actual=0 expected="> 0"PASSCheck loc values are absolute HTTP(S) URLs actual=0 expected=0 invalidLocs=[]FAILFetched content was not a valid sitemap format="unknown"Validate sitemap field quality [fail]! No valid sitemap was available for field-quality validation.INFOValidate sitemap field qualitySKIPSkipped field-quality checks because no valid sitemap was availableValidate URL scope [fail]! No valid sitemap was available for URL scope validation.INFOValidate URL scope origin="https://experiment.com"INFOChecking listed URLs against the scanned origin hostSKIPSkipped URL-scope checks because no valid sitemap was available

Agent Ease of UseMCPEmerging recommendation

MCP Server Card

MCP Server Card has a validation warning at "Discover MCP server card".

25 Warning

Needs attention

MCP Server Card

Warning
01

Issue

No MCP server card was found at current, transitional, or linked discovery paths.

02

Why it matters

MCP server cards give agents a stable, public pre-connection discovery surface for server identity, remote transports, protocol compatibility, and safe routing without guessing endpoints.

Check name

MCP Server Card

Score

50/100

Status

warning

Category

MCP

Maturity

Emerging recommendation

Goal

Publish an MCP Server Card that helps agents discover remote MCP server transports before opening a session.

Result

MCP Server Card has a validation warning at "Discover MCP server card".

Validation steps

  1. Discover MCP server card

    No MCP server card was found at current, transitional, or linked discovery paths.

Evidence log1 step · 14 lines
Discover MCP server card [warning]! No MCP server card was found at current, transitional, or linked discovery paths.INFODiscover MCP server card candidateCount=5INFOBuild MCP server-card candidate list currentPath="/.well-known/mcp-server-card" transitionalPaths=["/.well-known/mcp/server-card.json","/.well-known/mcp/server-cards.json","/mcp.json","/.well-known/mcp.json"] linkedPaths=[]PASSCheck whether page claims MCP support actual=false expected="true only when HTML or Link headers mention MCP" textMatches=[] headerLinkCount=0INFOTrying to fetch /.well-known/mcp-server-card url="https://experiment.com/.well-known/mcp-server-card" source="current"FAIL/.well-known/mcp-server-card did not return a usable server card statusCode=404 contentType="text/html; charset=UTF-8"INFOTrying to fetch /.well-known/mcp/server-card.json url="https://experiment.com/.well-known/mcp/server-card.json" source="transitional"FAIL/.well-known/mcp/server-card.json did not return a usable server card statusCode=404 contentType="text/html; charset=UTF-8"INFOTrying to fetch /.well-known/mcp/server-cards.json url="https://experiment.com/.well-known/mcp/server-cards.json" source="transitional"FAIL/.well-known/mcp/server-cards.json did not return a usable server card statusCode=404 contentType="text/html; charset=UTF-8"INFOTrying to fetch /mcp.json url="https://experiment.com/mcp.json" source="transitional"FAIL/mcp.json did not return a usable server card statusCode=404 contentType="text/html; charset=UTF-8"INFOTrying to fetch /.well-known/mcp.json url="https://experiment.com/.well-known/mcp.json" source="transitional"FAIL/.well-known/mcp.json did not return a usable server card statusCode=404 contentType="text/html; charset=UTF-8"WARNNo MCP server card was found reason="No MCP server card was found at current, transitional, or linked discovery paths."

Agent Ease of UseMCPEmerging recommendation

WebMCP

WebMCP has a validation warning at "Probe WebMCP operability".

25 Warning

Needs attention

WebMCP

Warning
01

Issue

No WebMCP surface was found to probe.

Details

02

Why it matters

WebMCP gives agents structured page and browser tool hints so they can understand actions without relying only on screen scraping.

Check name

WebMCP

Score

50/100

Status

warning

Category

MCP

Maturity

Emerging recommendation

Goal

Expose browser/page WebMCP tools and compatible static WebMCP metadata when a site wants agents to understand in-page actions.

Result

WebMCP has a validation warning at "Probe WebMCP operability".

Validation steps

  1. Detect WebMCP runtime API

    Expose current WebMCP tools through document.modelContext.registerTool(), or clearly document navigator.modelContext as a compatibility/polyfill profile.

  2. Probe WebMCP operability

    No WebMCP surface was found to probe.

    WebMCP operability findings
    • No WebMCP surface was found to probe.
    • Conventional WebMCP manifest paths were checked but did not return a valid manifest.
  3. Validate declarative WebMCP form tools

    No W3C-style declarative WebMCP form attributes were found.

  4. Validate MCP-aware HTML annotations

    No data-mcp-tool or hyphenated WebMCP compatibility annotations were found.

  5. Validate static WebMCP JSON compatibility

    No static WebMCP JSON manifest or WMCP interaction graph was found.

  6. Validate WebMCP tool metadata quality

    Use clear tool names, useful descriptions, constrained schemas, side-effect clarity, and profile-appropriate naming.

  7. Review WebMCP security and policy signals

    Remove secrets and prompt-injection text from WebMCP metadata, avoid private endpoints, and use Permissions-Policy and annotations for tool safety.

Evidence log7 steps · 32 lines
Detect WebMCP runtime API [informational]INFODetect WebMCP runtime API status="informational"INFOProbe rendered browser for WebMCP runtime objects SKIPCheck current W3C runtime API actual="not detected" expected="document.modelContext/registerTool available"INFOWebMCP evidence was recorded for context. status="informational"Probe WebMCP operability [warning]! No WebMCP surface was found to probe.INFOProbe WebMCP operability status="warning"INFORun safe WebMCP operability checks safeProbeOnly=trueWARNCheck usable WebMCP evidence actual=0 expected="at least 1 usable runtime, declarative, annotation, or static manifest signal"WARNWebMCP operability warning warning="No WebMCP surface was found to probe."WARNWebMCP operability warning warning="Conventional WebMCP manifest paths were checked but did not return a valid manifest."WARNNo WebMCP surface was found to probe.Validate declarative WebMCP form tools [informational]! No W3C-style declarative WebMCP form attributes were found.INFOValidate declarative WebMCP form tools status="informational"INFOInspect visible forms and controls for current declarative WebMCP attributes annotatedElements=0 formsWithAttributes=0 controlsWithAttributes=0SKIPValidate declarative WebMCP attribute quality actual=0 expected=0INFONo W3C-style declarative WebMCP form attributes were found. status="informational"Validate MCP-aware HTML annotations [informational]! No data-mcp-tool or hyphenated WebMCP compatibility annotations were found.INFOValidate MCP-aware HTML annotations status="informational"INFOInspect HTML for MCP compatibility annotations compatibilityAttributeCount=0 dataMcpToolCount=0 examples=[]SKIPValidate compatibility annotation quality actual=0 expected=0INFONo data-mcp-tool or hyphenated WebMCP compatibility annotations were found. status="informational"Validate static WebMCP JSON compatibility [warning]! No static WebMCP JSON manifest or WMCP interaction graph was found.INFOValidate static WebMCP JSON compatibility status="warning"INFODiscover static WebMCP manifest candidates conventionalPaths=["/.well-known/webmcp.json","/webmcp.json"] checkedCount=2 profileCounts={}INFOWebMCP manifest candidate checked source="path" path="/.well-known/webmcp.json" url="https://experiment.com/.well-known/webmcp.json" statusCode=404 contentType="text/html; charset=UTF-8"INFOWebMCP manifest candidate checked source="path" path="/webmcp.json" url="https://experiment.com/webmcp.json" statusCode=404 contentType="text/html; charset=UTF-8"WARNValidate discovered static WebMCP metadata actual={"validManifestCount":0,"invalidManifestCount":0,"toolCount":0,"wmcpActionCount":0} expected="at least 1 valid tools[] manifest or WMCP graph when static metadata is present"WARNNo static WebMCP JSON manifest or WMCP interaction graph was found.Validate WebMCP tool metadata quality [informational]INFOValidate WebMCP tool metadata quality status="informational"INFOInspect WebMCP tool names, descriptions, schemas, and safety hints toolCount=0SKIPCheck tool metadata findings actual={"issueCount":0,"warningCount":0} expected="0 issues and 0 warnings"INFOWebMCP evidence was recorded for context. status="informational"Review WebMCP security and policy signals [informational]INFOReview WebMCP security and policy signals status="informational"INFOInspect WebMCP security and policy signals permissionsPolicy="(missing)" failureCount=0 warningCount=0PASSCheck security findings actual={"failures":0,"warnings":0} expected="0 failures and 0 warnings"INFOWebMCP evidence was recorded for context. status="informational"

Agent Ease of UseAuthEmerging recommendation

Auth.md Agent Registration

Auth.md Agent Registration has a validation warning at "Warn when auth surface lacks Auth.md".

17 Warning

Needs attention

Auth.md Agent Registration

Warning
01

Issue

The site appears to support login, signup, account access, or credentials but does not publish /auth.md.

02

Why it matters

Human login and signup flows are often opaque to agents. Auth.md gives automated clients a stable registration contract instead of forcing them to scrape docs, automate browser forms, or guess credential flows.

Check name

Auth.md Agent Registration

Score

50/100

Status

warning

Category

Auth

Maturity

Emerging recommendation

Goal

Publish Auth.md v1 metadata so agents can discover how to register, claim a user, and obtain credentials.

Result

Auth.md Agent Registration has a validation warning at "Warn when auth surface lacks Auth.md".

Validation steps

  1. Warn when auth surface lacks Auth.md

    The site appears to support login, signup, account access, or credentials but does not publish /auth.md.

Evidence log1 step · 2 lines
Warn when auth surface lacks Auth.md [warning]! The site appears to support login, signup, account access, or credentials but does not publish /auth.md.INFOWarn when auth surface lacks Auth.mdWARNThe site appears to support login, signup, account access, or credentials but does not publish /auth.md.

Agent Ease of UseAuthEstablished

OAuth / OIDC discovery

OAuth / OIDC discovery has a validation warning at "Detect OAuth/OIDC applicability".

17 Warning

Needs attention

OAuth / OIDC discovery

Warning
01

Issue

Generic authentication signals were found, but no OAuth/OIDC discovery signal was detected.

02

Why it matters

OAuth and OIDC discovery let agents and API clients find authorization, token, and key endpoints programmatically instead of scraping login pages or guessing provider setup.

Check name

OAuth / OIDC discovery

Score

50/100

Status

warning

Category

Auth

Maturity

Established

Goal

Publish OAuth/OIDC discovery metadata only when the site operates or advertises a real OAuth/OIDC authorization server.

Result

OAuth / OIDC discovery has a validation warning at "Detect OAuth/OIDC applicability".

Validation steps

  1. Detect OAuth/OIDC applicability

    Generic authentication signals were found, but no OAuth/OIDC discovery signal was detected.

Evidence log1 step · 4 lines
Detect OAuth/OIDC applicability [warning]! Generic authentication signals were found, but no OAuth/OIDC discovery signal was detected.INFODetect OAuth/OIDC applicabilityINFOInspecting homepage, headers, and known auth/API signals for OAuth or OIDC claims applies=false signalsCount=0 genericAuthSignalsCount=3 checkedCount=2WARNCheck OAuth/OIDC applicability signal actual=false expected="true when metadata exists or OAuth/OIDC is claimed" checked=[{"path":"/.well-known/openid-configuration","statusCode":404,"contentType":"text/html; charset=UTF-8","length":1687},{"path":"/.well-known/oauth-authorization-server","statusCode":404,"contentType":"text/html; charset=UTF-8","length":1687}]WARNDetect OAuth/OIDC applicability completed with warnings issue="Generic authentication signals were found, but no OAuth/OIDC discovery signal was detected."

Agent Ease of UseAuthEmerging recommendation

OAuth Protected Resource

OAuth Protected Resource has a validation warning at "Detect protected-resource applicability".

17 Warning

Needs attention

OAuth Protected Resource

Warning
01

Issue

Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected.

02

Why it matters

Protected-resource metadata tells agents which API/resource is locked, which authorization servers can issue tokens for it, and how a 401 challenge maps back to the correct resource.

Check name

OAuth Protected Resource

Score

50/100

Status

warning

Category

Auth

Maturity

Emerging recommendation

Goal

Publish OAuth Protected Resource Metadata for OAuth-protected APIs and MCP resources so clients can identify the resource and its authorization servers.

Result

OAuth Protected Resource has a validation warning at "Detect protected-resource applicability".

Validation steps

  1. Detect protected-resource applicability

    Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected.

Evidence log1 step · 4 lines
Detect protected-resource applicability [warning]! Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected.INFODetect protected-resource applicabilityINFOInspecting auth headers, MCP/OAuth claims, and protected-resource hints applies=false requiresAuthorizationServers=false signalsCount=0 genericAuthSignalsCount=3 checkedCount=1WARNCheck protected-resource metadata applicability actual=false expected="true when RFC 9728 metadata exists or support is claimed" checked=[{"url":"https://experiment.com/.well-known/oauth-protected-resource","path":"/.well-known/oauth-protected-resource","source":"root-well-known","resourceIdentifier":"https://experiment.com","statusCode":404,"contentType":"text/html; charset=UTF-8","length":1687}]WARNDetect protected-resource applicability completed with warnings issue="Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected."

AI DiscoverabilityBot Access ControlEmerging recommendation

RSL license signal

No RSL declarations were found.

17 Warning

Needs attention

RSL license signal

Warning
01

Issue

No RSL declarations were found.

02

Why it matters

Really Simple Licensing is an emerging rights-expression layer for communicating content usage and licensing terms separately from robots.txt crawl permission.

Check name

RSL license signal

Score

50/100

Status

warning

Category

Bot Access Control

Maturity

Emerging recommendation

Goal

Declare machine-readable content licensing terms for compliant AI and crawler systems when the site needs them.

Result

No RSL declarations were found.

Validation steps

  1. Discover RSL declarations

    No RSL declarations were found.

Evidence log1 step · 4 lines
Discover RSL declarations [warning]! No RSL declarations were found.INFODiscover RSL declarationsINFOChecking robots.txt License records, HTTP Link rel=license headers, HTML license links, and inline RSL XML robotsFound=trueSKIPCount discovered RSL declarations actual=0 expected=">= 1 when RSL licensing terms are published" sources={}WARNNo RSL declarations were found on any supported discovery surface.

AI DiscoverabilityBot Access ControlEmerging recommendation

TDMRep declaration

No TDMRep declaration was found.

17 Warning

Needs attention

TDMRep declaration

Warning
01

Issue

No TDMRep declaration was found at /.well-known/tdmrep.json.

02

Why it matters

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

Check name

TDMRep declaration

Score

50/100

Status

warning

Category

Bot Access Control

Maturity

Emerging recommendation

Goal

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

Result

No TDMRep declaration was found.

Validation steps

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

    No TDMRep declaration was found at /.well-known/tdmrep.json.

Evidence log1 step · 4 lines
Fetch /.well-known/tdmrep.json [warning]! No TDMRep declaration was found at /.well-known/tdmrep.json.INFOFetch /.well-known/tdmrep.jsonINFORequesting origin-level TDMRep declaration at /.well-known/tdmrep.jsonWARNCompare TDMRep file response actual=404 expected="2xx with JSON array when origin-level TDMRep is published" contentType="text/html; charset=UTF-8" length=1687WARNNo TDMRep declaration was found at /.well-known/tdmrep.json. 

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

14 Fail

Needs attention

Content freshness signals

Failed check
01

Issue

Content freshness signals are incomplete: missing any valid freshness date in Last-Modified, Schema.org, Open Graph, Dublin Core, generic meta, or sitemap lastmod.

Details

02

Why it matters

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

Check name

Content freshness signals

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

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

Result

Content freshness signals is missing or incomplete.

Validation steps

  1. Validate Last-Modified header

    No valid Last-Modified HTTP header was found.

  2. Validate structured freshness dates

    No Schema.org freshness dates were found.

  3. Validate metadata freshness dates

    No Open Graph, Dublin Core, or generic meta freshness date was found.

  4. Corroborate with sitemap lastmod

    Add a sitemap entry with a valid lastmod for the canonical page URL when sitemap corroboration is useful.

Evidence log4 steps · 16 lines
Validate Last-Modified header [fail]! No valid Last-Modified HTTP header was found.INFOValidate Last-Modified headerINFOReading Last-Modified response headerFAILCheck Last-Modified header is present and parseable actual="missing" expected="valid" alternateDates=[]FAILLast-Modified header is missing or invalidValidate structured freshness dates [fail]! No Schema.org freshness dates were found.INFOValidate structured freshness datesINFOCollecting Schema.org freshness dates from JSON-LD, Microdata, and RDFaFAILCheck structured freshness date count actual=0 expected="> 0" invalidDateCount=0 formats={} alternateDates=[]FAILNo structured freshness dates foundValidate metadata freshness dates [fail]! No Open Graph, Dublin Core, or generic meta freshness date was found.INFOValidate metadata freshness datesINFOCollecting Open Graph, Dublin Core, and generic meta freshness datesFAILCheck metadata freshness date count actual=0 expected="> 0" metaDateCount=0 invalidDateCount=0 alternateDates=[]FAILNo metadata freshness dates foundCorroborate with sitemap lastmod [warning]INFOCorroborate with sitemap lastmodINFODiscovering sitemap candidates and matching the scanned page URL candidateCount=2 attempts=2WARNCheck matching sitemap lastmod actual="no match" expected="valid match when available" robotsStatusCode=200WARNNo matching sitemap lastmod found after sitemap attempts attempts=2

AI DiscoverabilityContent ReadinessEmerging recommendation

llms.txt

llms.txt failed at "Fetch root llms.txt".

14 Fail

Needs attention

llms.txt

Failed check
01

Issue

/llms.txt was not found or could not be fetched.

02

Why it matters

llms.txt is an emerging Markdown convention for giving language-model clients curated context and links before they crawl broadly. Broken, private, or low-signal links make the file much less useful even when it exists.

Check name

llms.txt

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Emerging recommendation

Goal

Publish a concise llms.txt index that helps agents discover useful public site context.

Result

llms.txt failed at "Fetch root llms.txt".

Validation steps

  1. Fetch root llms.txt

    /llms.txt was not found or could not be fetched.

  2. Inspect optional llms-full.txt

    Passed.

Evidence log2 steps · 7 lines
Fetch root llms.txt [fail]! /llms.txt was not found or could not be fetched.INFOFetch root llms.txt path="/llms.txt"INFOTrying to fetch /llms.txt url="https://experiment.com/llms.txt"FAIL/llms.txt was not found or could not be fetched statusCode=404FAILFetch root llms.txt failed reason="/llms.txt is required for this check."Inspect optional llms-full.txt [informational]INFOInspect optional llms-full.txtINFOTrying to fetch /llms-full.txt url="https://experiment.com/llms-full.txt"SKIP/llms-full.txt is not present statusCode=404

AI DiscoverabilityContent ReadinessEstablished

Organization / WebSite schema

Organization / WebSite schema is missing or incomplete.

14 Fail

Needs attention

Organization / WebSite schema

Failed check
01

Issue

No Organization or Organization subtype was found in Schema.org structured data. No WebSite entity was found in Schema.org structured data. Missing identity field(s): Organization.name, Organization.url, WebSite.name, WebSite.url. WebSite.publisher is missing. Organization schema is missing logo and sameAs or public contact evidence.

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

Content Readiness

Maturity

Established

Goal

Identify the site owner and website entity in structured data.

Result

Organization / WebSite schema is missing or incomplete.

Validation steps

  1. Organization entity

    No Organization or Organization subtype was found in Schema.org structured data.

  2. WebSite entity

    No WebSite entity was found in Schema.org structured data.

  3. Identity fields

    Missing identity field(s): Organization.name, Organization.url, WebSite.name, WebSite.url.

  4. WebSite publisher linkage

    WebSite.publisher is missing.

  5. Organization trust fields

    Organization schema is missing logo and sameAs or public contact evidence.

Evidence log5 steps · 23 lines
Organization entity [fail]! No Organization or Organization subtype was found in Schema.org structured data.INFOOrganization entityINFOLooking for Organization or Organization subtype in structured data observedTypes=[]FAILCheck Organization entity presence actual=false expected=true fields=[{"name":"Organization.@type","present":false},{"name":"Organization.@id","present":false},{"name":"Organization.name","present":false},{"name":"Organization.url","present":false},{"name":"Organization.logo","present":false},{"name":"Organization.sameAs","present":false}]FAILOrganization entity is missingWebSite entity [fail]! No WebSite entity was found in Schema.org structured data.INFOWebSite entityINFOLooking for WebSite entity in structured data FAILCheck WebSite entity presence actual=false expected=true fields=[{"name":"WebSite.@type","present":false},{"name":"WebSite.@id","present":false},{"name":"WebSite.name","present":false},{"name":"WebSite.url","present":false},{"name":"WebSite.publisher.@id","present":false},{"name":"WebSite.publisher.name","present":false},{"name":"WebSite.publisher.url","present":false}]FAILWebSite entity is missingIdentity fields [fail]! Missing identity field(s): Organization.name, Organization.url, WebSite.name, WebSite.url.INFOIdentity fieldsINFOChecking Organization and WebSite name/url fields FAILCheck required identity fields actual=0 expected=4 missing=["Organization.name","Organization.url","WebSite.name","WebSite.url"] organizationFields=[{"name":"Organization.@type","present":false},{"name":"Organization.@id","present":false},{"name":"Organization.name","present":false},{"name":"Organization.url","present":false},{"name":"Organization.logo","present":false},{"name":"Organization.sameAs","present":false}] websiteFields=[{"name":"WebSite.@type","present":false},{"name":"WebSite.@id","present":false},{"name":"WebSite.name","present":false},{"name":"WebSite.url","present":false},{"name":"WebSite.publisher.@id","present":false},{"name":"WebSite.publisher.name","present":false},{"name":"WebSite.publisher.url","present":false}]WARNCheck identity URLs match scanned origin actual={"organizationUrlMatchesOrigin":false,"websiteUrlMatchesOrigin":false} expected={"organizationUrlMatchesOrigin":true,"websiteUrlMatchesOrigin":true}FAILIdentity fields are missing missing=["Organization.name","Organization.url","WebSite.name","WebSite.url"]WebSite publisher linkage [fail]! WebSite.publisher is missing.INFOWebSite publisher linkageINFOChecking whether WebSite.publisher points to the Organization entity FAILCheck publisher presence actual=false expected=true publisher={"present":false,"matchesOrganization":false} website={} organization={}FAILCheck publisher matches Organization actual=false expected=trueFAILWebSite publisher is missingOrganization trust fields [fail]! Organization schema is missing logo and sameAs or public contact evidence.INFOOrganization trust fieldsINFOChecking logo, sameAs, and public contact evidence FAILCheck logo presence actual=false expected=true fields=[{"name":"Organization.logo","present":false},{"name":"Organization.sameAs","present":false},{"name":"Organization.contactPoint","present":false},{"name":"Organization.telephone","present":false},{"name":"Organization.email","present":false},{"name":"Organization.address","present":false}]FAILCheck sameAs or contact evidence actual=0 expected=">= 1" sameAsCount=0 contactSignalCount=0 fields=[{"name":"Organization.logo","present":false},{"name":"Organization.sameAs","present":false},{"name":"Organization.contactPoint","present":false},{"name":"Organization.telephone","present":false},{"name":"Organization.email","present":false},{"name":"Organization.address","present":false}]FAILOrganization trust fields are missing

AI DiscoverabilityContent ReadinessEstablished

Semantic HTML

Semantic HTML is partially implemented.

13 Warning

Needs attention

Semantic HTML

Warning
01

Issue

Semantic HTML is incomplete: expected exactly one visible main landmark, found 0; skipped or empty headings; 132 links missing accessible names; 1 links are not crawlable; 1 controls missing accessible names; 2 form controls missing labels; 0/1 applicable personal-data inputs have valid autocomplete attributes (1 missing); 68 images missing alt attributes.

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

8/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

Expose readable page structure through semantic HTML and accessible controls.

Result

Semantic HTML is partially implemented.

Validation steps

  1. Page landmarks

    Expected exactly one visible main landmark; found 0.

  2. Heading structure

    Headings skip levels or include empty heading elements.

  3. Links

    132 links are missing accessible names.

  4. Buttons and interactive controls

    1 button controls are missing accessible names.

  5. Form labels and autocomplete

    2 user-fillable form controls are missing labels.

  6. Image text alternatives

    68 images are missing alt attributes.

Evidence log6 steps · 18 lines
Page landmarks [fail]! Expected exactly one visible main landmark; found 0.INFOPage landmarksFAILCheck page landmarks evidence actual={"counts":{"main":0,"roleMain":0,"nav":1,"roleNavigation":0,"header":1,"roleBanner":0,"footer":1,"pageFooter":1,"roleContentinfo":0},"main":false} expected="semantic HTML evidence for this step"FAILPage landmarks failed issue="Expected exactly one visible main landmark; found 0."Heading structure [fail]! Headings skip levels or include empty heading elements.INFOHeading structureFAILCheck heading structure evidence actual={"counts":{"h1":1,"visibleH1":1,"headings":60,"emptyHeadings":1},"meaningfulH1":true} expected="semantic HTML evidence for this step"FAILHeading structure failed issue="Headings skip levels or include empty heading elements."Links [fail]! 132 links are missing accessible names.INFOLinksFAILCheck links evidence actual={"counts":{"links":284,"inaccessibleLinks":132,"nonCrawlableLinks":1,"genericLinks":0},"accessibleLinks":false} expected="semantic HTML evidence for this step"FAILLinks failed issue="132 links are missing accessible names."Buttons and interactive controls [fail]! 1 button controls are missing accessible names.INFOButtons and interactive controlsFAILCheck buttons and interactive controls evidence actual={"counts":{"buttons":12,"inaccessibleButtons":1},"accessibleButtons":false} expected="links, buttons, and form controls expose accessible names"FAILButtons and interactive controls failed issue="1 button controls are missing accessible names."Form labels and autocomplete [fail]! 2 user-fillable form controls are missing labels.INFOForm labels and autocompleteFAILCheck form labels and autocomplete evidence actual={"counts":{"formControls":2,"unlabeledFormControls":2,"autocompleteInputs":1,"inputsWithAutocomplete":0,"missingAutocompleteInputs":1},"formLabelCoverage":false} expected="semantic HTML evidence for this step"FAILForm labels and autocomplete failed issue="2 user-fillable form controls are missing labels."Image text alternatives [fail]! 68 images are missing alt attributes.INFOImage text alternativesFAILCheck image text alternatives evidence actual={"counts":{"images":103,"imagesWithAlt":35,"imageAltIssues":0},"imageAltCoverage":false} expected="semantic HTML evidence for this step"FAILImage text alternatives failed issue="68 images are missing alt attributes."

AI DiscoverabilityContent ReadinessEstablished

Markdown negotiation

Markdown negotiation is missing or incomplete.

13 Fail

Needs attention

Markdown negotiation

Failed check
01

Issue

Best candidate returned Content-Type "text/html; charset=utf-8" instead of text/markdown.

02

Why it matters

Markdown representations give agents a cleaner page form while preserving normal HTML for browsers and cache-safe representation handling.

Check name

Markdown negotiation

Score

10/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose a useful Markdown representation through negotiation or an explicit alternate URL.

Result

Markdown negotiation is missing or incomplete.

Validation steps

  1. Markdown representation

    No usable Markdown representation was found through negotiation, advertised alternates, or conservative .md mirror checks.

  2. Same-URL negotiation

    Same-URL Accept: text/markdown did not return a valid Markdown representation.

  3. Markdown format validation

    Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation.

  4. Advertised Markdown alternate

    No Link or HTML rel=alternate text/markdown URL was advertised.

  5. Conventional .md mirror

    Conventional .md mirror candidates did not return valid Markdown.

Evidence log5 steps · 15 lines
Markdown representation [fail]! No usable Markdown representation was found through negotiation, advertised alternates, or conservative .md mirror checks.INFOMarkdown representationFAILCheck usable Markdown representation was selected actual={"source":"negotiated","url":"https://experiment.com/","statusCode":200,"contentType":"text/html; charset=utf-8","mediaType":"text/html","vary":"Accept, Accept-Encoding","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"pass","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"html-heavy","hasHeading":false,"headingCount":0,"wordCount":7995,"features":{"markdownLinks":0,"referenceLinks":0,"listItems":0,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":1393,"jsxOrMdxSignals":0},"issues":["missing-heading","raw-html-heavy","plain-text-like"],"excerpt":"<!DOCTYPE html><html lang=\"en-us\"><link rel=\"stylesheet\" href=\"https://d3t9s8cdqyboc5.cloudfront.net/assets/nucleus/print-f246294df2f9b158c0f42e692e1a3d20bd14f8e3d7da1e189ac6d3547e7e30d1.css\" media=\"print\" /><link rel=\"stylesheet\" href=\"htt","issue":"Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation."}} expected="negotiated, advertised alternate, or conventional mirror" selected={"source":"negotiated","url":"https://experiment.com/","statusCode":200,"contentType":"text/html; charset=utf-8","mediaType":"text/html","vary":"Accept, Accept-Encoding","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"pass","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"html-heavy","hasHeading":false,"headingCount":0,"wordCount":7995,"features":{"markdownLinks":0,"referenceLinks":0,"listItems":0,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":1393,"jsxOrMdxSignals":0},"issues":["missing-heading","raw-html-heavy","plain-text-like"],"excerpt":"<!DOCTYPE html><html lang=\"en-us\"><link rel=\"stylesheet\" href=\"https://d3t9s8cdqyboc5.cloudfront.net/assets/nucleus/print-f246294df2f9b158c0f42e692e1a3d20bd14f8e3d7da1e189ac6d3547e7e30d1.css\" media=\"print\" /><link rel=\"stylesheet\" href=\"htt","issue":"Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation."}} candidatesChecked=2FAILMarkdown representation failed issue="No usable Markdown representation was found through negotiation, advertised alternates, or conservative .md mirror checks."Same-URL negotiation [fail]! Same-URL Accept: text/markdown did not return a valid Markdown representation.INFOSame-URL negotiationFAILCheck negotiated Markdown response actual={"statusCode":200,"mediaType":"text/html","vary":"Accept, Accept-Encoding"} expected="HTTP 2xx text/markdown with Vary: Accept" url="https://experiment.com/" statusCode=200 mediaType="text/html" vary="Accept, Accept-Encoding"FAILSame-URL negotiation failed issue="Same-URL Accept: text/markdown did not return a valid Markdown representation."Markdown format validation [fail]! Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation.INFOMarkdown format validationFAILCheck Markdown body quality actual={"valid":false,"wordCount":7995,"headingCount":0,"dialect":"html-heavy"} expected="valid Markdown with substantive text and headings" valid=false dialect="html-heavy" wordCount=7995 headingCount=0FAILMarkdown format validation failed issue="Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation."Advertised Markdown alternate [warning]! No Link or HTML rel=alternate text/markdown URL was advertised.INFOAdvertised Markdown alternateWARNCheck advertised Markdown alternate candidates actual=0 expected="> 0 when HTML advertises a Markdown alternate" advertisedUrls=[] candidateCount=0WARNAdvertised Markdown alternate has a warning issue="No Link or HTML rel=alternate text/markdown URL was advertised."Conventional .md mirror [fail]! Conventional .md mirror candidates did not return valid Markdown.INFOConventional .md mirrorFAILCheck conventional Markdown mirror candidates actual=1 expected="> 0 when a conventional mirror is discoverable" conventionalUrls=["https://experiment.com/index.html.md"] candidateCount=1FAILConventional .md mirror failed issue="Conventional .md mirror candidates did not return valid Markdown."

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

A2A Agent Card has a validation warning at "Discover A2A Agent Card".

13 Warning

Needs attention

A2A Agent Card

Warning
01

Issue

No A2A Agent Card was found at the current, legacy, or fallback discovery paths.

02

Why it matters

A2A Agent Cards provide protocol-specific discovery for agent identity, skills, input and output modes, transport bindings, capabilities, and security requirements. Legacy A2A also used /.well-known/agent.json, so scanners must classify the card shape before reporting readiness.

Check name

A2A Agent Card

Score

50/100

Status

warning

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish a version-appropriate A2A Agent Card so A2A-compatible clients can discover agent skills and invoke the declared endpoint safely.

Result

A2A Agent Card has a validation warning at "Discover A2A Agent Card".

Validation steps

  1. Discover A2A Agent Card

    No A2A Agent Card was found at the current, legacy, or fallback discovery paths.

Evidence log1 step · 8 lines
Discover A2A Agent Card [warning]! No A2A Agent Card was found at the current, legacy, or fallback discovery paths.INFODiscover A2A Agent CardINFOTry A2A discovery paths in priority order paths=["/.well-known/agent-card.json","/.well-known/agent.json","/agent-card.json","/.well-known/a2a/agent-card.json"]WARNA2A candidate path did not return a usable card path="/.well-known/agent-card.json" statusCode=404 contentType="text/html; charset=UTF-8"WARNA2A candidate path did not return a usable card path="/.well-known/agent.json" statusCode=404 contentType="text/html; charset=UTF-8"WARNA2A candidate path did not return a usable card path="/agent-card.json" statusCode=404 contentType="text/html; charset=UTF-8"WARNA2A candidate path did not return a usable card path="/.well-known/a2a/agent-card.json" statusCode=404 contentType="text/html; charset=UTF-8"WARNNo A2A Agent Card candidate was selectedWARNNo A2A Agent Card was found at the current, legacy, or fallback discovery paths.

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

Agent Skills index has a validation warning at "Discover Agent Skills index".

13 Warning

Needs attention

Agent Skills index

Warning
01

Issue

No Agent Skills discovery index was found at the canonical or legacy path.

02

Why it matters

An Agent Skills index lets agents discover task-specific instructions through a small trusted index, then verify and load only the skill artifacts they need.

Check name

Agent Skills index

Score

50/100

Status

warning

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an Agent Skills discovery index that advertises digest-pinned SKILL.md or archive artifacts.

Result

Agent Skills index has a validation warning at "Discover Agent Skills index".

Validation steps

  1. Discover Agent Skills index

    No Agent Skills discovery index was found at the canonical or legacy path.

Evidence log1 step · 5 lines
Discover Agent Skills index [warning]! No Agent Skills discovery index was found at the canonical or legacy path.INFODiscover Agent Skills indexINFOTry Agent Skills index paths in priority order paths=["/.well-known/agent-skills/index.json","/.well-known/skills/index.json"]WARNAgent Skills index candidate was not usable path="/.well-known/agent-skills/index.json" url="https://experiment.com/.well-known/agent-skills/index.json" statusCode=404WARNAgent Skills index candidate was not usable path="/.well-known/skills/index.json" url="https://experiment.com/.well-known/skills/index.json" statusCode=404WARNNo Agent Skills discovery index was found at the canonical or legacy path.

Agent Ease of UseSkill DiscoveryEmerging recommendation

agents.json

agents.json has a validation warning at "Discover agents.json".

13 Warning

Needs attention

agents.json

Warning
01

Issue

No Wildcard-style agents.json file was found.

02

Why it matters

Wildcard agents.json gives agents workflow-level context beyond plain OpenAPI, including flows, links, examples, and API action structure. It is an emerging OpenAPI-adjacent proposal, so scanners should validate the contract shape without treating it as an A2A or IETF standard.

Check name

agents.json

Score

50/100

Status

warning

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish a Wildcard-style agents.json file so agents can discover OpenAPI-backed workflows, links, examples, and authentication requirements.

Result

agents.json has a validation warning at "Discover agents.json".

Validation steps

  1. Discover agents.json

    No Wildcard-style agents.json file was found.

Evidence log1 step · 6 lines
Discover agents.json [warning]! No Wildcard-style agents.json file was found.INFODiscover agents.jsonINFOTry agents.json discovery paths in priority order paths=["/.well-known/agents.json","/agents.json"]WARNagents.json candidate path did not return a usable contract path="/.well-known/agents.json" statusCode=404 contentType="text/html; charset=UTF-8"WARNagents.json candidate path did not return a usable contract path="/agents.json" statusCode=404 contentType="text/html; charset=UTF-8"WARNNo agents.json candidate was selectedWARNNo Wildcard-style agents.json file was found.

Agent Ease of UseSkill DiscoveryEmerging recommendation

DNS-AID Agent Discovery

DNS-AID Agent Discovery has a validation warning at "Query DNS-AID records".

13 Warning

Needs attention

DNS-AID Agent Discovery

Warning
01

Issue

No DNS-AID HTTPS/SVCB records were found under _agents.

02

Why it matters

DNS-AID lets agents discover index, A2A, and other agent entrypoints before fetching HTTP metadata. HTTPS/SVCB records provide the service-binding substrate, while DNSSEC can authenticate the discovery answer when available.

Check name

DNS-AID Agent Discovery

Score

50/100

Status

warning

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish DNS-AID HTTPS/SVCB records under _agents for DNS-based agent entrypoint discovery.

Result

DNS-AID Agent Discovery has a validation warning at "Query DNS-AID records".

Validation steps

  1. Query DNS-AID records

    No DNS-AID HTTPS/SVCB records were found under _agents.

  2. Check DNSSEC authentication evidence

    DNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.

Evidence log2 steps · 23 lines
Query DNS-AID records [warning]! No DNS-AID HTTPS/SVCB records were found under _agents.INFOQuery DNS-AID recordsINFOBuild DNS-AID query names from hostname hostname="experiment.com" labels=["_index._agents.experiment.com","_a2a._agents.experiment.com"] claimedOnPage=falseWARNDNS query returned no DNS-AID answers name="_index._agents.experiment.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.experiment.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.experiment.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _index._agents.experiment.com"WARNDNS query returned no DNS-AID answers name="_a2a._agents.experiment.com" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.experiment.com" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.experiment.com" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _a2a._agents.experiment.com"WARNCompare total DNS-AID answer count actual=0 expected="> 0"WARNNo DNS-AID HTTPS/SVCB records were found under _agents.Check DNSSEC authentication evidence [warning]! DNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.INFOCheck DNSSEC authentication evidenceWARNCompare DNSSEC authenticated-data flag actual=false expected=trueWARNCompare visible DNSSEC material actual=false expected=trueWARNResolver did not confirm authenticated DNSSEC data name="_index._agents.experiment.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.experiment.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.experiment.com" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.experiment.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.experiment.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.experiment.com" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.experiment.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.experiment.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="experiment.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNDNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.

Security & TrustSecurity & TrustEstablished

Frame protection

Frame protection has a validation warning at "Validate CSP frame-ancestors".

10 Warning

Needs attention

Frame protection

Warning
01

Issue

Frame protection relies only on X-Frame-Options; CSP frame-ancestors is the modern control.

02

Why it matters

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

Check name

Frame protection

Score

81/100

Status

warning

Category

Security & Trust

Maturity

Established

Goal

Prevent unwanted framing with an enforcing CSP frame-ancestors directive or a valid X-Frame-Options fallback.

Result

Frame protection has a validation warning at "Validate CSP frame-ancestors".

Validation steps

  1. Validate CSP frame-ancestors

    Frame protection relies only on X-Frame-Options; CSP frame-ancestors is the modern control.

Evidence log1 step · 4 lines
Validate CSP frame-ancestors [warning]! Frame protection relies only on X-Frame-Options; CSP frame-ancestors is the modern control.INFOValidate CSP frame-ancestorsINFORead CSP frame-ancestors signals enforcingHeaderPresent=false reportOnlyHeaderPresent=false metaFrameAncestors=false policyCount=0 duplicateDirectives=[]WARNCompare effective frame-ancestors directive actual="missing" expected="valid restrictive enforcing frame-ancestors" issue="Frame protection relies only on X-Frame-Options; CSP frame-ancestors is the modern control."WARNFrame protection relies only on X-Frame-Options; CSP frame-ancestors is the modern control.

AI DiscoverabilityBot Access ControlInformational

Content Signal

Content Signal has a validation warning at "Validate declared usage preferences".

8 Warning

Needs attention

Content Signal

Warning
01

Issue

Declared content usage preferences are valid but partial or include unrecognized extension terms.

02

Why it matters

Content usage preference signals communicate intended downstream AI use separately from robots.txt crawl permission. They can express training and search preferences for compliant systems without replacing access-control rules.

Check name

Content Signal

Score

75/100

Status

warning

Category

Bot Access Control

Maturity

Informational

Goal

Declare AI content usage preferences when the site intentionally publishes machine-readable usage policy.

Result

Content Signal has a validation warning at "Validate declared usage preferences".

Validation steps

  1. Validate declared usage preferences

    Declared content usage preferences are valid but partial or include unrecognized extension terms.

Evidence log1 step · 5 lines
Validate declared usage preferences [warning]! Declared content usage preferences are valid but partial or include unrecognized extension terms.INFOValidate declared usage preferencesINFOParsing declared preferences into terms and values recordCount=1INFORecognized declaration formats formats=["legacy-content-signal"] sources=["robots.txt"]WARNCompare valid declarations to declared records actual=1 expected=">= 1 valid declaration with recognized preference terms" invalidRecords=[] warningRecords=[{"source":"robots.txt","directive":"Content-Signal","format":"legacy-content-signal","line":29,"preferences":["search=yes","ai-train=no"],"warnings":["Legacy Content-Signal declaration is partial; missing ai-input."]}]WARNLegacy Content-Signal declaration is partial; missing ai-input. record={"source":"robots.txt","directive":"Content-Signal","format":"legacy-content-signal","line":29,"preferences":["search=yes","ai-train=no"]}

AI DiscoverabilityContent ReadinessEstablished

Structured data

Structured data failed at "Parseability".

8 Fail

Needs attention

Structured data

Failed check
01

Issue

Detected structured data could not be parsed for: microdata.

02

Why it matters

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

Check name

Structured data

Score

42/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose machine-readable page entities and relationships through a recognized structured-data syntax.

Result

Structured data failed at "Parseability".

Validation steps

  1. Parseability

    Detected structured data could not be parsed for: microdata.

  2. Schema.org entity typing

    Structured data was detected, but no typed Schema.org entities were extracted.

  3. Page-relevant schema family

    The page has specific visible content intent, but structured data does not include a matching primary schema family.

Evidence log3 steps · 12 lines
Parseability [fail]! Detected structured data could not be parsed for: microdata.INFOParseabilityINFOChecking detected structured data for parse errors formatsFound=["microdata"]FAILCheck invalid detected formats actual=1 expected=0 invalidPresentFormats=["microdata"] parseErrors=[{"format":"microdata","error":"itemprop attributes found without an enclosing itemscope entity."}]FAILDetected structured data has fatal parse issues invalidPresentFormats=["microdata"]Schema.org entity typing [fail]! Structured data was detected, but no typed Schema.org entities were extracted.INFOSchema.org entity typingINFOExtracting typed Schema.org entities from parsed structured dataFAILCheck extracted Schema.org type count actual=0 expected="> 0" schemaTypes=[] entityCount=0FAILNo typed Schema.org entities were extractedPage-relevant schema family [fail]! The page has specific visible content intent, but structured data does not include a matching primary schema family.INFOPage-relevant schema familyINFOInferring specific page intent and comparing it with detected Schema.org typesFAILCheck schema types matching specific visible page intent actual=0 expected="> 0" inferredIntents=["qa","profile"] expectedTypes=["QAPage","FAQPage","ProfilePage","Person"] matchingTypes=[] observedTypes=[]FAILNo primary schema family matches the inferred page intent expectedTypes=["QAPage","FAQPage","ProfilePage","Person"] primaryTypes=[]

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Citable passages

GEO: Citable passages scored 0/100 and needs a fix.

7 Fail

Needs attention

GEO: Citable passages

Failed check
01

Issue

No evidence-backed, citation-length explanatory paragraph was found.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Citable passages

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: Citable passages scored 0/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first passages

AEO: Answer-first passages scored 24/100 and needs a fix.

7 Fail

Needs attention

AEO: Answer-first passages

Failed check
01

Issue

43 section(s) bury or omit a concise opening answer.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Answer-first passages

Score

24/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Answer-first passages scored 24/100 and needs a fix.

AI DiscoverabilityContent ReadinessEstablished

Author attribution

Author attribution is partially implemented.

6 Warning

Needs attention

Author attribution

Warning
01

Issue

No named author or publisher identity could be extracted.

02

Why it matters

Author attribution helps agents cite content responsibly, assess source credibility, and distinguish editorial pages from anonymous marketing copy.

Check name

Author attribution

Score

55/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

Identify content authors or publishers for trust and attribution.

Result

Author attribution is partially implemented.

Validation steps

  1. Schema.org attribution

    Schema.org attribution is incomplete or relies only on publisher/fallback evidence.

  2. Author identity quality

    No named author or publisher identity could be extracted.

Evidence log2 steps · 8 lines
Schema.org attribution [warning]! Schema.org attribution is incomplete or relies only on publisher/fallback evidence.INFOSchema.org attributionINFOChecking structured data for author, creator, and publisher contributorsWARNCheck named Schema.org author count actual=0 expected="> 0" authorCount=0 publisherCount=0 namedContributors=0 authors=[] publishers=[] formats=[]WARNSchema.org attribution is incomplete or fallback-only authorCount=0 publisherCount=0 authors=[] publishers=[]Author identity quality [fail]! No named author or publisher identity could be extracted.INFOAuthor identity qualityINFOChecking contributors for stable identity signalsFAILCheck identified contributor count actual=0 expected="> 0" namedContributors=0 identifiedContributors=[] unidentifiedContributors=[]FAILNo named contributor identity could be extracted

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Evidence and trust

AEO: Evidence and trust scored 29/100 and needs a fix.

6 Fail

Needs attention

AEO: Evidence and trust

Failed check
01

Issue

Missing answer evidence or trust signals: author, publisher, freshnessDate, sameAs, policyLinks.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Evidence and trust

Score

29/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Evidence and trust scored 29/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Source and trust signals

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

5 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

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Source and trust signals

Score

33/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Source and trust signals

GEO: Source and trust signals scored 33/100 and needs a fix.

5 Fail

Needs attention

GEO: Source and trust signals

Failed check
01

Issue

Missing source or trust signals: authorOrOwner, freshnessDate, policyLinks, entityLinks.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Source and trust signals

Score

33/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: Source and trust signals scored 33/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: AI retrieval access

GEO: AI retrieval access scored 35/100 and needs a fix.

5 Fail

Needs attention

GEO: AI retrieval access

Failed check
01

Issue

Relevant AI retrieval crawler(s) appear blocked for this URL: ClaudeBot.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: AI retrieval access

Score

35/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: AI retrieval access scored 35/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Structured extraction

GEO: Structured extraction scored 63/100 and needs improvement.

3 Warning

Needs attention

GEO: Structured extraction

Warning
01

Issue

Missing or weak extraction signals: clean heading hierarchy, summary or key takeaways, typed JSON-LD structured data.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Structured extraction

Score

63/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: Structured extraction scored 63/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Entity clarity

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

2 Warning

Needs attention

GEO: Entity clarity

Warning
01

Issue

Title/H1 terms missing from description: fund, curiosity, fuel, discovery.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Entity clarity

Score

73/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Page experience proxy

AIO: Page experience proxy scored 75/100 and needs improvement.

2 Warning

Needs attention

AIO: Page experience proxy

Warning
01

Issue

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

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Page experience proxy

Score

75/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Page experience proxy scored 75/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question and answer structure

AEO: Question and answer structure scored 82/100 and needs improvement.

2 Warning

Needs attention

AEO: Question and answer structure

Warning
01

Issue

Heading structure issues were detected.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Question and answer structure

Score

82/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Question and answer structure scored 82/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

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

1 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

Title, h1, description, and opening copy are weakly aligned.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Entity and definition clarity

Score

83/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Visible content clarity

AIO: Visible content clarity scored 82/100 and needs improvement.

1 Warning

Needs attention

AIO: Visible content clarity

Warning
01

Issue

Title, h1, description, and opening copy are weakly aligned. 43 section(s) may benefit from clearer answer-first openings. Heading outline issues were detected.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Visible content clarity

Score

82/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Visible content clarity scored 82/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Google Search eligibility

AIO: Google Search eligibility scored 85/100 and needs improvement.

1 Warning

Needs attention

AIO: Google Search eligibility

Warning
01

Issue

Canonical tag is missing.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Google Search eligibility

Score

85/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Google Search eligibility scored 85/100 and needs improvement.

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 log2 steps · 10 lines
Find advertised IndexNow key location [informational]! No IndexNow key location was advertised in HTML, Link headers, or robots.txt.INFOFind advertised IndexNow key locationINFOLook for IndexNow key hints in HTML, Link headers, and robots.txt supportedHints=["robots.txt IndexNow-Key","rel=indexnow-key","meta name=indexnow-key-location"]PASSCompare advertised key location count actual=0 expected="> 0"WARNNo IndexNow key location was advertised in HTML, Link headers, or robots.txt.Fetch and validate IndexNow key file [informational]! No discoverable IndexNow key file was found.INFOFetch and validate IndexNow key fileINFOLook for IndexNow key hints in HTML, Link headers, and robots.txt supportedHints=["robots.txt IndexNow-Key","rel=indexnow-key","meta name=indexnow-key-location"]PASSCompare advertised key location count actual=0 expected="> 0"INFOFetch each advertised same-origin key file and validate filename/body matchFAILCompare valid IndexNow key file count actual=0 expected="> 0"WARNNo discoverable IndexNow key file was found.

Performance and AccessibilityAccessibilityBrowser audit

Heading elements are not in a sequentially-descending order

50 Fail

Check name

Heading elements are not in a sequentially-descending order

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

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

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

Performance and AccessibilityAccessibilityBrowser audit

Image elements do not have `[alt]` attributes

50 Fail

Check name

Image elements do not have `[alt]` attributes

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. [Learn more about the `alt` attribute](https://dequeuniversity.com/rules/axe/4.11/image-alt).

Evidence
{
  "description": "Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. [Learn more about the `alt` attribute](https://dequeuniversity.com/rules/axe/4.11/image-alt)."
}

SEOSEOBrowser audit

Image elements do not have `[alt]` attributes

50 Fail

Check name

Image elements do not have `[alt]` attributes

Score

0/100

Status

fail

Device

desktop

Category

SEO

Fix guidance

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. [Learn more about the `alt` attribute](https://dequeuniversity.com/rules/axe/4.11/image-alt).

Evidence
{
  "description": "Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. [Learn more about the `alt` attribute](https://dequeuniversity.com/rules/axe/4.11/image-alt)."
}

SEOSEOBrowser audit

Links do not have descriptive text

50 Fail

Check name

Links do not have descriptive text

Score

0/100

Status

fail

Device

desktop

Category

SEO

Estimated savings

1 link found

Fix guidance

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

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

Performance and AccessibilityPerformanceBrowser audit

Improve image delivery

17 Fail

Check name

Improve image delivery

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 790 KiB

Fix guidance

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

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

Performance and AccessibilityPerformanceBrowser audit

Reduce unused CSS

17 Fail

Check name

Reduce unused CSS

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 254 KiB

Fix guidance

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

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

Performance and AccessibilityPerformanceBrowser audit

Reduce unused JavaScript

17 Fail

Check name

Reduce unused JavaScript

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 1,839 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
{
  "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/).",
  "displayValue": "Est savings of 1,839 KiB",
  "numericValue": 1280
}

Performance and AccessibilityPerformanceBrowser audit

Touch targets do not have sufficient size or spacing.

17 Fail

Check name

Touch targets do not have sufficient size or spacing.

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. [Learn more about touch targets](https://dequeuniversity.com/rules/axe/4.11/target-size).

Evidence
{
  "description": "Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. [Learn more about touch targets](https://dequeuniversity.com/rules/axe/4.11/target-size)."
}

Performance and AccessibilityPerformanceBrowser audit

Use efficient cache lifetimes

17 Fail

Check name

Use efficient cache lifetimes

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 13,603 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
{
  "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).",
  "displayValue": "Est savings of 13,603 KiB"
}

Performance and AccessibilityPerformanceBrowser audit

Loading performance

11 Fail

Check name

Loading performance

Score

36/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": "first-contentful-paint",
      "score": 7,
      "title": "First Contentful Paint",
      "displayValue": "2.9 s",
      "numericValue": 2925.5306611938654
    },
    {
      "id": "total-blocking-time",
      "score": 41,
      "title": "Total Blocking Time",
      "displayValue": "400 ms",
      "numericValue": 403
    },
    {
      "id": "max-potential-fid",
      "score": 12,
      "title": "Max Potential First Input Delay",
      "displayValue": "450 ms",
      "numericValue": 445
    },
    {
      "id": "server-response-time",
      "score": 100,
      "title": "Initial server response time was short",
      "displayValue": "Root document took 0 ms",
      "numericValue": 3
    },
    {
      "id": "network-rtt",
      "score": 100,
      "title": "Network Round Trip Times",
      "displayValue": "10 ms",
      "numericValue": 14.99211
    },
    {
      "id": "largest-contentful-paint",
      "score": 7,
      "title": "Largest Contentful Paint",
      "displayValue": "5.3 s",
      "numericValue": 5286.786006264458
    },
    {
      "id": "interactive",
      "score": 10,
      "title": "Time to Interactive",
      "displayValue": "8.2 s",
      "numericValue": 8181.64605578052
    },
    {
      "id": "speed-index",
      "score": 10,
      "title": "Speed Index",
      "displayValue": "3.9 s",
      "numericValue": 3948.6999820327724
    }
  ]
}

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
54/100Level 3, Bot-AwareCurrent report