UCP Checker
Check a store
UCP status report

meet5.com

meet5.com responded, but its profile did not pass schema validation.

Invalid
43/100
UCP Score · grade D →
1 problem · 9 passed
HTTP 200 Release none Checked 25 Oct, 00:00 UTC

Findings

9 passed · 1 problem
To fix first
Problem
Serve profile as application/json
The profile URL did not return parseable JSON. How to fix →
Passed
9 OK
HTTPS, AI bot access, llms.txt, sitemap.xml, Open Graph tags, Organization schema (JSON-LD), Mobile viewport meta, Public keys published, No validation warnings
Show all 9
  • HTTPS: Profile URL uses https://
  • AI bot access: robots.txt allows /.well-known/ucp
  • llms.txt: Found at /llms.txt
  • sitemap.xml: Found at /sitemap.xml
  • Open Graph tags: og:title and og:type/url present
  • Organization schema (JSON-LD): Organization-typed JSON-LD detected
  • Mobile viewport meta: <meta name="viewport"> present
  • Public keys published: Keys published at the top level
  • No validation warnings: No outstanding validation issues
Check trace

How meet5.com answered our check

The five ways an agent can reach this store, what each one met, and every request we made.

1 of 5 open
4 requests · 567 ms at the store · public requests only
  1. 01Hosting ↗
    Finding the profile
    Open
  2. 02Identity Linking ↗
    Acting for the buyer
    Not offered
  3. 03Embedded ↗
    In the buyer's browser
    Not offered
  4. 04Services ↗
    Calling its services
    None
  5. 05continue_url ↗
    Sending the buyer to the website
    Not declared
UCP Checkerpublic requests
  • 2 requestsFinding the profile/.well-known/ucp · 200
  • read from profileActing for the buyernot declared
  • read from profileIn the buyer's browsernot declared
  • not calledCalling its servicesnone declared
  • read from profileSending to the websitenot declared
  • 2 requestsOutside UCPhomepage · /llms.txt
Open
01 · Finding the profile2 requests
Served at /.well-known/ucp with 200 OK, 2.8 KB. robots.txt allows /.well-known/ucp.
Not offered
02 · Acting for the buyerread from profile
The profile doesn't declare identity linking, so an agent can't act for a signed-in buyer.
Not offered
03 · In the buyer's browserread from profile
No Embedded service is declared.
None
04 · Calling its servicesnot called
No services are declared.
Not declared
05 · Sending the buyer to the websiteread from profile
No permalink declared. Whether error replies carry a continue_url shows only in an agent run.
  1. 01 PROFILEGET /.well-known/ucp → 200, 2.8 KB of JSON567 ms
  2. 01 PROFILEGET /robots.txt → allows /.well-known/ucp–
  3. 01 PROFILEProfile did not pass schema validation: Response is not a valid JSON objectlocal
  4. OUTSIDE UCPGET / → 200, Organization schema found–
  5. OUTSIDE UCPGET /llms.txt → 200, 3.0 KB–
UCP profile as served 2.8 KB · 54 lines 
<!doctype html>
<html lang="en">
    <head>
        <meta charset="UTF-8" />
        <meta name="viewport" content="width=device-width, initial-scale=1.0" />
        <meta name="color-scheme" content="light dark" />
        <base href="/" data-app-base-path />
        <script>
            (function () {
                var root = document.documentElement;
                var isDark =
                    typeof window.matchMedia === 'function' &&
                    window.matchMedia('(prefers-color-scheme: dark)').matches;
                var theme = isDark ? 'dark' : 'light';

                root.classList.toggle('dark', isDark);
                root.dataset.theme = theme;
                root.style.colorScheme = theme;
            })();
        </script>
        <link rel="preconnect" href="https://static.wixstatic.com" crossorigin />
        <link rel="icon" type="image/webp" href="./favicon.webp" />
        <!-- Opaque and full-bleed: iOS paints alpha black and applies its own corner mask. -->
        <link rel="apple-touch-icon" sizes="180x180" href="./apple-touch-icon.png" />
        <!-- Structured data (basic Organization) -->
        <script type="application/ld+json">
            {
                "@context": "https://schema.org",
                "@type": "Organization",
                "name": "Meet5",
                "url": "https://www.meet5.com",
                "logo": "https://static.wixstatic.com/media/5d095a_52150a5c9f8b47d095be98e6779ca190~mv2_d_5325_1545_s_2.png/v1/crop/x_1492,y_103,w_3833,h_1339/fill/w_125,h_45,al_c,q_85,usm_0.66_1.00_0.01,enc_avif,quality_auto/Logo_good-quality.png",
                "sameAs": ["https://www.facebook.com/meet5", "https://www.instagram.com/meet5"]
            }
        </script>
        <!--ssr-head-->
      <script type="module" crossorigin src="./assets/index-D7pHq5HQ.js"></script>
      <link rel="modulepreload" crossorigin href="./assets/rolldown-runtime-CNC7AqOf.js">
      <link rel="modulepreload" crossorigin href="./assets/react-vendor-CpAvoE1t.js">
      <link rel="modulepreload" crossorigin href="./assets/schemas-ZpWSDJG5.js">
      <link rel="modulepreload" crossorigin href="./assets/env-Di1w3ZA2.js">
      <link rel="modulepreload" crossorigin href="./assets/LocaleUseCases-kBopeXTq.js">
      <link rel="modulepreload" crossorigin href="./assets/logger-DDUN-Tx9.js">
      <link rel="modulepreload" crossorigin href="./assets/paths-Dw2-ck_g.js">
      <link rel="modulepreload" crossorigin href="./assets/internalPath-z4B1E9Jw.js">
      <link rel="modulepreload" crossorigin href="./assets/client-events-C78T2OI2.js">
      <link rel="stylesheet" crossorigin href="./assets/index-FGA4tOpq.css">
    </head>
    <body>
        <noscript>You need to enable JavaScript to run this app.</noscript>
        <div id="root"><!--ssr-html--></div>
    </body>
</html>
What goes in a UCP profile →Check your JSON in the Validator →Guides by store platform →
Is meet5.com your store?
Claim it with one DNS record.
Claim this store

Questions

Why is meet5.com's profile invalid?
We found a UCP profile, but it failed schema validation against the official spec. The findings on this page list what failed — usually missing required fields, wrong data types, or version mismatches. A UCP agent may not be able to use a profile that doesn't validate, so these are worth fixing first.
How can meet5.com fix this?
Run the profile through our UCP Validator — it shows each problem and where it is in the file. Fix those, publish the profile again, then run a new check.
Does this mean meet5.com is broken for shoppers?
No. This check looks only at the UCP profile, not at the website people shop on. It only affects UCP agents, which read the profile.
How was this UCP report for meet5.com generated?
With public requests on 25 October 2026: we asked for meet5.com/.well-known/ucp and read its robots.txt, then validated the profile against the UCP release it declares and checked that its spec and schema links resolve. No sign-in, no purchase and no manual review. How we check.
How do I get a newer result for meet5.com?
This page shows the stored result of our last check (25 October 2026). To run a new one, enter meet5.com on the Check page.
Why does this status matter?
Universal Commerce Protocol is an open standard that lets a UCP agent find out what a store sells, build a cart and check out through a published contract instead of reading web pages. A valid UCP profile is how a store declares that support.