Skip to main content
Products answers: when a buyer asks ChatGPT what to buy, which products does it put in front of them, and are yours among them? It reads the product cards in the answers your project already collects. Nothing extra is asked, and nothing is changed anywhere.

Before you start

Product cards appear for buying questions, such as “best running shoes under $100”. If your prompts are all research questions, add a few buying ones in Prompts. Only ChatGPT shows product cards we can read. The screen says which engines in your scope report them and which don’t.

What is on it, top to bottom

The sentence

One line says what the window found: how many products ChatGPT showed, in how many shopping answers, and how many of them are yours. Under it, how many of ChatGPT’s answers showed products at all, and which engines report cards. A shopping answer is an answer with at least one product card. Visibility on this screen is a share of shopping answers, not of every answer, so a project with mostly research questions does not show every product near zero.

Shown

Every product ChatGPT showed, most visible first: Hover a row to see how often it was the first card (its win rate) and its average position. Filter by All, Yours or Others. Open a product to see Product detail. Without a catalog, a product is yours when its card links to your own site.

Your catalog

Appears once a catalog is connected. One line counts how many of your products appeared, how many never did, and how many are quoted at a price your catalog doesn’t have. Each row: your product and its catalog price, its visibility (or not shown), the price ChatGPT quoted with differs when it is more than 1% off in the same currency, and the AI-referred revenue, sessions and conversions of its page from GA4. Add to Gaps turns a product that is never shown, or quoted at a different price, into a Gaps work item. Filter by All, Not shown or Price differs.

Connecting a catalog

Choose one of three ways. Choosing one shows the one field it needs.
  • Shopify store: your store’s domain. Citino reads the store’s public product list once a day as CitinoBot, if your robots.txt allows it. Nothing to install.
  • Merchant feed: the product feed URL you give Google Merchant Center, read once a day.
  • CSV file: drop a sheet with id, title and url columns, and price with a currency (or a price like 229.00 USD). It is read in your browser, you see how many products it holds, and it uploads in batches with a progress line. Upload again to replace it.
Up to 5,000 products are kept. Owners, admins and editors can connect, sync and disconnect.

States

  • No engine in scope shows product cards: names the engines; there is nothing to change.
  • No answers yet: the scope needs one full run first.
  • No shopping answers: answers exist, and none showed product cards. Add buying questions in Prompts.
  • Reading your catalog: a sync is running; results in a minute or two.
  • Last sync failed: the reason, and what to do instead (a feed URL or a CSV). The last good catalog stays in use.
  • Truncated: the catalog has more than 5,000 products and the first 5,000 were kept.
  • Connect GA4: the revenue cells link to Integrations; the rest of the row still shows.

Product detail

One product: its trend, prompts and prices.

Gaps

Where a product fix becomes a work item.