UCP Checker
Back to status
romand.co.kr icon
UCP Score

UCP Score for romand.co.kr

UCP conformance score, top priorities, impact & effort matrix, and copy-paste fixes for every issue.

Not Detected
F22/100
Analyzed Sep 22, 2026 · 4 recommendations ·Cafe24
UCP Conformance Score

No score — no UCP manifest found

Publish a manifest at /.well-known/ucp and it will be read and scored on the next check.

Blocking

Publish a UCP manifest at /.well-known/ucp — No manifest was found at the well-known path.

Start Here

Publish a UCP manifest at /.well-known/ucp → Publish Organization schema (JSON-LD) on the homepage → Publish a /llms.txt brand brief

⚠️
Connection Issue:

Endpoint is returning HTTP 404. Agents treat this as a failure.

Not Detected

No UCP manifest was found at /.well-known/ucp on romand.co.kr.

Latency
660ms
Version
Robots.txt
Allowed ✅

Top Priorities

1
Publish a UCP manifest at /.well-known/ucp

No manifest was found at the well-known path.

High impact High effort
2
Publish Organization schema (JSON-LD) on the homepage

No Organization-typed JSON-LD detected on your homepage.

Medium impact Medium effort
3
Publish a /llms.txt brand brief

No /llms.txt file detected at the root of your domain.

Low impact Low effort Emerging

Impact & Effort Matrix

Prioritised recommendations by expected impact and implementation effort

Quick Wins(0)

High impact, low effort

  • No items
Strategic Investments(1)

High impact, high effort

  • Publish a UCP manifest at /.well-known/ucp
Incremental Gains(1)

Medium impact & effort

  • Publish Organization schema (JSON-LD) on the homepage
Consider Later(2)

Lower priority

  • Publish a /llms.txt brand brief
  • Add Open Graph meta tags to the homepage

Recommendations

All improvements ranked by priority, with evidence and actionable fixes.

1

Publish a UCP manifest at /.well-known/ucp

High impact High effort

No manifest was found at the well-known path.

Why it matters

Without a manifest, agents fall back to scraping HTML — slower, more error-prone, and far more likely to fail at checkout. UCP turns "guess what this store sells" into a contract.

Show fix

Serve a JSON document at /.well-known/ucp with at minimum a ucp.version, ucp.capabilities, and ucp.services. See the developer tools page for platform-specific guides.

GET https://yourstore.com/.well-known/ucp
Content-Type: application/json

{
  "ucp": { "version": "2026-08-25", "capabilities": {...}, "services": {...} },
  "keys": [...]
}
UCP_NOT_DETECTED
2

Publish Organization schema (JSON-LD) on the homepage

Medium impact Medium effort

No Organization-typed JSON-LD detected on your homepage.

Why it matters

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 manifest data to a recognizable entity.

Show fix

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

<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>
UCP_MISSING_ORG_SCHEMA
3

Publish a /llms.txt brand brief

Low impact Low effort Emerging

No /llms.txt file detected at the root of your domain.

Why it matters

llms.txt is an emerging convention (analogous to robots.txt) that lets you give AI agents a hand-written brief about your brand, product categories, return policy, and crawl preferences. Strict UCP agents do not require it, but recommendation/discovery agents increasingly read it for context.

Show fix

Save as /llms.txt at your site root. Plain text, written for an LLM audience. The format is informal — these section headings are a working convention, not a spec. Replace the placeholders with your own brand details and update when policies or product lines change.

# llms.txt
# Public brief for AI agents about Yourstore

# About
One or two sentences on what you sell, who you sell to, and any defining context (founded, mission, sustainability stance, etc.).

# Product Categories
- Category one
- Category two
- Category three

# Policies
- Returns: e.g. 30 days, full refund
- Shipping: e.g. Free over $30, 3-5 business days
- Any other policy worth surfacing (cruelty-free, vegan, made-to-order, etc.)

# Agent Capabilities
- UCP manifest: /.well-known/ucp
- Supported flows: cart, checkout, tokenized payment, etc.
- Anything explicitly NOT supported (e.g. "no subscription products via agent")

# Contact
[email protected]
UCP_MISSING_LLMS_TXT
4

Add Open Graph meta tags to the homepage

Low impact Low effort

OG tags missing or incomplete on your homepage.

Why it matters

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.

Show fix

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

<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">
UCP_MISSING_OG_TAGS

Full Check Breakdown

Every signal we evaluate, grouped by category.

Agent Discovery4/8 passed

Can AI agents find your store and its UCP manifest?

  • HTTPSCore

    Manifest served over a secure connection.

    Manifest URL uses https://

    Why it matters

    Agents reject non-HTTPS endpoints outright. Signed payloads over HTTP are meaningless because the channel itself is tamperable.

  • UCP manifest reachableCore

    Manifest fetched OK from /.well-known/ucp.

    HTTP 404

    Why it matters

    Agents start every session by fetching this URL. If it 404s or times out, the store is invisible to agent commerce.

  • AI bot accessCore

    robots.txt allows agent crawlers to fetch the manifest.

    robots.txt allows /.well-known/ucp

    Why it matters

    Agents respect robots.txt. Even a published manifest gets ignored if the file is disallowed for known agent user-agents.

  • llms.txtExperimental

    Hand-written brief at /llms.txt for AI agents.

    HTTP 404 at /llms.txt

    Why it matters

    Emerging convention (analogous to robots.txt). Recommendation/discovery agents read it for brand context, return policy, and crawl preferences.

  • sitemap.xmlCore

    XML sitemap published at /sitemap.xml.

    Found at /sitemap.xml

    Why it matters

    Tells agents which pages are canonical and how often they change. Without it, agents fall back to following internal links.

  • Open Graph tagsCore

    OG meta tags on the homepage.

    Missing or incomplete on homepage

    Why it matters

    OG tags drive how your store unfurls in agent surfaces, Slack, iMessage, and ChatGPT shares.

  • Organization schema (JSON-LD)Core

    Schema.org Organization (or OnlineStore) JSON-LD on homepage.

    Missing or incomplete on homepage

    Why it matters

    Gives agents a structured representation of your brand identity — used to verify you are who your manifest claims you are.

  • Mobile viewport metaCore

    Viewport meta tag for mobile rendering.

    <meta name="viewport"> present

    Why it matters

    Mobile agent sessions render in browser sandboxes that respect this. Without it, screenshots taken by agents are unreadable.

UCP Conformance0/1 passed

Does your manifest meet the published spec?

  • Manifest present for spec validationCore

    Conformance checks require a fetchable manifest.

    Status: Not Detected

    Why it matters

    Once the manifest is fetchable, this section will show 4+ structural checks (validity, version format, signing keys, validation warnings).

Capability Coverage0/1 passed

What operations can agents actually perform?

  • Capabilities visibleCore

    Capability checks require a fetchable manifest.

    Status: Not Detected

    Why it matters

    Once the manifest is fetchable, this section will show capability count, checkout coverage, transports, and payment handler health.

Technical Vitals

Technical details for this UCP endpoint
UCP Status Not Detected
Endpoint https://romand.co.kr/.well-known/ucp
HTTP Status 404
UCP Version
Transports
Last Observed
Last Full Index

Embed your UCP Score

Drop the live grade into your README, status page, or marketing site. The badge auto-updates as your score changes.

UCP Score for romand.co.kr badge for https://ucpchecker.com/score/romand.co.krLive preview
Markdown
[![UCP Score for romand.co.kr](https://ucpchecker.com/score/romand.co.kr/badge.svg)](https://ucpchecker.com/score/romand.co.kr)
HTML
<a href="https://ucpchecker.com/score/romand.co.kr"><img src="https://ucpchecker.com/score/romand.co.kr/badge.svg" alt="UCP Score for romand.co.kr"></a>
New · Early access open
Is romand.co.kr yours? Claim it & monitor it daily

Prove ownership with one DNS record and the new monitoring dashboard watches it every day — score trends, break alerts, staging drift and a watchlist that benchmarks you against the field. Free while in beta.

Start monitoring →

This score reflects data from the most recent crawl. Run a fresh check to update, or read the methodology to see how each signal is scored.

Save this report

Track romand.co.kr's UCP score over time. We'll re-run the full check weekly and email you if the score drops, a capability regresses, or status flips.

Free. One email when something changes — no marketing. Privacy.