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 11, 2026, 7:03 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
61/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability29%Agent Easeof Use53%Security& Trust89%GEO, AIO, AEO53%SEO92%Performance97%Accessibility100%
  • AI Discoverability 29 out of 100
  • Agent Ease of Use 53 out of 100
  • Security & Trust 89 out of 100
  • GEO, AIO and AEO 53 out of 100
  • SEO 92 out of 100
  • Performance 97 out of 100
  • Accessibility 100 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Front page favicon

Front page

Front page of Self Service

Open Agent View

Next step

Turn this report into a fix workflow

3 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
29
Priority fix1562View details
Discoverability
7
Priority fix100
Content Readiness
21
Priority fix931View details
Bot Access Control
53
Needs work531View details
Agent Ease of Use
53
Needs work200
Google Agentic Browsing
67
Needs work200
GEO, AIO and AEO
53
Needs work600
GEO Readiness
Not Applicable
Not Applicable100
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable200
SEO
92
Strong800
SEO
92
Strong800
Security & Trust
89
Mostly ready2300
Security & Trust
89
Mostly ready2300
Performance
97
Strong1700
Performance
97
Strong1700

Prioritized recommendations

Issues ranked by score impact

3 items need attention

AI DiscoverabilityContent ReadinessEstablished

Author attribution

Author attribution is partially implemented.

95 Fail

Needs attention

Author attribution

Failed check
01

Issue

Applicable editorial content has no usable author, creator, publisher, visible byline, or HTML attribution signal.

Details

02

Why it matters

Author attribution helps agents cite content responsibly, assess source credibility, and distinguish editorial pages from anonymous marketing copy.

Check name

Author attribution

Score

5/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Identify content authors or publishers for trust and attribution.

Result

Author attribution is partially implemented.

Validation steps

  1. Schema.org attribution

    Editorial content has no Schema.org author, creator, or publisher attribution.

    Schema.org author attribution is missing or incomplete
  2. Author identity quality

    No named author or publisher identity could be extracted.

    Author identity quality is incomplete
  3. Visible byline parity

    Structured author/publisher names were not found in visible byline text.

    Author attribution does not match visible byline content
  4. HTML attribution support

    No supporting HTML author metadata, rel=author link, or visible byline was found.

    HTML author attribution support is missing
Evidence log4 steps · 16 lines
Schema.org attribution [fail]! Editorial content has no Schema.org author, creator, or publisher attribution.INFOSchema.org attributionINFOChecking structured data for author, creator, and publisher contributorsFAILCheck named Schema.org author count actual=0 expected="> 0" authorCount=0 publisherCount=0 namedContributors=0 authors=[] publishers=[] formats=[]FAILNo Schema.org author, creator, or publisher attribution foundAuthor identity quality [fail]! No named author or publisher identity could be extracted.INFOAuthor identity qualityINFOChecking contributors for stable identity signalsFAILCheck identified contributor count actual=0 expected="> 0" namedContributors=0 identifiedContributors=[] unidentifiedContributors=[]FAILNo named contributor identity could be extractedVisible byline parity [fail]! Structured author/publisher names were not found in visible byline text.INFOVisible byline parityINFOComparing structured contributor names with visible byline evidenceFAILCheck visible attribution matches actual=0 expected="> 0 or visible byline present" visibleByline=false bylineCount=0FAILNo visible byline parity foundHTML attribution support [warning]! No supporting HTML author metadata, rel=author link, or visible byline was found.INFOHTML attribution supportINFOChecking meta author, rel=author, and visible byline supportWARNCheck HTML attribution support signals actual=0 expected="> 0" metaAuthor=false relAuthor=false visibleByline=falseWARNNo supporting HTML attribution signal found

AI DiscoverabilityBot Access ControlEstablished

AI bot rules in robots.txt

AI bot rules in robots.txt failed at "Fetch robots.txt".

50 Fail

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

No robots.txt content was available to inspect for AI bot rules.

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

0/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 "Fetch robots.txt".

Validation steps

  1. Fetch robots.txt

    No robots.txt content was available to inspect for AI bot rules.

    robots.txt is missing for AI crawler policy inspection
  2. Classify AI crawler rules

    No explicit User-agent rules were found for major AI crawler tokens.

    robots.txt lacks explicit AI crawler rules
Evidence log2 steps · 10 lines
Fetch robots.txt [fail]! No robots.txt content was available to inspect for AI bot rules.INFOFetch robots.txtINFORequesting /robots.txt from the site originFAILCheck whether robots.txt content is available actual="no content" expected="content returned" length=0FAILNo robots.txt content was available to inspect for AI bot rules.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=0 unspecified=21

AI DiscoverabilityBot Access ControlEmerging recommendation

ai.txt policy

ai.txt policy failed at "Validate policy content".

24 Fail

Needs attention

ai.txt policy

Failed check
01

Issue

ai.txt is too short to provide useful advisory policy guidance.

Details

02

Why it matters

ai.txt is a fragmented emerging convention. It can communicate human-readable AI crawling, training, attribution, restriction, and contact guidance, but it is not a standard access-control mechanism and absence should not be penalized.

Check name

ai.txt policy

Score

53/100

Status

fail

Category

Bot Access Control

Maturity

Emerging recommendation

Goal

Publish an advisory human-readable AI usage policy only when the site intentionally needs one.

Result

ai.txt policy failed at "Validate policy content".

Validation steps

  1. Parse ai.txt policy

    ai.txt is present but does not follow the AI Visibility section model.

    /ai.txt policy format is missing required sections or non-standard
  2. Validate policy content

    ai.txt is too short to provide useful advisory policy guidance.

    /ai.txt content is incomplete or unsafe
Evidence log2 steps · 10 lines
Parse ai.txt policy [warning]! ai.txt is present but does not follow the AI Visibility section model.INFOParse ai.txt policyINFODetecting ai.txt convention from bracket sections, frontmatter, headings, and ai.txt context linksINFODetected policy structure convention="generic-markdown" sections=[] markdownHeadings=["No content may be crawled for AI purposes"]WARNCheck AI Visibility required sections actual="missing identity, permissions, restrictions" expected="identity, permissions, and restrictions" missingRecommended=["attribution","contact","content-types"]WARNai.txt is present but does not follow the AI Visibility section model.Validate policy content [fail]! ai.txt is too short to provide useful advisory policy guidance.INFOValidate policy contentINFOChecking required section content, permission/restriction language, attribution, contact details, and safety risks convention="generic-markdown"INFODetected policy signals hasPermissionLanguage=true hasRestrictionLanguage=true hasTrainingLanguage=false hasAttributionLanguage=false hasContact=falseFAILCheck required and recommended section coverage actual={"missingRequired":["identity","permissions","restrictions"],"missingRecommended":["attribution","contact","content-types"]} expected={"missingRequired":[],"recommendedPresentWhenPossible":true}FAILai.txt is too short to provide useful advisory policy guidance.

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