02
Told when it's overwritten
If the platform or a PIM overwrites a field Clione pushed, the next sync flags it, with the date and the exact fields.
Features · Publish
JSON-LD and schema markup on every product page.
Assistants and search engines read a product best when it is described as data: what it is, who makes it, what it costs, what people ask about it. Clione writes that graph from your catalog and publishes it when you press Push.
The graph, as a crawler receives it
This is the shape of what Clione publishes on a product page: one @graph holding your company, your site, the breadcrumb trail and the product with its offer, plus the questions when the product has them. Every node points at the others by @id, so a machine reads one connected description instead of four loose ones.
JSON-LDproduct page, in the head
{ "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://nubiasleep.com/#org", "name": "Nubia Sleep", "logo": "https://nubiasleep.com/logo.png" }, { "@type": "WebSite", "@id": "https://nubiasleep.com/#site", "publisher": { "@id": "https://nubiasleep.com/#org" } }, { "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Mattresses" }, { "@type": "ListItem", "position": 2, "name": "Cloud Mattress" } ] }, { "@type": "Product", "@id": "https://nubiasleep.com/cloud#product", "name": "Cloud Memory Foam Mattress", "sku": "NUB-CLD-Q", "brand": { "@type": "Brand", "name": "Nubia" }, "description": "Medium-feel memory foam with a washable cover.", "keywords": "memory foam mattress, medium firm mattress", "offers": { "@type": "Offer", "price": "899.00", "priceCurrency": "USD" } }, { "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "Is it good for side sleepers?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. The medium feel lets the shoulder sink in." } } ] } ] }
Shortened for the page: the real graph carries every field the store and the enrichment can fill. The product node's @id is stable, which is what lets it sit beside your theme's own markup. What JSON-LD is, and what schema markup is, if you want the long version.
What fills it
Real fields, not a template with blanks.
Name, brand, SKU and price come from the store. The description, the keywords and the questions come from the enrichment you approved. Your company's name, logo and details are filled in once, for the whole store.
- One Offer per product, from the price the store serves
- Star ratings from your store's own reviews; a product with no reviews carries no rating
- Keywords in the graph's own
keywordsfield and in the meta description, not inmeta keywords - An FAQPage node when the product has questions, from the question manager
Where it lands
Published the platform's own way. No code.
Clione writes through each platform's own API, so the graph is in the page the store sends and a crawler doesn't have to run anything to find it.
- BigCommerce: rendered on the server through the Widget API
- Shopify: written to metafields and app embeds, the graph in the head and the FAQ accordion in the body
- Both embeds switch on from the Clione dashboard in one click
Beside your theme
Next to your theme's markup, not on top of it.
Your theme probably prints a Product node of its own. Clione's carries a stable @id and sits beside it instead of duplicating it, so you don't have to strip the theme first.
After the push
Then it reads the page back.
01
Checked on the live page
Clione fetches the live product page and reports, signal by signal, what rendered against what it pushed.
What it reads back →03
Three versions kept
Restore any of the last three versions of an entity. The restore is a version too, and it reaches the store with the next push.
What it has done
Measured on real pages.
+13%
impressions on 39 enriched BenroUSA product pages, while the whole site grew 8%
June 2026, Search Console, read by the agency Wenstein over ten days.
+25%
impressions on the nine of those pages that also got FAQs
Same store, same period. Most of the nine also moved up in position.
+25%
clicks on Rotten Tomatoes pages with structured data, against pages without
A case Google publishes in its own introduction to structured data.
Before you push
What people ask about the graph.
Will it clash with the schema my theme already prints?
No. Clione's Product node has its own stable @id and sits beside your theme's node instead of duplicating it. You don't have to remove anything from the theme first.
Do I need a developer?
No. You connect the store, sync the catalog and switch the embed on from the dashboard. The setup checklist in Clione walks you through it and checks that the graph is installed.
Which pages get the graph?
Every product page, with Organization, WebSite, BreadcrumbList and Product, plus FAQPage when the product has questions. Categories, collections and content pages get their meta description and keywords today, and their own graph is on the way.
Can I edit what it writes before it goes live?
Yes. Every signal sits next to what your store serves today. Edit it, refine it with one instruction in plain words, or leave it. Nothing reaches the storefront until you press Push.
What about a headless storefront?
Hydrogen storefronts on Shopify render the graph, the meta tags and the FAQ on the server from the same metafields, and Clione checks them like any other store. For any other headless storefront, talk to us: Clione can feed it through a package of its own, and the setup is worked out with you.
What does it cost?
Nothing, during the beta. Clione is taking selected clients into this stage, in limited places, free of charge, and prices are published when the beta ends in Q1 2027.
Keep reading
Where it goes from here.
Start
Bring one product. See the graph it gets.
On a short call: your store, one product, the markup it serves today beside the graph Clione would publish.
Clione is in beta: selected clients, limited places, free until the beta ends in Q1 2027.