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 13, 2026, 12:00 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
56/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability18%Agent Easeof Use6%Security& Trust60%GEO, AIO, AEO73%SEO100%Performance94%Accessibility83%
  • AI Discoverability 18 out of 100
  • Agent Ease of Use 6 out of 100
  • Security & Trust 60 out of 100
  • GEO, AIO and AEO 73 out of 100
  • SEO 100 out of 100
  • Performance 94 out of 100
  • Accessibility 83 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Home | SimplyInsured favicon

Home | SimplyInsured

We have every small business health insurance plan from every carrier with the lowest rates, guaranteed. Choose from the best medical, dental, and vision plans available in your area. SimplyInsured provides unbiased recommendations to help...

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
18
Priority fix400
Discoverability
17
Priority fix100
Content Readiness
43
Priority fix300
Agent Ease of Use
6
Priority fix010View details
Skill Discovery
5
Priority fix010View details
GEO, AIO and AEO
73
Needs work600
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable200
AEO Readiness
Not Applicable
Not Applicable200
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
60
Needs work300
Security & Trust
60
Needs work300
Performance
94
Strong1700
Performance
94
Strong1700
Accessibility
83
Mostly ready420View details
Accessibility
83
Mostly ready420View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

A2A Agent Card failed at "Fetch to find resource".

100 Fail

Needs attention

A2A Agent Card

Failed check
01

Issue

A2A Agent Card was not found at the expected path.

02

Why it matters

A2A Agent Cards let compatible clients discover agent skills, input and output modes, and the endpoint used to invoke those skills.

Check name

A2A Agent Card

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an agent card so A2A-compatible clients can discover capabilities.

Result

A2A Agent Card failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    A2A Agent Card was not found at the expected path.

AccessibilityAccessibilityBrowser audit

`[role]`s are not contained by their required parent element

50 Fail

Check name

`[role]`s are not contained by their required parent element

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. [Learn more about ARIA roles and required parent element](https://dequeuniversity.com/rules/axe/4.11/aria-required-parent).

Evidence
{
  "description": "Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. [Learn more about ARIA roles and required parent element](https://dequeuniversity.com/rules/axe/4.11/aria-required-parent)."
}

AccessibilityAccessibilityBrowser audit

`<html>` element does not have a `[lang]` attribute

50 Fail

Check name

`<html>` element does not have a `[lang]` attribute

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. [Learn more about the `lang` attribute](https://dequeuniversity.com/rules/axe/4.11/html-has-lang).

Evidence
{
  "description": "If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. [Learn more about the `lang` attribute](https://dequeuniversity.com/rules/axe/4.11/html-has-lang)."
}

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