01
Failures that say why
The Publishing page lists every signal that failed, with the reason. A deliberate no-op is recorded as skipped, never as a success or a failure.
Features · Check
Structured data, checked on the live page.
A signal that never rendered is a product an assistant can't read. Clione reads your live pages back, signal by signal, and tells you when one goes missing.
Read back
What rendered, against what was pushed.
Clione fetches the live page and compares it with what it pushed, one signal at a time. A signal it can't find is marked "not read back from the store", so a gap never passes for a success.
- Every one of the signals it publishes: the JSON-LD graph, the meta description, the keywords, the FAQs
- Products, categories, collections and content pages, on Shopify and BigCommerce
- A verification score for the store, with the entities checked and the entities drifted
- "Verify now" runs a check the moment you want one
When one goes missing
A signal disappears. You hear about it.
Every entity type is re-checked on a schedule, and the store's owner is alerted the moment a verified signal goes missing. A theme change or a new app can drop a tag without telling anyone; Clione notices.
- A "This week" list on the store Overview: what to fix, each item linked to the screen that fixes it
- The same list in the owner's inbox, every week
When the store writes back
Overwritten? You get the date and the fields.
When the platform or a PIM overwrites a field Clione pushed, the next sync flags the entity with the date and the exact fields, and clears the flag when the values come back.
- A warning when the store changed an entity after its last push: Clione compares the two dates, so you can push again before the page and the signals disagree
- Pushing again is a decision you make, never an automatic overwrite
Control
Every result has a reason.
02
Three versions kept
Roll back to any of the last three versions of an entity. The restore is a version too, and it reaches the store with the next push.
03
Any page, before you connect
The Clione Pulse extension reads the structured data of any page, with no store connected.
Check any page with Pulse →The rule
Clione tells you. You decide.
Verify reads your pages and reports what it found. When a signal is missing or overwritten, Clione flags it and waits: pushing again is your call, like every push before it.
The whole loop: sync, enrich, push, verify →Before you push
What people ask about the check.
What happens when a signal goes missing?
The store's owner gets an alert, and the entity shows which signal was not read back from the store. Clione doesn't push again on its own: you look, you decide, you press Push.
How is this different from a schema validator?
A validator checks the markup you hand it. Verify reads the page your store actually serves and checks that what Clione pushed is there, signal by signal. That second job has a name: publication verification.
How often does it check?
On a schedule, and whenever you ask. Every entity type is re-checked on your plan's cadence, and "Verify now" runs a check at once. Overwrites are caught on the next sync, and a stale catalog syncs on its own.
What if my PIM or ERP writes over what Clione pushed?
The next sync flags the entity with the date and the exact fields that changed, and the flag clears when the values come back. Clione also compares when the store last changed an entity with when it was last pushed, and warns you when the store moved first.
Does it work across client stores?
Yes. An organization holds many stores and each one is checked on its own. The agency dashboard sets every client store side by side, with its coverage.
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.
Publish
Schema and JSON-LD publishing
One graph per product page, through the platform's own API. What Verify reads back.
Write
Question manager
FAQs generated, imported, deduplicated and pushed as FAQPage, across the whole store.
Measure
AI visibility
See whether ChatGPT and Gemini recommend you, and who replaces you.
Start
Bring one product. We'll read its page with you.
On a short call: your store, one product, what its live page serves today beside what Clione would push and check.
Clione is in beta: selected clients, limited places, free until the beta ends in Q1 2027.