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, 9:49 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
65/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability53%Agent Easeof Use50%Security& Trust83%GEO, AIO, AEO63%SEO100%Performance97%Accessibility81%
  • AI Discoverability 53 out of 100
  • Agent Ease of Use 50 out of 100
  • Security & Trust 83 out of 100
  • GEO, AIO and AEO 63 out of 100
  • SEO 100 out of 100
  • Performance 97 out of 100
  • Accessibility 81 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Upload your App - Diawi - Development and In-house Apps Wireless Installation

Upload an iOS or Android app, share the link with testers, and let them install it on device with one tap. Wireless app installation for development, ad-hoc and in-house builds. Since 2010.

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
53
Needs work2610View details
Discoverability
67
Needs work800
Content Readiness
50
Needs work1700
Bot Access Control
45
Priority fix110View details
GEO, AIO and AEO
63
Needs work1000
GEO Readiness
Not Applicable
Not Applicable300
AIO Readiness
Not Applicable
Not Applicable500
AEO Readiness
Not Applicable
Not Applicable200
SEO
100
Strong900
SEO
100
Strong900
Security & Trust
83
Mostly ready2122View details
Security & Trust
83
Mostly ready2122View details
Performance
97
Strong1400
Performance
97
Strong1400
Accessibility
81
Mostly ready510View details
Accessibility
81
Mostly ready510View 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.

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Evaluate fetch baseline".

50 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

default-src is present but not meaningfully restrictive.

02

Why it matters

Content Security Policy reduces the impact of injection bugs by limiting where scripts, styles, frames, forms, and other browser resources can load or execute.

Check name

Content-Security-Policy

Score

50/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Constrain browser resource loading and script execution with an enforcing Content-Security-Policy header.

Result

Content-Security-Policy failed at "Evaluate fetch baseline".

Validation steps

  1. Evaluate fetch baseline

    default-src is present but not meaningfully restrictive.

  2. Evaluate script execution

    default-src leaves script execution broadly unrestricted.

  3. Review hardening directives

    CSP is missing recommended hardening directives: object-src, base-uri, form-action.

  4. Review CSP reporting

    CSP does not define a reporting endpoint.

AccessibilityAccessibilityBrowser audit

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

100 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)."
}

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