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, 3:23 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
66/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability72%Agent Easeof Use46%Security& Trust73%GEO, AIO, AEO73%SEO100%Performance100%Accessibility47%
  • AI Discoverability 72 out of 100
  • Agent Ease of Use 46 out of 100
  • Security & Trust 73 out of 100
  • GEO, AIO and AEO 73 out of 100
  • SEO 100 out of 100
  • Performance 100 out of 100
  • Accessibility 47 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Keyword Rank Tracker and AI Visibility Tracker | Keyword.com favicon

Keyword Rank Tracker and AI Visibility Tracker | Keyword.com

A keyword rank tracker and AI visibility monitoring platform for SEO agencies. Track Google rankings, AI Overviews, and local results with data you can trust.

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
72
Needs work3900
Discoverability
67
Needs work800
Content Readiness
88
Mostly ready2800
Bot Access Control
63
Needs work300
Agent Ease of Use
46
Priority fix310View details
Auth
48
Priority fix100
Google Agentic Browsing
67
Needs work210View details
GEO, AIO and AEO
73
Needs work1200
GEO Readiness
Not Applicable
Not Applicable400
AIO Readiness
Not Applicable
Not Applicable500
AEO Readiness
Not Applicable
Not Applicable300
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
73
Needs work1610View details
Security & Trust
73
Needs work1610View details
Performance
100
Strong1700
Performance
100
Strong1700
Accessibility
47
Priority fix010View details
Accessibility
47
Priority fix010View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Find enforcing CSP delivery".

60 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

Applicable HTML response is missing an enforcing Content-Security-Policy header.

Details

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

40/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 "Find enforcing CSP delivery".

Validation steps

  1. Find enforcing CSP delivery

    Applicable HTML response is missing an enforcing Content-Security-Policy header.

    Enforcing Content-Security-Policy header is missing
Evidence log1 step · 4 lines
Find enforcing CSP delivery [fail]! Applicable HTML response is missing an enforcing Content-Security-Policy header.INFOFind enforcing CSP deliveryINFORead CSP delivery headers enforcingHeader="missing" reportOnlyHeader="missing" metaPolicyCount=0 legacyHeadersPresent=[]FAILRequire enforcing Content-Security-Policy header actual="missing" expected="present" issue="Applicable HTML response is missing an enforcing Content-Security-Policy header."FAILApplicable HTML response is missing an enforcing Content-Security-Policy header.

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

AccessibilityAccessibilityBrowser audit

Certain ARIA roles must contain particular children

100 Fail

Check name

Certain ARIA roles must contain particular children

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Certain ARIA roles must contain particular children

Evidence
{
  "ruleId": "aria-required-children",
  "impact": "critical",
  "description": "Ensure elements with an ARIA role that require child roles contain them",
  "tags": [
    "cat.aria",
    "wcag2a",
    "wcag131",
    "EN-301-549",
    "EN-9.1.3.1",
    "RGAAv4",
    "RGAA-9.3.1"
  ],
  "affectedNodeCount": 1,
  "nodes": [
    {
      "target": [
        ".nav-menu"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 70
      },
      "failureSummary": "Fix any of the following:\n  Element has children which are not allowed: button, button[aria-haspopup]"
    }
  ]
}

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