Export Report
OVERALL SCORE
Level 2, Agent-Limited
- AI Discoverability 45 out of 100
- Agent Ease of Use 50 out of 100
- Security & Trust 44 out of 100
- GEO, AIO and AEO 18 out of 100
- SEO 85 out of 100
- Performance 44 out of 100
- Accessibility 55 out of 100
What AI sees of your website
No page title captured
No page metadata or readable excerpt was captured.
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 | 45 | Priority fix | 18 | 2 | 1 | View details |
| Discoverability | 67 | Needs work | 8 | 0 | 0 | |
| Content Readiness | 8 | Priority fix | 6 | 0 | 0 | |
| Bot Access Control | 57 | Needs work | 4 | 2 | 1 | View details |
| Agent Ease of Use | 50 | Needs work | 2 | 1 | 0 | View details |
| Auth | 54 | Needs work | 2 | 0 | 0 | |
| Google Agentic Browsing | 43 | Priority fix | 0 | 1 | 0 | View details |
| GEO, AIO and AEO | 18 | Priority fix | 2 | 4 | 2 | View details |
| AIO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AEO Readiness | 17 | Priority fix | 0 | 4 | 2 | View details |
| SEO | 85 | Mostly ready | 8 | 0 | 0 | |
| SEO | 85 | Mostly ready | 8 | 0 | 0 | |
| Security & Trust | 44 | Priority fix | 5 | 0 | 0 | |
| Security & Trust | 44 | Priority fix | 5 | 0 | 0 | |
| Performance | 44 | Priority fix | 12 | 0 | 0 | |
| Performance | 44 | Priority fix | 12 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
8 items need attention
AI DiscoverabilityBot Access ControlEmerging recommendation
ai.txt policy
ai.txt policy failed at "Fetch /ai.txt".
67 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 429.
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
33/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 429.
/ai.txt could not be fetched when present
Parse ai.txt policy
ai.txt is present but does not follow the AI Visibility section model.
/ai.txt policy format is missing required sections or non-standard
Validate policy content
ai.txt is too short to provide useful advisory policy guidance.
/ai.txt content is incomplete or unsafe
Evidence log3 steps · 14 lines
Fetch /ai.txt [fail]! /ai.txt returned HTTP 429.INFOFetch /ai.txtINFORequesting optional advisory policy file at /ai.txtFAILCompare /ai.txt HTTP response actual=429 expected="2xx when ai.txt is intentionally published; 404/410 means absent optional file" contentType="text/plain" length=68FAIL/ai.txt returned HTTP 429. statusCode=429Parse ai.txt policy [warning]! ai.txt is present but does not follow the AI Visibility section model.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"]WARNai.txt is present but does not follow the AI Visibility section model.Validate policy content [fail]! ai.txt is too short to provide useful advisory policy guidance.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=false hasAttributionLanguage=false hasContact=falseFAILCheck required and recommended section coverage actual={"missingRequired":["identity","permissions","restrictions"],"missingRecommended":["attribution","contact","content-types"]} expected={"missingRequired":[],"recommendedPresentWhenPossible":true}FAILai.txt is too short to provide useful advisory policy guidance.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 0/100 and needs a fix.
6 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 0/100 and needs a fix.
Needs attention
AEO: Entity and definition clarity
Issue
Missing title tag. Expected exactly one h1, found 0. Missing meta description or Open Graph description. Title, h1, description, and opening copy are weakly aligned. No direct definition sentence was detected.
Details
Why it matters
Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.
Check name
AEO: Entity and definition clarity
Score
0/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.
Result
AEO: Entity and definition clarity scored 0/100 and needs a fix.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Evidence and trust
AEO: Evidence and trust scored 0/100 and needs a fix.
6 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Evidence and trust
AEO: Evidence and trust scored 0/100 and needs a fix.
Needs attention
AEO: Evidence and trust
Issue
Missing answer evidence or trust signals: author, publisher, freshnessDate, sources, sameAs, aboutOrContact, policyLinks.
Details
Why it matters
Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.
Check name
AEO: Evidence and trust
Score
0/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.
Result
AEO: Evidence and trust scored 0/100 and needs a fix.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question and answer structure
AEO: Question and answer structure scored 40/100 and needs a fix.
3 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question and answer structure
AEO: Question and answer structure scored 40/100 and needs a fix.
Needs attention
AEO: Question and answer structure
Issue
No natural question headings were detected. No visible FAQ or Q&A pattern was detected. Heading structure issues were detected. No list or table answer format was detected.
Details
Why it matters
Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.
Check name
AEO: Question and answer structure
Score
40/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.
Result
AEO: Question and answer structure scored 40/100 and needs a fix.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Extractable visible copy
AEO: Extractable visible copy scored 46/100 and needs a fix.
3 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Extractable visible copy
AEO: Extractable visible copy scored 46/100 and needs a fix.
Needs attention
AEO: Extractable visible copy
Issue
Only 10 visible words were detected for answer extraction. Visible text has few answer-oriented terms or explanatory markers.
Details
Why it matters
Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.
Check name
AEO: Extractable visible copy
Score
46/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.
Result
AEO: Extractable visible copy scored 46/100 and needs a fix.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first passages
AEO: Answer-first passages scored 55/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first passages
AEO: Answer-first passages scored 55/100 and needs improvement.
Needs attention
AEO: Answer-first passages
Issue
No h2/h3 answer sections were detected. No direct definition pattern was detected.
Details
Why it matters
Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.
Check name
AEO: Answer-first passages
Score
55/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.
Result
AEO: Answer-first passages scored 55/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-surface controls
AEO: Answer-surface controls scored 65/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-surface controls
AEO: Answer-surface controls scored 65/100 and needs improvement.
Needs attention
AEO: Answer-surface controls
Issue
3 answer retrieval crawler(s) are blocked for the scanned path.
Details
Why it matters
Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.
Check name
AEO: Answer-surface controls
Score
65/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.
Result
AEO: Answer-surface controls scored 65/100 and needs improvement.
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."
}Sign in to see 45 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