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 8, 2026, 7:08 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
65/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability63%Agent Easeof Use53%Security& Trust88%GEO, AIO, AEO68%SEO92%Performance62%Accessibility75%
  • AI Discoverability 63 out of 100
  • Agent Ease of Use 53 out of 100
  • Security & Trust 88 out of 100
  • GEO, AIO and AEO 68 out of 100
  • SEO 92 out of 100
  • Performance 62 out of 100
  • Accessibility 75 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Transform Your Fashion Business with Exenta ERP favicon

Transform Your Fashion Business with Exenta ERP

Streamline design, production, inventory and sales with Aptean’s Fashion ERP Exenta Edition—purpose-built ERP for the apparel industry.

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
63
Needs work3100
Discoverability
67
Needs work800
Content Readiness
60
Needs work2000
Bot Access Control
63
Needs work300
Agent Ease of Use
53
Needs work210View details
API
67
Needs work100
Google Agentic Browsing
50
Needs work110View details
GEO, AIO and AEO
68
Needs work800
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable200
AEO Readiness
Not Applicable
Not Applicable400
SEO
92
Strong900
SEO
92
Strong900
Security & Trust
88
Mostly ready2422View details
Security & Trust
88
Mostly ready2422View details
Performance
62
Needs work1400
Performance
62
Needs work1400
Accessibility
75
Mostly ready010View details
Accessibility
75
Mostly ready010View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

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

50 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

default-src is present but not meaningfully restrictive.

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

50/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. Evaluate fetch baseline

    default-src is present but not meaningfully restrictive.

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

    script-src leaves script execution broadly unrestricted.

    CSP script execution policy is unsafe
  3. Review hardening directives

    CSP is missing recommended hardening directives: object-src, base-uri.

    CSP hardening directives are missing or weak
  4. Review CSP reporting

    CSP does not define a reporting endpoint.

    CSP reporting is missing or incomplete
Evidence log4 steps · 16 lines
Evaluate fetch baseline [fail]! default-src is present but not meaningfully restrictive.INFOEvaluate fetch baselineINFOEvaluate resource loading fallback defaultSrc=["'self'","https:"] explicitFetchDirectives=["connect-src","font-src","frame-src","img-src","script-src","style-src"]FAILCompare fetch baseline actual=["'self'","https:"] expected="restricted default-src or broad explicit fetch coverage" issue="default-src is present but not meaningfully restrictive."FAILdefault-src is present but not meaningfully restrictive.Evaluate script execution [fail]! script-src leaves script execution broadly unrestricted.INFOEvaluate script executionINFOInspect effective script directive effectiveDirective="script-src" sources=["'self'","'unsafe-inline'","'unsafe-eval'","https:","blob:"]FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":true,"hasUnsafeEval":true,"hasWildcardHost":false,"hasBroadScheme":true,"dangerousSchemes":["blob:"]} expected="constrained script sources without unsafe execution allowances" issue="script-src leaves script execution broadly unrestricted."FAILscript-src leaves script execution broadly unrestricted.Review hardening directives [warning]! CSP is missing recommended hardening directives: object-src, base-uri.INFOReview hardening directivesINFOInspect CSP hardening directives objectSrcFallback=["'self'","https:"] frameAncestors=["'self'","https://*.optimizely.com"] formCount=0WARNCompare recommended hardening coverage actual=["object-src","base-uri"] expected="no missing object-src/base-uri/form-action requirements" issue="CSP is missing recommended hardening directives: object-src, base-uri."WARNCSP is missing recommended hardening directives: object-src, base-uri.Review CSP reporting [warning]! CSP does not define a reporting endpoint.INFOReview CSP reportingINFOInspect CSP reporting directives reportOnlyHeaderPresent=true reportOnlyDirectives=["default-src","script-src","style-src","img-src","font-src","frame-src","media-src","connect-src","worker-src","object-src","base-uri","form-action","frame-ancestors","upgrade-insecure-requests"]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."
}

AccessibilityAccessibilityBrowser audit

ARIA attributes must conform to valid values

100 Fail

Check name

ARIA attributes must conform to valid values

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

ARIA attributes must conform to valid values

Evidence
{
  "ruleId": "aria-valid-attr-value",
  "impact": "critical",
  "description": "Ensure all ARIA attributes have valid values",
  "tags": [
    "cat.aria",
    "wcag2a",
    "wcag412",
    "EN-301-549",
    "EN-9.4.1.2",
    "RGAAv4",
    "RGAA-7.1.1"
  ],
  "affectedNodeCount": 1,
  "nodes": [
    {
      "target": [
        "#tab-the-simplest-path-from-concept-to-consumer"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 269
      },
      "failureSummary": "Fix all of the following:\n  Invalid ARIA attribute value: aria-controls=\"panel-the-simplest-path-from-concept-to-consumer\""
    }
  ]
}

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

3 reports
Public score history report links
Scan dateScoreReadinessReport
70/100Level 3, Bot-AwareView report
61/100Level 3, Bot-AwareView report
65/100Level 3, Bot-AwareCurrent report