Real queries into the enrichment
One Google sign-in, read-only and revocable from Store Settings. The queries people actually use to reach a product feed its next enrichment, and its search performance shows in the product's own Insights.
Clione reads what Google already knows about your store and uses it: the real queries from Search Console go into the enrichment, Analytics shows which orders came from AI assistants, and Merchant Center gets a supplemental feed from the enriched catalog.
One Google sign-in, read-only and revocable from Store Settings. The queries people actually use to reach a product feed its next enrichment, and its search performance shows in the product's own Insights.
Clione matches your store's orders to the visits that produced them and shows which came from AI assistants, and which AI sources cannot be measured at all.
AI attribution →Color, material, size, gender and age group, filled only where your store states them, and Google's product category only when it matches Google's own list exactly.
Product feeds →Clione puts your shoppers' questions to Gemini and to ChatGPT, and shows whether they name your products, and who takes your place when they don't.
How AI visibility is measured →The Search Console connection is read-only, and you can revoke it from Store Settings. Clione reads; it does not change your Google settings.
It gives Google better data to work with. Whether and where products appear is Google's call, not ours.
Yes. The settings explain how to use it in Microsoft Merchant Center and Meta, and list the last five builds with what each left out and why.
On a short call we open one product: the queries that reach it today, and what Clione would publish.