Export Report
OVERALL SCORE
Level 2, Agent-Limited
- AI Discoverability 29 out of 100
- Agent Ease of Use 50 out of 100
- Security & Trust 41 out of 100
- GEO, AIO and AEO 23 out of 100
- SEO 82 out of 100
- Performance 0 out of 100
- Accessibility 86 out of 100
What AI sees of your website
shutterstock.com
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 | 29 | Priority fix | 11 | 3 | 1 | View details |
| Discoverability | 20 | Priority fix | 2 | 0 | 0 | |
| Content Readiness | 8 | Priority fix | 6 | 0 | 0 | |
| Bot Access Control | 54 | Needs work | 3 | 3 | 1 | View details |
| GEO, AIO and AEO | 23 | Priority fix | 3 | 7 | 2 | View details |
| AIO Readiness | 37 | Priority fix | 2 | 3 | 1 | View details |
| AEO Readiness | 22 | Priority fix | 1 | 4 | 1 | View details |
| SEO | 82 | Mostly ready | 6 | 0 | 0 | |
| SEO | 82 | Mostly ready | 6 | 0 | 0 | |
| Security & Trust | 41 | Priority fix | 6 | 0 | 0 | |
| Security & Trust | 41 | Priority fix | 6 | 0 | 0 | |
| Performance | 0 | Priority fix | 15 | 0 | 0 | |
| Performance | 0 | Priority fix | 15 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
10 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 403.
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 403.
Validate transport
ai.txt appears to be an HTML page or error document rather than a plain-text policy.
Parse ai.txt policy
Transport validation failed before policy parsing could be trusted.
Validate policy content
ai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.
Evidence log4 steps · 18 lines
Fetch /ai.txt [fail]! /ai.txt returned HTTP 403.INFOFetch /ai.txtINFORequesting optional advisory policy file at /ai.txtFAILCompare /ai.txt HTTP response actual=403 expected="2xx when ai.txt is intentionally published; 404/410 means absent optional file" contentType="text/html;charset=utf-8" length=784FAIL/ai.txt returned HTTP 403. statusCode=403Validate 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;charset=utf-8" length=784 lineCount=1FAILCompare 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=false hasAttributionLanguage=false 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.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 0/100 and needs a fix.
8 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 0/100 and needs a fix.
Needs attention
AIO: Source and trust signals
Issue
Missing AIO trust signals: author, publisher, freshnessDate, aboutOrContact, policyLinks, sourceLinks.
Details
Why it matters
Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.
Check name
AIO: Source and trust signals
Score
0/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.
Result
AIO: Source and trust signals 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.
7 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
AIO: Google Search eligibility
AIO: Google Search eligibility scored 25/100 and needs a fix.
6 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Google Search eligibility
AIO: Google Search eligibility scored 25/100 and needs a fix.
Needs attention
AIO: Google Search eligibility
Issue
HTTP status is 403; Google Search AI features require an indexable 2xx page. Canonical tag is missing. Only 2 visible words were detected.
Details
Why it matters
Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.
Check name
AIO: Google Search eligibility
Score
25/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.
Result
AIO: Google Search eligibility scored 25/100 and needs a fix.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible content clarity
AIO: Visible content clarity scored 42/100 and needs a fix.
4 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible content clarity
AIO: Visible content clarity scored 42/100 and needs a fix.
Needs attention
AIO: Visible content clarity
Issue
Expected exactly one h1, found 0. Missing meta description or Open Graph description. Only 2 visible words were detected. Heading outline issues were detected.
Details
Why it matters
Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.
Check name
AIO: Visible content clarity
Score
42/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.
Result
AIO: Visible content clarity scored 42/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.
4 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: Entity and definition clarity
AEO: Entity and definition clarity scored 44/100 and needs a fix.
4 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 44/100 and needs a fix.
Needs attention
AEO: Entity and definition clarity
Issue
Expected exactly one h1, found 0. Missing meta description or Open Graph description. 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
44/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 44/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.
4 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 2 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
AIO: Page experience proxy
AIO: Page experience proxy scored 75/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Page experience proxy
AIO: Page experience proxy scored 75/100 and needs improvement.
Needs attention
AIO: Page experience proxy
Issue
Only 2 words of visible rendered text were detected.
Details
Why it matters
Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.
Check name
AIO: Page experience proxy
Score
75/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.
Result
AIO: Page experience proxy scored 75/100 and needs improvement.
Sign in to see 35 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