Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 42 out of 100
- Agent Ease of Use 56 out of 100
- Security & Trust 77 out of 100
- GEO, AIO and AEO 74 out of 100
- SEO 92 out of 100
- Performance 60 out of 100
- Accessibility 28 out of 100
What AI sees of your website
Security Threat Intelligences Services & Solutions | OpenText
Our threat intelligence services secure businesses & their products worldwide utilizing AI & a global sensor network to strengthen & secure partner solutions.
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 | 42 | Priority fix | 20 | 3 | 1 | View details |
| Discoverability | 20 | Priority fix | 2 | 0 | 0 | |
| Content Readiness | 50 | Needs work | 15 | 0 | 0 | |
| Bot Access Control | 54 | Needs work | 3 | 3 | 1 | View details |
| Agent Ease of Use | 56 | Needs work | 4 | 1 | 0 | View details |
| API | 67 | Needs work | 1 | 0 | 0 | |
| Auth | 48 | Priority fix | 1 | 0 | 0 | |
| Google Agentic Browsing | 67 | Needs work | 2 | 1 | 0 | View details |
| GEO, AIO and AEO | 74 | Needs work | 12 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 5 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| Security & Trust | 77 | Mostly ready | 20 | 0 | 0 | |
| Security & Trust | 77 | Mostly ready | 20 | 0 | 0 | |
| Performance | 60 | Needs work | 12 | 0 | 0 | |
| Performance | 60 | Needs work | 12 | 0 | 0 | |
| Accessibility | 28 | Priority fix | 0 | 1 | 0 | View details |
| Accessibility | 28 | Priority fix | 0 | 1 | 0 | View details |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
AI DiscoverabilityBot Access ControlEmerging recommendation
ai.txt policy
ai.txt policy failed at "Fetch /ai.txt".
82 Fail
AI DiscoverabilityBot Access ControlEmerging recommendation
ai.txt policy
ai.txt policy failed at "Fetch /ai.txt".
Needs attention
ai.txt policy
Issue
/ai.txt returned HTTP 490.
Details
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
18/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 "Fetch /ai.txt".
Validation steps
Fetch /ai.txt
/ai.txt returned HTTP 490.
/ai.txt could not be fetched when present
Validate transport
ai.txt appears to be an HTML page or error document rather than a plain-text policy.
/ai.txt transport is invalid or not plain text
Parse ai.txt policy
Transport validation failed before policy parsing could be trusted.
/ai.txt policy format is missing required sections or non-standard
Validate policy content
ai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.
/ai.txt content is incomplete or unsafe
Evidence log4 steps · 18 lines
Fetch /ai.txt [fail]! /ai.txt returned HTTP 490.INFOFetch /ai.txtINFORequesting optional advisory policy file at /ai.txtFAILCompare /ai.txt HTTP response actual=490 expected="2xx when ai.txt is intentionally published; 404/410 means absent optional file" contentType="text/html" length=339214FAIL/ai.txt returned HTTP 490. statusCode=490Validate 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" length=339214 lineCount=4925FAILCompare 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 [warning]! ai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.INFOValidate policy contentINFOChecking required section content, permission/restriction language, attribution, contact details, and safety risks convention="unknown-text"INFODetected policy signals hasPermissionLanguage=false hasRestrictionLanguage=false hasTrainingLanguage=true hasAttributionLanguage=true hasContact=falseWARNCheck required and recommended section coverage actual={"missingRequired":["identity","permissions","restrictions"],"missingRecommended":["attribution","contact","content-types"]} expected={"missingRequired":[],"recommendedPresentWhenPossible":true}WARNai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.
Agent Ease of UseGoogle Agentic BrowsingBrowser audit
Accessibility tree is not well-formed
100 Fail
Agent Ease of UseGoogle Agentic BrowsingBrowser audit
Accessibility tree is not well-formed
Check name
Accessibility tree is not well-formed
Score
0/100
Status
fail
Device
desktop
Category
Google Agentic Browsing
Fix guidance
A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page.
Evidence
{
"description": "A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page."
}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": [
".nav"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 78
},
"failureSummary": "Fix any of the following:\n Element has children which are not allowed: li"
}
]
}Sign in to see 46 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