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 10, 2026, 9:25 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
70/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability64%Agent Easeof Use53%Security& Trust90%GEO, AIO, AEO62%SEO100%Performance97%Accessibility74%
  • AI Discoverability 64 out of 100
  • Agent Ease of Use 53 out of 100
  • Security & Trust 90 out of 100
  • GEO, AIO and AEO 62 out of 100
  • SEO 100 out of 100
  • Performance 97 out of 100
  • Accessibility 74 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Fastest protection for WordPress security vulnerabilities - Patchstack favicon

Fastest protection for WordPress security vulnerabilities - Patchstack

Keep your WordPress sites and JavaScript apps safe from vulnerable plugins, themes & npm packages. Protect sites with virtual patching.

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
64
Needs work3731View details
Discoverability
47
Priority fix620View details
Content Readiness
83
Mostly ready2811View details
Bot Access Control
63
Needs work300
Agent Ease of Use
53
Needs work210View details
Google Agentic Browsing
67
Needs work210View details
GEO, AIO and AEO
62
Needs work700
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable200
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
90
Strong2300
Security & Trust
90
Strong2300
Performance
97
Strong1800
Performance
97
Strong1800

Prioritized recommendations

Issues ranked by score impact

3 items need attention

AI DiscoverabilityDiscoverabilityEstablished

Link headers

Link headers failed at "Find useful Link headers".

100 Fail

Needs attention

Link headers

Failed check
01

Issue

No useful agent discovery Link headers were found.

Details

02

Why it matters

Link headers let automated clients discover API catalogs, documentation, and machine-readable alternates without parsing page markup first.

Check name

Link headers

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Include Link response headers for agent discovery using RFC 8288.

Result

Link headers failed at "Find useful Link headers".

Validation steps

  1. Find useful Link headers

    No useful agent discovery Link headers were found.

    Link header lacks useful discovery relations
  2. Fetch same-origin Link header targets

    Link headers did not expose any same-origin targets to validate.

    Link header targets are unreachable or media types mismatch
Evidence log2 steps · 9 lines
Find useful Link headers [fail]! No useful agent discovery Link headers were found.INFOFind useful Link headersINFOParse response Link header linkCount=0FAILCompare registered agent-useful relation count actual=0 expected="> 0"FAILCompare community relation count actual=0 expected="accepted as weaker evidence"FAILNo useful agent discovery Link headers were found.Fetch same-origin Link header targets [fail]! Link headers did not expose any same-origin targets to validate.INFOFetch same-origin Link header targetsINFOFetch same-origin Link header targets and record external skipsFAILCompare same-origin Link target failures actual=1 expected=0FAILLink headers did not expose any same-origin targets to validate.

AI DiscoverabilityContent ReadinessEmerging recommendation

llms.txt

llms.txt failed at "Score llms.txt structure and usefulness".

34 Fail

Needs attention

llms.txt

Failed check
01

Issue

llms.txt includes unsafe or private links that should not be advertised to agents.

Details

02

Why it matters

llms.txt is an emerging Markdown convention for giving language-model clients curated context and links before they crawl broadly. Broken, private, or low-signal links make the file much less useful even when it exists.

Check name

llms.txt

Score

66/100

Status

fail

Category

Content Readiness

Maturity

Emerging recommendation

Goal

Publish a concise llms.txt index that helps agents discover useful public site context.

Result

llms.txt failed at "Score llms.txt structure and usefulness".

Validation steps

  1. Score llms.txt structure and usefulness

    llms.txt includes unsafe or private links that should not be advertised to agents.

    llms.txt advertises unsafe or private links

    1 links point to private, internal, credentialed, or non-HTTP(S) targets.

  2. Probe sampled linked resources

    Some sampled llms.txt links were broken, redirected unexpectedly, or did not return clearly agent-readable content.

    Sampled llms.txt links are broken

    1/25 probed links were broken or unreachable.

    Sampled llms.txt links are not clearly agent-readable

    1/25 probed links did not look agent-readable.

  3. Inspect optional llms-full.txt

    Passed.

Evidence log3 steps · 17 lines
Score llms.txt structure and usefulness [fail]! llms.txt includes unsafe or private links that should not be advertised to agents.INFOScore llms.txt structure and usefulnessINFOChecking recommended summary, sections, link labels, agent-friendly links, duplicates, and unsafe targetsPASSCheck blockquote summary is present actual=true expected=truePASSCheck H2 section count actual=8 expected="> 0"PASSCheck Markdown-formatted links actual=23 expected="> 0"FAILCheck unsafe/private link count actual=1 expected=0FAILllms.txt structure-quality validation failed reason="llms.txt includes unsafe or private links that should not be advertised to agents."Probe sampled linked resources [warning]! Some sampled llms.txt links were broken, redirected unexpectedly, or did not return clearly agent-readable content.INFOProbe sampled linked resourcesINFOSelecting safe, useful links for bounded probing selectedCount=25PASSCheck probed links were attempted actual=25 expected="> 0"WARNCheck broken probed link count actual=1 expected=0WARNBroken sampled llms.txt link url="https://www.npmjs.com/package/@patchstack/connect" label="https://www.npmjs.com/package/@patchstack/connect" statusCode=403 contentType="text/html; charset=UTF-8" method="GET" agentReadable=falsePASSCheck agent-readable probed links actual=24 expected="> 0"WARNLinked resource probe validation completed with warnings reason="Some sampled llms.txt links were broken, redirected unexpectedly, or did not return clearly agent-readable content."Inspect optional llms-full.txt [informational]INFOInspect optional llms-full.txtINFOTrying to fetch /llms-full.txt url="https://patchstack.com/llms-full.txt"SKIP/llms-full.txt is not present statusCode=404

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

Sign in to see 30 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
70/100Level 3, Bot-AwareCurrent report