CanAgentUse tools

UCP Suite

Validate Universal Commerce Protocol discovery, then test product search, carts, checkout links, and merchant handoff flows.

MCP Playground

Connect to remote MCP servers, inspect tools and resources, test prompts, auth, headers, notifications, and JSON-RPC responses.

A2A Playground

Inspect Agent Cards, validate advertised endpoints, and prepare safe requests for agent-to-agent workflows.

Agent Website Viewer

Enter a public URL and see the roles, names, landmarks, controls, and blockers that shape how AI agents understand the page.

SCANNED
Jul 11, 2026, 4:32 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
48/100

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability56%Agent Easeof Use52%Security& Trust84%GEO, AIO, AEO50%SEO85%Performance44%Accessibility0%
  • 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

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

The Official Cybersecurity Summit favicon

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...

Open Agent View

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.

Fix with MCP / CLI
Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
56
Needs work2710View details
Discoverability
63
Needs work700
Content Readiness
63
Needs work1900
Bot Access Control
45
Priority fix110View details
Agent Ease of Use
52
Needs work221View details
Agent Commerce
72
Needs work211View details
Google Agentic Browsing
41
Priority fix010View details
GEO, AIO and AEO
50
Needs work300
GEO Readiness
Not Applicable
Not Applicable100
AIO Readiness
Not Applicable
Not Applicable100
AEO Readiness
Not Applicable
Not Applicable100
SEO
85
Mostly ready800
SEO
85
Mostly ready800
Security & Trust
84
Mostly ready2200
Security & Trust
84
Mostly ready2200
Performance
44
Priority fix900
Performance
44
Priority fix900

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

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

No explicit User-agent rules were found for major AI crawler tokens.

Details

02

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

  1. 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=0

Agent Ease of UseAgent CommerceInformational

ACP - Agentic Commerce Protocol

ACP - Agentic Commerce Protocol failed at "Review ACP cache and retry metadata".

28 Fail

Needs attention

ACP - Agentic Commerce Protocol

Failed check
01

Issue

ACP discovery returned 429 or 503 without Retry-After.

Details

02

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

  1. Fetch ACP discovery

    ACP-like signals were found, but /.well-known/acp.json was not available.

    ACP discovery is missing or not parseable
  2. 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

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.

Email code

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.

Fix with MCP / CLI

Score history

Public scan score over time

Public reports for this website origin. Select any point or report link to open that canonical report.

1 reports
Public score history report links
Scan dateScoreReadinessReport
48/100Level 2, Agent-LimitedCurrent report