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
Jun 15, 2026, 2:03 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
63/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability44%Agent Easeof Use50%Security& Trust91%GEO, AIO, AEO58%SEO100%Performance98%Accessibility92%
  • AI Discoverability 44 out of 100
  • Agent Ease of Use 50 out of 100
  • Security & Trust 91 out of 100
  • GEO, AIO and AEO 58 out of 100
  • SEO 100 out of 100
  • Performance 98 out of 100
  • Accessibility 92 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Scoutzie - Build, Launch, and Win With Your MVP | Startup Development Agency favicon

Scoutzie - Build, Launch, and Win With Your MVP | Startup Development Agency

Build and launch your MVP in just 2 weeks. Expert startup development agency helping founders turn ideas into profitable products. Get real users fast.

Open Agent View

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.

Fix with MCP / CLI
Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
44
Priority fix1610View details
Discoverability
67
Needs work800
Content Readiness
19
Priority fix700
Bot Access Control
45
Priority fix110View details
GEO, AIO and AEO
58
Needs work900
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable400
AEO Readiness
Not Applicable
Not Applicable300
SEO
100
Strong900
SEO
100
Strong900
Security & Trust
91
Strong2200
Security & Trust
91
Strong2200
Performance
98
Strong2000
Performance
98
Strong2000
Accessibility
92
Strong720View details
Accessibility
92
Strong720View details

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.

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.

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

AccessibilityAccessibilityBrowser audit

Background and foreground colors do not have a sufficient contrast ratio.

50 Fail

Check name

Background and foreground colors do not have a sufficient contrast ratio.

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast](https://dequeuniversity.com/rules/axe/4.11/color-contrast).

Evidence
{
  "description": "Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast](https://dequeuniversity.com/rules/axe/4.11/color-contrast)."
}

AccessibilityAccessibilityBrowser audit

Elements with visible text labels do not have matching accessible names.

50 Fail

Check name

Elements with visible text labels do not have matching accessible names.

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. [Learn more about accessible names](https://dequeuniversity.com/rules/axe/4.11/label-content-name-mismatch).

Evidence
{
  "description": "Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. [Learn more about accessible names](https://dequeuniversity.com/rules/axe/4.11/label-content-name-mismatch)."
}

Sign in to see 26 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.

Fix with MCP / CLI

Score history