Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 58 out of 100
- Agent Ease of Use 50 out of 100
- Security & Trust 95 out of 100
- GEO, AIO and AEO 66 out of 100
- SEO 100 out of 100
- Performance 99 out of 100
- Accessibility 96 out of 100
What AI sees of your website
Is it down? Check service status | DownStatus
Check if your favourite app or website is down right now. Real-time outage map and status updates based on user reports.
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 | 4 | 1 | View details |
| Discoverability | 67 | Needs work | 8 | 2 | 0 | View details |
| Content Readiness | 44 | Priority fix | 18 | 2 | 1 | View details |
| Bot Access Control | 63 | Needs work | 3 | 0 | 0 | |
| Agent Ease of Use | 50 | Needs work | 4 | 0 | 0 | |
| API | 50 | Needs work | 4 | 0 | 0 | |
| GEO, AIO and AEO | 66 | Needs work | 11 | 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 | 3 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| Security & Trust | 95 | Strong | 25 | 0 | 0 | |
| Security & Trust | 95 | Strong | 25 | 0 | 0 | |
| Performance | 99 | Strong | 17 | 0 | 0 | |
| Performance | 99 | Strong | 17 | 0 | 0 | |
| Accessibility | 96 | Strong | 5 | 0 | 0 | |
| Accessibility | 96 | Strong | 5 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
100 Fail
AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
Needs attention
Link headers
Issue
No useful agent discovery Link headers were found.
Why it matters
Link headers let automated clients discover API catalogs, documentation, and machine-readable alternates without parsing page markup first.
Check name
Link headers
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Include Link response headers for agent discovery using RFC 8288.
Result
Link headers failed at "Find useful Link headers".
Validation steps
Find useful Link headers
No useful agent discovery Link headers were found.
Fetch same-origin Link header targets
Link headers did not expose any same-origin targets to validate.
Evidence log2 steps · 23 lines
Find useful Link headers [fail]! No useful agent discovery Link headers were found.INFOFind useful Link headersINFOParse response Link header linkCount=14FAILCompare registered agent-useful relation count actual=0 expected="> 0"FAILCompare community relation count actual=0 expected="accepted as weaker evidence"INFOIgnored non-discovery Link relation rel="alternate" url="https://isitdownstatus.com/en"INFOIgnored non-discovery Link relation rel="alternate" url="https://isitdownstatus.com/uk"INFOIgnored non-discovery Link relation rel="alternate" url="https://isitdownstatus.com/ru"INFOIgnored non-discovery Link relation rel="alternate" url="https://isitdownstatus.com/pl"INFOIgnored non-discovery Link relation rel="alternate" url="https://isitdownstatus.com/de"INFOIgnored non-discovery Link relation rel="alternate" url="https://isitdownstatus.com/es"INFOIgnored non-discovery Link relation rel="alternate" url="https://isitdownstatus.com/fr"INFOIgnored non-discovery Link relation rel="alternate" url="https://isitdownstatus.com/ja"INFOIgnored non-discovery Link relation rel="alternate" url="https://isitdownstatus.com/ar"INFOIgnored non-discovery Link relation rel="alternate" url="https://isitdownstatus.com/it"INFOIgnored non-discovery Link relation rel="alternate" url="https://isitdownstatus.com/pt"INFOIgnored non-discovery Link relation rel="alternate" url="https://isitdownstatus.com/tr"INFOIgnored non-discovery Link relation rel="alternate" url="https://isitdownstatus.com/ko"INFOIgnored non-discovery Link relation rel="alternate" url="https://isitdownstatus.com/"FAILNo useful agent discovery Link headers were found.Fetch same-origin Link header targets [fail]! Link headers did not expose any same-origin targets to validate.INFOFetch same-origin Link header targetsINFOFetch same-origin Link header targets and record external skipsFAILCompare same-origin Link target failures actual=1 expected=0FAILLink headers did not expose any same-origin targets to validate.
AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt failed at "Fetch root llms.txt".
50 Fail
AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt failed at "Fetch root llms.txt".
Needs attention
llms.txt
Issue
/llms.txt was not found or could not be fetched.
Why it matters
llms.txt is an emerging Markdown convention for giving language-model clients curated context and links before they crawl broadly. Broken, private, or low-signal links make the file much less useful even when it exists.
Check name
llms.txt
Score
0/100
Status
fail
Category
Content Readiness
Maturity
Emerging recommendation
Goal
Publish a concise llms.txt index that helps agents discover useful public site context.
Result
llms.txt failed at "Fetch root llms.txt".
Validation steps
Fetch root llms.txt
/llms.txt was not found or could not be fetched.
Inspect optional llms-full.txt
Passed.
Evidence log2 steps · 7 lines
Fetch root llms.txt [fail]! /llms.txt was not found or could not be fetched.INFOFetch root llms.txt path="/llms.txt"INFOTrying to fetch /llms.txt url="https://isitdownstatus.com/llms.txt"FAIL/llms.txt was not found or could not be fetched statusCode=404FAILFetch root llms.txt failed reason="/llms.txt is required for this check."Inspect optional llms-full.txt [informational]INFOInspect optional llms-full.txtINFOTrying to fetch /llms-full.txt url="https://isitdownstatus.com/llms-full.txt"SKIP/llms-full.txt is not present statusCode=404
AI DiscoverabilityContent ReadinessEstablished
Author attribution
Author attribution is partially implemented.
22 Warning
AI DiscoverabilityContent ReadinessEstablished
Author attribution
Author attribution is partially implemented.
Needs attention
Author attribution
Issue
No named author or publisher identity could be extracted.
Why it matters
Author attribution helps agents cite content responsibly, assess source credibility, and distinguish editorial pages from anonymous marketing copy.
Check name
Author attribution
Score
55/100
Status
warning
Category
Content Readiness
Maturity
Established
Goal
Identify content authors or publishers for trust and attribution.
Result
Author attribution is partially implemented.
Validation steps
Schema.org attribution
Schema.org attribution is incomplete or relies only on publisher/fallback evidence.
Author identity quality
No named author or publisher identity could be extracted.
Evidence log2 steps · 8 lines
Schema.org attribution [warning]! Schema.org attribution is incomplete or relies only on publisher/fallback evidence.INFOSchema.org attributionINFOChecking structured data for author, creator, and publisher contributorsWARNCheck named Schema.org author count actual=0 expected="> 0" authorCount=0 publisherCount=0 namedContributors=0 authors=[] publishers=[] formats=[]WARNSchema.org attribution is incomplete or fallback-only authorCount=0 publisherCount=0 authors=[] publishers=[]Author identity quality [fail]! No named author or publisher identity could be extracted.INFOAuthor identity qualityINFOChecking contributors for stable identity signalsFAILCheck identified contributor count actual=0 expected="> 0" namedContributors=0 identifiedContributors=[] unidentifiedContributors=[]FAILNo named contributor identity could be extracted
Sign in to see 24 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