Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 56 out of 100
- Agent Ease of Use 63 out of 100
- Security & Trust 76 out of 100
- GEO, AIO and AEO 59 out of 100
- SEO 92 out of 100
- Performance 85 out of 100
- Accessibility 93 out of 100
What AI sees of your website
Global leader in eye tracking for over 20 years - Tobii
Tobii is on a mission to improve the world with our eye tracking and attention computing technology that understands human attention and intent.
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 | 56 | Needs work | 27 | 3 | 2 | View details |
| Discoverability | 67 | Needs work | 8 | 0 | 0 | |
| Content Readiness | 59 | Needs work | 18 | 2 | 2 | View details |
| Bot Access Control | 45 | Priority fix | 1 | 1 | 0 | View details |
| Agent Ease of Use | 63 | Needs work | 5 | 0 | 0 | |
| API | 67 | Needs work | 1 | 0 | 0 | |
| Skill Discovery | 54 | Needs work | 1 | 0 | 0 | |
| Google Agentic Browsing | 100 | Strong | 3 | 0 | 0 | |
| GEO, AIO and AEO | 59 | Needs work | 6 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| Security & Trust | 76 | Mostly ready | 19 | 0 | 0 | |
| Security & Trust | 76 | Mostly ready | 19 | 0 | 0 | |
| Performance | 85 | Mostly ready | 17 | 0 | 0 | |
| Performance | 85 | Mostly ready | 17 | 0 | 0 |
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 "Classify AI crawler rules".
69 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 DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
25 Fail
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
Needs attention
Content freshness signals
Issue
Content freshness signals are invalid: json-ld uploadDate is not a parseable date ()..
Details
Why it matters
Freshness signals help agents, crawlers, and search systems decide whether content is current enough to cite, summarize, cache, or compare against newer sources.
Check name
Content freshness signals
Score
50/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Expose modified and published dates for freshness-aware retrieval, citation, and ranking.
Result
Content freshness signals is missing or incomplete.
Validation steps
Validate structured freshness dates
No Schema.org freshness dates were found.
Structured freshness dates are missing or invalid
Check date validity and consistency
json-ld uploadDate is not a parseable date ().; Sitemap lastmod dates and structured modified/upload dates do not appear to agree.
Freshness dates are invalid or inconsistent
Evidence log2 steps · 8 lines
Validate structured freshness dates [warning]! No Schema.org freshness dates were found.INFOValidate structured freshness datesINFOCollecting Schema.org freshness dates from JSON-LD, Microdata, and RDFaWARNCheck structured freshness date count actual=2 expected="> 0" invalidDateCount=1 formats={"json-ld":2} alternateDates=[{"source":"json-ld","channel":"structured","property":"uploadDate","value":"2025-11-25 00:00","parsed":"2025-11-25T00:00:00.000Z","location":"JSON-LD structured data <script type=\"application/ld+json\"> property VideoObject.uploadDate"},{"source":"sitemap","channel":"sitemap","property":"lastmod","value":"2026-06-16T13:32:09.894Z","parsed":"2026-06-16T13:32:09.894Z","location":"matching sitemap <lastmod> entry for this page URL"}]WARNStructured freshness dates include invalid values invalidDateCount=1Check date validity and consistency [fail]! json-ld uploadDate is not a parseable date ().; Sitemap lastmod dates and structured modified/upload dates do not appear to agree.INFOCheck date validity and consistencyINFOChecking collected freshness dates for invalid values, future dates, and inconsistent orderingFAILCheck critical freshness issue count actual=1 expected=0 warningIssueCount=1 issues=[{"severity":"fail","message":"json-ld uploadDate is not a parseable date ()."},{"severity":"warning","message":"Sitemap lastmod dates and structured modified/upload dates do not appear to agree.","details":{"left":[{"source":"sitemap","channel":"sitemap","property":"lastmod","value":"2026-06-16T13:32:09.894Z","parsed":"2026-06-16T13:32:09.894Z","where":"matching sitemap <lastmod> entry for this page URL"}],"right":[{"source":"json-ld","channel":"structured","property":"uploadDate","value":"2025-11-25 00:00","parsed":"2025-11-25T00:00:00.000Z","location":"script[type=\"application/ld+json\"] > VideoObject.uploadDate","where":"JSON-LD structured data <script type=\"application/ld+json\"> property VideoObject.uploadDate","schemaTypes":["VideoObject"]}]}}]FAILInvalid freshness date issue found issues=["json-ld uploadDate is not a parseable date ()."]
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.
Details
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.
Schema.org author attribution is missing or incomplete
Author identity quality
No named author or publisher identity could be extracted.
Author identity quality is incomplete
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 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
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 |
|---|---|---|---|
| 69/100 | Level 3, Bot-Aware | Current report |