15 copy-and-paste prompts to test whether ChatGPT can find your products

15 copy-and-paste prompts to find out whether AI can actually find, understand and recommend what you sell, with a scorecard and a map from each failure to the layer responsible.

On this page

Ask ChatGPT for a product recommendation in your category and watch what comes back. It finds some products, names some merchants, and gets a detail wrong. The price is last month's. It says to check store availability rather than answering. Or your product is not in the answer at all.

None of that is a ranking problem. It is a retrieval problem, and unlike ranking it is measurable. The facts about your products either can or cannot be reached by the system assembling the answer, and the point where that breaks is specific enough to find in an afternoon.

This is the field test we run with clients. Fifteen prompts, a scorecard for what came back, and a map from each failure to the layer most likely responsible.

What's in the AI product catalogue retrieval test

On this page you get the five stages of retrieval, the five categories the test covers, and one example prompt from each. The full PDF has all fifteen and the diagnostic.

  • 15 copy-and-paste prompts across discovery, price and inventory, relationships, product knowledge and a deliberately difficult stress test
  • Five versions of that stress test, one each for multi-store retail, B2B and wholesale, parts and compatibility, multi-region, and programs and services
  • A scorecard covering discovery, attribute accuracy, variant accuracy, price, availability, fulfilment, relationships and source quality
  • A map from each failed prompt to the retrieval stage most likely responsible
  • Guidance on re-testing, because the before-and-after comparison is worth more than a single result

Get the PDF using the form on this page.

How do you rank in ChatGPT?

You do not rank in ChatGPT the way you rank in Google. There is no position to climb and no results page to move up. When someone asks for a product, the system assembles an answer from whatever it can find, understand and trust at that moment.

Three things decide whether you appear in it. It has to find the product in answer to a question that never mentions your brand. It has to understand the facts, which means typed attributes rather than adjectives buried in prose. And it has to trust the source, which means the price it quotes is the price you are charging today and the stock it promises is stock you actually have.

A page that looks complete to a person can still be invisible to retrieval. A person can read a specification table, click through to store availability, and combine three things on screen. A retrieval system reads what is exposed to it and nothing else.

Why can't AI find your products?

When AI misses something you sell, the failure almost always sits at one point along the path from a page a person can read to a source a machine can query. The stages run in order, and finding where yours stops is the whole diagnosis.

  • Human-visible. A customer can find the information by using the interface.
  • Crawlable. A retrieval system can reliably fetch it.
  • Structured. It exists as explicit commercial data rather than being inferred from prose.
  • Channel-ingested. It is supplied through a feed or data source the destination supports.
  • Integrated for retrieval. A live service or API is explicitly connected to the system answering the query.

Most teams are at the first stage and assume they are at the third. Store-level stock behind a find-in-store button, compatibility held in a PDF, and a specification table rendered by the CMS but never stored as fields are the three most common examples.

So the useful question is not why an AI did not rank you. It is whether the business can answer the question internally, and if so, where the retrieval path stops. Two or more failures at the same stage is a platform problem rather than a content problem.

How do you test whether AI can find your products?

Pick 5 to 10 representative products and include at least one difficult one, with multiple variants, local stock, accessories, compatibility rules or complex fulfilment. Use a clean or logged-out session. Then compare each answer against the commercial truth in your own systems.

The test covers five categories. One example from each is below, and the rest are in the PDF.

Discovery

Whether an AI can find your product at all when the customer never types your brand name.

I need a [product category] under [budget] for [specific use case]. What would you recommend and where can I buy it?

Check whether your product appears without the brand being named, which competitors appear instead, and which sources get cited.

Price, inventory and fulfilment

The facts that change. These are the answers most likely to be confidently wrong, because they were true when they were last published.

I'm in [suburb or postcode]. Where can I buy [product] in stock today?

Check whether it resolves store-level availability, or stops at a generic instruction to check store availability.

Relationships and compatibility

What works with what. Conversational shopping produces relational questions constantly, and most catalogues hold the answer in a PDF or a diagram.

I already own [model or product]. Which [part or accessory] is compatible with it?

Check whether the relationship is correct and supported by an authoritative source.

Product knowledge

The specifics a buyer asks before committing. This is where an answer sounds authoritative and is subtly wrong.

Does [product] support [technical requirement]? Give me the exact specification and source.

Check whether the answer is grounded in an explicit specification, manual or structured field.

The stress test

The most useful test in the guide. It forces identity, attributes, relationships, price, inventory, location and fulfilment to resolve in one answer, and the point where it breaks tells you which layer to fix.

I'm in [location]. I need [product category] under [budget], with [attribute], compatible with [existing product], available for pickup by [date]. What are my best options?

The PDF has five versions of this one, because the difficult query is not the same for a distributor, a franchise network and a membership organisation.

This is not a ranking test. A product missing from one answer does not prove your catalogue is broken. Treat it as a blind-spot diagnostic for discovery, structure, price, inventory, fulfilment and relationships, and run the same prompts again after you change something.

Who this test is for

  • Ecommerce and digital leads who need to know whether AI channels are reaching their catalogue before peak season
  • Merchandising and product data owners responsible for attributes, variants and feed quality
  • SEO and content teams extending their remit from pages to product data
  • Platform and architecture teams deciding where commercial truth should live

Your catalogue is becoming an interface

The goal is not to build a separate catalogue for ChatGPT, then another for Google, then another for whatever launches next. That recreates the problem every time an interface appears, and guarantees the versions drift apart.

Model the commercial truth once, covering identity, attributes, variants, price, availability, relationships and fulfilment, then make each retrieval channel an output of it.

The full research behind this test is in product feed optimization for AI shopping, which covers what OpenAI and Google currently ask merchants to structure. For the paid side of the same surface, see ChatGPT ads and eCommerce.

Back to all guides

AI product retrieval FAQ

You do not rank in ChatGPT the way you rank in Google. There is no position to climb and no results page to move up. When someone asks for a product, the system assembles an answer from whatever it can find, understand and trust at that moment.

Three things decide whether you appear. It has to find the product in answer to a question that never mentions your brand. It has to understand the facts, which means typed attributes rather than adjectives buried in prose. And it has to trust the source, which means the price it quotes is the price you are charging today and the stock it promises is stock you actually have.

Read the full answer →

AI Overviews are assembled from passages, not whole pages, so the unit that matters is the section rather than the document. A page can be cited for one heading and ignored for everything else on it.

The structure that works is direct. Put the question as the heading, answer it plainly in the first two sentences, and keep the section true when it is read on its own with no surrounding context. Supporting detail goes after the answer, never before it.

Read the full answer →

By being the cleanest authoritative source for a specific fact, not by publishing more. Assistants cite what they can extract without ambiguity and attribute with confidence.

In practice that means three things. State the fact explicitly rather than implying it. Keep each section true on its own, so it survives being lifted out of the page around it. And make the claim traceable to you as the merchant or manufacturer, because a system choosing between your page and a reseller's will favour the source it can attribute.

Read the full answer →

Run a fixed set of prompts on a schedule and record what changed between runs. The before-and-after comparison is the measurement. A single result on a single day tells you very little, because answers vary between sessions.

Track three things: whether you appear at all, whether the facts in the answer are correct, and which source was cited. Tools such as PromptWatch and Profound monitor citation share across prompts over time, and Search Console still records impressions where AI surfaces are involved.

Read the full answer →

Usually because the facts are visible to a person but not reachable by a machine. The failure sits at one point along a path, and identifying which point is the whole diagnosis.

The stages run in order. Human-visible, where a customer can find it by using the interface. Crawlable, where a retrieval system can fetch it. Structured, where it exists as explicit data rather than prose. Channel-ingested, where it is supplied through a feed the destination supports. And integrated for retrieval, where a live service is connected to the system answering the question.

Read the full answer →

SEO optimises a page for a position. AI search optimization optimises data for retrieval. The overlap is real, since both reward being crawlable, explicit and authoritative, but the objective has moved.

Three things change in practice. The unit drops from the page to the passage, and for commerce from the product page to the product data. The outcome changes from a visit to an answer, which means a correct citation with no click counts as success rather than failure. And freshness matters more, because an assistant quoting a stale price does you more damage than not appearing at all.

Read the full answer →

AI product retrieval is an AI system finding, understanding and answering questions about your products, pricing, availability, compatibility and fulfilment. It is worth separating from agentic commerce, where an AI opens a website, navigates it and takes actions on a customer's behalf.

Retrieval is the one affecting almost every merchant today, because it happens whether or not you have done anything about it. A shopper asks for a recommendation and the system assembles an answer. Your products are either in it with accurate facts, in it with wrong facts, or absent.

Read the full answer →

No. A channel-specific catalogue recreates the problem every time a new interface appears, and it guarantees the versions drift apart.

The stronger architecture is to model the commercial truth once, covering identity, attributes, variants, price, availability, relationships and fulfilment, then expose the appropriate version through your website, structured data, merchant feeds and supported AI integrations. Each channel becomes an output rather than a separate source.

Read the full answer →

Related guides

Enterprise AI agent implementation blueprint: deploy safely in production

Enterprise AI agent implementation blueprint: deploy safely in production

A practical blueprint for digital, platform, and governance leaders putting AI agents into production. Four phases, the controls that matter at each one, and the questions to...
Get Free Guide →
On this page