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 · Write
Every question answered, on every product page.
Shoppers and their assistants arrive with questions the product page never answers. Clione writes, imports and keeps those answers for the whole catalog, and publishes them as FAQ schema and a visible FAQ when you press Push.
The FAQ schema a crawler receives
Every question on a product becomes a Question with its accepted Answer, inside one FAQPage node that sits in the same @graph as the product. A crawler reads the questions as part of the product, not as a loose block of text beside it.
JSON-LDproduct page, the FAQPage node of the graph
{ "@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." } }, { "@type": "Question", "name": "Can I wash the cover?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. It unzips and goes in the machine on a cold cycle." } } ] }
Shortened for the page: the real node carries every question the product has. The same entries render as the accordion in the page body, so the shopper reads what the crawler reads. What FAQPage is, if you want the long version.
Write them
Generated, written or imported.
Generate questions for one product or the whole store, with the count, the language and the topic you choose. Add your own by hand, or bring the ones you already have.
- By hand for a product, a variant, a category, a collection, a brand or a page, per locale
- CSV import and export, matched on your platform's own entity ids
Keep them
One library, no duplicates.
Every question lives in one library for the store, with duplicates caught. Reorder, edit or delete them entity by entity.
- Products, variants, categories, collections, brands and pages, each with its own set
- The whole library exported to CSV whenever you want it back
Publish them
Markup for the crawler, an accordion for the shopper.
Each entry is pushed as FAQ JSON-LD with the product's other signals, and the same questions show on the page as an accordion. Nothing goes live until you press Push.
- Shopify: the Clione FAQ embed, switched on from the dashboard in one click
- BigCommerce: the FAQ renderer, installed from Store Settings
- Any other site: universal snippets (an auto-detect loader, Liquid, or JSON-LD only) with an API key and allowed domains
- A public FAQ API, for the places a snippet can't reach
- "Push FAQs only" when the questions changed and nothing else did
After the push
Then it keeps them there.
01
Read back from the live page
Clione fetches the page, checks that the questions it pushed rendered, and alerts you when one goes missing.
What Verify reads →03
In the product's graph
The FAQPage node joins the same graph as the product, which sits beside your theme's markup instead of duplicating it.
The JSON-LD graph →What it has done
Measured on real pages.
+25%
impressions on the nine enriched BenroUSA product pages that also got FAQs
June 2026, Search Console, read by the agency Wenstein over ten days. Most of the nine also moved up in position.
+13%
impressions on all 39 enriched pages of the same store, while the whole site grew 8%
Same store, same period, against the baseline before enrichment.
Before you publish
What people ask about the questions.
What is FAQ schema, and why put it on product pages?
FAQ schema is the FAQPage markup that tells a machine which questions a page answers and what the answers are. On a product page it puts the answers shoppers look for into the same graph as the product, so a crawler doesn't have to guess which text is an answer.
Will Google show my FAQs in its results?
That's Google's call, and no tool can promise it. What Clione controls is that the markup is on the page, that the same questions are visible in the accordion, and that both are still there after the push.
Can I bring the FAQs I already have?
Yes. Import them by CSV, matched on your platform's own entity ids, and the library catches the duplicates. Export works the same way, so the questions are never locked in.
Do I need a developer to show them on the page?
No. On Shopify you switch on the Clione FAQ embed from the dashboard; on BigCommerce you install the FAQ renderer from Store Settings. Setup checks the FAQ widget for you, and no step needs code: that is the whole idea of Clione for merchants.
What's the difference between this and enrichment?
Enrichment writes what the product is: its identity, its reasoning, its meta description and keywords. The question manager handles the questions. Both reach the store in the same push, and "Push FAQs only" sends the questions alone. The product overview shows how the pieces fit.
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. Where the FAQPage node lands.
Write
Semantic enrichment
An identity, a reasoning set, a meta description and keywords for every product, category, collection and page.
Check
Verify
The live page read back, signal by signal, and an alert when one goes missing.
Start
Bring one product. Leave with its questions answered.
On a short call: your store, one product, the questions shoppers ask about it and the FAQ Clione would publish.
Clione is in beta: selected clients, limited places, free until the beta ends in Q1 2027.