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 12, 2026, 11:24 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
32/100

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability23%Agent Easeof Use44%Security& Trust54%GEO, AIO, AEO28%SEO92%Performance51%Accessibility0%
  • AI Discoverability 23 out of 100
  • Agent Ease of Use 44 out of 100
  • Security & Trust 54 out of 100
  • GEO, AIO and AEO 28 out of 100
  • SEO 92 out of 100
  • Performance 51 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

No page title captured

No page metadata or readable excerpt was captured.

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
23
Priority fix1300
Discoverability
28
Priority fix300
Content Readiness
13
Priority fix800
Bot Access Control
26
Priority fix200
Agent Ease of Use
44
Priority fix2830View details
API
44
Priority fix700
Auth
42
Priority fix700
MCP
42
Priority fix400
Skill Discovery
51
Needs work200
Agent Commerce
46
Priority fix820View details
Google Agentic Browsing
37
Priority fix010View details
GEO, AIO and AEO
28
Priority fix400
GEO Readiness
Not Applicable
Not Applicable100
AIO Readiness
Not Applicable
Not Applicable200
AEO Readiness
Not Applicable
Not Applicable100
SEO
92
Strong800
SEO
92
Strong800
Security & Trust
54
Needs work1100
Security & Trust
54
Needs work1100
Performance
51
Needs work800
Performance
51
Needs work800
Accessibility
0
Priority fix010View details
Accessibility
0
Priority fix010View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Agent Ease of UseAgent CommerceInformational

ACP - Agentic Commerce Protocol

ACP - Agentic Commerce Protocol failed at "Fetch ACP discovery".

54 Fail

Needs attention

ACP - Agentic Commerce Protocol

Failed check
01

Issue

ACP discovery content type "text/html; charset=UTF-8" is not JSON-compatible.

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

46/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 "Fetch ACP discovery".

Validation steps

  1. Fetch ACP discovery

    ACP discovery content type "text/html; charset=UTF-8" is not JSON-compatible.

    ACP discovery is missing or not parseable
  2. Validate ACP discovery shape

    ACP discovery could not be parsed.

    ACP discovery protocol metadata is invalid
Evidence log2 steps · 9 lines
Fetch ACP discovery [fail]! ACP discovery content type "text/html; charset=UTF-8" is not JSON-compatible.INFOFetch ACP discovery status="fail"INFOFetch canonical ACP discovery /.well-known/acp.json statusCode=202 contentType="text/html; charset=UTF-8" parsed=false error="Unexpected end of JSON input"FAILCheck canonical ACP discovery response actual=false expected=true canonicalFound=trueFAILACP discovery content type "text/html; charset=UTF-8" is not JSON-compatible.Validate ACP discovery shape [fail]! ACP discovery could not be parsed.INFOValidate ACP discovery shape status="fail"INFOValidate ACP protocol object, name, date version, and supported_versions orderingFAILCheck protocol object and name actual={"hasProtocol":false} expected={"hasProtocol":true,"protocolName":"acp"}FAILCheck protocol version history actual={"supportedVersionCount":0,"supportedVersionsOrdered":false,"supportedVersionsEndWithCurrent":false} expected="date version with chronological supported_versions ending in current version"FAILACP discovery could not be parsed.

AccessibilityAccessibilityBrowser audit

Accessibility audit

100 Fail

Check name

Accessibility audit

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Make sure the page can load in Chrome and run Accessibility checks.

Evidence
{
  "error": "Accessibility audit did not return a result."
}

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