UCP status report

chaumet.com

Q: How was this UCP report for chaumet.com generated?

Our crawler fetches chaumet.com/.well-known/ucp directly, parses the profile against the official UCP JSON schema, checks robots.txt for its rules for AI crawlers, and runs payment-handler validation. No manual review, no opinions — just what the profile actually says. The check ran 2 days ago.

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

Invalid

40/100

UCP Score · grade D →

3 problems · 7 passed

HTTP 200 Release none Checked 17 Oct, 05:00 UTC

Findings

7 passed · 3 problems

To fix first

Problem

Serve profile as application/json

The profile URL did not return parseable JSON. How to fix →

Also worth fixing

To fix

Publish a /llms.txt brand brief

No /llms.txt file detected at the root of your domain. How to fix →

To fix

Publish a sitemap.xml

No sitemap.xml detected at the root of your domain. How to fix →

Passed

7 OK

HTTPS, AI bot access, Open Graph tags, Organization schema (JSON-LD), Mobile viewport meta, Public keys published, No validation warnings

Show all 7

HTTPS: Profile URL uses https://
AI bot access: robots.txt allows /.well-known/ucp
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 chaumet.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 · 954 ms at the store · public requests only

01Hosting ↗

Finding the profile

Open
02Identity Linking ↗

Acting for the buyer

Not offered
03Embedded ↗

In the buyer's browser

Not offered
04Services ↗

Calling its services

None
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, 518.0 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.

01 PROFILEGET /.well-known/ucp → 200, 518.0 KB of JSON954 ms
01 PROFILEGET /robots.txt → allows /.well-known/ucp–
01 PROFILEProfile did not pass schema validation: Response is not a valid JSON objectlocal
OUTSIDE UCPGET / → 200, Organization schema found–
OUTSIDE UCPGET /llms.txt → 200, not found–

UCP profile as served 3.9 KB · 128 lines

<!doctype html><html
  lang="fr"
  dir="ltr"
  data-high-contrast="false"
>
  <head>
    
    



<!-- OneTrust Cookies Consent Notice start for chaumet.com -->
<script
  src="https://cdn.cookielaw.org/scripttemplates/otSDKStub.js"
  data-document-language="true"
  type="text/javascript"
  charset="UTF-8"
  data-domain-script="33e98ae0-62b8-4b45-9294-f73667c1287c"
></script>
<script type="text/javascript">
  function OptanonWrapper() {}
</script>
<!-- OneTrust Cookies Consent Notice end for chaumet.com -->


    
    <style data-shopify>
  
  @font-face {
  font-family: "Work Sans";
  font-weight: 400;
  font-style: normal;
  font-display: swap;
  src: url("//www.chaumet.com/cdn/fonts/work_sans/worksans_n4.b7973b3d07d0ace13de1b1bea9c45759cdbe12cf.woff2") format("woff2"),
       url("//www.chaumet.com/cdn/fonts/work_sans/worksans_n4.cf5ceb1e6d373a9505e637c1aff0a71d0959556d.woff") format("woff");
}

  @font-face {
  font-family: "Work Sans";
  font-weight: 700;
  font-style: normal;
  font-display: swap;
  src: url("//www.chaumet.com/cdn/fonts/work_sans/worksans_n7.e2cf5bd8f2c7e9d30c030f9ea8eafc69f5a92f7b.woff2") format("woff2"),
       url("//www.chaumet.com/cdn/fonts/work_sans/worksans_n7.20f1c80359e7f7b4327b81543e1acb5c32cd03cd.woff") format("woff");
}

  @font-face {
  font-family: "Work Sans";
  font-weight: 700;
  font-style: italic;
  font-display: swap;
  src: url("//www.chaumet.com/cdn/fonts/work_sans/worksans_i7.7cdba6320b03c03dcaa365743a4e0e729fe97e54.woff2") format("woff2"),
       url("//www.chaumet.com/cdn/fonts/work_sans/worksans_i7.42a9f4016982495f4c0b0fb3dc64cf8f2d0c3eaa.woff") format("woff");
}

  @font-face {
  font-family: "Work Sans";
  font-weight: 400;
  font-style: italic;
  font-display: swap;
  src: url("//www.chaumet.com/cdn/fonts/work_sans/worksans_i4.16ff51e3e71fc1d09ff97b9ff9ccacbeeb384ec4.woff2") format("woff2"),
       url("//www.chaumet.com/cdn/fonts/work_sans/worksans_i4.ed4a1418cba5b7f04f79e4d5c8a5f1a6bd34f23b.woff") format("woff");
}


  :root {
    --pre-header-height: 0px;
  }
</style>


    
    
      <link rel="preconnect" href="https://fonts.shopifycdn.com" crossorigin>

      
      <link href="//www.chaumet.com/cdn/fonts/work_sans/worksans_n4.b7973b3d07d0ace13de1b1bea9c45759cdbe12cf.woff2" as="font" crossorigin="anonymous" rel="preload">
    

    
    <meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width,initial-scale=1,viewport-fit=cover"><link
    rel="icon"
    type="image/png"
    href="//www.chaumet.com/cdn/shop/files/Favicon_Chaumet_512X512_d2a89400-507f-4827-a036-e47d154250fa.jpg?crop=center&height=32&v=1783414479&width=32"
  >
  <link
    rel="apple-touch-icon"
    href="//www.chaumet.com/cdn/shop/files/Favicon_Chaumet_512X512_d2a89400-507f-4827-a036-e47d154250fa.jpg?crop=center&height=180&v=1783414479&width=180"
  ><meta
  property="og:site_name"
  content="Chaumet"
>
<meta
  property="og:url"
  content="https://www.chaumet.com/fr-fr"
>
<meta
  property="og:title"
  content="Joaillerie et Horlogerie de luxe depuis 1780 | Chaumet FR"
>
<meta
  property="og:type"
  content="website"
>
<meta
  property="og:description"
  content="Explorer l&#39;univers de la Maison de Haute Joaillerie Chaumet. Joaillier au savoir-faire d’exception, la Maison façonne depuis 1780 des créations au style très parisien."
><meta
  name="twitter:card"
  content="summary_large_image"
>
<meta
  name="twitter:title"
  content="Joaillerie et Horlogerie de luxe depuis 1780 | Chaumet FR"
>
<meta
  name="twitter:description"
  content="Explorer l&#39;univers de la Maison de Haute Joaillerie Chaumet. Joaillier au savoir-faire d’exception, la Maison façonne depuis 1780 des créations au style très parisien."
>

<title>Joaillerie et Horlogerie de luxe depuis 1780 | Chaumet FR</title>


  <meta
    name="description"
    content="Explorer l&#39;univers de la Maison de Haute Joaillerie Chaumet. Joaillier au savoir-faire d’exception, la Maison...

What goes in a UCP profile →Check your JSON in the Validator →Guides by store platform →

Is chaumet.com your store?

Claim it with one DNS record.

Claim this store

Questions

Why is chaumet.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. Agents reject profiles that don't validate, so this needs fixing before chaumet.com is agent-ready.

How can chaumet.com fix this?

Run the profile through our UCP Validator — it shows line-by-line schema deviations and how to fix each one. Most invalid profiles are quick fixes: a missing field, a typo, or an outdated spec version.

Does this mean chaumet.com is broken for shoppers?

No — the regular website still works fine for human customers. Only AI agents that strictly validate the profile will refuse to use the UCP integration. The store just isn't agent-ready until the validation issues are resolved.

How was this UCP report for chaumet.com generated?

Our crawler fetches chaumet.com/.well-known/ucp directly, parses the profile against the official UCP JSON schema, checks robots.txt for its rules for AI crawlers, and runs payment-handler validation. No manual review, no opinions — just what the profile actually says. The check ran 2 days ago.

How do I get a newer result for chaumet.com?

This page shows the stored result of our last check and when it was observed. To run a new check, use Check again on this 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.