What is Clione?
Delivery and reception (30 Oct 2026): generation, publication and reception are separate states. Published scoring remains formula 1; the reader proposal is inactive. The study measured APIs and Claude Code, not consumer apps, recommendations or sales. See the reader table.
Clione prepares catalog facts and publishes supported signals through your platform integration. Verify the served page rather than assuming every reader receives the same content.
Assistants use different retrieval paths. Clione helps you review, publish and verify catalog content; it does not guarantee appearance in recommendations.
What problem it solves
Traditional SEO was written for keyword-matching crawlers. AI assistants match meaning. A product titled "SKU-23487 · Premium Item" tells an assistant almost nothing about what it is or who it is for.
Clione reads the products, categories, collections and pages of your store and produces, for each one:
- A natural-language identity — what it is, who it's for, when to recommend it.
- Structured attributes — use case, price positioning and similar facts grounded in your own catalog text.
- Search keywords — the queries people actually type, in the same language as your content.
- SEO meta — a meta title and a meta description.
- Schema.org JSON-LD — structured product data whose direct reception differs by reader and placement.
- FAQs — questions and answers you review before they go live.
How it works
- Connect your BigCommerce, Shopify or WooCommerce store.
- Sync your catalog into Clione.
- Enrich the entities you choose. Each enrichment uses one credit from your plan.
- Review what Clione wrote, edit it and approve it.
- Publish to your storefront. Meta fields and JSON-LD reach your store only when you publish. On BigCommerce with the Schema Injector installed, approved FAQs show in the accordion right away (FAQs that Clione generates are saved as approved).
- Verify that the signals are live. Verification is available from the Growth plan.
What it writes to your store
Clione writes only what you publish:
- The SEO title and meta description fields of BigCommerce and Shopify.
- On BigCommerce, structured data (JSON-LD) written server-side through BigCommerce's widgets when you publish. The Schema Injector script renders the FAQ accordion, its styles and the agent links.
- On Shopify, structured data (JSON-LD) through the Clione SEO theme app embed and the FAQ accordion through the Clione FAQ theme app embed. Both embeds, and the
.mddocuments under/apps/clione, need the Clione Shopify app. A store connected with its own app from Shopify's Dev Dashboard (Client ID and Client Secret) still gets sync, enrichment and the meta title and description. See Connect your Shopify store to Clione. - On WooCommerce, the signals are stored as
_clione_*post meta and rendered by the Clione WordPress plugin. Clione doesn't write the SEO title and description to WooCommerce's native fields. - On Shopify, if you turn on Enriched product description in Store Settings, a block added below your own product description. Your own text is never replaced, and turning the setting off removes the block on the next publish.
What it doesn't do
- It doesn't replace your e-commerce platform. Your store stays on BigCommerce, Shopify or WooCommerce.
- It doesn't publish on its own. Enriching never changes your storefront; publishing is always something you do.
- It doesn't fabricate reviews or sales data. Quality scores are opinions the AI forms from your catalog text, useful for comparing products within your own catalog. See Understanding Quality Scores.
Where to start
Follow the tutorials in order:
To understand what goes into an enrichment, read Understanding enrichment.