Export Report
OVERALL SCORE
Level 2, Agent-Limited
- AI Discoverability 56 out of 100
- Agent Ease of Use 52 out of 100
- Security & Trust 84 out of 100
- GEO, AIO and AEO 50 out of 100
- SEO 85 out of 100
- Performance 44 out of 100
- Accessibility 0 out of 100
What AI sees of your website
The Official Cybersecurity Summit
The Cybersecurity Summit, ranked as one of the “Top 50 Must-Attend Conferences”, connect C-Level & Senior Executives responsible for protecting their company’s critical infrastructures with cutting-edge technology providers & renowned info...
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 | 1 | 0 | View details |
| Discoverability | 63 | Needs work | 7 | 0 | 0 | |
| Content Readiness | 63 | Needs work | 19 | 0 | 0 | |
| Bot Access Control | 45 | Priority fix | 1 | 1 | 0 | View details |
| Agent Ease of Use | 52 | Needs work | 2 | 2 | 1 | View details |
| Agent Commerce | 72 | Needs work | 2 | 1 | 1 | View details |
| Google Agentic Browsing | 41 | Priority fix | 0 | 1 | 0 | View details |
| GEO, AIO and AEO | 50 | Needs work | 3 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 1 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 1 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 1 | 0 | 0 | |
| SEO | 85 | Mostly ready | 8 | 0 | 0 | |
| SEO | 85 | Mostly ready | 8 | 0 | 0 | |
| Security & Trust | 84 | Mostly ready | 22 | 0 | 0 | |
| Security & Trust | 84 | Mostly ready | 22 | 0 | 0 | |
| Performance | 44 | Priority fix | 9 | 0 | 0 | |
| Performance | 44 | Priority fix | 9 | 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=0Agent Ease of UseAgent CommerceInformational
ACP - Agentic Commerce Protocol
ACP - Agentic Commerce Protocol failed at "Review ACP cache and retry metadata".
28 Fail
Agent Ease of UseAgent CommerceInformational
ACP - Agentic Commerce Protocol
ACP - Agentic Commerce Protocol failed at "Review ACP cache and retry metadata".
Needs attention
ACP - Agentic Commerce Protocol
Issue
ACP discovery returned 429 or 503 without Retry-After.
Details
Why it matters
ACP discovery lets agents find the seller's ACP API base URL, supported versions, transports, and stable services before attempting authenticated checkout-session negotiation.
Check name
ACP - Agentic Commerce Protocol
Score
72/100
Status
fail
Category
Agent Commerce
Maturity
Informational
Goal
Expose valid ACP discovery when this origin supports Agentic Commerce Protocol workflows.
Result
ACP - Agentic Commerce Protocol failed at "Review ACP cache and retry metadata".
Validation steps
Fetch ACP discovery
ACP-like signals were found, but /.well-known/acp.json was not available.
ACP discovery is missing or not parseable
Review ACP cache and retry metadata
ACP discovery returned 429 or 503 without Retry-After.
ACP discovery cache or retry metadata needs review
Evidence log2 steps · 10 lines
Fetch ACP discovery [warning]! ACP-like signals were found, but /.well-known/acp.json was not available.INFOFetch ACP discovery status="warning"INFOFetch canonical ACP discovery /.well-known/acp.json statusCode=429 contentType="text/html; charset=UTF-8" parsed=falseINFOFetch compatibility ACP discovery /.well-known/acp statusCode=429 contentType="text/html; charset=UTF-8" parsed=falseWARNCheck canonical ACP discovery response actual=false expected=true canonicalFound=false compatibilityFound=falseWARNACP-like signals were found, but /.well-known/acp.json was not available.Review ACP cache and retry metadata [fail]! ACP discovery returned 429 or 503 without Retry-After.INFOReview ACP cache and retry metadata status="fail"INFOInspect ACP discovery cache headers and retry guidance statusCode=429 cacheControl=null retryAfter=nullFAILCheck Cache-Control header on successful discovery actual="missing" expected="present for cacheable public discovery"FAILCheck Retry-After on rate-limit or unavailable responses actual="not required" expected="present only for 429 or 503"FAILACP discovery returned 429 or 503 without Retry-After.
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 45 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 |
|---|---|---|---|
| 48/100 | Level 2, Agent-Limited | Current report |