Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 56 out of 100
- Agent Ease of Use 53 out of 100
- Security & Trust 88 out of 100
- GEO, AIO and AEO 54 out of 100
- SEO 92 out of 100
- Performance 81 out of 100
- Accessibility 0 out of 100
What AI sees of your website
News, Sports, Business | Knoxville News Sentinel
News, crime, weather, photos, video, University of Tennessee, Tennessee Vols football, and sports for Knoxville, Tennessee, from the Knoxville News Sentinel.
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 | 56 | Needs work | 26 | 4 | 0 | View details |
| Discoverability | 67 | Needs work | 8 | 0 | 0 | |
| Content Readiness | 55 | Needs work | 16 | 0 | 0 | |
| Bot Access Control | 48 | Priority fix | 2 | 4 | 0 | View details |
| Agent Ease of Use | 53 | Needs work | 3 | 1 | 0 | View details |
| API | 67 | Needs work | 1 | 0 | 0 | |
| Auth | 48 | Priority fix | 1 | 0 | 0 | |
| Google Agentic Browsing | 50 | Needs work | 1 | 1 | 0 | View details |
| GEO, AIO and AEO | 54 | Needs work | 5 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 1 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 1 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| Security & Trust | 88 | Mostly ready | 24 | 0 | 0 | |
| Security & Trust | 88 | Mostly ready | 24 | 0 | 0 | |
| Performance | 81 | Mostly ready | 17 | 0 | 0 | |
| Performance | 81 | Mostly ready | 17 | 0 | 0 | |
| Accessibility | 0 | Priority fix | 0 | 1 | 0 | View details |
| Accessibility | 0 | Priority fix | 0 | 1 | 0 | View details |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
AI DiscoverabilityBot Access ControlEmerging recommendation
ai.txt policy
ai.txt policy failed at "Fetch /ai.txt".
100 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 406.
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
0/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 406.
/ai.txt could not be fetched when present
Validate transport
ai.txt was reachable but empty.
/ai.txt transport is invalid or not plain text
Parse ai.txt policy
Transport validation failed before policy parsing could be trusted.
/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 log4 steps · 18 lines
Fetch /ai.txt [fail]! /ai.txt returned HTTP 406.INFOFetch /ai.txtINFORequesting optional advisory policy file at /ai.txtFAILCompare /ai.txt HTTP response actual=406 expected="2xx when ai.txt is intentionally published; 404/410 means absent optional file" contentType=null length=0FAIL/ai.txt returned HTTP 406. statusCode=406Validate transport [fail]! ai.txt was reachable but empty.INFOValidate transportINFOChecking ai.txt media type, size, line count, and whether the response looks like plain text contentType=null length=0 lineCount=1FAILCompare media type to preferred text/plain transport actual="missing" expected="text/plain preferred; readable text required"FAILai.txt was reachable but empty.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 [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.
AccessibilityAccessibilityBrowser audit
Accessibility audit
100 Fail
AccessibilityAccessibilityBrowser audit
Accessibility audit
Check name
Accessibility audit
Score
0/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
Make sure the page can load in Chrome and run Accessibility checks.
Evidence
{
"error": "__name is not defined"
}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 36 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