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
Jun 27, 2026, 10:26 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
71/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability64%Agent Easeof Use51%Security& Trust92%GEO, AIO, AEO67%SEO100%Performance95%Accessibility88%
  • AI Discoverability 64 out of 100
  • Agent Ease of Use 51 out of 100
  • Security & Trust 92 out of 100
  • GEO, AIO and AEO 67 out of 100
  • SEO 100 out of 100
  • Performance 95 out of 100
  • Accessibility 88 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

बिटकॉइन और क्রिप्टोक्যूরেंসী खরীদেं | वॉলেट, সমাচার, শিक্ষা। favicon

बिटकॉइन और क्রिप्टोक्যूরেंসী खরীদেं | वॉলেट, সমাচার, শিक্ষা।

बिटकॉइन और क्রिप्टोकরেন্সী कে লিए দুনিযা कা প্রবেশ দ্বার। BTC, ETH, BCH, AVAX, MATIC और সৈकড়োं अন্য ডিজিटল সंপত্তিযোं कো खরীদেं, বেচেं, खর্চ করেं, স্বৈপ করেं औর নিবেশ করেं। क्রिप्टো, DeFi औর বেব3 कে বারে মেं সূচিত রহেं।

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 work3172View details
Discoverability
67
Needs work820View details
Content Readiness
61
Needs work2052View details
Bot Access Control
63
Needs work300
Agent Ease of Use
51
Needs work100
Skill Discovery
54
Needs work100
GEO, AIO and AEO
67
Needs work1000
GEO Readiness
Not Applicable
Not Applicable300
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable400
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
92
Strong2300
Security & Trust
92
Strong2300
Performance
95
Strong2000
Performance
95
Strong2000

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.

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.

  2. Fetch same-origin Link header targets

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

Evidence log2 steps · 16 lines
Find useful Link headers [fail]! No useful agent discovery Link headers were found.INFOFind useful Link headersINFOParse response Link header linkCount=7FAILCompare registered agent-useful relation count actual=0 expected="> 0"FAILCompare community relation count actual=0 expected="accepted as weaker evidence"INFOIgnored non-discovery Link relation rel="preload" url="/_next/static/media/Elza_CondensedBlack.p.1zmb88n2da3jp.woff2"INFOIgnored non-discovery Link relation rel="preload" url="/_next/static/media/Satoshi_Variable.p.2ta4m073o532p.woff2"INFOIgnored non-discovery Link relation rel="preload" url="/_next/static/chunks/1kh4vi11xlrj7.css"INFOIgnored non-discovery Link relation rel="preload" url="/_next/static/chunks/2bt1p5exq5iaj.css"INFOIgnored non-discovery Link relation rel="preload" url="/_next/static/chunks/44-b-l-shmvis.css"INFOIgnored non-discovery Link relation rel="preload" url="/_next/static/chunks/1rh69pthqmwg-.css"INFOIgnored non-discovery Link relation rel="preload" url="/_next/static/chunks/2uhfl045noj4o.css"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 ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

50 Fail

Needs attention

Content freshness signals

Failed check
01

Issue

Content freshness signals are incomplete: missing any valid freshness date in Last-Modified, Schema.org, Open Graph, Dublin Core, generic meta, or sitemap lastmod.

Details

02

Why it matters

Freshness signals help agents, crawlers, and search systems decide whether content is current enough to cite, summarize, cache, or compare against newer sources.

Check name

Content freshness signals

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose modified and published dates for freshness-aware retrieval, citation, and ranking.

Result

Content freshness signals is missing or incomplete.

Validation steps

  1. Validate Last-Modified header

    No valid Last-Modified HTTP header was found.

  2. Validate structured freshness dates

    No Schema.org freshness dates were found.

  3. Validate metadata freshness dates

    No Open Graph, Dublin Core, or generic meta freshness date was found.

  4. Corroborate with sitemap lastmod

    Add a sitemap entry with a valid lastmod for the canonical page URL when sitemap corroboration is useful.

Evidence log4 steps · 16 lines
Validate Last-Modified header [fail]! No valid Last-Modified HTTP header was found.INFOValidate Last-Modified headerINFOReading Last-Modified response headerFAILCheck Last-Modified header is present and parseable actual="missing" expected="valid" alternateDates=[]FAILLast-Modified header is missing or invalidValidate structured freshness dates [fail]! No Schema.org freshness dates were found.INFOValidate structured freshness datesINFOCollecting Schema.org freshness dates from JSON-LD, Microdata, and RDFaFAILCheck structured freshness date count actual=0 expected="> 0" invalidDateCount=0 formats={} alternateDates=[]FAILNo structured freshness dates foundValidate metadata freshness dates [fail]! No Open Graph, Dublin Core, or generic meta freshness date was found.INFOValidate metadata freshness datesINFOCollecting Open Graph, Dublin Core, and generic meta freshness datesFAILCheck metadata freshness date count actual=0 expected="> 0" metaDateCount=0 invalidDateCount=0 alternateDates=[]FAILNo metadata freshness dates foundCorroborate with sitemap lastmod [warning]INFOCorroborate with sitemap lastmodINFODiscovering sitemap candidates and matching the scanned page URL candidateCount=2 attempts=7WARNCheck matching sitemap lastmod actual="no match" expected="valid match when available" robotsStatusCode=200WARNNo matching sitemap lastmod found after sitemap attempts attempts=7

AI DiscoverabilityContent ReadinessEstablished

Author attribution

Author attribution is partially implemented.

35 Warning

Needs attention

Author attribution

Warning
01

Issue

No named author or publisher identity could be extracted.

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

30/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.

  2. Author identity quality

    No named author or publisher identity could be extracted.

  3. Visible byline parity

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

Evidence log3 steps · 12 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=3 publisherCount=2 namedContributors=0 authors=[{"role":"author","id":"https://www.bitcoin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false},{"role":"author","id":"https://www.bitcoin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false},{"role":"author","id":"https://www.bitcoin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false}] publishers=[{"role":"publisher","id":"https://www.bitcoin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false},{"role":"publisher","id":"https://www.bitcoin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false}] formats=["json-ld"]WARNSchema.org attribution is incomplete or fallback-only authorCount=3 publisherCount=2 authors=[{"role":"author","id":"https://www.bitcoin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false},{"role":"author","id":"https://www.bitcoin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false},{"role":"author","id":"https://www.bitcoin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false}] publishers=[{"role":"publisher","id":"https://www.bitcoin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false},{"role":"publisher","id":"https://www.bitcoin.com/#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":"author","id":"https://www.bitcoin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false},{"role":"author","id":"https://www.bitcoin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false},{"role":"author","id":"https://www.bitcoin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false},{"role":"publisher","id":"https://www.bitcoin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false},{"role":"publisher","id":"https://www.bitcoin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false}]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 found

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.

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