The checklist
1. Let OpenAI's search crawler in
OpenAI documents OAI-SearchBot as the crawler "used to surface websites in search results in ChatGPT's search features". If it cannot fetch your product pages, ChatGPT cannot read them directly.
- Check
robots.txt for a rule that blocks OAI-SearchBot, or a broad rule under User-agent: * that blocks product paths. - Check your CDN or host's bot protection. Store platforms and security services sometimes challenge unknown bots, which silently drops crawler requests.
- Remember GPTBot is a separate crawler for model training. Blocking it does not block search, and allowing it does not help search.
OpenAI says a robots.txt change can take about 24 hours to take effect.
The frame at the top is that check on our own site, which sells software, not products: in the 30 days to 2026-10-04, OAI-SearchBot was seen on all 30 of our most-fetched pages, and /pricing was fetched by all three OpenAI agents. Run the same check on your product and category pages; the crawler log shows it, robots.txt alone does not.
2. Make product pages readable without JavaScript
Crawlers fetch HTML. If your product title, price, description and availability only appear after scripts run, a crawler may see an empty shell. Most hosted store platforms render product pages on the server, but themes and apps can move content into scripts. Fetch a product page with a plain HTTP client and check the important text is there.
3. Keep product data consistent everywhere
ChatGPT uses structured data from third-party providers. That means your price, availability and description live in several places you do not fully control: marketplaces, comparison and price sites, feeds you syndicate. When they disagree, the engine has to pick one.
- Add Product structured data to your product pages with name, price, currency, availability, brand and an identifier such as GTIN where you have one.
- Make the visible price and the structured price identical.
- Audit the listings you syndicate to, and fix stale ones first for your best sellers.
4. Write product copy that matches how shoppers ask
Shoppers describe needs, not product names. "For flat feet", "for a small kitchen", "for beginners", "quiet". If your description lists specifications but never says who the product is for, there is nothing for a needs-based question to match.
For each important product, the description should state in plain sentences: who it is for, the problem it solves, what makes it different from the obvious alternative, and the facts a shopper would check (size, material, compatibility, care). One clear paragraph beats a wall of bullet points.
5. Earn reviews and mentions where ChatGPT reads
OpenAI names reviews and third-party content as inputs. For product questions, the third-party pages that decide answers are usually review sites, buying guides, roundups, forums and videos. The work here is the same as classic PR, aimed at the pages that already appear in answers:
- Ask customers for reviews on the platforms your category uses.
- Send products to the editors of buying guides that ChatGPT cites for your category.
- Answer real questions in communities where your products are discussed, openly as the brand.
6. Consider OpenAI's merchant programme
OpenAI runs a merchant programme through which approved merchants can share a product feed directly. If you sell at scale, apply. It does not replace the steps above, because product selection still depends on relevance and third-party content.
7. Keep collection and category pages useful
Collections such as "running shoes for flat feet" are pages that match shopper questions directly. A collection with an introduction that explains who it is for, and how to choose within it, is a strong candidate for both Google and ChatGPT. A collection that is only a grid of thumbnails gives an engine nothing to quote.