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

OVERALL SCORE

Level 4, Mostly Ready

Good readiness for AI agents
AIDiscoverability75%Agent Easeof Use64%Security& Trust91%GEO, AIO, AEO69%SEO100%Performance87%Accessibility94%
  • AI Discoverability 75 out of 100
  • Agent Ease of Use 64 out of 100
  • Security & Trust 91 out of 100
  • GEO, AIO and AEO 69 out of 100
  • SEO 100 out of 100
  • Performance 87 out of 100
  • Accessibility 94 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Secure Privacy - Cookie Consent & Privacy Compliance Platform favicon

Secure Privacy - Cookie Consent & Privacy Compliance Platform

Simplify cookie consent and privacy compliance for global teams. Consent Solution & Privacy Governance supporting 55+ privacy laws including GDPR, CCPA, LGPD. SOC2 certified.

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
75
Mostly ready4011View details
Discoverability
73
Needs work600
Content Readiness
77
Mostly ready2911View details
Bot Access Control
75
Mostly ready500
Agent Ease of Use
64
Needs work2141View details
API
72
Needs work1111View details
Auth
37
Priority fix130View details
MCP
59
Needs work300
Skill Discovery
57
Needs work300
Google Agentic Browsing
100
Strong300
GEO, AIO and AEO
69
Needs work1000
GEO Readiness
Not Applicable
Not Applicable300
AIO Readiness
Not Applicable
Not Applicable400
AEO Readiness
Not Applicable
Not Applicable300
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
91
Strong2500
Security & Trust
91
Strong2500
Performance
87
Mostly ready1800
Performance
87
Mostly ready1800

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 "Fetch and validate /auth.md".

90 Fail

Needs attention

Auth.md Agent Registration

Failed check
01

Issue

auth.md response did not match Auth.md v1 agent registration guidance. missing registration instructions; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance; missing credential usage, expiry, error, or revocation guidance.

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

10/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 "Fetch and validate /auth.md".

Validation steps

  1. Fetch and validate /auth.md

    auth.md response did not match Auth.md v1 agent registration guidance. missing registration instructions; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance; missing credential usage, expiry, error, or revocation guidance.

    /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 · 21 lines
Fetch and validate /auth.md [fail]! auth.md response did not match Auth.md v1 agent registration guidance. missing registration instructions; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance; missing credential usage, expiry, error, or revocation guidance.INFOFetch and validate /auth.mdINFOFetch Auth.md-related resource path="/auth.md" statusCode=200 contentType="text/markdown; charset=utf-8" bytes=895FAILCompare response Content-Type with expected Auth.md media type actual=true expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILCompare Auth.md content length actual=853 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"FAILAuth.md validation issue issue="auth.md response did not match Auth.md v1 agent registration guidance. missing registration instructions; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance; missing credential usage, expiry, error, or revocation guidance."FAILauth.md response did not match Auth.md v1 agent registration guidance. missing registration instructions; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance; missing credential usage, expiry, error, or revocation guidance.Validate 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=12175FAILCompare 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=12183FAILCompare 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 DiscoverabilityContent ReadinessEstablished

Author attribution

Author attribution is partially implemented.

45 Warning

Needs attention

Author attribution

Warning
01

Issue

No named author or publisher identity could be extracted.

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

55/100

Status

warning

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

    Schema.org attribution is incomplete or relies only on publisher/fallback evidence.

    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
Evidence log2 steps · 8 lines
Schema.org attribution [warning]! Schema.org attribution is incomplete or relies only on publisher/fallback evidence.INFOSchema.org attributionINFOChecking structured data for author, creator, and publisher contributorsWARNCheck named Schema.org author count actual=0 expected="> 0" authorCount=0 publisherCount=1 namedContributors=0 authors=[] publishers=[{"role":"publisher","id":"https://secureprivacy.ai/#organization","sameAs":[],"format":"json-ld","mergedName":false}] formats=["json-ld"]WARNSchema.org attribution is incomplete or fallback-only authorCount=0 publisherCount=1 authors=[] publishers=[{"role":"publisher","id":"https://secureprivacy.ai/#organization","sameAs":[],"format":"json-ld","mergedName":false}]Author 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=[{"role":"publisher","id":"https://secureprivacy.ai/#organization","sameAs":[],"format":"json-ld","mergedName":false}]FAILNo named contributor identity could be extracted

Agent Ease of UseAPIEstablished

API Catalog

API Catalog failed at "Validate API catalog targets".

21 Fail

Needs attention

API Catalog

Failed check
01

Issue

API catalog target https://secureprivacy.ai/sitemap.xml (sitemap) could not be fetched: The operation was aborted due to timeout.

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

79/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 targets

    API catalog target https://secureprivacy.ai/sitemap.xml (sitemap) could not be fetched: The operation was aborted due to timeout.

    API catalog targets are unreachable or media types mismatch
Evidence log2 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; profile=\"https://www.rfc-editor.org/info/rfc9727\"; charset=utf-8"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 targets [fail]! API catalog target https://secureprivacy.ai/sitemap.xml (sitemap) could not be fetched: The operation was aborted due to timeout.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsPASSAPI catalog target is reachable rel="describedby" href="https://secureprivacy.ai/llms.txt" statusCode=200 contentType="text/plain; charset=utf-8" advertisedType="text/plain"PASSAPI catalog target is reachable rel="describedby" href="https://secureprivacy.ai/llms-full.txt" statusCode=200 contentType="text/plain; charset=utf-8" advertisedType="text/plain"PASSAPI catalog target is reachable rel="service-doc" href="https://secureprivacy.ai/support" statusCode=200 contentType="text/html; charset=utf-8" advertisedType="text/html"FAILAPI catalog target fetch failed rel="sitemap" href="https://secureprivacy.ai/sitemap.xml" error="The operation was aborted due to timeout"PASSAPI catalog target is reachable rel="alternate" href="https://secureprivacy.ai/auth.md" statusCode=200 contentType="text/markdown; charset=utf-8" advertisedType="text/markdown"PASSAPI catalog target is reachable rel="service-doc" href="https://secureprivacy.ai/support" statusCode=200 contentType="text/html; charset=utf-8" advertisedType="text/html"PASSAPI catalog target is reachable rel="service-doc" href="https://secureprivacy.ai/auth.md" statusCode=200 contentType="text/markdown; charset=utf-8" advertisedType="text/markdown"FAILCompare API catalog target failure count actual=1 expected=0FAILAPI catalog target https://secureprivacy.ai/sitemap.xml (sitemap) could not be fetched: The operation was aborted due to timeout.

Sign in to see 27 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
78/100Level 4, Mostly ReadyCurrent report