CanAgentUse

CanAgentUse products

Agentic Browsing AuditCheck dialogs, menus, drawers, popovers, form errors, checkout steps, and other UI states that a standard Lighthouse scan may not capture.View product MCP ServerInstall CanAgentUse in your coding agent so scan findings become repo-ready fixes.View product WooCommerce PluginPublish UCP discovery and agent-ready commerce signals from WooCommerce without rebuilding checkout.View product Shopify PluginAdd UCP discovery, storefront metadata checks, and controlled cart-to-checkout flows for shopping agents.View product AgentReady CIScan commits and PRs, publish reports, and choose which agent-readiness failures should block merges.View product

CanAgentUse tools

UCP Suite

Validate Universal Commerce Protocol discovery, then test product search, carts, checkout links, and merchant handoff flows.

UCP ValidatorUCP Playground

MCP Playground

Connect to remote MCP servers, inspect tools and resources, test prompts, auth, headers, notifications, and JSON-RPC responses.

MCP Playground

A2A Playground

Inspect Agent Cards, validate advertised endpoints, and prepare safe requests for agent-to-agent workflows.

A2A Playground

Agent Website Viewer

Enter a public URL and see the roles, names, landmarks, controls, and blockers that shape how AI agents understand the page.

Agent Website Viewer
New Scan
https://www.ibm.com/products/cloudant
SCANNED
Jun 13, 2026, 12:44 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
40/100

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability22%Agent Easeof Use10%Security& Trust60%GEO, AIO, AEO63%SEO92%Performance30%Accessibility80%
  • AI Discoverability 22 out of 100
  • Agent Ease of Use 10 out of 100
  • Security & Trust 60 out of 100
  • GEO, AIO and AEO 63 out of 100
  • SEO 92 out of 100
  • Performance 30 out of 100
  • Accessibility 80 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

IBM Cloudant favicon

IBM Cloudant

Built on CouchDB technology, IBM Cloudant supports flexible, schema-free JSON document storage, which is ideal for apps that need rapid, iterative development.

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
22
Priority fix400
Discoverability
33
Priority fix200
Content Readiness
38
Priority fix200
Agent Ease of Use
10
Priority fix110View details
MCP
25
Priority fix100
Skill Discovery
5
Priority fix010View details
GEO, AIO and AEO
63
Needs work714View details
GEO Readiness
Not Applicable
Not Applicable300
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
54
Needs work114View details
SEO
92
Strong900
SEO
92
Strong900
Security & Trust
60
Needs work300
Security & Trust
60
Needs work300
Performance
30
Priority fix900
Performance
30
Priority fix900
Accessibility
80
Mostly ready210View details
Accessibility
80
Mostly ready210View details

Prioritized recommendations

Issues ranked by score impact

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

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer evidence and trust

AEO: Answer evidence and trust scored 0/100 and needs a fix.

8 Fail

Needs attention

AEO: Answer evidence and trust

Failed check
01

Issue

Missing AIO trust signals: author, publisher, freshnessDate, aboutOrContact, policyLinks.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Answer evidence and trust

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Answer evidence and trust scored 0/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first sections

AEO: Answer-first sections scored 65/100 and needs improvement.

4 Warning

Needs attention

AEO: Answer-first sections

Warning
01

Issue

10 section(s) may benefit from a clearer opening answer; this is optional for feature/card sections.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Answer-first sections

Score

65/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Answer-first sections scored 65/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question-led structure

AEO: Question-led structure scored 50/100 and needs improvement.

3 Warning

Needs attention

AEO: Question-led structure

Warning
01

Issue

10 section(s) may benefit from a clearer opening answer; this is optional for feature/card sections.

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Question-led structure

Score

50/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Question-led structure scored 50/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

AEO: Entity and definition clarity scored 85/100 and needs improvement.

1 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

Entity or definition gaps: no clear definition pattern found.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Entity and definition clarity

Score

85/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Entity and definition clarity scored 85/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer intent coverage

AEO: Answer intent coverage scored 70/100 and needs improvement.

1 Warning

Needs attention

AEO: Answer intent coverage

Warning
01

Issue

Missing likely AI Overview intent sections: how, cost, compare.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Answer intent coverage

Score

70/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Answer intent coverage scored 70/100 and needs improvement.

AccessibilityAccessibilityBrowser audit

`button`, `link`, and `menuitem` elements do not have accessible names.

100 Fail

Check name

`button`, `link`, and `menuitem` elements do not have accessible names.

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. [Learn how to make command elements more accessible](https://dequeuniversity.com/rules/axe/4.11/aria-command-name).

Evidence
{
  "description": "When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. [Learn how to make command elements more accessible](https://dequeuniversity.com/rules/axe/4.11/aria-command-name)."
}

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