Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 56 out of 100
- Agent Ease of Use 50 out of 100
- Security & Trust 57 out of 100
- GEO, AIO and AEO 56 out of 100
- SEO 83 out of 100
- Performance and Accessibility 68 out of 100
What AI sees of your website
Website Change Monitoring | PageCrawl.io
Track website changes with AI summaries and deliver scheduled reports to stakeholders. Group monitors by tag, folder, or domain and send daily, weekly, or monthly digests. Trusted by thousands of companies since 2018.
Next step
Turn this report into a fix workflow
20 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.
| Metric | Score | Status | Passed | Failed | Warning | Evidence |
|---|---|---|---|---|---|---|
| AI Discoverability | 56 | Needs work | 35 | 17 | 8 | View details |
| Discoverability | 67 | Needs work | 8 | 2 | 0 | View details |
| Content Readiness | 61 | Needs work | 21 | 8 | 5 | View details |
| Bot Access Control | 44 | Priority fix | 6 | 7 | 3 | View details |
| Agent Ease of Use | 50 | Needs work | 35 | 22 | 20 | View details |
| API | 65 | Needs work | 9 | 4 | 2 | View details |
| Auth | 64 | Needs work | 9 | 2 | 4 | View details |
| MCP | 42 | Priority fix | 4 | 5 | 2 | View details |
| Skill Discovery | 47 | Priority fix | 6 | 6 | 8 | View details |
| Agent Commerce | 45 | Priority fix | 7 | 5 | 4 | View details |
| GEO, AIO and AEO | 56 | Needs work | 6 | 2 | 10 | View details |
| GEO Readiness | 52 | Needs work | 2 | 1 | 3 | View details |
| AIO Readiness | 66 | Needs work | 2 | 0 | 4 | |
| AEO Readiness | 51 | Needs work | 2 | 1 | 3 | View details |
| SEO | 83 | Mostly ready | 7 | 2 | 0 | View details |
| SEO | 83 | Mostly ready | 7 | 2 | 0 | View details |
| Security & Trust | 57 | Needs work | 9 | 3 | 6 | View details |
| Security & Trust | 57 | Needs work | 9 | 3 | 6 | View details |
| Performance and Accessibility | 68 | Needs work | 22 | 4 | 1 | View details |
| Performance | 55 | Needs work | 15 | 4 | 1 | View details |
| Accessibility | 91 | Strong | 7 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
49 items need attention
AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
100 Fail
AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
Needs attention
Link headers
Issue
No useful agent discovery Link headers were found.
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
Find useful Link headers
No useful agent discovery Link headers were found.
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
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog media type".
Needs attention
API Catalog
Issue
Content-Type "text/html; charset=utf-8" is not valid for an RFC 9727 API catalog.
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
Check API catalog HEAD Link header
HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".
Validate API catalog media type
Content-Type "text/html; charset=utf-8" is not valid for an RFC 9727 API catalog.
Validate Linkset shape
Unexpected token '<', "<!doctype "... is not valid JSON
Unexpected token '<', "<!doctype "... is not valid JSON
Classify API catalog relations
API catalog did not include API endpoint links or useful API discovery relations.
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 UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Validate server-card shape".
30 Fail
Agent Ease of UseMCPEmerging recommendation
MCP Server Card
MCP Server Card failed at "Validate server-card shape".
Needs attention
MCP Server Card
Issue
MCP Server Card response is not valid JSON.
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
Validate server-card shape
MCP Server Card response is not valid JSON.
Validate MCP remotes
No usable MCP remote transport was declared.
Validate HTTP delivery
Content-Type "text/html; charset=utf-8" is not JSON.
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://pagecrawl.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:"WARNCheck browser-readable CORS header actual="missing" expected="Access-Control-Allow-Origin present"PASSCheck cache header is present actual="no-cache, private" expected="Cache-Control present"FAILMCP server-card HTTP delivery failed issues=["Content-Type \"text/html; charset=utf-8\" is not JSON.","CORS header Access-Control-Allow-Origin is absent."] 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
Agent Ease of UseMCPEmerging recommendation
WebMCP
WebMCP failed at "Probe WebMCP operability".
Needs attention
WebMCP
Issue
Discovered WebMCP static metadata was fetchable but invalid.
Details
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
Detect WebMCP runtime API
WebMCP-like strings were found, but rendered browser evidence did not confirm a usable runtime API.
Probe WebMCP operability
Discovered WebMCP static metadata was fetchable but invalid.
WebMCP operability findings
- Discovered WebMCP static metadata was fetchable but invalid.
Validate declarative WebMCP form tools
No W3C-style declarative WebMCP form attributes were found.
Validate MCP-aware HTML annotations
No data-mcp-tool or hyphenated WebMCP compatibility annotations were found.
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://pagecrawl.io/.well-known/webmcp.json" statusCode=200 contentType="text/html; charset=utf-8"PASSWebMCP manifest candidate found source="path" path="/webmcp.json" url="https://pagecrawl.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.
AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation is missing or incomplete.
23 Fail
AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation is missing or incomplete.
Needs attention
Markdown negotiation
Issue
Best candidate returned Content-Type "text/html; charset=utf-8" instead of text/markdown.
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
Markdown representation
No usable Markdown representation was found through negotiation, advertised alternates, or conservative .md mirror checks.
Same-URL negotiation
Same-URL Accept: text/markdown did not return a valid Markdown representation.
Markdown format validation
Markdown response appears to expose MDX/JSX source rather than rendered agent-facing Markdown.
Advertised Markdown alternate
No Link or HTML rel=alternate text/markdown URL was advertised.
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://pagecrawl.io/","statusCode":200,"contentType":"text/html; charset=utf-8","mediaType":"text/html","vary":"","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"fail","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"mdx-like","hasHeading":false,"headingCount":0,"wordCount":888669,"features":{"markdownLinks":1787,"referenceLinks":0,"listItems":0,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":2437,"jsxOrMdxSignals":2},"issues":["missing-heading","raw-html-heavy","mdx-jsx-source-leakage"],"excerpt":"<!doctype html>\n<html lang=\"en\" class=\"web-app\">\n<head>\n <meta charset=\"utf-8\">\n <meta http-equiv=\"X-UA-Compatible\" content=\"IE=edge\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0, viewport-fit=cover\">","issue":"Markdown response appears to expose MDX/JSX source rather than rendered agent-facing Markdown."}} expected="negotiated, advertised alternate, or conventional mirror" selected={"source":"negotiated","url":"https://pagecrawl.io/","statusCode":200,"contentType":"text/html; charset=utf-8","mediaType":"text/html","vary":"","requireVaryAccept":true,"contentTypeStatus":"fail","cacheStatus":"fail","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"mdx-like","hasHeading":false,"headingCount":0,"wordCount":888669,"features":{"markdownLinks":1787,"referenceLinks":0,"listItems":0,"tables":0,"taskListItems":0,"fencedCodeBlocks":0,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":2437,"jsxOrMdxSignals":2},"issues":["missing-heading","raw-html-heavy","mdx-jsx-source-leakage"],"excerpt":"<!doctype html>\n<html lang=\"en\" class=\"web-app\">\n<head>\n <meta charset=\"utf-8\">\n <meta http-equiv=\"X-UA-Compatible\" content=\"IE=edge\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0, viewport-fit=cover\">","issue":"Markdown response appears to expose MDX/JSX source rather than rendered agent-facing Markdown."}} 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":""} expected="HTTP 2xx text/markdown with Vary: Accept" url="https://pagecrawl.io/" statusCode=200 mediaType="text/html"FAILSame-URL negotiation failed issue="Same-URL Accept: text/markdown did not return a valid Markdown representation."Markdown format validation [fail]! Markdown response appears to expose MDX/JSX source rather than rendered agent-facing Markdown.INFOMarkdown format validationFAILCheck Markdown body quality actual={"valid":false,"wordCount":888669,"headingCount":0,"dialect":"mdx-like"} expected="valid Markdown with substantive text and headings" valid=false dialect="mdx-like" wordCount=888669 headingCount=0FAILMarkdown format validation failed issue="Markdown response appears to expose MDX/JSX source rather than rendered agent-facing Markdown."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://pagecrawl.io/index.html.md"] candidateCount=1FAILConventional .md mirror failed issue="Conventional .md mirror candidates did not return valid Markdown."
Agent Ease of UseAgent CommerceInformational
Universal Commerce Protocol
Universal Commerce Protocol failed at "Fetch UCP profile".
21 Fail
Agent Ease of UseAgent CommerceInformational
Universal Commerce Protocol
Universal Commerce Protocol failed at "Fetch UCP profile".
Needs attention
Universal Commerce Protocol
Issue
UCP profile content type "text/html; charset=utf-8" is not JSON-compatible.
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
Fetch UCP profile
UCP profile content type "text/html; charset=utf-8" is not JSON-compatible.
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.
AI DiscoverabilityBot Access ControlEmerging recommendation
TDMRep declaration
TDMRep declaration failed at "Fetch /.well-known/tdmrep.json".
20 Fail
AI DiscoverabilityBot Access ControlEmerging recommendation
TDMRep declaration
TDMRep declaration failed at "Fetch /.well-known/tdmrep.json".
Needs attention
TDMRep declaration
Issue
Response is not valid JSON.
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
Fetch /.well-known/tdmrep.json
Response is not valid JSON.
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=5953503FAILResponse 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
Agent Ease of UseAgent CommerceInformational
ACP - Agentic Commerce Protocol
ACP - Agentic Commerce Protocol failed at "Fetch ACP discovery".
19 Fail
Agent Ease of UseAgent CommerceInformational
ACP - Agentic Commerce Protocol
ACP - Agentic Commerce Protocol failed at "Fetch ACP discovery".
Needs attention
ACP - Agentic Commerce Protocol
Issue
ACP discovery content type "text/html; charset=utf-8" is not JSON-compatible.
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
42/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
Fetch ACP discovery
ACP discovery content type "text/html; charset=utf-8" is not JSON-compatible.
Validate ACP discovery shape
ACP discovery could not be parsed.
Review ACP cache and retry metadata
ACP discovery Cache-Control does not include max-age.
Evidence log3 steps · 14 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.Review ACP cache and retry metadata [warning]! ACP discovery Cache-Control does not include max-age.INFOReview ACP cache and retry metadata status="warning"INFOInspect ACP discovery cache headers and retry guidance statusCode=200 cacheControl="no-cache, private" retryAfter=nullWARNCheck Cache-Control header on successful discovery actual="no-cache, private" expected="present for cacheable public discovery"WARNCheck Retry-After on rate-limit or unavailable responses actual="not required" expected="present only for 429 or 503"WARNACP discovery Cache-Control does not include max-age.
Agent Ease of UseAuthEmerging recommendation
Auth.md Agent Registration
Auth.md Agent Registration failed at "Fetch and validate /auth.md".
17 Fail
Agent Ease of UseAuthEmerging recommendation
Auth.md Agent Registration
Auth.md Agent Registration failed at "Fetch and validate /auth.md".
Needs attention
Auth.md Agent Registration
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.
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
48/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
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.
Validate Auth.md authorization metadata
OAuth authorization-server metadata did not include usable Auth.md v1 fields. agent_registration_endpoint issues: [{"field":"agent_registration_endpoint","issue":"Expected an absolute HTTPS URL."}]; missing credential_types_supported.
Evidence log2 steps · 14 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.INFOFetch and validate /auth.mdINFOFetch Auth.md-related resource path="/auth.md" statusCode=200 contentType="text/html; charset=utf-8" bytes=5953503FAILCompare 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=5825615 expected=">= 80 characters"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."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.Validate Auth.md authorization metadata [warning]! OAuth authorization-server metadata did not include usable Auth.md v1 fields. agent_registration_endpoint issues: [{"field":"agent_registration_endpoint","issue":"Expected an absolute HTTPS URL."}]; missing credential_types_supported.INFOValidate Auth.md authorization metadataINFOFetch Auth.md-related resource path="/.well-known/oauth-authorization-server" statusCode=200 contentType="application/json" bytes=399WARNCompare response Content-Type with expected Auth.md media type actual=true expected=trueWARNCompare Auth.md/OAuth metadata validation result actual=false expected=trueWARNCompare supported credential type count actual=0 expected="> 0"WARNAuth.md validation issue issue="OAuth authorization-server metadata did not include usable Auth.md v1 fields. agent_registration_endpoint issues: [{\"field\":\"agent_registration_endpoint\",\"issue\":\"Expected an absolute HTTPS URL.\"}]; missing credential_types_supported."WARNOAuth authorization-server metadata did not include usable Auth.md v1 fields. agent_registration_endpoint issues: [{"field":"agent_registration_endpoint","issue":"Expected an absolute HTTPS URL."}]; missing credential_types_supported.
Agent Ease of UseSkill DiscoveryEmerging recommendation
agents.json
agents.json failed at "Validate Wildcard schema shape".
16 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
agents.json
agents.json failed at "Validate Wildcard schema shape".
Needs attention
agents.json
Issue
agents.json response is not valid JSON.
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
Validate Wildcard schema shape
agents.json response is not valid JSON.
Validate API actions
Wildcard agents.json must include valid OpenAPI-derived action or operation definitions.
Validate flows and links
No executable flows were found.
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 DiscoverabilityBot Access ControlEmerging recommendation
ai.txt policy
ai.txt policy failed at "Validate transport".
16 Fail
AI DiscoverabilityBot Access ControlEmerging recommendation
ai.txt policy
ai.txt policy failed at "Validate transport".
Needs attention
ai.txt policy
Issue
ai.txt appears to be an HTML page or error document rather than a plain-text policy.
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
20/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
Validate transport
ai.txt appears to be an HTML page or error document rather than a plain-text policy.
Parse ai.txt policy
Transport validation failed before policy parsing could be trusted.
Validate policy content
ai.txt contains prompt-injection style instructions instead of policy guidance.
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=5953503 lineCount=196FAILCompare 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="unknown-text" 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 [fail]! ai.txt contains prompt-injection style instructions instead of policy guidance.INFOValidate policy contentINFOChecking required section content, permission/restriction language, attribution, contact details, and safety risks convention="unknown-text"INFODetected policy signals hasPermissionLanguage=true hasRestrictionLanguage=true hasTrainingLanguage=true hasAttributionLanguage=true hasContact=falseFAILCheck required and recommended section coverage actual={"missingRequired":["identity","permissions","restrictions"],"missingRecommended":["attribution","contact","content-types"]} expected={"missingRequired":[],"recommendedPresentWhenPossible":true}FAILai.txt contains prompt-injection style instructions instead of policy guidance. promptInjectionPhrases=["you are now","You are now","system prompt"]
Agent Ease of UseAgent CommerceEmerging recommendation
x402 Protocol
x402 Protocol failed at "Probe x402 runtime response".
15 Fail
Agent Ease of UseAgent CommerceEmerging recommendation
x402 Protocol
x402 Protocol failed at "Probe x402 runtime response".
Needs attention
x402 Protocol
Issue
x402 candidate routes were found, but none returned HTTP 402 before payment.
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
Probe x402 runtime response
x402 candidate routes were found, but none returned HTTP 402 before payment.
Validate x402 V2 headers
No x402 runtime response was available for header validation.
Validate x402 payment requirement payload
No x402 runtime response was available for payload validation.
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://pagecrawl.io/" headers={} textSample="<!doctype html> <html lang=\"en\" class=\"web-app\"> <head> <meta charset=\"utf-8\"> <meta http-equiv=\"X-UA-Compatible\" content=\"IE=edge\"> <meta name=\"viewport\" content=\"width=device-wid"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=["Payment Required","Payment Required","Payment Required","Payment Required"] wellKnown={"found":true,"statusCode":200,"contentType":"text/html; charset=utf-8","markers":["Payment Required"],"candidateCount":1} runtime402=falseWARNCheck runtime 402 evidence against metadata actual={"openApiSignals":["Payment Required","Payment Required","Payment Required","Payment Required"],"wellKnown":{"found":true,"statusCode":200,"contentType":"text/html; charset=utf-8","markers":["Payment Required"],"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 UseAuthEstablished
OAuth / OIDC discovery
OAuth / OIDC discovery failed at "Validate metadata profile".
14 Fail
Agent Ease of UseAuthEstablished
OAuth / OIDC discovery
OAuth / OIDC discovery failed at "Validate metadata profile".
Needs attention
OAuth / OIDC discovery
Issue
Response is not valid JSON.
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
58/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
Validate metadata profile
Response is not valid JSON.
Validate discovery CORS
Discovery metadata did not include Access-Control-Allow-Origin: *, so browser-based clients may be unable to fetch it cross-origin.
Evidence log2 steps · 10 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."Validate discovery CORS [warning]! Discovery metadata did not include Access-Control-Allow-Origin: *, so browser-based clients may be unable to fetch it cross-origin.INFOValidate discovery CORSINFOChecking whether browser clients can read the public discovery document profile="unknown" corsPresent=trueWARNCheck Access-Control-Allow-Origin header actual="missing" expected="present or wildcard for browser-readable discovery"WARNValidate discovery CORS completed with warnings issue="Discovery metadata did not include Access-Control-Allow-Origin: *, so browser-based clients may be unable to fetch it cross-origin."
Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Detect A2A card version".
13 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Detect A2A card version".
Needs attention
A2A Agent Card
Issue
The discovered JSON document does not match a supported A2A Agent Card version family.
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
Detect A2A card version
The discovered JSON document does not match a supported A2A Agent Card version family.
Validate version-specific card shape
A2A Agent Card response is not valid JSON.
Validate HTTP delivery
The card was parseable JSON but was not served with a JSON-compatible content type.
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.
AI DiscoverabilityContent ReadinessEstablished
Organization / WebSite schema
Organization / WebSite schema is partially implemented.
13 Warning
AI DiscoverabilityContent ReadinessEstablished
Organization / WebSite schema
Organization / WebSite schema is partially implemented.
Needs attention
Organization / WebSite schema
Issue
No WebSite entity was found in Schema.org structured data. WebSite.publisher is missing.
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
WebSite entity
No WebSite entity was found in Schema.org structured data.
Identity fields
Missing identity field(s): WebSite.name, WebSite.url.
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":"PageCrawl.io","format":"json-ld"},{"name":"Organization.url","present":true,"value":"https://pagecrawl.io","format":"json-ld"},{"name":"Organization.logo","present":true,"value":"https://pagecrawl.io/images/logo.png","format":"json-ld"},{"name":"Organization.sameAs","present":true,"value":["https://www.g2.com/products/pagecrawl-io/reviews","https://www.producthunt.com/products/pagecrawl"],"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":"PageCrawl.io","url":"https://pagecrawl.io"}FAILCheck publisher matches Organization actual=false expected=trueFAILWebSite publisher is missing
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
Agent Ease of UseSkill DiscoveryEmerging recommendation
DNS-AID Agent Discovery
DNS-AID Agent Discovery has a validation warning at "Query DNS-AID records".
Needs attention
DNS-AID Agent Discovery
Issue
No DNS-AID HTTPS/SVCB records were found under _agents.
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
Query DNS-AID records
No DNS-AID HTTPS/SVCB records were found under _agents.
Check DNSSEC authentication evidence
DNSSEC material was visible, but authenticated-data was not confirmed for these resolver answers.
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="pagecrawl.io" labels=["_index._agents.pagecrawl.io","_a2a._agents.pagecrawl.io"] claimedOnPage=falseWARNDNS query returned no DNS-AID answers name="_index._agents.pagecrawl.io" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=0 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.pagecrawl.io" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=0 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.pagecrawl.io" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _index._agents.pagecrawl.io"WARNDNS query returned no DNS-AID answers name="_a2a._agents.pagecrawl.io" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=0 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.pagecrawl.io" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=0 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.pagecrawl.io" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _a2a._agents.pagecrawl.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 material was visible, but authenticated-data was not confirmed for these resolver answers.INFOCheck DNSSEC authentication evidenceWARNCompare DNSSEC authenticated-data flag actual=false expected=trueWARNCompare visible DNSSEC material actual=true expected=trueWARNResolver did not confirm authenticated DNSSEC data name="_index._agents.pagecrawl.io" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.pagecrawl.io" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.pagecrawl.io" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.pagecrawl.io" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.pagecrawl.io" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.pagecrawl.io" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.pagecrawl.io" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.pagecrawl.io" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="pagecrawl.io" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=["DNSKEY","DNSKEY","RRSIG"]WARNDNSSEC material was visible, but authenticated-data was not confirmed for these resolver answers.
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Find enforcing CSP delivery".
12 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Find enforcing CSP delivery".
Needs attention
Content-Security-Policy
Issue
Applicable HTML response is missing an enforcing Content-Security-Policy header.
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
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.Agent Ease of UseSkill DiscoveryEmerging recommendation
Agent Skills index
Agent Skills index failed at "Validate discovery index schema".
11 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
Agent Skills index
Agent Skills index failed at "Validate discovery index schema".
Needs attention
Agent Skills index
Issue
Agent Skills index was not served with a JSON-compatible Content-Type.
Details
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
Validate discovery index schema
Agent Skills index was not served with a JSON-compatible Content-Type.
Response is not valid JSON.
Verify advertised artifacts
No valid skill artifacts were available to verify.
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.
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 DiscoverabilityContent ReadinessEstablished
Author attribution
Author attribution is partially implemented.
11 Warning
AI DiscoverabilityContent ReadinessEstablished
Author attribution
Author attribution is partially implemented.
Needs attention
Author attribution
Issue
No named author or publisher identity could be extracted.
Why it matters
Author attribution helps agents cite content responsibly, assess source credibility, and distinguish editorial pages from anonymous marketing copy.
Check name
Author attribution
Score
55/100
Status
warning
Category
Content Readiness
Maturity
Established
Goal
Identify content authors or publishers for trust and attribution.
Result
Author attribution is partially implemented.
Validation steps
Schema.org attribution
Schema.org attribution is incomplete or relies only on publisher/fallback evidence.
Author identity quality
No named author or publisher identity could be extracted.
Evidence log2 steps · 8 lines
Schema.org attribution [warning]! Schema.org attribution is incomplete or relies only on publisher/fallback evidence.INFOSchema.org attributionINFOChecking structured data for author, creator, and publisher contributorsWARNCheck named Schema.org author count actual=0 expected="> 0" authorCount=0 publisherCount=0 namedContributors=0 authors=[] publishers=[] formats=[]WARNSchema.org attribution is incomplete or fallback-only authorCount=0 publisherCount=0 authors=[] publishers=[]Author identity quality [fail]! No named author or publisher identity could be extracted.INFOAuthor identity qualityINFOChecking contributors for stable identity signalsFAILCheck identified contributor count actual=0 expected="> 0" namedContributors=0 identifiedContributors=[] unidentifiedContributors=[]FAILNo named contributor identity could be extracted
Security & TrustSecurity & TrustEstablished
Frame protection
Frame protection failed at "Validate X-Frame-Options".
11 Fail
Security & TrustSecurity & TrustEstablished
Frame protection
Frame protection failed at "Validate X-Frame-Options".
Needs attention
Frame protection
Issue
X-Frame-Options is not DENY or SAMEORIGIN.
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
Validate CSP frame-ancestors
No enforcing CSP frame-ancestors directive is present.
Validate X-Frame-Options
X-Frame-Options is not DENY or SAMEORIGIN.
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]! X-Frame-Options is not DENY or SAMEORIGIN.INFOValidate X-Frame-OptionsINFORead X-Frame-Options fallback value="SAMEORIGIN SAMEORIGIN" parsedValues=["SAMEORIGIN SAMEORIGIN"] normalizedValues=["sameorigin sameorigin"]FAILCompare X-Frame-Options value actual="invalid" expected="DENY or SAMEORIGIN" valid=false obsoleteAllowFrom=false duplicateOrConflicting=false issue="X-Frame-Options is not DENY or SAMEORIGIN."FAILX-Frame-Options is not DENY or SAMEORIGIN.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=48 sameOriginCount=38 htmlDocumentCount=1WARNCompare observed HTML frame protection actual={"missingOrInvalidFrameProtectionCount":1,"broadFrameAncestorsCount":0,"affected":[{"url":"https://pagecrawl.io/","status":200,"resourceType":"document","contentType":"text/html; charset=utf-8","contentSecurityPolicy":null,"contentSecurityPolicyReportOnly":null,"xFrameOptions":"SAMEORIGIN SAMEORIGIN"}]} 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.
AI DiscoverabilityBot Access ControlInformational
Web Bot Auth request signing
Web Bot Auth request signing failed at "Validate directory media type".
11 Fail
AI DiscoverabilityBot Access ControlInformational
Web Bot Auth request signing
Web Bot Auth request signing failed at "Validate directory media type".
Needs attention
Web Bot Auth request signing
Issue
Content-Type "text/html; charset=utf-8" is not valid for a Web Bot Auth signing key directory.
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
Validate directory media type
Content-Type "text/html; charset=utf-8" is not valid for a Web Bot Auth signing key directory.
Validate public signing keys
Directory body is not valid JSON.
Directory body is not valid JSON.
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.
Security & TrustSecurity & TrustEstablished
HSTS header
HSTS header failed at "Find Strict-Transport-Security".
10 Fail
Security & TrustSecurity & TrustEstablished
HSTS header
HSTS header failed at "Find Strict-Transport-Security".
Needs attention
HSTS header
Issue
HTTPS response is missing Strict-Transport-Security.
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
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.AI DiscoverabilityBot Access ControlInformational
Content Signal
Content Signal has a validation warning at "Validate declared usage preferences".
10 Warning
AI DiscoverabilityBot Access ControlInformational
Content Signal
Content Signal has a validation warning at "Validate declared usage preferences".
Needs attention
Content Signal
Issue
No Content-Usage or Content-Signal declarations were found.
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
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
AI DiscoverabilityBot Access ControlEmerging recommendation
RSL license signal
No RSL declarations were found.
Needs attention
RSL license signal
Issue
No RSL declarations were found.
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
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.GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Citable passages
GEO: Citable passages scored 0/100 and needs a fix.
9 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Citable passages
GEO: Citable passages scored 0/100 and needs a fix.
Needs attention
GEO: Citable passages
Issue
No evidence-backed, citation-length explanatory paragraph was found.
Details
Why it matters
Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.
Check name
GEO: Citable passages
Score
0/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.
Result
GEO: Citable passages scored 0/100 and needs a fix.
Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy has a validation warning at "Find Referrer-Policy header".
8 Warning
Security & TrustSecurity & TrustEstablished
Referrer-Policy
Referrer-Policy has a validation warning at "Find Referrer-Policy header".
Needs attention
Referrer-Policy
Issue
Referrer policy is present only in meta markup; send it as an HTTP response header.
Why it matters
Referrer-Policy controls how much URL context is sent to other origins, limiting accidental leakage of paths, queries, and identifiers.
Check name
Referrer-Policy
Score
60/100
Status
warning
Category
Security & Trust
Maturity
Established
Goal
Limit how much referrer data leaves the site with an explicit Referrer-Policy header.
Result
Referrer-Policy has a validation warning at "Find Referrer-Policy header".
Validation steps
Find Referrer-Policy header
Referrer policy is present only in meta markup; send it as an HTTP response header.
Review markup policy signals
Meta referrer policy is useful, but it is weaker evidence than an HTTP Referrer-Policy header.
Review observed browser responses
One or more same-origin HTML documents observed by Chrome did not emit Referrer-Policy.
Evidence log3 steps · 12 lines
Find Referrer-Policy header [warning]! Referrer policy is present only in meta markup; send it as an HTTP response header.INFOFind Referrer-Policy headerINFORead Referrer-Policy delivery header="referrer-policy" value="missing" metaReferrerPolicyCount=1 browserDefault="strict-origin-when-cross-origin"WARNRequire explicit HTTP Referrer-Policy header actual="meta only" expected="HTTP response header present" issue="Referrer policy is present only in meta markup; send it as an HTTP response header."WARNReferrer policy is present only in meta markup; send it as an HTTP response header.Review markup policy signals [warning]! Meta referrer policy is useful, but it is weaker evidence than an HTTP Referrer-Policy header.INFOReview markup policy signalsINFOInspect markup-level referrer controls metaCount=1 metaPolicies=[{"tokens":["strict-origin"],"effectivePolicy":"strict-origin","unknownTokens":[]}] referrerPolicyAttributeCount=0 noreferrerLinkCount=2WARNCompare markup controls with HTTP header actual="markup controls present" expected="supplemental only; HTTP header remains page default" issue="Meta referrer policy is useful, but it is weaker evidence than an HTTP Referrer-Policy header."WARNMeta referrer policy is useful, but it is weaker evidence than an HTTP Referrer-Policy header.Review observed browser responses [warning]! One or more same-origin HTML documents observed by Chrome did not emit Referrer-Policy.INFOReview observed browser responsesINFOSample Chrome-observed same-origin responses observedResponseCount=48 sameOriginCount=38 htmlDocumentCount=1WARNCompare observed Referrer-Policy coverage actual={"missingPolicyCount":1,"unsafeOrInvalidPolicyCount":0,"weakPolicyCount":0,"affected":[{"url":"https://pagecrawl.io/","status":200,"resourceType":"document","contentType":"text/html; charset=utf-8","referrerPolicy":null,"classification":"invalid"}]} expected="0 missing, unsafe, invalid, or weak same-origin HTML responses" issue="One or more same-origin HTML documents observed by Chrome did not emit Referrer-Policy."WARNOne or more same-origin HTML documents observed by Chrome did not emit Referrer-Policy.
AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is partially implemented.
8 Warning
AI DiscoverabilityContent ReadinessEstablished
Semantic HTML
Semantic HTML is partially implemented.
Needs attention
Semantic HTML
Issue
Semantic HTML is incomplete: skipped or empty headings; 6 image alt text quality issues.
Details
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
68/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
Heading structure
Headings skip levels or include empty heading elements.
Links
1 links use generic anchor text.
Image text alternatives
6 image alt text issues were found.
Evidence log3 steps · 9 lines
Heading structure [fail]! Headings skip levels or include empty heading elements.INFOHeading structureFAILCheck heading structure evidence actual={"counts":{"h1":1,"visibleH1":1,"headings":60,"emptyHeadings":0},"meaningfulH1":true} expected="semantic HTML evidence for this step"FAILHeading structure failed issue="Headings skip levels or include empty heading elements."Links [warning]! 1 links use generic anchor text.INFOLinksWARNCheck links evidence actual={"counts":{"links":140,"inaccessibleLinks":0,"nonCrawlableLinks":0,"genericLinks":1},"accessibleLinks":true} expected="semantic HTML evidence for this step"WARNLinks has a warning issue="1 links use generic anchor text."Image text alternatives [warning]! 6 image alt text issues were found.INFOImage text alternativesWARNCheck image text alternatives evidence actual={"counts":{"images":10,"imagesWithAlt":10,"imageAltIssues":6},"imageAltCoverage":true} expected="semantic HTML evidence for this step"WARNImage text alternatives has a warning issue="6 image alt text issues were found."
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first passages
AEO: Answer-first passages scored 33/100 and needs a fix.
6 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first passages
AEO: Answer-first passages scored 33/100 and needs a fix.
Needs attention
AEO: Answer-first passages
Issue
45 section(s) bury or omit a concise opening answer.
Details
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
33/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 33/100 and needs a fix.
Agent Ease of UseAuthEmerging recommendation
OAuth Protected Resource
OAuth Protected Resource has a validation warning at "Validate metadata shape".
5 Warning
Agent Ease of UseAuthEmerging recommendation
OAuth Protected Resource
OAuth Protected Resource has a validation warning at "Validate metadata shape".
Needs attention
OAuth Protected Resource
Issue
Access-Control-Allow-Origin is absent; browser-based clients may not be able to read metadata.
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
85/100
Status
warning
Category
Auth
Maturity
Emerging recommendation
Goal
Publish OAuth Protected Resource Metadata for OAuth-protected APIs and MCP resources so clients can identify the resource and its authorization servers.
Result
OAuth Protected Resource has a validation warning at "Validate metadata shape".
Validation steps
Validate metadata shape
Access-Control-Allow-Origin is absent; browser-based clients may not be able to read metadata.
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 log2 steps · 19 lines
Validate metadata shape [warning]! Access-Control-Allow-Origin is absent; browser-based clients may not be able to read metadata.INFOValidate metadata shapeINFOParsing and validating RFC 9728 protected-resource metadata valid=true compatibleContentType=true warningsCount=1 resource="https://pagecrawl.io" resourceIssuesCount=0 authorizationServersCount=1 authorizationServerIssuesCount=0 scopesSupportedCount=1 bearerMethodsSupportedCount=0PASSCheck metadata resource field is present actual="https://pagecrawl.io" expected="absolute protected resource identifier"PASSCheck required metadata field failures actual=0 expected=0 missing=[]WARNCheck protected-resource metadata is browser-readable and complete for OAuth clients actual="1 client-usage warning(s)" expected="no CORS, authorization-server, or compatibility warnings" warnings=["Access-Control-Allow-Origin is absent; browser-based clients may not be able to read metadata."]WARNProtected-resource metadata client-usage warning warning="Access-Control-Allow-Origin is absent; browser-based clients may not be able to read metadata."WARNValidate metadata shape completed with warnings issue="Access-Control-Allow-Origin is absent; browser-based clients may not be able to read metadata."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=8INFOChecked protected route challenge url="https://pagecrawl.io/use-cases/api-documentation-monitoring" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://pagecrawl.io/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://pagecrawl.io" metadataResource="https://pagecrawl.io" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://pagecrawl.io/help/integrations/article/mcp-server-ai-tools" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://pagecrawl.io/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://pagecrawl.io" metadataResource="https://pagecrawl.io" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://pagecrawl.io/help/features/article/api-webhooks-for-custom-integrations" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://pagecrawl.io/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://pagecrawl.io" metadataResource="https://pagecrawl.io" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://pagecrawl.io/mcp-server" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://pagecrawl.io/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://pagecrawl.io" metadataResource="https://pagecrawl.io" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://pagecrawl.io/api/scans" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://pagecrawl.io/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://pagecrawl.io" metadataResource="https://pagecrawl.io" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://pagecrawl.io/api/admin/scans" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://pagecrawl.io/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://pagecrawl.io" metadataResource="https://pagecrawl.io" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://pagecrawl.io/api/admin/summary" statusCode=200 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://pagecrawl.io/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://pagecrawl.io" metadataResource="https://pagecrawl.io" resourceMatches=true scopePresent=falseINFOChecked protected route challenge url="https://pagecrawl.io/mcp" statusCode=405 wwwAuthenticate={"valid":false,"present":false,"params":{}} expectedMetadataUrl="https://pagecrawl.io/.well-known/oauth-protected-resource" metadataUrlMatches=true expectedResource="https://pagecrawl.io" metadataResource="https://pagecrawl.io" resourceMatches=true scopePresent=falseWARNCheck challenge includes resource_metadata linkage actual=8 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."
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question and answer structure
AEO: Question and answer structure scored 50/100 and needs improvement.
4 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question and answer structure
AEO: Question and answer structure scored 50/100 and needs improvement.
Needs attention
AEO: Question and answer structure
Issue
No natural question headings were detected. Heading structure issues were detected.
Details
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
50/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 50/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Evidence and trust
AEO: Evidence and trust scored 57/100 and needs improvement.
4 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Evidence and trust
AEO: Evidence and trust scored 57/100 and needs improvement.
Needs attention
AEO: Evidence and trust
Issue
Missing answer evidence or trust signals: author, publisher, freshnessDate.
Details
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
57/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 57/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 50/100 and needs improvement.
4 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 50/100 and needs improvement.
Needs attention
AIO: Source and trust signals
Issue
Missing AIO trust signals: author, publisher, freshnessDate.
Details
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
50/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 50/100 and needs improvement.
Agent Ease of UseAPIEstablished
OpenAPI discovery
OpenAPI discovery has a validation warning at "Check machine-usable details".
4 Warning
Agent Ease of UseAPIEstablished
OpenAPI discovery
OpenAPI discovery has a validation warning at "Check machine-usable details".
Needs attention
OpenAPI discovery
Issue
OpenAPI is valid, but missing schemas, parameters, servers, auth, operation IDs, tags, or examples reduces machine usability.
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
93/100
Status
warning
Category
API
Maturity
Established
Goal
Publish a valid OpenAPI or Swagger document for public API discovery when this origin exposes public APIs.
Result
OpenAPI discovery has a validation warning at "Check machine-usable details".
Validation steps
Check machine-usable details
OpenAPI is valid, but missing schemas, parameters, servers, auth, operation IDs, tags, or examples reduces machine usability.
Evidence log1 step · 5 lines
Check machine-usable details [warning]! OpenAPI is valid, but missing schemas, parameters, servers, auth, operation IDs, tags, or examples reduces machine usability.INFOCheck machine-usable details status="warning"INFOInspect machine-usable operation details hasServers=true hasSecuritySchemes=true hasExplicitNoAuth=true requestBodyOperationCount=4 parameterOperationCount=12 responseSchemaOperationCount=32 operationIdCount=15 taggedOperationCount=19 exampleOperationCount=3WARNCheck OpenAPI operations include enough detail for agents to call them safely actual="1 machine-usability warning(s)" expected="servers, auth/no-auth signals, operationIds, parameters, request bodies, responses, tags, and examples where relevant"WARNMachine-usability warning warning="YAML validation used a conservative structural heuristic; JSON evidence is richer until a YAML parser is available."WARNOpenAPI is valid, but missing schemas, parameters, servers, auth, operation IDs, tags, or examples reduces machine usability.GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Source and trust signals
GEO: Source and trust signals scored 67/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Source and trust signals
GEO: Source and trust signals scored 67/100 and needs improvement.
Needs attention
GEO: Source and trust signals
Issue
Missing source or trust signals: authorOrOwner, freshnessDate.
Details
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
GEO: Extractable HTML
GEO: Extractable HTML scored 75/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Extractable HTML
GEO: Extractable HTML scored 75/100 and needs improvement.
Needs attention
GEO: Extractable HTML
Issue
Initial HTML is large (6308131 bytes), which can make extraction slower and noisier. Initial HTML has low visible-text density.
Details
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: Extractable HTML
Score
75/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.
Result
GEO: Extractable HTML scored 75/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 81/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 81/100 and needs improvement.
Needs attention
AEO: Entity and definition clarity
Issue
Title, h1, description, and opening copy are weakly aligned.
Details
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
81/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 81/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
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Page experience proxy
AIO: Page experience proxy scored 80/100 and needs improvement.
Needs attention
AIO: Page experience proxy
Issue
HTML size is large (6308131 bytes).
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 80/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible content clarity
AIO: Visible content clarity scored 80/100 and needs improvement.
Needs attention
AIO: Visible content clarity
Issue
Title, h1, description, and opening copy are weakly aligned. 45 section(s) may benefit from clearer answer-first openings. Heading outline issues were detected.
Details
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
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: Visible content clarity scored 80/100 and needs improvement.
Security & TrustSecurity & TrustEstablished
X-Content-Type-Options
X-Content-Type-Options has a validation warning at "Review observed browser responses".
1 Warning
Security & TrustSecurity & TrustEstablished
X-Content-Type-Options
X-Content-Type-Options has a validation warning at "Review observed browser responses".
Needs attention
X-Content-Type-Options
Issue
One or more same-origin active resources observed by Chrome did not emit X-Content-Type-Options: nosniff.
Why it matters
X-Content-Type-Options tells browsers to trust declared media types instead of sniffing content, reducing the risk that mislabeled files execute as active content.
Check name
X-Content-Type-Options
Score
93/100
Status
warning
Category
Security & Trust
Maturity
Established
Goal
Prevent browser MIME sniffing for browser-loadable responses with X-Content-Type-Options: nosniff.
Result
X-Content-Type-Options has a validation warning at "Review observed browser responses".
Validation steps
Review observed browser responses
One or more same-origin active resources observed by Chrome did not emit X-Content-Type-Options: nosniff.
Evidence log1 step · 4 lines
Review observed browser responses [warning]! One or more same-origin active resources observed by Chrome did not emit X-Content-Type-Options: nosniff.INFOReview observed browser responsesINFOSample Chrome-observed same-origin resources observedResponseCount=48 sameOriginCount=38 eligibleCount=38WARNCompare observed nosniff coverage actual={"missingNosniffCount":37,"malformedNosniffCount":0,"activeResourceMissingNosniffCount":25,"affected":[{"url":"https://pagecrawl.io/build/assets/DwVaTP44.css","status":200,"resourceType":"stylesheet","contentType":"text/css"},{"url":"https://pagecrawl.io/build/assets/DlU2dEz8.css","status":200,"resourceType":"stylesheet","contentType":"text/css"},{"url":"https://pagecrawl.io/images/logo.png","status":200,"resourceType":"image","contentType":"image/png"},{"url":"https://pagecrawl.io/images/logo-small.png","status":200,"resourceType":"image","contentType":"image/png"},{"url":"https://pagecrawl.io/fonts/raleway-latin.woff2","status":200,"resourceType":"font","contentType":"application/octet-stream"},{"url":"https://pagecrawl.io/manifest.json","status":200,"resourceType":"manifest","contentType":"application/json"},{"url":"https://pagecrawl.io/images/integrations/slack.svg","status":200,"resourceType":"image","contentType":"image/svg+xml"},{"url":"https://pagecrawl.io/images/integrations/teams.svg","status":200,"resourceType":"image","contentType":"image/svg+xml"},{"url":"https://pagecrawl.io/images/integrations/discord.svg","status":200,"resourceType":"image","contentType":"image/svg+xml"},{"url":"https://pagecrawl.io/images/integrations/telegram.svg","status":200,"resourceType":"image","contentType":"image/svg+xml"},{"url":"https://pagecrawl.io/images/integrations/google-sheets.svg","status":200,"resourceType":"image","contentType":"image/svg+xml"},{"url":"https://pagecrawl.io/images/integrations/zapier.svg","status":200,"resourceType":"image","contentType":"image/svg+xml"}]} expected="0 missing or malformed eligible same-origin responses" issue="One or more same-origin active resources observed by Chrome did not emit X-Content-Type-Options: nosniff."WARNOne or more same-origin active resources observed by Chrome did not emit X-Content-Type-Options: nosniff.GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Google Search eligibility
AIO: Google Search eligibility scored 85/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Google Search eligibility
AIO: Google Search eligibility scored 85/100 and needs improvement.
Needs attention
AIO: Google Search eligibility
Issue
Canonical tag is missing.
Details
Why it matters
Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.
Check name
AIO: Google Search eligibility
Score
85/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.
Result
AIO: Google Search eligibility scored 85/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Structured extraction
GEO: Structured extraction scored 88/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
GEO: Structured extraction
GEO: Structured extraction scored 88/100 and needs improvement.
Needs attention
GEO: Structured extraction
Issue
Missing or weak extraction signals: clean heading hierarchy.
Details
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
88/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 88/100 and needs improvement.
AI DiscoverabilityDiscoverabilityEstablished
IndexNow key
IndexNow key is informational for this page.
Informational
AI DiscoverabilityDiscoverabilityEstablished
IndexNow key
IndexNow key is informational for this page.
Needs attention
IndexNow key
Issue
IndexNow key is informational for this page.
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
Find advertised IndexNow key location
No IndexNow key location was advertised in HTML, Link headers, or robots.txt.
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.
SEOSEOBrowser audit
Links are not crawlable
50 Fail
SEOSEOBrowser audit
Links are not crawlable
Check name
Links are not crawlable
Score
0/100
Status
fail
Device
desktop
Category
SEO
Fix guidance
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. [Learn how to make links crawlable](https://support.google.com/webmasters/answer/9112205)
Evidence
{
"description": "Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. [Learn how to make links crawlable](https://support.google.com/webmasters/answer/9112205)"
}SEOSEOBrowser audit
Links do not have descriptive text
50 Fail
SEOSEOBrowser audit
Links do not have descriptive text
Check name
Links do not have descriptive text
Score
0/100
Status
fail
Device
desktop
Category
SEO
Estimated savings
1 link found
Fix guidance
Descriptive link text helps search engines understand your content. [Learn how to make links more accessible](https://developer.chrome.com/docs/lighthouse/seo/link-text/).
Evidence
{
"description": "Descriptive link text helps search engines understand your content. [Learn how to make links more accessible](https://developer.chrome.com/docs/lighthouse/seo/link-text/).",
"displayValue": "1 link found"
}Performance and AccessibilityPerformanceBrowser audit
Document request latency
20 Fail
Performance and AccessibilityPerformanceBrowser audit
Document request latency
Check name
Document request latency
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
Est savings of 1,410 ms
Fix guidance
Your first network request is the most important. [Reduce its latency](https://developer.chrome.com/docs/performance/insights/document-latency) by avoiding redirects, ensuring a fast server response, and enabling text compression.
References
https://web.dev/learn/performance/Evidence
{
"description": "Your first network request is the most important. [Reduce its latency](https://developer.chrome.com/docs/performance/insights/document-latency) by avoiding redirects, ensuring a fast server response, and enabling text compression.",
"displayValue": "Est savings of 1,410 ms"
}Performance and AccessibilityPerformanceBrowser audit
LCP breakdown
20 Fail
Performance and AccessibilityPerformanceBrowser audit
LCP breakdown
Check name
LCP breakdown
Score
0/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
Each [subpart has specific improvement strategies](https://developer.chrome.com/docs/performance/insights/lcp-breakdown). Ideally, most of the LCP time should be spent on loading the resources, not within delays.
References
https://web.dev/learn/performance/Evidence
{
"description": "Each [subpart has specific improvement strategies](https://developer.chrome.com/docs/performance/insights/lcp-breakdown). Ideally, most of the LCP time should be spent on loading the resources, not within delays."
}Performance and AccessibilityPerformanceBrowser audit
Touch targets do not have sufficient size or spacing.
20 Fail
Performance and AccessibilityPerformanceBrowser audit
Touch targets do not have sufficient size or spacing.
Check name
Touch targets do not have sufficient size or spacing.
Score
0/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. [Learn more about touch targets](https://dequeuniversity.com/rules/axe/4.11/target-size).
References
https://web.dev/learn/performance/Evidence
{
"description": "Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. [Learn more about touch targets](https://dequeuniversity.com/rules/axe/4.11/target-size)."
}Performance and AccessibilityPerformanceBrowser audit
Loading performance
11 Fail
Performance and AccessibilityPerformanceBrowser audit
Loading performance
Check name
Loading performance
Score
44/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
Review the grouped loading performance checks and improve the failing sub-checks listed in evidence.
References
https://web.dev/learn/performance/Evidence
{
"checks": [
{
"id": "speed-index",
"score": 12,
"title": "Speed Index",
"displayValue": "3.8 s",
"numericValue": 3780.2829795975576
},
{
"id": "server-response-time",
"score": 0,
"title": "Reduce initial server response time",
"displayValue": "Root document took 1,510 ms",
"numericValue": 1510
},
{
"id": "total-blocking-time",
"score": 30,
"title": "Total Blocking Time",
"displayValue": "490 ms",
"numericValue": 493.80417279611675
},
{
"id": "largest-contentful-paint",
"score": 65,
"title": "Largest Contentful Paint",
"displayValue": "1.9 s",
"numericValue": 1932.9165440776587
},
{
"id": "first-contentful-paint",
"score": 32,
"title": "First Contentful Paint",
"displayValue": "1.9 s",
"numericValue": 1932.9165440776587
},
{
"id": "interactive",
"score": 66,
"title": "Time to Interactive",
"displayValue": "3.7 s",
"numericValue": 3668.8703259054814
},
{
"id": "network-rtt",
"score": 100,
"title": "Network Round Trip Times",
"displayValue": "30 ms",
"numericValue": 34.13546999999996
},
{
"id": "max-potential-fid",
"score": 49,
"title": "Max Potential First Input Delay",
"displayValue": "250 ms",
"numericValue": 250.99999999999955
}
]
}Performance and AccessibilityPerformanceBrowser audit
Reduce unused CSS
10 Warning
Performance and AccessibilityPerformanceBrowser audit
Reduce unused CSS
Check name
Reduce unused CSS
Score
50/100
Status
warning
Device
desktop
Category
Performance
Estimated savings
Est savings of 96 KiB
Fix guidance
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS](https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/).
References
https://web.dev/learn/performance/Evidence
{
"description": "Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS](https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/).",
"displayValue": "Est savings of 96 KiB",
"numericValue": 0
}Fix with MCP or CLI
Use this report as the handoff into remediation. Generate a coding-agent prompt with the failing checks attached, or jump to the MCP and CLI setup docs before your next rescan.
Score history
Public scan score over time
Public reports for this website origin. Select any point or report link to open that canonical report.
| Scan date | Score | Readiness | Report |
|---|---|---|---|
| 58/100 | Level 3, Bot-Aware | Current report |