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.

Rescan Report
Share Report
Copy Report Link
Export Report
58/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability59%Agent Easeof Use56%Security& Trust81%GEO, AIO, AEO61%SEO92%Performance66%Accessibility33%
  • AI Discoverability 59 out of 100
  • Agent Ease of Use 56 out of 100
  • Security & Trust 81 out of 100
  • GEO, AIO and AEO 61 out of 100
  • SEO 92 out of 100
  • Performance 66 out of 100
  • Accessibility 33 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

IP Analytics Software for Patent Intelligence Insights favicon

IP Analytics Software for Patent Intelligence Insights

IP analytics software to uncover patent trends, track competitors, and drive innovation with powerful IP intelligence and data-driven insights

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
59
Needs work2700
Discoverability
47
Priority fix600
Content Readiness
67
Needs work1800
Bot Access Control
63
Needs work300
Agent Ease of Use
56
Needs work310View details
API
67
Needs work100
Google Agentic Browsing
67
Needs work210View details
GEO, AIO and AEO
61
Needs work700
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable200
SEO
92
Strong900
SEO
92
Strong900
Security & Trust
81
Mostly ready2211View details
Security & Trust
81
Mostly ready2211View details
Performance
66
Needs work1310View details
Performance
66
Needs work1310View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Evaluate script execution".

27 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

script-src allows dangerous script schemes: data:, blob:.

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

73/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 "Evaluate script execution".

Validation steps

  1. Evaluate script execution

    script-src allows dangerous script schemes: data:, blob:.

    CSP script execution policy is unsafe
  2. Review CSP reporting

    CSP does not define a reporting endpoint.

    CSP reporting is missing or incomplete
Evidence log2 steps · 8 lines
Evaluate script execution [fail]! script-src allows dangerous script schemes: data:, blob:.INFOEvaluate script executionINFOInspect effective script directive effectiveDirective="script-src" sources=["'self'","'unsafe-inline'","'unsafe-eval'","data:","blob:","https://www.googletagmanager.com","https://www.google-analytics.com","https://stats.g.doubleclick.net","https://googleads.g.doubleclick.net","https://www.clarity.ms","https://scripts.clarity.ms","https://analytics.ahrefs.com","https://analytics.wpmucdn.com","https://tags.clickagy.com","https://js.adsrvr.org","https://cdn.cookielaw.org","https://static.onetrust.com","https://*.onetrust.com","https://*.cookielaw.org","https://js.hs-scripts.com","https://js-na1.hs-scripts.com","https://js.hs-analytics.net","https://js.hubspot.com","https://js.hscollectedforms.net","https://js.hsforms.net","https://js.hscta.net","https://cta-service-cms2.hubspot.com","https://js.hs-banner.com","https://js.hsadspixel.net","https://js.usemessages.com","https://js.zi-scripts.com","https://static.hsappstatic.net","https://snap.licdn.com","https://platform-api.sharethis.com","https://buttons-config.sharethis.com","https://ws-assets.zoominfo.com","https://ws.zoominfo.com","https://www.youtube.com","https://yoast.com","https://*.yoast.com","https://ams.wpml.org"]FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":true,"hasUnsafeEval":true,"hasWildcardHost":false,"hasBroadScheme":false,"dangerousSchemes":["data:","blob:"]} expected="constrained script sources without unsafe execution allowances" issue="script-src allows dangerous script schemes: data:, blob:."FAILscript-src allows dangerous script schemes: data:, blob:.Review CSP reporting [warning]! CSP does not define a reporting endpoint.INFOReview CSP reportingINFOInspect CSP reporting directives reportOnlyHeaderPresent=false reportOnlyDirectives=[]WARNCompare violation reporting configuration actual="no reporting endpoint" expected="report-to or report-uri present" issue="CSP does not define a reporting endpoint."WARNCSP does not define a reporting endpoint.

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

PerformancePerformanceBrowser audit

Forced reflow

100 Fail

Check name

Forced reflow

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations.

Evidence
{
  "description": "A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations."
}

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