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 | 45 | 3 | 0 | View details |
| API | 88 | Mostly ready | 13 | 1 | 0 | View details |
| Auth | 46 | Priority fix | 3 | 2 | 0 | View details |
| MCP | 85 | Mostly ready | 8 | 0 | 0 | |
| Skill Discovery | 82 | Mostly ready | 17 | 0 | 0 | |
| 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 | 18 | 0 | 0 | |
| Performance | 100 | Strong | 18 | 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 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.
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog targets".
17 Fail
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog targets".
Needs attention
API Catalog
Issue
API catalog target https://relayto.com/developers/llms.txt (service-meta) could not be fetched: fetch failed.
Details
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
83/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 targets".
Validation steps
Validate API catalog targets
API catalog target https://relayto.com/developers/llms.txt (service-meta) could not be fetched: fetch failed.
API catalog targets are unreachable or media types mismatch
Evidence log1 step · 14 lines
Validate API catalog targets [fail]! API catalog target https://relayto.com/developers/llms.txt (service-meta) could not be fetched: fetch failed.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsPASSAPI catalog target is reachable rel="item" href="https://relayto.com/api/site/v1" statusCode=200 contentType="application/json"PASSAPI catalog target is reachable rel="item" href="https://relayto.com/api/site/sandbox/v1" statusCode=200 contentType="application/json"PASSAPI catalog target is reachable rel="service-desc" href="https://relayto.com/openapi.json" statusCode=200 contentType="application/json" advertisedType="application/openapi+json"PASSAPI catalog target is reachable rel="service-desc" href="https://relayto.com/openapi.yaml" statusCode=200 contentType="application/yaml; charset=utf-8" advertisedType="application/openapi+yaml"PASSAPI catalog target is reachable rel="service-doc" href="https://relayto.com/developers" statusCode=200 contentType="text/html" advertisedType="text/html"PASSAPI catalog target is reachable rel="service-doc" href="https://relayto.com/developers.md" statusCode=200 contentType="text/markdown; charset=utf-8" advertisedType="text/markdown"PASSAPI catalog target is reachable rel="service-doc" href="https://relayto.com/hub/api" statusCode=200 contentType="text/html" advertisedType="text/html"FAILAPI catalog target fetch failed rel="service-meta" href="https://relayto.com/developers/llms.txt" error="fetch failed"PASSAPI catalog target is reachable rel="service-desc" href="https://relayto.com/openapi.json" statusCode=200 contentType="application/json" advertisedType="application/openapi+json"PASSAPI catalog target is reachable rel="service-doc" href="https://relayto.com/docs/sandbox" statusCode=200 contentType="text/html; charset=utf-8" advertisedType="text/html"FAILCompare API catalog target failure count actual=1 expected=0FAILAPI catalog target https://relayto.com/developers/llms.txt (service-meta) could not be fetched: fetch failed.Sign in to see 21 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