Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 53 out of 100
- Agent Ease of Use 49 out of 100
- Security & Trust 54 out of 100
- GEO, AIO and AEO 72 out of 100
- SEO 100 out of 100
- Performance 96 out of 100
- Accessibility 81 out of 100
What AI sees of your website
New Era Casino
Step into the world of secure and fast online banking at New Era Casino. Explore top-rated casinos offering instant bank transfers, fast withdrawals, and diverse payment methods.
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 | 53 | Needs work | 23 | 5 | 1 | View details |
| Discoverability | 40 | Priority fix | 4 | 0 | 0 | |
| Content Readiness | 65 | Needs work | 15 | 1 | 1 | View details |
| Bot Access Control | 55 | Needs work | 4 | 4 | 0 | View details |
| Agent Ease of Use | 49 | Priority fix | 1 | 1 | 0 | View details |
| Google Agentic Browsing | 47 | Priority fix | 1 | 1 | 0 | View details |
| GEO, AIO and AEO | 72 | Needs work | 10 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 2 | 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 | 54 | Needs work | 10 | 0 | 0 | |
| Security & Trust | 54 | Needs work | 10 | 0 | 0 | |
| Performance | 96 | Strong | 20 | 0 | 0 | |
| Performance | 96 | Strong | 20 | 0 | 0 |
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 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
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 403.
/ai.txt could not be fetched when present
Validate transport
ai.txt appears to be an HTML page or error document rather than a plain-text policy.
/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 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="text/html;charset=utf8" length=116FAIL/ai.txt returned HTTP 403. statusCode=403Validate transport [fail]! ai.txt appears to be an HTML page or error document rather than a plain-text policy.INFOValidate transportINFOChecking ai.txt media type, size, line count, and whether the response looks like plain text contentType="text/html;charset=utf8" length=116 lineCount=3FAILCompare media type to preferred text/plain transport actual="text/html" expected="text/plain preferred; readable text required"FAILai.txt appears to be an HTML page or error document rather than a plain-text policy.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.
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
0 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: dateModified (2024-08-27T16:26:23+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00).; dateModified (2024-08-27T16:19:36+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00).; dateModified (2024-08-27T16:16:09+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00).; dateModified (2024-08-27T16:12:59+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00).; dateModified (2024-08-27T16:04:17+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00).; dateModified (2024-08-27T16:19:36+00:00) is earlier than datePublished (2024-08-27T16:26:21+00:00).; dateModified (2024-08-27T16:16:09+00:00) is earlier than datePublished (2024-08-27T16:26:21+00:00).; dateModified (2024-08-27T16:12:59+00:00) is earlier than datePublished (2024-08-27T16:26:21+00:00).; dateModified (2024-08-27T16:04:17+00:00) is earlier than datePublished (2024-08-27T16:26:21+00:00).; dateModified (2024-08-27T16:16:09+00:00) is earlier than datePublished (2024-08-27T16:19:21+00:00).; dateModified (2024-08-27T16:12:59+00:00) is earlier than datePublished (2024-08-27T16:19:21+00:00).; dateModified (2024-08-27T16:04:17+00:00) is earlier than datePublished (2024-08-27T16:19:21+00:00).; dateModified (2024-08-27T16:12:59+00:00) is earlier than datePublished (2024-08-27T16:16:06+00:00).; dateModified (2024-08-27T16:04:17+00:00) is earlier than datePublished (2024-08-27T16:16:06+00:00).; dateModified (2024-08-27T16:04:17+00:00) is earlier than datePublished (2024-08-27T16:12:49+00:00)..
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
100/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
Corroborate with sitemap lastmod
Add a sitemap entry with a valid lastmod for the canonical page URL when sitemap corroboration is useful.
Sitemap lastmod corroboration is missing
Check date validity and consistency
dateModified (2024-08-27T16:26:23+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00).; dateModified (2024-08-27T16:19:36+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00).; dateModified (2024-08-27T16:16:09+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00).; dateModified (2024-08-27T16:12:59+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00).; dateModified (2024-08-27T16:04:17+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00).; dateModified (2024-08-27T16:19:36+00:00) is earlier than datePublished (2024-08-27T16:26:21+00:00).; dateModified (2024-08-27T16:16:09+00:00) is earlier than datePublished (2024-08-27T16:26:21+00:00).; dateModified (2024-08-27T16:12:59+00:00) is earlier than datePublished (2024-08-27T16:26:21+00:00).; dateModified (2024-08-27T16:04:17+00:00) is earlier than datePublished (2024-08-27T16:26:21+00:00).; dateModified (2024-08-27T16:16:09+00:00) is earlier than datePublished (2024-08-27T16:19:21+00:00).; dateModified (2024-08-27T16:12:59+00:00) is earlier than datePublished (2024-08-27T16:19:21+00:00).; dateModified (2024-08-27T16:04:17+00:00) is earlier than datePublished (2024-08-27T16:19:21+00:00).; dateModified (2024-08-27T16:12:59+00:00) is earlier than datePublished (2024-08-27T16:16:06+00:00).; dateModified (2024-08-27T16:04:17+00:00) is earlier than datePublished (2024-08-27T16:16:06+00:00).; dateModified (2024-08-27T16:04:17+00:00) is earlier than datePublished (2024-08-27T16:12:49+00:00).
Freshness dates are invalid or inconsistent
Evidence log2 steps · 8 lines
Corroborate with sitemap lastmod [warning]INFOCorroborate with sitemap lastmodINFODiscovering sitemap candidates and matching the scanned page URL candidateCount=1 attempts=1WARNCheck matching sitemap lastmod actual="no match" expected="valid match when available" robotsStatusCode=200WARNNo matching sitemap lastmod found after sitemap attempts attempts=1Check date validity and consistency [fail]! dateModified (2024-08-27T16:26:23+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00).; dateModified (2024-08-27T16:19:36+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00).; dateModified (2024-08-27T16:16:09+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00).; dateModified (2024-08-27T16:12:59+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00).; dateModified (2024-08-27T16:04:17+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00).; dateModified (2024-08-27T16:19:36+00:00) is earlier than datePublished (2024-08-27T16:26:21+00:00).; dateModified (2024-08-27T16:16:09+00:00) is earlier than datePublished (2024-08-27T16:26:21+00:00).; dateModified (2024-08-27T16:12:59+00:00) is earlier than datePublished (2024-08-27T16:26:21+00:00).; dateModified (2024-08-27T16:04:17+00:00) is earlier than datePublished (2024-08-27T16:26:21+00:00).; dateModified (2024-08-27T16:16:09+00:00) is earlier than datePublished (2024-08-27T16:19:21+00:00).; dateModified (2024-08-27T16:12:59+00:00) is earlier than datePublished (2024-08-27T16:19:21+00:00).; dateModified (2024-08-27T16:04:17+00:00) is earlier than datePublished (2024-08-27T16:19:21+00:00).; dateModified (2024-08-27T16:12:59+00:00) is earlier than datePublished (2024-08-27T16:16:06+00:00).; dateModified (2024-08-27T16:04:17+00:00) is earlier than datePublished (2024-08-27T16:16:06+00:00).; dateModified (2024-08-27T16:04:17+00:00) is earlier than datePublished (2024-08-27T16:12:49+00:00).INFOCheck date validity and consistencyINFOChecking collected freshness dates for invalid values, future dates, and inconsistent orderingFAILCheck critical freshness issue count actual=15 expected=0 warningIssueCount=0 issues=[{"severity":"fail","message":"dateModified (2024-08-27T16:26:23+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00)."},{"severity":"fail","message":"dateModified (2024-08-27T16:19:36+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00)."},{"severity":"fail","message":"dateModified (2024-08-27T16:16:09+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00)."},{"severity":"fail","message":"dateModified (2024-08-27T16:12:59+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00)."},{"severity":"fail","message":"dateModified (2024-08-27T16:04:17+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00)."},{"severity":"fail","message":"dateModified (2024-08-27T16:19:36+00:00) is earlier than datePublished (2024-08-27T16:26:21+00:00)."},{"severity":"fail","message":"dateModified (2024-08-27T16:16:09+00:00) is earlier than datePublished (2024-08-27T16:26:21+00:00)."},{"severity":"fail","message":"dateModified (2024-08-27T16:12:59+00:00) is earlier than datePublished (2024-08-27T16:26:21+00:00)."},{"severity":"fail","message":"dateModified (2024-08-27T16:04:17+00:00) is earlier than datePublished (2024-08-27T16:26:21+00:00)."},{"severity":"fail","message":"dateModified (2024-08-27T16:16:09+00:00) is earlier than datePublished (2024-08-27T16:19:21+00:00)."}]FAILInvalid freshness date issue found issues=["dateModified (2024-08-27T16:26:23+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00).","dateModified (2024-08-27T16:19:36+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00).","dateModified (2024-08-27T16:16:09+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00).","dateModified (2024-08-27T16:12:59+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00).","dateModified (2024-08-27T16:04:17+00:00) is earlier than datePublished (2024-08-27T16:29:24+00:00)."]
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 32 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