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://entityclouds.com/
SCANNED
Jul 11, 2026, 9:18 AM
VISIBILITY
Public
SUITE2026.06.10
Rescan Report
Share Report
Copy Report Link
Export Report
62/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability48%Agent Easeof Use61%Security& Trust78%GEO, AIO, AEO26%SEO45%Performance100%Accessibility79%
  • AI Discoverability 48 out of 100
  • Agent Ease of Use 61 out of 100
  • Security & Trust 78 out of 100
  • GEO, AIO and AEO 26 out of 100
  • SEO 45 out of 100
  • Performance 100 out of 100
  • Accessibility 79 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

WordPress › Error

No page metadata or readable excerpt was captured.

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
48
Priority fix2210View details
Discoverability
67
Needs work800
Content Readiness
28
Priority fix1100
Bot Access Control
50
Needs work310View details
Agent Ease of Use
61
Needs work400
Skill Discovery
54
Needs work100
Google Agentic Browsing
100
Strong300
GEO, AIO and AEO
26
Priority fix431View details
GEO Readiness
Not Applicable
Not Applicable100
AIO Readiness
37
Priority fix231View details
AEO Readiness
Not Applicable
Not Applicable100
SEO
45
Priority fix500
SEO
45
Priority fix500
Security & Trust
78
Mostly ready1711View details
Security & Trust
78
Mostly ready1711View details
Performance
100
Strong2100
Performance
100
Strong2100

Prioritized recommendations

Issues ranked by score impact

6 items need attention

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

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

80 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

20/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. Validate CSP applicability

    The response is an error page, so it may not represent the browser application.

    CSP applicability could not be confirmed for a browser-rendered page

  2. Find enforcing CSP delivery

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

    Enforcing Content-Security-Policy header is missing
Evidence log2 steps · 8 lines
Validate CSP applicability [warning]! The response is an error page, so it may not represent the browser application.INFOValidate CSP applicabilityINFOInspect scanned response finalUrl="https://entityclouds.com/" status=500 contentType="text/html; charset=UTF-8" htmlBytes=3466WARNCompare response type actual="HTML document" expected="browser-rendered HTML document" reason="The response is an error page, so it may not represent the browser application."WARNThe response is an error page, so it may not represent the browser application.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.

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.

Details

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.

    robots.txt lacks explicit AI crawler rules
Evidence log1 step · 6 lines
Classify AI crawler rules [fail]! No explicit User-agent rules were found for major AI crawler tokens.INFOClassify AI crawler rulesINFOParsing User-agent groups and Allow/Disallow records for known AI crawler tokens evaluatedPath="/"INFOEvaluating exact User-agent matches before wildcard fallback exactAiPolicyCount=0 totalCrawlerTokens=18FAILNo explicit AI crawler User-agent groups were found examplesExpected=["GPTBot","OAI-SearchBot","ClaudeBot","Google-Extended","CCBot"]FAILCompare explicit AI crawler coverage actual=0 expected="> 0 explicit non-search AI crawler policies" missingTokens=["GPTBot","OAI-SearchBot","ChatGPT-User","ClaudeBot","Claude-SearchBot","Claude-User","Google-Extended","Applebot-Extended","Amazonbot","Amzn-SearchBot","Amzn-User","PerplexityBot"]INFOResolved effective root-path policy for crawler tokens blocked=0 allowed=21 unspecified=0

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Google Search eligibility

AIO: Google Search eligibility scored 0/100 and needs a fix.

8 Fail

Needs attention

AIO: Google Search eligibility

Failed check
01

Issue

HTTP status is 500; Google Search AI features require an indexable 2xx page. Noindex directive found: noindex, follow. Canonical tag is missing. Only 16 visible words were detected.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Google Search eligibility

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Google Search eligibility scored 0/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Source and trust signals

AIO: Source and trust signals scored 33/100 and needs a fix.

5 Fail

Needs attention

AIO: Source and trust signals

Failed check
01

Issue

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

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Source and trust signals

Score

33/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Source and trust signals scored 33/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Visible content clarity

AIO: Visible content clarity scored 42/100 and needs a fix.

4 Fail

Needs attention

AIO: Visible content clarity

Failed check
01

Issue

Expected exactly one h1, found 0. Missing meta description or Open Graph description. Only 16 visible words were detected. Heading outline issues were detected.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Visible content clarity

Score

42/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Visible content clarity scored 42/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Page experience proxy

AIO: Page experience proxy scored 75/100 and needs improvement.

2 Warning

Needs attention

AIO: Page experience proxy

Warning
01

Issue

Only 16 words of visible rendered text were detected.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Page experience proxy

Score

75/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Page experience proxy scored 75/100 and needs improvement.

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