Export Report
OVERALL SCORE
Level 2, Agent-Limited
- AI Discoverability 17 out of 100
- Agent Ease of Use 50 out of 100
- Security & Trust 54 out of 100
- GEO, AIO and AEO 44 out of 100
- SEO 91 out of 100
- Performance 92 out of 100
- Accessibility 76 out of 100
What AI sees of your website
JsonGrid - All-In-One JSON Solution
Online JSON Viewer - Convert JSON Strings to a Friendly Readable Format, View JSON in table or Grid
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 | 17 | Priority fix | 3 | 2 | 0 | View details |
| Discoverability | 7 | Priority fix | 1 | 0 | 0 | |
| Content Readiness | 2 | Priority fix | 2 | 0 | 0 | |
| Bot Access Control | 38 | Priority fix | 0 | 2 | 0 | View details |
| GEO, AIO and AEO | 44 | Priority fix | 4 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 1 | 0 | 0 | |
| SEO | 91 | Strong | 7 | 0 | 0 | |
| SEO | 91 | Strong | 7 | 0 | 0 | |
| Security & Trust | 54 | Needs work | 10 | 0 | 0 | |
| Security & Trust | 54 | Needs work | 10 | 0 | 0 | |
| Performance | 92 | Strong | 17 | 0 | 0 | |
| Performance | 92 | Strong | 17 | 0 | 0 | |
| Accessibility | 76 | Mostly ready | 6 | 2 | 0 | View details |
| Accessibility | 76 | Mostly ready | 6 | 2 | 0 | View details |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Fetch robots.txt".
100 Fail
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Fetch robots.txt".
Needs attention
AI bot rules in robots.txt
Issue
No robots.txt content was available to inspect for AI bot rules.
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
0/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 "Fetch robots.txt".
Validation steps
Fetch robots.txt
No robots.txt content was available to inspect for AI bot rules.
Classify AI crawler rules
No explicit User-agent rules were found for major AI crawler tokens.
Evidence log2 steps · 10 lines
Fetch robots.txt [fail]! No robots.txt content was available to inspect for AI bot rules.INFOFetch robots.txtINFORequesting /robots.txt from the site originFAILCheck whether robots.txt content is available actual="no content" expected="content returned" length=0FAILNo robots.txt content was available to inspect for AI bot rules.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=0 unspecified=21
AccessibilityAccessibilityBrowser audit
Background and foreground colors do not have a sufficient contrast ratio.
50 Fail
AccessibilityAccessibilityBrowser audit
Background and foreground colors do not have a sufficient contrast ratio.
Check name
Background and foreground colors do not have a sufficient contrast ratio.
Score
0/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast](https://dequeuniversity.com/rules/axe/4.11/color-contrast).
Evidence
{
"description": "Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast](https://dequeuniversity.com/rules/axe/4.11/color-contrast)."
}AccessibilityAccessibilityBrowser audit
Buttons do not have an accessible name
50 Fail
AccessibilityAccessibilityBrowser audit
Buttons do not have an accessible name
Check name
Buttons do not have an accessible name
Score
0/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. [Learn how to make buttons more accessible](https://dequeuniversity.com/rules/axe/4.11/button-name).
Evidence
{
"description": "When a button doesn't have an accessible name, screen readers announce it as \"button\", making it unusable for users who rely on screen readers. [Learn how to make buttons more accessible](https://dequeuniversity.com/rules/axe/4.11/button-name)."
}Sign in to see 33 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