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 14, 2026, 12:14 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
76/100

OVERALL SCORE

Level 4, Mostly Ready

Good readiness for AI agents
AIDiscoverability79%Agent Easeof Use60%Security& Trust70%GEO, AIO, AEO61%SEO100%Performance97%Accessibility100%
  • AI Discoverability 79 out of 100
  • Agent Ease of Use 60 out of 100
  • Security & Trust 70 out of 100
  • GEO, AIO and AEO 61 out of 100
  • SEO 100 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

Best B2B/B2C Online Marketplace Platform | Webkul favicon

Best B2B/B2C Online Marketplace Platform | Webkul

Top-rated B2B/B2C eCommerce, marketplace, hyperlocal and mobile app development. We worked with fortune 500 in last 15 years - Let's work together.

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
79
Mostly ready4010View details
Discoverability
100
Strong1000
Content Readiness
83
Mostly ready2700
Bot Access Control
58
Needs work310View details
Agent Ease of Use
60
Needs work1733View details
API
70
Needs work612View details
Auth
40
Priority fix221View details
MCP
34
Priority fix200
Skill Discovery
59
Needs work400
Google Agentic Browsing
100
Strong300
GEO, AIO and AEO
61
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
70
Needs work1600
Security & Trust
70
Needs work1600
Performance
97
Strong1600
Performance
97
Strong1600

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Agent Ease of UseAuthEmerging recommendation

Auth.md Agent Registration

Auth.md Agent Registration failed at "Validate protected resource metadata".

72 Fail

Needs attention

Auth.md Agent Registration

Failed check
01

Issue

OAuth Protected Resource Metadata could not be fetched.

Details

02

Why it matters

Human login and signup flows are often opaque to agents. Auth.md gives automated clients a stable registration contract instead of forcing them to scrape docs, automate browser forms, or guess credential flows.

Check name

Auth.md Agent Registration

Score

28/100

Status

fail

Category

Auth

Maturity

Emerging recommendation

Goal

Publish Auth.md v1 metadata so agents can discover how to register, claim a user, and obtain credentials.

Result

Auth.md Agent Registration failed at "Validate protected resource metadata".

Validation steps

  1. Fetch and validate /auth.md

    Serve /auth.md as Markdown or text with Auth.md v1 registration guidance, protected-resource metadata discovery, credential types, claim ceremony guidance, and revocation/error handling.

    /auth.md is missing or not usable as agent registration guidance
  2. Validate protected resource metadata

    OAuth Protected Resource Metadata could not be fetched.

    Auth.md protected-resource metadata is missing or incomplete
  3. Validate Auth.md authorization metadata

    OAuth authorization-server metadata could not be fetched.

    Authorization-server metadata lacks Auth.md v1 fields
Evidence log3 steps · 20 lines
Fetch and validate /auth.md [warning]INFOFetch and validate /auth.mdINFOFetch Auth.md-related resource path="/auth.md" statusCode=200 contentType="text/markdown" bytes=2417WARNCompare response Content-Type with expected Auth.md media type actual=true expected=trueWARNCompare Auth.md/OAuth metadata validation result actual=true expected=trueWARNCompare Auth.md content length actual=2311 expected=">= 80 characters"WARNAuth.md validation warning warning="missing agent_verified/user_claimed or claim ceremony guidance"WARNAuth.md validation warning warning="missing credential usage, expiry, error, or revocation guidance"WARNAuth.md step completed with warningsValidate protected resource metadata [fail]! OAuth Protected Resource Metadata could not be fetched.INFOValidate protected resource metadataINFOFetch Auth.md-related resource path="/.well-known/oauth-protected-resource" statusCode=404 contentType="text/html; charset=UTF-8" bytes=26068FAILCompare response Content-Type with expected Auth.md media type actual=false expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILAuth.md validation issue issue="OAuth Protected Resource Metadata could not be fetched."FAILOAuth Protected Resource Metadata could not be fetched.Validate Auth.md authorization metadata [fail]! OAuth authorization-server metadata could not be fetched.INFOValidate Auth.md authorization metadataINFOFetch Auth.md-related resource path="/.well-known/oauth-authorization-server" statusCode=404 contentType="text/html; charset=UTF-8" bytes=26068FAILCompare response Content-Type with expected Auth.md media type actual=false expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILAuth.md validation issue issue="OAuth authorization-server metadata could not be fetched."FAILOAuth authorization-server metadata could not be fetched.

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

Agent Ease of UseAPIEstablished

API Catalog

API Catalog failed at "Validate API catalog targets".

27 Fail

Needs attention

API Catalog

Failed check
01

Issue

API catalog target https://webkul.com/llms.txt (service-meta) advertised text/markdown but returned text/plain.

Details

02

Why it matters

API catalogs help agents find API endpoints, service descriptions, documentation, status resources, auth metadata, and related machine-readable contracts without guessing entry points.

Check name

API Catalog

Score

73/100

Status

fail

Category

API

Maturity

Established

Goal

Publish an API catalog for automated public API discovery using RFC 9727 when this origin exposes public APIs.

Result

API Catalog failed at "Validate API catalog targets".

Validation steps

  1. Check API catalog HEAD Link header

    HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".

    API catalog HEAD Link discovery is incomplete
  2. Validate API catalog media type

    The API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter.

    API catalog media type is not application/linkset+json
  3. Validate API catalog targets

    API catalog target https://webkul.com/llms.txt (service-meta) advertised text/markdown but returned text/plain.

    API catalog targets are unreachable or media types mismatch
Evidence log3 steps · 15 lines
Check API catalog HEAD Link header [warning]! HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".INFOCheck API catalog HEAD Link headerINFOSend HEAD request to API catalog path attempted=true statusCode=200 contentType="application/linkset+json"WARNCompare HEAD Link rel=api-catalog count actual=0 expected="> 0"WARNHEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog". status="warning"Validate API catalog media type [warning]! The API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter.INFOValidate API catalog media typeWARNCompare API catalog media type actual="application/linkset+json" expected="application/linkset+json"WARNCompare RFC 9727 profile parameter actual=false expected=trueWARNThe API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter. status="warning"Validate API catalog targets [fail]! API catalog target https://webkul.com/llms.txt (service-meta) advertised text/markdown but returned text/plain.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsPASSAPI catalog target is reachable rel="service-desc" href="https://webkul.com/wp-json/" statusCode=200 contentType="application/json; charset=UTF-8" advertisedType="application/json"FAILAPI catalog target failed validation rel="service-meta" href="https://webkul.com/llms.txt" statusCode=200 contentType="text/plain" advertisedType="text/markdown" typeMatches=falsePASSAPI catalog target is reachable rel="service-desc" href="https://webkul.com/wp-json/wp/v2" statusCode=200 contentType="application/json; charset=UTF-8" advertisedType="application/json"FAILCompare API catalog target failure count actual=1 expected=0FAILAPI catalog target https://webkul.com/llms.txt (service-meta) advertised text/markdown but returned text/plain.

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.

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