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

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability55%Agent Easeof Use45%Security& Trust67%GEO, AIO, AEO64%SEO100%Performance& Accessibility96%
  • AI Discoverability 55 out of 100
  • Agent Ease of Use 45 out of 100
  • Security & Trust 67 out of 100
  • GEO, AIO and AEO 64 out of 100
  • SEO 100 out of 100
  • Performance and Accessibility 96 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

ETLR - AI workflows as code. Deployed in minutes. favicon

ETLR - AI workflows as code. Deployed in minutes.

AI workflows as code. Deployed in minutes.

Next step

Turn this report into a fix workflow

24 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
55
Needs work32198View details
Discoverability
67
Needs work820View details
Content Readiness
53
Needs work18114View details
Bot Access Control
47
Priority fix664View details
Agent Ease of Use
45
Priority fix322916View details
API
44
Priority fix771View details
Auth
42
Priority fix762View details
MCP
42
Priority fix452View details
Skill Discovery
47
Priority fix668View details
Agent Commerce
46
Priority fix853View details
GEO, AIO and AEO
64
Needs work828View details
GEO Readiness
61
Needs work312View details
AIO Readiness
80
Mostly ready303
AEO Readiness
51
Needs work213View details
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
67
Needs work1532View details
Security & Trust
67
Needs work1532View details
Performance and Accessibility
96
Strong2122View details
Performance
98
Strong1602
Accessibility
93
Strong520View details

Prioritized recommendations

Issues ranked by score impact

44 items need attention

AI DiscoverabilityDiscoverabilityEstablished

Link headers

Link headers failed at "Find useful Link headers".

100 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

API Catalog

API Catalog failed at "Validate API catalog media type".

32 Fail

Needs attention

API Catalog

Failed check
01

Issue

Content-Type "text/html; charset=utf-8" is not valid for an RFC 9727 API catalog.

02

Why it matters

API catalogs help agents find API endpoints, service descriptions, documentation, status resources, auth metadata, and related machine-readable contracts without guessing entry points.

Check name

API Catalog

Score

37/100

Status

fail

Category

API

Maturity

Established

Goal

Publish an API catalog for automated public API discovery using RFC 9727 when this origin exposes public APIs.

Result

API Catalog failed at "Validate API catalog media type".

Validation steps

  1. Check API catalog HEAD Link header

    HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".

  2. Validate API catalog media type

    Content-Type "text/html; charset=utf-8" is not valid for an RFC 9727 API catalog.

  3. Validate Linkset shape

    Unexpected token '<', "<!DOCTYPE "... is not valid JSON

    Unexpected token '<', "<!DOCTYPE "... is not valid JSON

  4. Classify API catalog relations

    API catalog did not include API endpoint links or useful API discovery relations.

  5. Validate API catalog targets

    API catalog did not expose any href targets to validate.

Evidence log5 steps · 23 lines
Check API catalog HEAD Link header [warning]! HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".INFOCheck API catalog HEAD Link headerINFOSend HEAD request to API catalog path attempted=true statusCode=200 contentType="text/html; charset=utf-8"WARNCompare HEAD Link rel=api-catalog count actual=0 expected="> 0"WARNHEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog". status="warning"Validate API catalog media type [fail]! Content-Type "text/html; charset=utf-8" is not valid for an RFC 9727 API catalog.INFOValidate API catalog media typeFAILCompare API catalog media type actual="text/html; charset=utf-8" expected="application/linkset+json"FAILCompare JSON compatibility fallback actual=false expected=trueFAILContent-Type "text/html; charset=utf-8" is not valid for an RFC 9727 API catalog.Validate Linkset shape [fail]! Unexpected token '<', "<!DOCTYPE "... is not valid JSONINFOValidate Linkset shapeFAILCompare Linkset JSON parse result actual=false expected=trueFAILCompare top-level linkset item count actual=0 expected="> 0"FAILCompare extracted href target count actual=0 expected="> 0"FAILLinkset shape issue issue="Unexpected token '<', \"<!DOCTYPE \"... is not valid JSON"FAILLinkset JSON parse error error="Unexpected token '<', \"<!DOCTYPE \"... is not valid JSON"FAILUnexpected token '<', "<!DOCTYPE "... is not valid JSONClassify API catalog relations [fail]! API catalog did not include API endpoint links or useful API discovery relations.INFOClassify API catalog relationsINFOClassify API catalog relation types relations=[] summary={"registered":[],"metadata":[],"adjacent":[],"community":[],"legacy":[],"unknown":[]}FAILCompare registered or metadata API relation count actual=0 expected="> 0"FAILAPI catalog did not include API endpoint links or useful API discovery relations.Validate API catalog targets [fail]! API catalog did not expose any href targets to validate.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsFAILCompare API catalog target failure count actual=0 expected=0FAILAPI catalog did not expose any href targets to validate.

Agent Ease of UseAuthEmerging recommendation

Auth.md Agent Registration

Auth.md Agent Registration failed at "Fetch and validate /auth.md".

30 Fail

Needs attention

Auth.md Agent Registration

Failed check
01

Issue

auth.md response did not match Auth.md v1 agent registration guidance. Content-Type "text/html; charset=utf-8" is not Markdown or text/plain; missing OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance.

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

10/100

Status

fail

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 failed at "Fetch and validate /auth.md".

Validation steps

  1. Fetch and validate /auth.md

    auth.md response did not match Auth.md v1 agent registration guidance. Content-Type "text/html; charset=utf-8" is not Markdown or text/plain; missing OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance.

  2. Validate protected resource metadata

    Response is not valid JSON.

  3. Validate Auth.md authorization metadata

    Response is not valid JSON.

Evidence log3 steps · 20 lines
Fetch and validate /auth.md [fail]! auth.md response did not match Auth.md v1 agent registration guidance. Content-Type "text/html; charset=utf-8" is not Markdown or text/plain; missing OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance.INFOFetch and validate /auth.mdINFOFetch Auth.md-related resource path="/auth.md" statusCode=200 contentType="text/html; charset=utf-8" bytes=73253FAILCompare response Content-Type with expected Auth.md media type actual=false expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILCompare Auth.md content length actual=71279 expected=">= 80 characters"WARNAuth.md validation warning warning="missing agent_verified/user_claimed or claim ceremony guidance"FAILAuth.md validation issue issue="auth.md response did not match Auth.md v1 agent registration guidance. Content-Type \"text/html; charset=utf-8\" is not Markdown or text/plain; missing OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance."FAILauth.md response did not match Auth.md v1 agent registration guidance. Content-Type "text/html; charset=utf-8" is not Markdown or text/plain; missing OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance.Validate protected resource metadata [fail]! Response is not valid JSON.INFOValidate protected resource metadataINFOFetch Auth.md-related resource path="/.well-known/oauth-protected-resource" statusCode=200 contentType="text/html; charset=utf-8" bytes=73253FAILCompare response Content-Type with expected Auth.md media type actual=false expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILAuth.md validation issue issue="Response is not valid JSON."FAILResponse is not valid JSON.Validate Auth.md authorization metadata [fail]! Response is not valid JSON.INFOValidate Auth.md authorization metadataINFOFetch Auth.md-related resource path="/.well-known/oauth-authorization-server" statusCode=200 contentType="text/html; charset=utf-8" bytes=73253FAILCompare response Content-Type with expected Auth.md media type actual=false expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILAuth.md validation issue issue="Response is not valid JSON."FAILResponse is not valid JSON.

Agent Ease of UseMCPEmerging recommendation

MCP Server Card

MCP Server Card failed at "Validate server-card shape".

30 Fail

Needs attention

MCP Server Card

Failed check
01

Issue

MCP Server Card response is not valid JSON.

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

40/100

Status

fail

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 failed at "Validate server-card shape".

Validation steps

  1. Validate server-card shape

    MCP Server Card response is not valid JSON.

  2. Validate MCP remotes

    No usable MCP remote transport was declared.

  3. Validate HTTP delivery

    Content-Type "text/html; charset=utf-8" is not JSON.

  4. Probe same-origin MCP endpoint

    No MCP remote endpoint could be probed.

Evidence log4 steps · 23 lines
Validate server-card shape [fail]! MCP Server Card response is not valid JSON.INFOValidate server-card shape profile="unknown-json"FAILCheck response body parsed as JSON actual=false expected=trueFAILCheck Content-Type is JSON-compatible actual=false expected=trueFAILCheck recognized MCP server-card profile actual="unknown-json" expected="sep-2127-draft"PASSCheck required card fields are present actual=0 expected=0 missing=[]PASSCheck MCP server-card uses the current remotes[] profile without legacy compatibility warnings actual="no compatibility warnings" expected="current sep-2127-draft card shape with no legacy compatibility warnings" warnings=[]FAILMCP server-card shape validation failed reason="MCP Server Card response is not valid JSON."Validate MCP remotes [fail]! No usable MCP remote transport was declared.INFOValidate MCP remotes remoteCount=0FAILCheck at least one MCP remote is declared actual=0 expected="> 0"PASSCheck invalid remote count actual=0 expected=0 invalidRemotes=[]PASSCheck same-origin remote coverage actual=0 expected=0FAILMCP remote validation failed reason="No usable MCP remote transport was declared."Validate HTTP delivery [fail]! Content-Type "text/html; charset=utf-8" is not JSON.INFOValidate HTTP delivery finalUrl="https://etlr.io/.well-known/mcp-server-card"PASSCheck server card returned HTTP 2xx actual=200 expected="200-299"FAILCheck card is served as JSON actual="text/html; charset=utf-8" expected="application/json or +json"PASSCheck card is served over HTTPS actual="https:" expected="https:"PASSCheck browser-readable CORS header actual="*" expected="Access-Control-Allow-Origin present"PASSCheck cache header is present actual="public, max-age=0, must-revalidate" expected="Cache-Control present"FAILMCP server-card HTTP delivery failed issues=["Content-Type \"text/html; charset=utf-8\" is not JSON."] reason="Content-Type \"text/html; charset=utf-8\" is not JSON."Probe same-origin MCP endpoint [warning]! No MCP remote endpoint could be probed.INFOProbe same-origin MCP endpoint probeCount=0INFOSelecting same-origin unauthenticated MCP remotes for a bounded initialize probeWARNCheck successful initialize probe count actual=0 expected="> 0 when a safe same-origin unauthenticated remote exists" activeProbeCount=0 authBlocked=0WARNMCP endpoint probe could not fully confirm operability reason="No MCP remote endpoint could be probed."

Agent Ease of UseMCPEmerging recommendation

WebMCP

WebMCP failed at "Probe WebMCP operability".

28 Fail

Needs attention

WebMCP

Failed check
01

Issue

Discovered WebMCP static metadata was fetchable but invalid.

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

44/100

Status

fail

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 failed at "Probe WebMCP operability".

Validation steps

  1. Detect WebMCP runtime API

    WebMCP-like strings were found, but rendered browser evidence did not confirm a usable runtime API.

  2. Probe WebMCP operability

    Discovered WebMCP static metadata was fetchable but invalid.

    WebMCP operability findings
    • Discovered WebMCP static metadata was fetchable but invalid.
  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

    A discovered WebMCP static manifest or WMCP interaction graph was invalid.

    Body is not valid JSON.

    Body is not valid JSON.

Evidence log5 steps · 23 lines
Detect WebMCP runtime API [warning]! WebMCP-like strings were found, but rendered browser evidence did not confirm a usable runtime API.INFODetect WebMCP runtime API status="warning"INFOProbe rendered browser for WebMCP runtime objects WARNCheck current W3C runtime API actual="not detected" expected="document.modelContext/registerTool available"WARNWebMCP-like strings were found, but rendered browser evidence did not confirm a usable runtime API.Probe WebMCP operability [fail]! Discovered WebMCP static metadata was fetchable but invalid.INFOProbe WebMCP operability status="fail"INFORun safe WebMCP operability checks safeProbeOnly=trueFAILCheck usable WebMCP evidence actual=0 expected="at least 1 usable runtime, declarative, annotation, or static manifest signal"FAILWebMCP operability failure issue="Discovered WebMCP static metadata was fetchable but invalid."FAILDiscovered WebMCP static metadata was fetchable but invalid.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 [fail]! A discovered WebMCP static manifest or WMCP interaction graph was invalid.INFOValidate static WebMCP JSON compatibility status="fail"INFODiscover static WebMCP manifest candidates conventionalPaths=["/.well-known/webmcp.json","/webmcp.json"] checkedCount=2 profileCounts={"unknown-webmcp-json":2}PASSWebMCP manifest candidate found source="path" path="/.well-known/webmcp.json" url="https://etlr.io/.well-known/webmcp.json" statusCode=200 contentType="text/html; charset=utf-8"PASSWebMCP manifest candidate found source="path" path="/webmcp.json" url="https://etlr.io/webmcp.json" statusCode=200 contentType="text/html; charset=utf-8"FAILValidate discovered static WebMCP metadata actual={"validManifestCount":0,"invalidManifestCount":2,"toolCount":0,"wmcpActionCount":0} expected="at least 1 valid tools[] manifest or WMCP graph when static metadata is present"FAILA discovered WebMCP static manifest or WMCP interaction graph was invalid.

Agent Ease of UseAPIEstablished

OpenAPI discovery

OpenAPI discovery failed at "Parse OpenAPI document".

25 Fail

Needs attention

OpenAPI discovery

Failed check
01

Issue

OpenAPI candidate was not parseable as JSON or YAML-like OpenAPI.

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

50/100

Status

fail

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 failed at "Parse OpenAPI document".

Validation steps

  1. Parse OpenAPI document

    OpenAPI candidate was not parseable as JSON or YAML-like OpenAPI.

  2. Validate OpenAPI shape

    Response is not valid JSON and does not match baseline OpenAPI YAML shape.

  3. Check machine-usable details

    Add servers, parameters, request bodies, response schemas, operation IDs, tags, examples, and security or explicit no-auth declarations where they apply.

Evidence log3 steps · 14 lines
Parse OpenAPI document [fail]! OpenAPI candidate was not parseable as JSON or YAML-like OpenAPI.INFOParse OpenAPI document status="fail"INFOParse selected document as JSON first, then YAML-like OpenAPI parsed=false format="unknown" versionFamily="missing"FAILCheck parse result actual="not parseable" expected="parseable OpenAPI 3.x or Swagger 2.0 document" compatibleContentType=falseFAILOpenAPI candidate was not parseable as JSON or YAML-like OpenAPI.Validate OpenAPI shape [fail]! Response is not valid JSON and does not match baseline OpenAPI YAML shape.INFOValidate OpenAPI shape status="fail"INFOValidate required OpenAPI shape versionFamily="missing" pathCount=0 webhookCount=0 operationCount=0PASSCheck operations define responses actual=0 expected="every operation should define responses"FAILCheck info metadata actual={"hasInfoTitle":false,"hasInfoVersion":false} expected="info.title and info.version present"FAILOpenAPI shape issue issue="Response is not valid JSON and does not match baseline OpenAPI YAML shape."FAILResponse is not valid JSON and does not match baseline OpenAPI YAML shape.Check machine-usable details [fail]INFOCheck machine-usable details status="fail"INFOInspect machine-usable operation details hasServers=false hasSecuritySchemes=false hasExplicitNoAuth=false requestBodyOperationCount=0 parameterOperationCount=0 responseSchemaOperationCount=0 operationIdCount=0 taggedOperationCount=0 exampleOperationCount=0PASSCheck OpenAPI operations include enough detail for agents to call them safely actual="no machine-usability warnings" expected="servers, auth/no-auth signals, operationIds, parameters, request bodies, responses, tags, and examples where relevant"FAILOpenAPI discovery validation failed.

Agent Ease of UseAgent CommerceInformational

Universal Commerce Protocol

Universal Commerce Protocol failed at "Fetch UCP profile".

21 Fail

Needs attention

Universal Commerce Protocol

Failed check
01

Issue

UCP profile content type "text/html; charset=utf-8" is not JSON-compatible.

02

Why it matters

UCP discovery lets agents identify commerce capabilities, service transports, payment handlers, and signing keys without scraping human checkout flows.

Check name

Universal Commerce Protocol

Score

36/100

Status

fail

Category

Agent Commerce

Maturity

Informational

Goal

Expose a valid Universal Commerce Protocol business profile when this origin supports agentic commerce workflows.

Result

Universal Commerce Protocol failed at "Fetch UCP profile".

Validation steps

  1. Fetch UCP profile

    UCP profile content type "text/html; charset=utf-8" is not JSON-compatible.

  2. Validate UCP profile shape

    UCP profile could not be parsed.

Evidence log2 steps · 11 lines
Fetch UCP profile [fail]! UCP profile content type "text/html; charset=utf-8" is not JSON-compatible.INFOFetch UCP profile status="fail"INFOFetch /.well-known/ucp statusCode=200 contentType="text/html; charset=utf-8" error="Unexpected token '<', \"<!DOCTYPE \"... is not valid JSON"FAILCheck UCP profile availability actual=true expected=trueFAILCheck JSON-compatible profile response actual=false expected=true jsonCompatible=false parsed=falseFAILUCP profile content type "text/html; charset=utf-8" is not JSON-compatible.Validate UCP profile shape [fail]! UCP profile could not be parsed.INFOValidate UCP profile shape status="fail"INFOValidate top-level ucp object, version, services, payment handlers, and supported versionsFAILCheck top-level ucp object actual=false expected=trueFAILCheck production-friendly version actual=false expected=true stableVersion=false draftVersion=falseFAILCheck required UCP sections actual={"services":false,"paymentHandlers":false,"supportedVersionCount":0} expected="services, payment_handlers, and supported versions"FAILUCP profile could not be parsed.

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

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

20 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 DiscoverabilityBot Access ControlEmerging recommendation

TDMRep declaration

TDMRep declaration failed at "Fetch /.well-known/tdmrep.json".

20 Fail

Needs attention

TDMRep declaration

Failed check
01

Issue

Response is not valid 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

0/100

Status

fail

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

TDMRep declaration failed at "Fetch /.well-known/tdmrep.json".

Validation steps

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

    Response is not valid JSON.

  2. Validate TDM declarations

    No valid TDM declarations were parsed from the declared TDMRep surface.

Evidence log2 steps · 8 lines
Fetch /.well-known/tdmrep.json [fail]! Response is not valid JSON.INFOFetch /.well-known/tdmrep.jsonINFORequesting origin-level TDMRep declaration at /.well-known/tdmrep.jsonFAILCompare TDMRep file response actual=200 expected="2xx with JSON array when origin-level TDMRep is published" contentType="text/html; charset=utf-8" length=73253FAILResponse is not valid JSON. compatibleContentType=falseValidate TDM declarations [fail]! No valid TDM declarations were parsed from the declared TDMRep surface.INFOValidate TDM declarationsINFOChecking reservation values, policy URLs, declaration source, and cross-surface consistency declarationCount=0FAILCompare malformed declaration count actual=1 expected=0 warnings=[]FAILNo valid TDM declarations were parsed from the declared TDMRep surface. source="well-known" index=-1

Security & TrustSecurity & TrustEstablished

Frame protection

Frame protection failed at "Validate X-Frame-Options".

19 Fail

Needs attention

Frame protection

Failed check
01

Issue

No valid X-Frame-Options fallback is present.

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

44/100

Status

fail

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 failed at "Validate X-Frame-Options".

Validation steps

  1. Validate CSP frame-ancestors

    No enforcing CSP frame-ancestors directive is present.

  2. Validate X-Frame-Options

    No valid X-Frame-Options fallback is present.

  3. Review observed browser responses

    One or more same-origin HTML documents observed by Chrome did not emit valid frame protection.

Evidence log3 steps · 12 lines
Validate CSP frame-ancestors [warning]! No enforcing CSP frame-ancestors directive is present.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="No enforcing CSP frame-ancestors directive is present."WARNNo enforcing CSP frame-ancestors directive is present.Validate X-Frame-Options [fail]! No valid X-Frame-Options fallback is present.INFOValidate X-Frame-OptionsINFORead X-Frame-Options fallback value="missing" parsedValues=[] normalizedValues=[]FAILCompare X-Frame-Options value actual="missing" expected="DENY or SAMEORIGIN" valid=false obsoleteAllowFrom=false duplicateOrConflicting=false issue="No valid X-Frame-Options fallback is present."FAILNo valid X-Frame-Options fallback is present.Review observed browser responses [warning]! One or more same-origin HTML documents observed by Chrome did not emit valid frame protection.INFOReview observed browser responsesINFOSample Chrome-observed same-origin responses observedResponseCount=23 sameOriginCount=14 htmlDocumentCount=1WARNCompare observed HTML frame protection actual={"missingOrInvalidFrameProtectionCount":1,"broadFrameAncestorsCount":0,"affected":[{"url":"https://etlr.io/","status":200,"resourceType":"document","contentType":"text/html; charset=utf-8","contentSecurityPolicy":null,"contentSecurityPolicyReportOnly":null}]} expected="0 missing/invalid or broad same-origin HTML responses" issue="One or more same-origin HTML documents observed by Chrome did not emit valid frame protection."WARNOne or more same-origin HTML documents observed by Chrome did not emit valid frame protection.

Agent Ease of UseAgent CommerceInformational

ACP - Agentic Commerce Protocol

ACP - Agentic Commerce Protocol failed at "Fetch ACP discovery".

18 Fail

Needs attention

ACP - Agentic Commerce Protocol

Failed check
01

Issue

ACP discovery content type "text/html; charset=utf-8" is not JSON-compatible.

02

Why it matters

ACP discovery lets agents find the seller's ACP API base URL, supported versions, transports, and stable services before attempting authenticated checkout-session negotiation.

Check name

ACP - Agentic Commerce Protocol

Score

46/100

Status

fail

Category

Agent Commerce

Maturity

Informational

Goal

Expose valid ACP discovery when this origin supports Agentic Commerce Protocol workflows.

Result

ACP - Agentic Commerce Protocol failed at "Fetch ACP discovery".

Validation steps

  1. Fetch ACP discovery

    ACP discovery content type "text/html; charset=utf-8" is not JSON-compatible.

  2. Validate ACP discovery shape

    ACP discovery could not be parsed.

Evidence log2 steps · 9 lines
Fetch ACP discovery [fail]! ACP discovery content type "text/html; charset=utf-8" is not JSON-compatible.INFOFetch ACP discovery status="fail"INFOFetch canonical ACP discovery /.well-known/acp.json statusCode=200 contentType="text/html; charset=utf-8" parsed=false error="Unexpected token '<', \"<!DOCTYPE \"... is not valid JSON"FAILCheck canonical ACP discovery response actual=false expected=true canonicalFound=trueFAILACP discovery content type "text/html; charset=utf-8" is not JSON-compatible.Validate ACP discovery shape [fail]! ACP discovery could not be parsed.INFOValidate ACP discovery shape status="fail"INFOValidate ACP protocol object, name, date version, and supported_versions orderingFAILCheck protocol object and name actual={"hasProtocol":false} expected={"hasProtocol":true,"protocolName":"acp"}FAILCheck protocol version history actual={"supportedVersionCount":0,"supportedVersionsOrdered":false,"supportedVersionsEndWithCurrent":false} expected="date version with chronological supported_versions ending in current version"FAILACP discovery could not be parsed.

Security & TrustSecurity & TrustEstablished

HSTS header

HSTS header failed at "Find Strict-Transport-Security".

17 Fail

Needs attention

HSTS header

Failed check
01

Issue

HTTPS response is missing Strict-Transport-Security.

02

Why it matters

HSTS tells browsers to keep using HTTPS after the first secure visit, reducing downgrade, SSL-stripping, and mixed-transport risk for repeat users.

Check name

HSTS header

Score

50/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Require HTTPS for repeat browser visits with a valid Strict-Transport-Security policy.

Result

HSTS header failed at "Find Strict-Transport-Security".

Validation steps

  1. Find Strict-Transport-Security

    HTTPS response is missing Strict-Transport-Security.

Evidence log1 step · 4 lines
Find Strict-Transport-Security [fail]! HTTPS response is missing Strict-Transport-Security.INFOFind Strict-Transport-SecurityINFORead Strict-Transport-Security header header="strict-transport-security" value="missing" effectiveValue=null duplicateHeaderValueCount=0FAILRequire HSTS header on HTTPS response actual="missing" expected="present" issue="HTTPS response is missing Strict-Transport-Security."FAILHTTPS response is missing Strict-Transport-Security.

Agent Ease of UseSkill DiscoveryEmerging recommendation

agents.json

agents.json failed at "Validate Wildcard schema shape".

16 Fail

Needs attention

agents.json

Failed check
01

Issue

agents.json response is not valid JSON.

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

35/100

Status

fail

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 failed at "Validate Wildcard schema shape".

Validation steps

  1. Validate Wildcard schema shape

    agents.json response is not valid JSON.

  2. Validate API actions

    Wildcard agents.json must include valid OpenAPI-derived action or operation definitions.

  3. Validate flows and links

    No executable flows were found.

  4. Review examples and LLM usability

    Examples or descriptions are too thin for reliable agent argument generation.

Evidence log4 steps · 17 lines
Validate Wildcard schema shape [fail]! agents.json response is not valid JSON.INFOValidate Wildcard schema shapeINFOParse agents.json and classify contract shape shape="unknown"FAILCompare contract shape actual="unknown" expected="wildcard"FAILCompare missing required schema fields actual="none" expected="none"FAILCompare Content-Type with JSON expectation actual=false expected=trueFAILagents.json response is not valid JSON.Validate API actions [fail]! Wildcard agents.json must include valid OpenAPI-derived action or operation definitions.INFOValidate API actionsFAILCompare API action count actual=0 expected="> 0"FAILCompare invalid action definitions actual=0 expected=0FAILWildcard agents.json must include valid OpenAPI-derived action or operation definitions.Validate flows and links [fail]! No executable flows were found.INFOValidate flows and linksFAILCompare workflow flow count actual=0 expected="> 0"FAILCompare operation link issues actual=0 expected=0FAILNo executable flows were found.Review examples and LLM usability [warning]! Examples or descriptions are too thin for reliable agent argument generation.INFOReview examples and LLM usabilityWARNCompare usable example count actual=0 expected="> 0 when actions are present"WARNExamples or descriptions are too thin for reliable agent argument generation.

AI DiscoverabilityContent ReadinessEstablished

Markdown negotiation

Markdown negotiation is missing or incomplete.

15 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://etlr.io/","statusCode":200,"contentType":"text/html; charset=utf-8","mediaType":"text/html","vary":"accept-encoding","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"fail","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"html-heavy","hasHeading":false,"headingCount":0,"wordCount":9647,"features":{"markdownLinks":0,"referenceLinks":0,"listItems":10,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":1264,"jsxOrMdxSignals":0},"issues":["missing-heading","raw-html-heavy"],"excerpt":"<!DOCTYPE html><html lang=\"en-GB\"> <head><meta charset=\"UTF-8\"><meta name=\"description\" content=\"AI workflows as code. Deployed in minutes.\"><meta name=\"viewport\" content=\"width=device-width\"><!-- Canonical URL --><link rel=\"canonical\" href","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://etlr.io/","statusCode":200,"contentType":"text/html; charset=utf-8","mediaType":"text/html","vary":"accept-encoding","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"fail","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"html-heavy","hasHeading":false,"headingCount":0,"wordCount":9647,"features":{"markdownLinks":0,"referenceLinks":0,"listItems":10,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":1264,"jsxOrMdxSignals":0},"issues":["missing-heading","raw-html-heavy"],"excerpt":"<!DOCTYPE html><html lang=\"en-GB\"> <head><meta charset=\"UTF-8\"><meta name=\"description\" content=\"AI workflows as code. Deployed in minutes.\"><meta name=\"viewport\" content=\"width=device-width\"><!-- Canonical URL --><link rel=\"canonical\" href","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-encoding"} expected="HTTP 2xx text/markdown with Vary: Accept" url="https://etlr.io/" statusCode=200 mediaType="text/html" vary="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":9647,"headingCount":0,"dialect":"html-heavy"} expected="valid Markdown with substantive text and headings" valid=false dialect="html-heavy" wordCount=9647 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://etlr.io/index.html.md"] candidateCount=1FAILConventional .md mirror failed issue="Conventional .md mirror candidates did not return valid Markdown."

Agent Ease of UseAuthEmerging recommendation

OAuth Protected Resource

OAuth Protected Resource failed at "Validate metadata shape".

15 Fail

Needs attention

OAuth Protected Resource

Failed check
01

Issue

Response is not valid JSON.

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

55/100

Status

fail

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 failed at "Validate metadata shape".

Validation steps

  1. Validate metadata shape

    Response is not valid JSON.

  2. Validate resource identity

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

  3. Validate authorization servers

    authorization_servers is omitted; this is allowed by base RFC 9728 but limits authorization server discovery.

  4. Validate protected resource challenge

    No protected route with a 401 resource_metadata challenge was detected; metadata shape is valid but route linkage was not proven.

Evidence log4 steps · 23 lines
Validate metadata shape [fail]! Response is not valid JSON.INFOValidate metadata shapeINFOParsing and validating RFC 9728 protected-resource metadata valid=false compatibleContentType=false issue="Response is not valid JSON." warningsCount=0 resourceIssuesCount=0 authorizationServersCount=0 authorizationServerIssuesCount=0 scopesSupportedCount=0 bearerMethodsSupportedCount=0 optionalFieldIssuesCount=0FAILCheck metadata resource field is present actual="missing" expected="absolute protected resource identifier"PASSCheck required metadata field failures actual=0 expected=0 missing=[]PASSCheck protected-resource metadata is browser-readable and complete for OAuth clients actual="no client-usage warnings" expected="no CORS, authorization-server, or compatibility warnings" warnings=[]FAILValidate metadata shape failed issue="Response is not valid JSON."Validate resource identity [fail]! Protected resource metadata `resource` did not match the resource identifier used to retrieve it.INFOValidate resource identityINFOComparing metadata resource identifier with the candidate resource expectedResource="https://etlr.io" candidatePresent=trueFAILCheck protected resource identity matches expected="https://etlr.io"FAILValidate resource identity failed issue="Protected resource metadata `resource` did not match the resource identifier used to retrieve it."Validate authorization servers [warning]! authorization_servers is omitted; this is allowed by base RFC 9728 but limits authorization server discovery.INFOValidate authorization serversINFOValidating advertised authorization server issuer URLs authorizationServerCount=0PASSCheck authorization server count actual=0 expected="> 0 when required"PASSCheck authorization server URL issue count actual=0 expected=0 issues=[]WARNValidate authorization servers completed with warnings issue="authorization_servers is omitted; this is allowed by base RFC 9728 but limits authorization server discovery."Validate protected resource challenge [warning]! No protected route with a 401 resource_metadata challenge was detected; metadata shape is valid but route linkage was not proven.INFOValidate protected resource challengeINFOProbing protected routes for WWW-Authenticate resource_metadata linkage checkedCount=4INFOChecked protected route challenge url="https://etlr.io/api/scans" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://etlr.io/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://etlr.io" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://etlr.io/api/admin/scans" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://etlr.io/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://etlr.io" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://etlr.io/api/admin/summary" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://etlr.io/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://etlr.io" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://etlr.io/mcp" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://etlr.io/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://etlr.io" resourceMatches=true scopePresent=falseWARNCheck challenge includes resource_metadata linkage actual=4 expected="> 0 matching protected route challenges"WARNValidate protected resource challenge completed with warnings issue="No protected route with a 401 resource_metadata challenge was detected; metadata shape is valid but route linkage was not proven."

Agent Ease of UseAgent CommerceEmerging recommendation

x402 Protocol

x402 Protocol failed at "Probe x402 runtime response".

15 Fail

Needs attention

x402 Protocol

Failed check
01

Issue

x402 candidate routes were found, but none returned HTTP 402 before payment.

02

Why it matters

x402 lets agents discover paid HTTP resources through ordinary 402 responses, understand accepted schemes and networks, and retry with a signed payment payload without scraping checkout flows.

Check name

x402 Protocol

Score

56/100

Status

fail

Category

Agent Commerce

Maturity

Emerging recommendation

Goal

Expose x402 V2 payment requirements on payable HTTP resources so agents can recognize and satisfy payment requirements programmatically.

Result

x402 Protocol failed at "Probe x402 runtime response".

Validation steps

  1. Probe x402 runtime response

    x402 candidate routes were found, but none returned HTTP 402 before payment.

  2. Validate x402 V2 headers

    No x402 runtime response was available for header validation.

  3. Validate x402 payment requirement payload

    No x402 runtime response was available for payload validation.

  4. Compare x402 metadata consistency

    x402 metadata was found, but no probed candidate returned HTTP 402.

Evidence log4 steps · 20 lines
Probe x402 runtime response [fail]! x402 candidate routes were found, but none returned HTTP 402 before payment.INFOProbe x402 runtime response status="fail"INFOProbe candidate GET routes without sending payment credentials checkedCount=1INFOProbe x402 candidate route path="/" source="well-known" statusCode=200 contentType="text/html; charset=utf-8" finalUrl="https://etlr.io/" headers={} textSample="<!DOCTYPE html><html lang=\"en-GB\"> <head><meta charset=\"UTF-8\"><meta name=\"description\" content=\"AI workflows as code. Deployed in minutes.\"><meta name=\"viewport\" content=\"width=de"FAILCheck pre-payment runtime response actual="none" expected=402 best={}FAILx402 candidate routes were found, but none returned HTTP 402 before payment.Validate x402 V2 headers [warning]! No x402 runtime response was available for header validation.INFOValidate x402 V2 headers status="warning"INFOInspect payment headers on the best HTTP 402 response observedHeaders={}WARNCheck PAYMENT-REQUIRED header actual=false expected=true hasLegacyOnly=falseWARNCheck legacy-only x402 header usage actual=false expected=falseWARNNo x402 runtime response was available for header validation.Validate x402 payment requirement payload [warning]! No x402 runtime response was available for payload validation.INFOValidate x402 payment requirement payload status="warning"INFODecode PAYMENT-REQUIRED as Base64 JSON and inspect accepted payment optionsWARNCheck PAYMENT-REQUIRED decoding actual={} expected={"decoded":true,"parsed":true}WARNCheck x402 payment option shape actual={} expected="x402Version 2 with accepted options containing payee and amount"INFOSummarize decoded payment requirement WARNNo x402 runtime response was available for payload validation.Compare x402 metadata consistency [warning]! x402 metadata was found, but no probed candidate returned HTTP 402.INFOCompare x402 metadata consistency status="warning"INFOCompare metadata-declared payable routes with observed runtime 402 behavior openApiSignals=[] wellKnown={"found":true,"statusCode":200,"contentType":"text/html; charset=utf-8","markers":[],"candidateCount":1} runtime402=falseWARNCheck runtime 402 evidence against metadata actual={"openApiSignals":[],"wellKnown":{"found":true,"statusCode":200,"contentType":"text/html; charset=utf-8","markers":[],"candidateCount":1},"runtime402":false} expected="metadata and runtime agree on payable resources"WARNx402 metadata was found, but no probed candidate returned HTTP 402.

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

A2A Agent Card failed at "Detect A2A card version".

13 Fail

Needs attention

A2A Agent Card

Failed check
01

Issue

The discovered JSON document does not match a supported A2A Agent Card version family.

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

48/100

Status

fail

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 failed at "Detect A2A card version".

Validation steps

  1. Detect A2A card version

    The discovered JSON document does not match a supported A2A Agent Card version family.

  2. Validate version-specific card shape

    A2A Agent Card response is not valid JSON.

  3. Validate HTTP delivery

    The card was parseable JSON but was not served with a JSON-compatible content type.

  4. Probe same-origin A2A endpoint

    A2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.

Evidence log4 steps · 17 lines
Detect A2A card version [fail]! The discovered JSON document does not match a supported A2A Agent Card version family.INFODetect A2A card versionINFORead version indicators from the card detectionEvidence=[]FAILCompare detected A2A version family actual="unknown" expected="v0.1, v0.2, v0.3, or v1"FAILThe discovered JSON document does not match a supported A2A Agent Card version family.Validate version-specific card shape [fail]! A2A Agent Card response is not valid JSON.INFOValidate version-specific card shapeFAILCompare missing required card fields actual="none" expected="none"FAILCheck every declared A2A skill has required name, description, and endpoint fields actual=0 expected=0 invalidSkills=[]INFOReview declared endpoint interfaces interfaces=[]FAILA2A Agent Card response is not valid JSON.Validate HTTP delivery [warning]! The card was parseable JSON but was not served with a JSON-compatible content type.INFOValidate HTTP deliveryWARNCompare card Content-Type with JSON expectation actual="text/html; charset=utf-8" expected="application/json or +json"INFOReview selected discovery path path="/.well-known/agent-card.json" pathClass="canonical-current"WARNThe card was parseable JSON but was not served with a JSON-compatible content type.Probe same-origin A2A endpoint [warning]! A2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.INFOProbe same-origin A2A endpointINFOProbe same-origin A2A endpoint when scanner policy allows itSKIPSkipped endpoint probe reason="No valid A2A card was available to probe."WARNA2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.

Agent Ease of UseAuthEstablished

OAuth / OIDC discovery

OAuth / OIDC discovery failed at "Validate metadata profile".

13 Fail

Needs attention

OAuth / OIDC discovery

Failed check
01

Issue

Response is not valid JSON.

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

62/100

Status

fail

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 failed at "Validate metadata profile".

Validation steps

  1. Validate metadata profile

    Response is not valid JSON.

Evidence log1 step · 6 lines
Validate metadata profile [fail]! Response is not valid JSON.INFOValidate metadata profileINFOParsing and validating OAuth/OIDC metadata profile valid=false compatibleContentType=false profile="unknown" issue="Response is not valid JSON." missingCount=0 warningsCount=0 endpointIssuesCount=0 responseTypesSupportedCount=0 grantTypesSupportedCount=0 inferredGrantTypes=falsePASSCheck metadata profile was recognized actual="unknown" expected="oauth-authorization-server, oidc, or hybrid"PASSCheck required metadata fields are present actual=0 expected=0 missing=[]PASSCheck OAuth metadata is fully usable by browser and agent clients actual="no client-usage warnings" expected="no CORS, endpoint, or compatibility warnings" warnings=[]FAILValidate metadata profile failed issue="Response is not valid JSON."

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="etlr.io" labels=["_index._agents.etlr.io","_a2a._agents.etlr.io"] claimedOnPage=falseWARNDNS query returned no DNS-AID answers name="_index._agents.etlr.io" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.etlr.io" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.etlr.io" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _index._agents.etlr.io"WARNDNS query returned no DNS-AID answers name="_a2a._agents.etlr.io" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.etlr.io" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.etlr.io" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _a2a._agents.etlr.io"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.etlr.io" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.etlr.io" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.etlr.io" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.etlr.io" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.etlr.io" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.etlr.io" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.etlr.io" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.etlr.io" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="etlr.io" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNDNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.

AI DiscoverabilityBot Access ControlEmerging recommendation

ai.txt policy

ai.txt policy failed at "Validate transport".

12 Fail

Needs attention

ai.txt policy

Failed check
01

Issue

ai.txt appears to be an HTML page or error document rather than a plain-text policy.

02

Why it matters

ai.txt is a fragmented emerging convention. It can communicate human-readable AI crawling, training, attribution, restriction, and contact guidance, but it is not a standard access-control mechanism and absence should not be penalized.

Check name

ai.txt policy

Score

38/100

Status

fail

Category

Bot Access Control

Maturity

Emerging recommendation

Goal

Publish an advisory human-readable AI usage policy only when the site intentionally needs one.

Result

ai.txt policy failed at "Validate transport".

Validation steps

  1. Validate transport

    ai.txt appears to be an HTML page or error document rather than a plain-text policy.

  2. Parse ai.txt policy

    Transport validation failed before policy parsing could be trusted.

  3. Validate policy content

    ai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.

Evidence log3 steps · 14 lines
Validate transport [fail]! ai.txt appears to be an HTML page or error document rather than a plain-text policy.INFOValidate transportINFOChecking ai.txt media type, size, line count, and whether the response looks like plain text contentType="text/html; charset=utf-8" length=73253 lineCount=146FAILCompare media type to preferred text/plain transport actual="text/html" expected="text/plain preferred; readable text required"FAILai.txt appears to be an HTML page or error document rather than a plain-text policy.Parse ai.txt policy [fail]! Transport validation failed before policy parsing could be trusted.INFOParse ai.txt policyINFODetecting ai.txt convention from bracket sections, frontmatter, headings, and ai.txt context linksINFODetected policy structure convention="generic-markdown" sections=[] markdownHeadings=[]WARNCheck AI Visibility required sections actual="missing identity, permissions, restrictions" expected="identity, permissions, and restrictions" missingRecommended=["attribution","contact","content-types"]WARNTransport validation failed before policy parsing could be trusted.Validate policy content [warning]! ai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.INFOValidate policy contentINFOChecking required section content, permission/restriction language, attribution, contact details, and safety risks convention="generic-markdown"INFODetected policy signals hasPermissionLanguage=false hasRestrictionLanguage=false hasTrainingLanguage=true hasAttributionLanguage=true hasContact=falseWARNCheck required and recommended section coverage actual={"missingRequired":["identity","permissions","restrictions"],"missingRecommended":["attribution","contact","content-types"]} expected={"missingRequired":[],"recommendedPresentWhenPossible":true}WARNai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.

AI DiscoverabilityContent ReadinessEstablished

Author attribution

Author attribution is partially implemented.

12 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

30/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.

  3. Visible byline parity

    Structured author/publisher names were not found in visible byline text.

Evidence log3 steps · 12 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 extractedVisible byline parity [fail]! Structured author/publisher names were not found in visible byline text.INFOVisible byline parityINFOComparing structured contributor names with visible byline evidenceFAILCheck visible attribution matches actual=0 expected="> 0 or visible byline present" visibleByline=false bylineCount=0FAILNo visible byline parity found

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

Agent Skills index failed at "Validate discovery index schema".

11 Fail

Needs attention

Agent Skills index

Failed check
01

Issue

Agent Skills index was not served with a JSON-compatible Content-Type.

Details

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

55/100

Status

fail

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 failed at "Validate discovery index schema".

Validation steps

  1. Validate discovery index schema

    Agent Skills index was not served with a JSON-compatible Content-Type.

    Response is not valid JSON.

  2. Verify advertised artifacts

    No valid skill artifacts were available to verify.

  3. Validate skill content

    For skill-md artifacts, include valid YAML frontmatter with name and description followed by Markdown. For archives, include a safe root SKILL.md and no unsafe paths.

  4. Review skill artifact security

    Do not publish secrets or prompt-injection instructions in skill artifacts. Treat scripts, archives, and cross-origin artifacts as software supply-chain surfaces.

Evidence log4 steps · 14 lines
Validate discovery index schema [fail]! Agent Skills index was not served with a JSON-compatible Content-Type.INFOValidate discovery index schemaINFOParse Agent Skills index JSON validJson=false contentTypeCompatible=falseFAILCompare $schema URI expected="https://schemas.agentskills.io/discovery/0.2.0/schema.json"FAILCompare top-level schema issue count actual=1 expected=0FAILCompare unknown top-level field count actual=0 expected=0FAILAgent Skills index was not served with a JSON-compatible Content-Type.Verify advertised artifacts [warning]! No valid skill artifacts were available to verify.INFOVerify advertised artifactsWARNCompare artifact fetch count actual=0 expected="> 0"WARNNo valid skill artifacts were available to verify.Validate skill content [warning]INFOValidate skill contentWARNAgent Skills step completed with warningsReview skill artifact security [warning]INFOReview skill artifact securityWARNCompare security finding count actual=0 expected=0WARNAgent Skills step completed with warnings

AI DiscoverabilityBot Access ControlInformational

Web Bot Auth request signing

Web Bot Auth request signing failed at "Validate directory media type".

11 Fail

Needs attention

Web Bot Auth request signing

Failed check
01

Issue

Content-Type "text/html; charset=utf-8" is not valid for a Web Bot Auth signing key directory.

02

Why it matters

Web Bot Auth lets bot and agent operators publish HTTP Message Signatures keys so receiving websites can verify signed automated requests without relying only on user-agent strings, IP lists, or reverse DNS.

Check name

Web Bot Auth request signing

Score

44/100

Status

fail

Category

Bot Access Control

Maturity

Informational

Goal

Validate public signing-key discovery when this origin operates signed bots or agents whose requests other sites can verify.

Result

Web Bot Auth request signing failed at "Validate directory media type".

Validation steps

  1. Validate directory media type

    Content-Type "text/html; charset=utf-8" is not valid for a Web Bot Auth signing key directory.

  2. Validate public signing keys

    Directory body is not valid JSON.

    Directory body is not valid JSON.

  3. Inspect directory response signature binding

    The directory response is not signed with RFC 9421 Signature and Signature-Input headers.

Evidence log3 steps · 12 lines
Validate directory media type [fail]! Content-Type "text/html; charset=utf-8" is not valid for a Web Bot Auth signing key directory.INFOValidate directory media type status="fail"INFORead directory Content-Type header contentType="text/html; charset=utf-8"FAILCompare directory media type actual="text/html; charset=utf-8" expected="application/http-message-signatures-directory+json" compatible=false draftConformant=falseFAILContent-Type "text/html; charset=utf-8" is not valid for a Web Bot Auth signing key directory.Validate public signing keys [fail]! Directory body is not valid JSON.INFOValidate public signing keys status="fail"INFOParse directory body as JWKS parsed=false parseError="Unexpected token '<', \"<!DOCTYPE \"... is not valid JSON"FAILCheck public signing keys actual="0 valid of 0 keys" expected="at least 1 valid public key and no key failures"FAILDirectory body is not valid JSON.Inspect directory response signature binding [warning]! The directory response is not signed with RFC 9421 Signature and Signature-Input headers.INFOInspect directory response signature binding status="warning"INFOInspect RFC 9421 response signature headers signatureHeaderPresent=false signatureInputHeaderPresent=false labels=[]WARNCheck required signature binding parameters actual={} expected="Signature, Signature-Input, directory tag, keyid, created, and expires"WARNThe directory response is not signed with RFC 9421 Signature and Signature-Input headers.

AI DiscoverabilityBot Access ControlInformational

Content Signal

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

10 Warning

Needs attention

Content Signal

Warning
01

Issue

No Content-Usage or Content-Signal declarations were found.

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

50/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

    No Content-Usage or Content-Signal declarations were found.

Evidence log1 step · 5 lines
Validate declared usage preferences [warning]! No Content-Usage or Content-Signal declarations were found.INFOValidate declared usage preferencesINFOParsing declared preferences into terms and values recordCount=0SKIPSkipping declaration validation because no Content-Usage or Content-Signal records were declared.SKIPCompare declared records to validation requirement actual=0 expected="No validation needed when no records are declared"WARNNo Content-Usage or Content-Signal declarations were present.

AI DiscoverabilityBot Access ControlEmerging recommendation

RSL license signal

No RSL declarations were found.

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

Organization / WebSite schema

Organization / WebSite schema is partially implemented.

9 Warning

Needs attention

Organization / WebSite schema

Warning
01

Issue

No WebSite entity was found in Schema.org structured data. WebSite.publisher is missing.

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

48/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

Identify the site owner and website entity in structured data.

Result

Organization / WebSite schema is partially implemented.

Validation steps

  1. WebSite entity

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

  2. Identity fields

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

  3. WebSite publisher linkage

    WebSite.publisher is missing.

Evidence log3 steps · 14 lines
WebSite 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 [warning]! Missing identity field(s): WebSite.name, WebSite.url.INFOIdentity fieldsINFOChecking Organization and WebSite name/url fields organizationFormat="json-ld"WARNCheck required identity fields actual=2 expected=4 missing=["WebSite.name","WebSite.url"] organizationFields=[{"name":"Organization.@type","present":true,"value":"Organization","format":"json-ld"},{"name":"Organization.@id","present":false,"format":"json-ld"},{"name":"Organization.name","present":true,"value":"ETLR","format":"json-ld"},{"name":"Organization.url","present":true,"value":"https://etlr.io","format":"json-ld"},{"name":"Organization.logo","present":true,"value":"https://etlr.io/favicons/apple-touch-icon.png","format":"json-ld"},{"name":"Organization.sameAs","present":true,"value":"https://github.com/ETLR-io","format":"json-ld"}] 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":true,"websiteUrlMatchesOrigin":false} expected={"organizationUrlMatchesOrigin":true,"websiteUrlMatchesOrigin":true}WARNIdentity fields are partially complete missing=["WebSite.name","WebSite.url"]WebSite publisher linkage [fail]! WebSite.publisher is missing.INFOWebSite publisher linkageINFOChecking whether WebSite.publisher points to the Organization entity organizationFormat="json-ld"FAILCheck publisher presence actual=false expected=true publisher={"present":false,"matchesOrganization":false} website={} organization={"name":"ETLR","url":"https://etlr.io"}FAILCheck publisher matches Organization actual=false expected=trueFAILWebSite publisher is missing

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Citable passages

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

8 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

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: Citable passages scored 35/100 and needs a fix.

AI DiscoverabilityContent ReadinessEmerging recommendation

llms.txt

llms.txt failed at "Validate Markdown discovery shape".

7 Fail

Needs attention

llms.txt

Failed check
01

Issue

llms.txt did not provide the minimum expected Markdown discovery shape.

Details

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

58/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 "Validate Markdown discovery shape".

Validation steps

  1. Validate Markdown discovery shape

    llms.txt did not provide the minimum expected Markdown discovery shape.

    Findings
    • Content-Type "text/html; charset=utf-8" is not text/markdown, another Markdown type, or text/plain.
    • Response looks like an HTML page rather than a Markdown/text llms.txt file.
    • Missing H1 title, such as '# Example Docs'.
  2. Score llms.txt structure and usefulness

    llms.txt is present, but its structure or link curation is weaker than the emerging proposal and production examples.

    Findings
    • Missing a blockquote summary. The llms.txt proposal recommends a concise blockquote after the H1.
    • Missing H2 sections for grouping important links.
    • No Markdown-formatted links were found.
    • Several links have vague labels or raw URL labels.
    • {
        "truncated": true,
        "omittedCount": 1,
        "originalCount": 5
      }
  3. Inspect optional llms-full.txt

    Passed.

Evidence log3 steps · 21 lines
Validate Markdown discovery shape [fail]! llms.txt did not provide the minimum expected Markdown discovery shape.INFOValidate Markdown discovery shapeINFOChecking response compatibility, title, content length, and usable linksFAILCheck content type is Markdown-compatible text actual="text/html; charset=utf-8" expected="text/markdown, text/x-markdown, text/plain, or another Markdown text type"FAILCheck response is not HTML actual=true expected=falseFAILCheck H1 title is present actual=false expected=truePASSCheck minimum text length actual=71279 expected=">= 160"PASSCheck at least one usable public link actual=35 expected="> 0" linkCount=35FAILMarkdown discovery shape validation failedScore llms.txt structure and usefulness [warning]! llms.txt is present, but its structure or link curation is weaker than the emerging proposal and production examples.INFOScore llms.txt structure and usefulnessINFOChecking recommended summary, sections, link labels, agent-friendly links, duplicates, and unsafe targetsWARNCheck blockquote summary is present actual=false expected=trueWARNCheck H2 section count actual=0 expected="> 0"WARNCheck Markdown-formatted links actual=0 expected="> 0"PASSCheck unsafe/private link count actual=0 expected=0WARNllms.txt structure-quality validation completed with warnings reason="llms.txt is present, but its structure or link curation is weaker than the emerging proposal and production examples."Inspect optional llms-full.txt [informational]INFOInspect optional llms-full.txtINFOTrying to fetch /llms-full.txt url="https://etlr.io/llms-full.txt"PASS/llms-full.txt returned HTTP 2xx statusCode=200 contentType="text/html; charset=utf-8" length=73253WARNCheck llms-full.txt content type is Markdown-compatible text actual="text/html; charset=utf-8" expected="text/markdown, text/x-markdown, text/plain, or another Markdown text type"PASSCheck llms-full.txt looks like supplemental full corpus content actual=true expected=truePASSOptional llms-full.txt inspection recorded

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first passages

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

7 Fail

Needs attention

AEO: Answer-first passages

Failed check
01

Issue

14 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

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Structured extraction

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

4 Warning

Needs attention

GEO: Structured extraction

Warning
01

Issue

Missing or weak extraction signals: clean heading hierarchy, summary or key takeaways, FAQ or question-answer section where appropriate.

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: Source and trust signals

GEO: Source and trust signals scored 67/100 and needs improvement.

4 Warning

Needs attention

GEO: Source and trust signals

Warning
01

Issue

Missing source or trust signals: freshnessDate, sourceLinks.

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

67/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: Source and trust signals scored 67/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Source and trust signals

AIO: Source and trust signals scored 67/100 and needs improvement.

3 Warning

Needs attention

AIO: Source and trust signals

Warning
01

Issue

Missing AIO trust signals: publisher, freshnessDate.

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

67/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: Source and trust signals scored 67/100 and needs improvement.

AI DiscoverabilityContent ReadinessEstablished

Semantic HTML

Semantic HTML is partially implemented.

3 Warning

Needs attention

Semantic HTML

Warning
01

Issue

Semantic HTML is incomplete: skipped or empty headings.

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

82/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. Heading structure

    Headings skip levels or include empty heading elements.

Evidence log1 step · 3 lines
Heading structure [fail]! Headings skip levels or include empty heading elements.INFOHeading structureFAILCheck heading structure evidence actual={"counts":{"h1":1,"visibleH1":1,"headings":37,"emptyHeadings":0},"meaningfulH1":true} expected="semantic HTML evidence for this step"FAILHeading structure failed issue="Headings skip levels or include empty heading elements."

AI DiscoverabilityContent ReadinessEstablished

Structured data

Structured data failed at "Page-relevant schema family".

3 Fail

Needs attention

Structured data

Failed check
01

Issue

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

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

83/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 "Page-relevant schema family".

Validation steps

  1. Page-relevant schema family

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

Evidence log1 step · 4 lines
Page-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=["event"] expectedTypes=["Event","BroadcastEvent"] matchingTypes=[] observedTypes=["Organization"]FAILNo primary schema family matches the inferred page intent expectedTypes=["Event","BroadcastEvent"] primaryTypes=[]

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Evidence and trust

AEO: Evidence and trust scored 71/100 and needs improvement.

3 Warning

Needs attention

AEO: Evidence and trust

Warning
01

Issue

Missing answer evidence or trust signals: publisher, freshnessDate.

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

71/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: Evidence and trust scored 71/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Page experience proxy

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

2 Warning

Needs attention

AIO: Page experience proxy

Warning
01

Issue

8 image(s) are missing width/height attributes.

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

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Visible content clarity

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

2 Warning

Needs attention

AIO: Visible content clarity

Warning
01

Issue

14 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

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

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

1 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

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

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

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question and answer structure

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

1 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

87/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 87/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

Background and foreground colors do not have a sufficient contrast ratio.

50 Fail

Check name

Background and foreground colors do not have a sufficient contrast ratio.

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast](https://dequeuniversity.com/rules/axe/4.11/color-contrast).

Evidence
{
  "description": "Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast](https://dequeuniversity.com/rules/axe/4.11/color-contrast)."
}

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 AccessibilityPerformanceBrowser audit

Image elements do not have explicit `width` and `height`

25 Warning

Check name

Image elements do not have explicit `width` and `height`

Score

50/100

Status

warning

Device

desktop

Category

Performance

Fix guidance

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. [Learn how to set image dimensions](https://web.dev/articles/optimize-cls#images_without_dimensions)

Evidence
{
  "description": "Set an explicit width and height on image elements to reduce layout shifts and improve CLS. [Learn how to set image dimensions](https://web.dev/articles/optimize-cls#images_without_dimensions)"
}

Performance and AccessibilityPerformanceBrowser audit

Use efficient cache lifetimes

25 Warning

Check name

Use efficient cache lifetimes

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 5 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 5 KiB"
}

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