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://ezhevita.dev/
SCANNED
Jul 30, 2026, 7:22 PM
VISIBILITY
Public
SUITE2026.06.10
Rescan Report
Share Report
Copy Report Link
Export Report
58/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability42%Agent Easeof Use61%Security& Trust62%GEO, AIO, AEO26%SEO91%Performance100%Accessibility79%
  • AI Discoverability 42 out of 100
  • Agent Ease of Use 61 out of 100
  • Security & Trust 62 out of 100
  • GEO, AIO and AEO 26 out of 100
  • SEO 91 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

ezhevita page

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
42
Priority fix1400
Discoverability
40
Priority fix400
Content Readiness
18
Priority fix700
Bot Access Control
63
Needs work300
Agent Ease of Use
61
Needs work410View details
Skill Discovery
55
Needs work210View details
Google Agentic Browsing
100
Strong200
GEO, AIO and AEO
26
Priority fix200
AIO Readiness
Not Applicable
Not Applicable200
SEO
91
Strong710View details
SEO
91
Strong710View details
Security & Trust
62
Needs work1410View details
Security & Trust
62
Needs work1410View details
Performance
100
Strong2000
Performance
100
Strong2000

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

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

60 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

40/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. Find enforcing CSP delivery

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

    Enforcing Content-Security-Policy header is missing
Evidence log1 step · 4 lines
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.

Agent Ease of UseSkill DiscoveryEmerging recommendation

DNS-AID Agent Discovery

DNS-AID Agent Discovery failed at "Validate HTTPS/SVCB shape".

29 Fail

Needs attention

DNS-AID Agent Discovery

Failed check
01

Issue

One or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.

Details

02

Why it matters

DNS-AID lets agents discover index, A2A, and other agent entrypoints before fetching HTTP metadata. HTTPS/SVCB records provide the service-binding substrate, while DNSSEC can authenticate the discovery answer when available.

Check name

DNS-AID Agent Discovery

Score

71/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish DNS-AID HTTPS/SVCB records under _agents for DNS-based agent entrypoint discovery.

Result

DNS-AID Agent Discovery failed at "Validate HTTPS/SVCB shape".

Validation steps

  1. Validate HTTPS/SVCB shape

    One or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.

    DNS-AID HTTPS/SVCB records are malformed
    Malformed record issues
    [
  {
    "ownerName": "_index._agents.ezhevita.dev",
    "rrtype": "HTTPS",
    "ttl": 300,
    "mode": "unknown",
    "targetName": "136",
    "params": [
      {
        "key": "00",
        "value": "present"
      },
      {
        "key": "01",
        "value": "present"
      },
      {
        "key": "00",
        "value": "present"
      },
      {
        "key": "00",
        "value": "present"
      },
      {
        "truncated": true,
        "omittedCount": 132,
        "originalCount": 136
      }
    ],
    "mandatory": [],
    "alpn": [],
    "endpointIssue": "missing endpoint",
    "unknownParams": [
      "00",
      "01",
      "00",
      "00",
      {
        "truncated": true,
        "omittedCount": 132,
        "originalCount": 136
      }
    ],
    "parseWarnings": [
      "SvcPriority is missing or not numeric."
    ],
    "source": "cloudflare-doh-json",
    "raw": "\\# 136 00 01 00 00 01 00 06 02 68 33 02 68 32 00 04 00 08 68 15 1a 9e ac 43 89 24 00 05 00 47 00 45 fe 0d 00 41 55 00 20 00 20 86 12 6a 1f 00 c7 4e 59 f4 d8 14 3d bd df 39 48 1c dc 22 2c b4 a5 b4 db 17 98 27 b9 60 4b 0f 29 00 04 00 01 00 01 00 12 63 6c 6f 75 64 66 6c 61 72 65 2d 65 63 68 2e 63 6f 6d 00 00 00 06 00 20 26 06 47 00 30 32 00 00 00 00 00 00 68 15 1a 9e 26 06 47 00 30 33 00 00 00 00 00 00 ac 43 89 24"
  },
  {
    "ownerName": "_a2a._agents.ezhevita.dev",
    "rrtype": "HTTPS",
    "ttl": 300,
    "mode": "unknown",
    "targetName": "136",
    "params": [
      {
        "key": "00",
        "value": "present"
      },
      {
        "key": "01",
        "value": "present"
      },
      {
        "key": "00",
        "value": "present"
      },
      {
        "key": "00",
        "value": "present"
      },
      {
        "truncated": true,
        "omittedCount": 132,
        "originalCount": 136
      }
    ],
    "mandatory": [],
    "alpn": [],
    "endpointIssue": "missing endpoint",
    "unknownParams": [
      "00",
      "01",
      "00",
      "00",
      {
        "truncated": true,
        "omittedCount": 132,
        "originalCount": 136
      }
    ],
    "parseWarnings": [
      "SvcPriority is missing or not numeric."
    ],
    "source": "cloudflare-doh-json",
    "raw": "\\# 136 00 01 00 00 01 00 06 02 68 33 02 68 32 00 04 00 08 68 15 1a 9e ac 43 89 24 00 05 00 47 00 45 fe 0d 00 41 55 00 20 00 20 86 12 6a 1f 00 c7 4e 59 f4 d8 14 3d bd df 39 48 1c dc 22 2c b4 a5 b4 db 17 98 27 b9 60 4b 0f 29 00 04 00 01 00 01 00 12 63 6c 6f 75 64 66 6c 61 72 65 2d 65 63 68 2e 63 6f 6d 00 00 00 06 00 20 26 06 47 00 30 32 00 00 00 00 00 00 68 15 1a 9e 26 06 47 00 30 33 00 00 00 00 00 00 ac 43 89 24"
  }
]
Evidence log1 step · 6 lines
Validate HTTPS/SVCB shape [fail]! One or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.INFOValidate HTTPS/SVCB shapeFAILCompare parsed DNS-AID record count actual=2 expected="> 0"FAILCompare ServiceMode record count actual=0 expected="> 0"FAILDNS-AID record has parse/shape warnings ownerName="_index._agents.ezhevita.dev" rrtype="HTTPS" mode="unknown" warnings=["SvcPriority is missing or not numeric."]FAILDNS-AID record has parse/shape warnings ownerName="_a2a._agents.ezhevita.dev" rrtype="HTTPS" mode="unknown" warnings=["SvcPriority is missing or not numeric."]FAILOne or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.

SEOSEOBrowser audit

Document does not have a meta description

100 Fail

Check name

Document does not have a meta description

Score

0/100

Status

fail

Device

desktop

Category

SEO

Fix guidance

Meta descriptions may be included in search results to concisely summarize page content. [Learn more about the meta description](https://developer.chrome.com/docs/lighthouse/seo/meta-description/).

Evidence
{
  "description": "Meta descriptions may be included in search results to concisely summarize page content. [Learn more about the meta description](https://developer.chrome.com/docs/lighthouse/seo/meta-description/)."
}

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