UCP Checker
UCP Score

UCP Score for evt-ucp.rcksld.com

Nearly there

79 out of 100, grade B: nearly there. The missing 21 points are spread across Discovery and Conformance and Capabilities.

Discovery 85Conformance 97Capabilities 50release 2026-09-30

How the score is made

three areas, weighted
Discovery 30%
Can a UCP agent find and read the profile: HTTPS, an answer at /.well-known/ucp, robots.txt allowing it, and five files outside UCP (llms.txt, sitemap, Open Graph, Organization schema, viewport).
85−4.5 pts
Conformance 40%
Does the profile follow the spec: valid against its release (counted three times), a dated release, keys published, few warnings, spec and schema links that resolve.
97−1.2 pts
Capabilities 30%
What an agent can do here: how many capabilities, checkout, at least one service, payment handlers, and services that answer our check.
50−15 pts
A85–100Ready for UCP agents
B70–84Nearly there
C50–69Partly ready
D30–49Hard for UCP agents
F0–29Not ready

Raise the score

fixes that move the number
+1
1Update to a published UCP version
The declared version is not in the published spec list.
Agents fall back to the closest known version, but breaking changes between releases can silently corrupt requests. Pin to a published version your stack actually supports.
Conformance · effort medium
"version": "2026-08-25"

See https://ucpchecker.com/spec for the current published version list.

part of +5
2Publish Organization schema (JSON-LD) on the homepage
No Organization-typed JSON-LD detected on your homepage.
Organization schema gives agents a structured representation of your brand identity: name, logo, social profiles, contact info, founding date. Agents use this to verify you are who you claim to be and to link your profile data to a recognizable entity.
Discovery · effort medium
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "OnlineStore",
  "name": "Yourstore",
  "url": "https://yourstore.com",
  "logo": "https://yourstore.com/logo.png",
  "sameAs": [
    "https://twitter.com/yourstore",
    "https://www.instagram.com/yourstore"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+1-800-000-0000",
    "contactType": "Customer Service"
  }
}
</script>

Drop into <head> or end of <body>. Use OnlineStore (more specific) when the entire site is an ecommerce store; Organization is the generic fallback.

part of +5
3Add Open Graph meta tags to the homepage
OG tags missing or incomplete on your homepage.
OG tags give agents and link unfurlers (Slack, iMessage, ChatGPT) a clean title, description, and image to represent your store. Without them, shares show garbled fallback text.
Discovery · effort low
<meta property="og:title" content="Yourstore | short tagline">
<meta property="og:type" content="website">
<meta property="og:url" content="https://yourstore.com/">
<meta property="og:description" content="One-sentence description of what you sell.">
<meta property="og:image" content="https://yourstore.com/og-cover.jpg">
<meta property="og:site_name" content="Yourstore">

Add inside <head>. og:title and og:type are the minimum; og:url, og:description, and og:image are strongly recommended.

part of +5
4Add a mobile viewport meta tag
No viewport meta tag detected on your homepage.
Mobile-originating agent sessions (ChatGPT iOS, Apple Intelligence) render store pages in browser sandboxes that respect the viewport tag. Without it, the page renders at desktop width and pinch-to-zoom UX kicks in, and agents that take screenshots of pages get unreadable images.
Discovery · effort low
<meta name="viewport" content="width=device-width, initial-scale=1">

One line inside <head>. Modern frontend frameworks add this automatically; its absence usually means a hand-rolled or legacy template.

Every check

11 passed · 6 to fix
Agent Discovery · 5 of 8
5 OK
HTTPS, UCP profile reachable, AI bot access, llms.txt, sitemap.xmlShow
  • HTTPS · Profile URL uses https://
  • UCP profile reachable · HTTP 200
  • AI bot access · robots.txt allows /.well-known/ucp
  • llms.txt · Found at /llms.txt
  • sitemap.xml · Found at /sitemap.xml
Problem
Open Graph tags
Missing or incomplete on homepage. Fix 3 above.
Discovery
Problem
Organization schema (JSON-LD)
Missing or incomplete on homepage. Fix 2 above.
Discovery
Problem
Mobile viewport meta
Missing or incomplete on homepage. Fix 4 above.
Discovery
UCP Conformance · 4 of 5
4 OK
Profile passes schema validation, Protocol version present and well-formed, Public keys published, Spec & schema URLs resolve (12)Show
  • Profile passes schema validation · No structural errors
  • Protocol version present and well-formed · Version: 2026-09-30
  • Public keys published · Keys published at the top level
  • Spec & schema URLs resolve (12) · All 12 URLs resolved.
To fix
No validation warnings
1 warning.
Conformance
Capability Coverage · 2 of 4
2 OK
Transports declared, Payment handlersShow
  • Transports declared · REST
  • Payment handlers · 2 handlers registered
Problem
Capabilities declared
0 of 6 capability families detected. A family counts once however many namespaces or extensions declare it.
Capabilities
Problem
Checkout capability
No checkout capability.
Capabilities