Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 68 out of 100
- Agent Ease of Use 48 out of 100
- Security & Trust 83 out of 100
- GEO, AIO and AEO 72 out of 100
- SEO 100 out of 100
- Performance 56 out of 100
- Accessibility 0 out of 100
What AI sees of your website
OpenObserve: Open Source Observability Platform | Logs, Metrics & Traces
Fast, scalable and cost-effective open source observability platform. Monitor logs, metrics & traces with 140x lower storage costs than Elasticsearch. Start in 2 minutes.
Next step
Turn this report into a fix workflow
1 failed check is 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 | 68 | Needs work | 34 | 0 | 0 | |
| Discoverability | 67 | Needs work | 8 | 0 | 0 | |
| Content Readiness | 74 | Needs work | 23 | 0 | 0 | |
| Bot Access Control | 63 | Needs work | 3 | 0 | 0 | |
| Agent Ease of Use | 48 | Priority fix | 2 | 0 | 0 | |
| API | 67 | Needs work | 1 | 0 | 0 | |
| Auth | 48 | Priority fix | 1 | 0 | 0 | |
| GEO, AIO and AEO | 72 | Needs work | 11 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 4 | 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 | 83 | Mostly ready | 20 | 1 | 0 | View details |
| Security & Trust | 83 | Mostly ready | 20 | 1 | 0 | View details |
| Performance | 56 | Needs work | 14 | 1 | 0 | View details |
| Performance | 56 | Needs work | 14 | 1 | 0 | View details |
| Accessibility | 0 | Priority fix | 0 | 1 | 0 | View details |
| Accessibility | 0 | Priority fix | 0 | 1 | 0 | View details |
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.
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.AccessibilityAccessibilityBrowser audit
Certain ARIA roles must contain particular children
100 Fail
AccessibilityAccessibilityBrowser audit
Certain ARIA roles must contain particular children
Check name
Certain ARIA roles must contain particular children
Score
0/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
Certain ARIA roles must contain particular children
Evidence
{
"ruleId": "aria-required-children",
"impact": "critical",
"description": "Ensure elements with an ARIA role that require child roles contain them",
"tags": [
"cat.aria",
"wcag2a",
"wcag131",
"EN-301-549",
"EN-9.1.3.1",
"RGAAv4",
"RGAA-9.3.1"
],
"affectedNodeCount": 1,
"nodes": [
{
"target": [
".list-none"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 77
},
"failureSummary": "Fix any of the following:\n Element has children which are not allowed: li"
}
]
}PerformancePerformanceBrowser audit
Forced reflow
100 Fail
PerformancePerformanceBrowser audit
Forced reflow
Check name
Forced reflow
Score
0/100
Status
fail
Device
desktop
Category
Performance
Fix guidance
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations.
References
web.dev/learn/performanceEvidence
{
"description": "A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations."
}Sign in to see 40 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