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 7, 2026, 1:50 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
48/100

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability43%Agent Easeof Use59%Security& Trust66%GEO, AIO, AEO54%SEO83%Performance75%Accessibility0%
  • AI Discoverability 43 out of 100
  • Agent Ease of Use 59 out of 100
  • Security & Trust 66 out of 100
  • GEO, AIO and AEO 54 out of 100
  • SEO 83 out of 100
  • Performance 75 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Enterprise Cloud Data Management | Actifio favicon

Enterprise Cloud Data Management | Actifio

Actifio enterprise cloud data management enables thousands of businesses to deliver their data just as they deliver their applications and infrastructure: as a service available instantly, anywhere.

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
43
Priority fix1510View details
Discoverability
67
Needs work800
Content Readiness
17
Priority fix600
Bot Access Control
45
Priority fix110View details
Agent Ease of Use
59
Needs work200
Google Agentic Browsing
100
Strong200
GEO, AIO and AEO
54
Needs work600
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable200
AEO Readiness
Not Applicable
Not Applicable200
SEO
83
Mostly ready700
SEO
83
Mostly ready700
Security & Trust
66
Needs work1512View details
Security & Trust
66
Needs work1512View details
Performance
75
Mostly ready1500
Performance
75
Mostly ready1500
Accessibility
0
Priority fix010View details
Accessibility
0
Priority fix010View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

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

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Evaluate fetch baseline".

35 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

CSP does not define default-src; several fetch directives may have no restrictive fallback.

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

65/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 fetch baseline".

Validation steps

  1. Parse CSP directives

    CSP directive "report-uri" appears more than once; browsers use the first occurrence.

    Content-Security-Policy directives are malformed or duplicated

    Duplicate CSP directive: report-uri. Browsers use the first occurrence and ignore later duplicates.

  2. Evaluate fetch baseline

    CSP does not define default-src; several fetch directives may have no restrictive fallback.

    CSP fetch baseline is too broad or missing
  3. Evaluate script execution

    script-src allows unsafe-eval.

    CSP script execution policy is unsafe
Evidence log3 steps · 12 lines
Parse CSP directives [warning]! CSP directive "report-uri" appears more than once; browsers use the first occurrence.INFOParse CSP directivesINFOParse enforcing CSP directives directives=["script-src","object-src","report-uri","base-uri"] reportOnlyDirectives=[]WARNCheck directive syntax actual={"duplicateDirectives":["report-uri"],"unknownDirectives":[],"malformedDirectives":[],"emptyPolicy":false} expected="parseable directives with no duplicate or malformed names" issue="CSP directive \"report-uri\" appears more than once; browsers use the first occurrence."WARNCSP directive "report-uri" appears more than once; browsers use the first occurrence.Evaluate fetch baseline [fail]! CSP does not define default-src; several fetch directives may have no restrictive fallback.INFOEvaluate fetch baselineINFOEvaluate resource loading fallback explicitFetchDirectives=["object-src","script-src"]FAILCompare fetch baseline actual="0 explicit fetch directives" expected="restricted default-src or broad explicit fetch coverage" issue="CSP does not define default-src; several fetch directives may have no restrictive fallback."FAILCSP does not define default-src; several fetch directives may have no restrictive fallback.Evaluate script execution [warning]! script-src allows unsafe-eval.INFOEvaluate script executionINFOInspect effective script directive effectiveDirective="script-src" sources=["'nonce-NjlMTK7nw9Q4RIenDCnH3Q'","'report-sample'","'strict-dynamic'","'unsafe-eval'","'unsafe-inline'","http:","https:"]WARNCompare script execution posture actual={"hasNonce":true,"hasHash":false,"hasStrictDynamic":true,"hasUnsafeInline":true,"hasUnsafeEval":true,"hasWildcardHost":false,"hasBroadScheme":true,"dangerousSchemes":[]} expected="constrained script sources without unsafe execution allowances" issue="script-src allows unsafe-eval."WARNscript-src allows unsafe-eval.

AccessibilityAccessibilityBrowser audit

Accessibility audit

100 Fail

Check name

Accessibility audit

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Make sure the page can load in Chrome and run Accessibility checks.

Evidence
{
  "error": "Accessibility audit did not return a result."
}

Sign in to see 32 other issues and the full report

Create a free account to unlock every issue, evidence details, exports, and higher free limits.

Email code

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

Public scan score over time

Public reports for this website origin. Select any point or report link to open that canonical report.

1 reports
Public score history report links
Scan dateScoreReadinessReport
48/100Level 2, Agent-LimitedCurrent report