Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 58 out of 100
- Agent Ease of Use 58 out of 100
- Security & Trust 45 out of 100
- GEO, AIO and AEO 68 out of 100
- SEO 85 out of 100
- Performance 55 out of 100
- Accessibility 15 out of 100
What AI sees of your website
Experience the Power of Assistive Technology with OrCam's AI Devices
OrCam's AI devices are revolutionizing the way you interact with the world. Explore our innovative devices and experience the future of assistive technology today.
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 | 58 | Needs work | 29 | 2 | 3 | View details |
| Discoverability | 67 | Needs work | 8 | 0 | 0 | |
| Content Readiness | 68 | Needs work | 18 | 0 | 0 | |
| Bot Access Control | 44 | Priority fix | 3 | 2 | 3 | View details |
| Agent Ease of Use | 58 | Needs work | 23 | 0 | 0 | |
| API | 44 | Priority fix | 7 | 0 | 0 | |
| Auth | 57 | Needs work | 5 | 0 | 0 | |
| MCP | 45 | Priority fix | 2 | 0 | 0 | |
| Agent Commerce | 58 | Needs work | 7 | 0 | 0 | |
| Google Agentic Browsing | 100 | Strong | 2 | 0 | 0 | |
| GEO, AIO and AEO | 68 | Needs work | 9 | 1 | 3 | View details |
| GEO Readiness | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| AIO Readiness | 68 | Needs work | 2 | 1 | 3 | View details |
| AEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| SEO | 85 | Mostly ready | 8 | 0 | 0 | |
| SEO | 85 | Mostly ready | 8 | 0 | 0 | |
| Security & Trust | 45 | Priority fix | 7 | 0 | 0 | |
| Security & Trust | 45 | Priority fix | 7 | 0 | 0 | |
| Performance | 55 | Needs work | 11 | 0 | 0 | |
| Performance | 55 | Needs work | 11 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
6 items need attention
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
35 Fail
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
Needs attention
AI bot rules in robots.txt
Issue
No explicit User-agent rules were found for major AI crawler tokens.
Details
Why it matters
AI crawler product tokens have different meanings. Explicit robots.txt groups make training, search, and retrieval access policy auditable for compliant crawler operators.
Check name
AI bot rules in robots.txt
Score
31/100
Status
fail
Category
Bot Access Control
Maturity
Established
Goal
Declare deliberate robots.txt rules for major AI training, AI search, user-triggered, and dataset crawlers.
Result
AI bot rules in robots.txt failed at "Classify AI crawler rules".
Validation steps
Classify AI crawler rules
No explicit User-agent rules were found for major AI crawler tokens.
robots.txt lacks explicit AI crawler rules
Evidence log1 step · 6 lines
Classify AI crawler rules [fail]! No explicit User-agent rules were found for major AI crawler tokens.INFOClassify AI crawler rulesINFOParsing User-agent groups and Allow/Disallow records for known AI crawler tokens evaluatedPath="/"INFOEvaluating exact User-agent matches before wildcard fallback exactAiPolicyCount=0 totalCrawlerTokens=18FAILNo explicit AI crawler User-agent groups were found examplesExpected=["GPTBot","OAI-SearchBot","ClaudeBot","Google-Extended","CCBot"]FAILCompare explicit AI crawler coverage actual=0 expected="> 0 explicit non-search AI crawler policies" missingTokens=["GPTBot","OAI-SearchBot","ChatGPT-User","ClaudeBot","Claude-SearchBot","Claude-User","Google-Extended","Applebot-Extended","Amazonbot","Amzn-SearchBot","Amzn-User","PerplexityBot"]INFOResolved effective root-path policy for crawler tokens blocked=0 allowed=21 unspecified=0AI DiscoverabilityBot Access ControlEmerging recommendation
ai.txt policy
ai.txt policy failed at "Fetch /ai.txt".
30 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.
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
40/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.
/ai.txt could not be fetched when present
Validate transport
ai.txt was served as application/xml; text/plain is preferred.
/ai.txt transport is invalid or not plain text
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 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 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="application/xml" length=243FAIL/ai.txt returned HTTP 403. statusCode=403Validate transport [warning]! ai.txt was served as application/xml; text/plain is preferred.INFOValidate transportINFOChecking ai.txt media type, size, line count, and whether the response looks like plain text contentType="application/xml" length=243 lineCount=2WARNCompare media type to preferred text/plain transport actual="application/xml" expected="text/plain preferred; readable text required"WARNai.txt was served as application/xml; text/plain is preferred. warnings=["ai.txt was served as application/xml; text/plain is preferred."]Parse 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 [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: Structured data consistency
AIO: Structured data consistency scored 0/100 and needs a fix.
8 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Structured data consistency
AIO: Structured data consistency scored 0/100 and needs a fix.
Needs attention
AIO: Structured data consistency
Issue
5 structured-data value(s) were not found in visible page text.
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: Structured data consistency
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: Structured data consistency scored 0/100 and needs a fix.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Page experience proxy
AIO: Page experience proxy scored 80/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Page experience proxy
AIO: Page experience proxy scored 80/100 and needs improvement.
Needs attention
AIO: Page experience proxy
Issue
22 image(s) are missing width/height attributes.
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
80/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 80/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 83/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Source and trust signals
AIO: Source and trust signals scored 83/100 and needs improvement.
Needs attention
AIO: Source and trust signals
Issue
Missing AIO trust signals: freshnessDate.
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
83/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: Source and trust signals scored 83/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible content clarity
AIO: Visible content clarity scored 85/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AIO: Visible content clarity
AIO: Visible content clarity scored 85/100 and needs improvement.
Needs attention
AIO: Visible content clarity
Issue
10 section(s) may benefit from clearer answer-first openings. 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
85/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: Visible content clarity scored 85/100 and needs improvement.
Sign in to see 50 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
Public scan score over time
Public reports for this website origin. Select any point or report link to open that canonical report.
| Scan date | Score | Readiness | Report |
|---|---|---|---|
| 51/100 | Level 3, Bot-Aware | Current report |