In plain text
llms.txt and one Markdown document per entity, for the agents that read text first.
Clione generates an llms.txt for your store and a Markdown document for every product, category, collection and content page. AI agents read the whole catalog as plain text, on your store's own domain.
This is the shape of one product's document: what the product is, who it suits, the words shoppers search with and the questions it answers, in plain Markdown with nothing around it. Every product, category, collection and content page gets one, served from your store's own domain.
# Cloud Memory Foam Mattress > A medium-feel memory foam mattress with a washable cover, for sleepers who want pressure relief without sinking in. ## Product Details - **Brand:** Nubia - **SKU:** NUB-CLD-Q ## Buying Guide **Recommended for:** side and back sleepers who wake up with sore shoulders. **Why choose this:** the medium feel lets the shoulder sink in while the hips stay level. **Common concerns:** memory foam can sleep warm; the cover comes off and goes in the wash. ## Search Keywords memory foam mattress, medium firm mattress, mattress for side sleepers ## Frequently Asked Questions ### Is it good for side sleepers? Yes. The medium feel lets the shoulder sink in.
Shortened for the page, and filled from an invented store: yours is written from your own catalog. The llms.txt file sits above all of these documents and tells a model what the store is.
llms.txt is a proposed convention: one Markdown file that tells a language model what a site is about. Clione generates your store's from its catalog and serves it on your own domain: on Shopify under /apps/clione/, on BigCommerce from a subdomain you point at Clione.
Each product, category, collection and content page gets a document of its own. An agent that wants one product reads that product, without the theme, the scripts and the menus around it.
A product deleted in the store disappears at once from what Clione serves to AI agents. No agent reading from Clione is told about something you no longer sell.
One JSON-LD graph per product page, published through the platform's own API.
The graph →Clione sends your catalog to ChatGPT shopping every day, and builds a supplemental feed for Google Merchant Center.
The feeds →llms.txt and one Markdown document per entity, for the agents that read text first.
A proposed convention: a Markdown file at a known address that tells a language model what a site is and where its most useful content lives. More on llms.txt, in the glossary.
From your store's own domain. On Shopify, through Shopify's app proxy, under /apps/clione/ on your store's address. On BigCommerce, from a subdomain of your domain that you point at Clione with one DNS record, set up once with you. Nothing on your theme has to change.
Every product, category, collection and content page Clione syncs from a Shopify or BigCommerce store. One entity, one document.
It disappears at once from what Clione serves to AI agents, and from Clione itself after a short grace period.
Yes. The questions Clione manages reach the product page as FAQPage markup, and a public FAQ API serves them too. How the questions are written.
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.
One graph per product page, through the platform's own API, beside your theme's markup.
Your catalog sent to ChatGPT shopping every day, and a supplemental feed for Google Merchant Center.
What the live page actually serves, read back after every push.
On a short call: your store, one product, and the plain-text version an AI agent would read.