Export Report
OVERALL SCORE
Level 4, Mostly Ready
- AI Discoverability 95 out of 100
- Agent Ease of Use 80 out of 100
- Security & Trust 76 out of 100
- GEO, AIO and AEO 76 out of 100
- SEO 100 out of 100
- Performance 100 out of 100
- Accessibility 100 out of 100
What AI sees of your website
Investor & Corporate Communications Platform | RELAYTO
RELAYTO turns investor decks, annual and ESG reports, benefits guides and proposals into interactive experiences on your domain, with AI answers and analytics.
Next step
Turn this report into a fix workflow
3 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 | 95 | Strong | 55 | 0 | 0 | |
| Discoverability | 100 | Strong | 12 | 0 | 0 | |
| Content Readiness | 98 | Strong | 34 | 0 | 0 | |
| Bot Access Control | 89 | Mostly ready | 9 | 0 | 0 | |
| Agent Ease of Use | 80 | Mostly ready | 43 | 4 | 2 | View details |
| API | 97 | Strong | 14 | 0 | 0 | |
| Auth | 46 | Priority fix | 3 | 2 | 0 | View details |
| MCP | 85 | Mostly ready | 8 | 0 | 0 | |
| Skill Discovery | 70 | Needs work | 14 | 2 | 2 | View details |
| Google Agentic Browsing | 100 | Strong | 4 | 0 | 0 | |
| GEO, AIO and AEO | 76 | Mostly ready | 13 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 5 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| Security & Trust | 76 | Mostly ready | 18 | 1 | 0 | View details |
| Security & Trust | 76 | Mostly ready | 18 | 1 | 0 | View details |
| Performance | 100 | Strong | 19 | 0 | 0 | |
| Performance | 100 | Strong | 19 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Find enforcing CSP delivery".
60 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.
Details
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.
Enforcing Content-Security-Policy header is missing
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
agents.json
agents.json failed at "Validate Wildcard schema shape".
55 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
agents.json
agents.json failed at "Validate Wildcard schema shape".
Needs attention
agents.json
Issue
agents.json does not match the expected Wildcard OpenAPI workflow shape.
Details
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
45/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 does not match the expected Wildcard OpenAPI workflow shape.
agents.json schema shape is invalid or incomplete
Missing required fields
- actions or OpenAPI paths
Validate API actions
Wildcard agents.json must include valid OpenAPI-derived action or operation definitions.
agents.json action definitions are invalid or missing
Validate flows and links
One or more flows or links reference missing or invalid operations.
agents.json flows or links are invalid
Review examples and LLM usability
Examples or descriptions are too thin for reliable agent argument generation.
agents.json examples or descriptions need improvement
Evidence log4 steps · 20 lines
Validate Wildcard schema shape [fail]! agents.json does not match the expected Wildcard OpenAPI workflow shape.INFOValidate Wildcard schema shapeINFOParse agents.json and classify contract shape shape="wildcard"FAILCompare contract shape actual="wildcard" expected="wildcard"FAILCompare missing required schema fields actual=["actions or OpenAPI paths"] expected="none"FAILCompare Content-Type with JSON expectation actual=true expected=trueINFORecorded remote OpenAPI/schema reference reference="https://relayto.com/openapi.json"WARNSchema-shape warning warning="schema/spec version is missing"WARNSchema-shape warning warning="document references roadmap-style workflow features that need review"FAILagents.json does not match the expected Wildcard OpenAPI workflow shape.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 [warning]! One or more flows or links reference missing or invalid operations.INFOValidate flows and linksWARNCompare workflow flow count actual=5 expected="> 0"WARNCompare operation link issues actual=0 expected=0WARNOne or more flows or links reference missing or invalid operations.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.
Agent Ease of UseAuthEmerging recommendation
Auth.md Agent Registration
Auth.md Agent Registration failed at "Validate protected resource metadata".
55 Fail
Agent Ease of UseAuthEmerging recommendation
Auth.md Agent Registration
Auth.md Agent Registration failed at "Validate protected resource metadata".
Needs attention
Auth.md Agent Registration
Issue
OAuth Protected Resource Metadata could not be fetched.
Details
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
45/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 "Validate protected resource metadata".
Validation steps
Validate protected resource metadata
OAuth Protected Resource Metadata could not be fetched.
Auth.md protected-resource metadata is missing or incomplete
Validate Auth.md authorization metadata
OAuth authorization-server metadata could not be fetched.
Authorization-server metadata lacks Auth.md v1 fields
Evidence log2 steps · 12 lines
Validate protected resource metadata [fail]! OAuth Protected Resource Metadata could not be fetched.INFOValidate protected resource metadataINFOFetch Auth.md-related resource path="/.well-known/oauth-protected-resource" statusCode=404 contentType="text/plain;charset=UTF-8" bytes=0FAILCompare response Content-Type with expected Auth.md media type actual=false expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILAuth.md validation issue issue="OAuth Protected Resource Metadata could not be fetched."FAILOAuth Protected Resource Metadata could not be fetched.Validate Auth.md authorization metadata [fail]! OAuth authorization-server metadata could not be fetched.INFOValidate Auth.md authorization metadataINFOFetch Auth.md-related resource path="/.well-known/oauth-authorization-server" statusCode=404 contentType="text/plain;charset=UTF-8" bytes=0FAILCompare response Content-Type with expected Auth.md media type actual=false expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILAuth.md validation issue issue="OAuth authorization-server metadata could not be fetched."FAILOAuth authorization-server metadata could not be fetched.
Sign in to see 19 other issues and the full report
Create a free account to unlock every issue, evidence details, exports, and higher free limits.
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