Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 70 out of 100
- Agent Ease of Use 56 out of 100
- Security & Trust 76 out of 100
- GEO, AIO and AEO 51 out of 100
- SEO 100 out of 100
- Performance 78 out of 100
- Accessibility 83 out of 100
What AI sees of your website
Ethereum Pool and Solo Staking | StakeWise
Simple and secure Ethereum staking. Liquid staking, institutional staking, solo staking - available within $1BN+ ecosystem. Trusted by over 100,000 users. Stake ETH or deploy your own pool now.
Next step
Turn this report into a fix workflow
2 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 | 70 | Needs work | 33 | 2 | 0 | View details |
| Discoverability | 67 | Needs work | 8 | 2 | 0 | View details |
| Content Readiness | 83 | Mostly ready | 22 | 0 | 0 | |
| Bot Access Control | 63 | Needs work | 3 | 0 | 0 | |
| Agent Ease of Use | 56 | Needs work | 3 | 1 | 0 | View details |
| API | 67 | Needs work | 1 | 0 | 0 | |
| Google Agentic Browsing | 67 | Needs work | 2 | 1 | 0 | View details |
| GEO, AIO and AEO | 51 | Needs work | 6 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| Security & Trust | 76 | Mostly ready | 20 | 2 | 2 | View details |
| Security & Trust | 76 | Mostly ready | 20 | 2 | 2 | View details |
| Performance | 78 | Mostly ready | 15 | 0 | 0 | |
| Performance | 78 | Mostly ready | 15 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
3 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.
Details
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.
Link header lacks useful discovery relations
Fetch same-origin Link header targets
Link headers did not expose any same-origin targets to validate.
Link header targets are unreachable or media types mismatch
Evidence log2 steps · 14 lines
Find useful Link headers [fail]! No useful agent discovery Link headers were found.INFOFind useful Link headersINFOParse response Link header linkCount=5FAILCompare registered agent-useful relation count actual=0 expected="> 0"FAILCompare community relation count actual=0 expected="accepted as weaker evidence"INFOIgnored non-discovery Link relation rel="preload" url="/_next/static/media/1351fdb5d3d44729-s.p.woff2"INFOIgnored non-discovery Link relation rel="preload" url="/_next/static/media/21350d82a1f187e9-s.p.woff2"INFOIgnored non-discovery Link relation rel="preload" url="/_next/static/media/84cb68b19443794f-s.p.woff2"INFOIgnored non-discovery Link relation rel="preload" url="/_next/static/media/a8e6892b3dcaa46a-s.p.woff2"INFOIgnored non-discovery Link relation rel="preload" url="/_next/static/media/e4af272ccee01ff0-s.p.woff2"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.
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Evaluate fetch baseline".
50 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Evaluate fetch baseline".
Needs attention
Content-Security-Policy
Issue
CSP does not define default-src; several fetch directives may have no restrictive fallback.
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
50/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 "Evaluate fetch baseline".
Validation steps
Evaluate fetch baseline
CSP does not define default-src; several fetch directives may have no restrictive fallback.
CSP fetch baseline is too broad or missing
Evaluate script execution
No script-src or default-src directive constrains script execution.
CSP script execution policy is unsafe
Review hardening directives
CSP is missing recommended hardening directives: object-src, base-uri.
CSP hardening directives are missing or weak
Review CSP reporting
CSP does not define a reporting endpoint.
CSP reporting is missing or incomplete
Evidence log4 steps · 16 lines
Evaluate fetch baseline [fail]! CSP does not define default-src; several fetch directives may have no restrictive fallback.INFOEvaluate fetch baselineINFOEvaluate resource loading fallback explicitFetchDirectives=[]FAILCompare fetch baseline actual="0 explicit fetch directives" expected="restricted default-src or broad explicit fetch coverage" issue="CSP does not define default-src; several fetch directives may have no restrictive fallback."FAILCSP does not define default-src; several fetch directives may have no restrictive fallback.Evaluate script execution [fail]! No script-src or default-src directive constrains script execution.INFOEvaluate script executionINFOInspect effective script directive FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":false,"hasUnsafeEval":false,"hasWildcardHost":false,"hasBroadScheme":false,"dangerousSchemes":[]} expected="constrained script sources without unsafe execution allowances" issue="No script-src or default-src directive constrains script execution."FAILNo script-src or default-src directive constrains script execution.Review hardening directives [warning]! CSP is missing recommended hardening directives: object-src, base-uri.INFOReview hardening directivesINFOInspect CSP hardening directives frameAncestors=["'self'","https://app.safe.global","https://*.blockscout.com"] formCount=0WARNCompare recommended hardening coverage actual=["object-src","base-uri"] expected="no missing object-src/base-uri/form-action requirements" issue="CSP is missing recommended hardening directives: object-src, base-uri."WARNCSP is missing recommended hardening directives: object-src, base-uri.Review CSP reporting [warning]! CSP does not define a reporting endpoint.INFOReview CSP reportingINFOInspect CSP reporting directives reportOnlyHeaderPresent=false reportOnlyDirectives=[]WARNCompare violation reporting configuration actual="no reporting endpoint" expected="report-to or report-uri present" issue="CSP does not define a reporting endpoint."WARNCSP does not define a reporting endpoint.
Agent Ease of UseGoogle Agentic BrowsingBrowser audit
llms.txt does not follow recommendations
100 Fail
Agent Ease of UseGoogle Agentic BrowsingBrowser audit
llms.txt does not follow recommendations
Check name
llms.txt does not follow recommendations
Score
0/100
Status
fail
Device
desktop
Category
Google Agentic Browsing
Fix guidance
If your llms.txt file does not follow recommendations, large language models may not be able to understand how you want your website to be crawled or used for training. The [llms.txt](https://llmstxt.org/) file should be a Markdown file containing at least one H1 header.
Evidence
{
"description": "If your llms.txt file does not follow recommendations, large language models may not be able to understand how you want your website to be crawled or used for training. The [llms.txt](https://llmstxt.org/) file should be a Markdown file containing at least one H1 header."
}Sign in to see 32 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