This guide distinguishes documented platform guidance from practical observations. AI and search platforms can change, and no placement or recommendation is guaranteed.
Start with one source of product truth
Product visibility begins with accurate facts. A product name, brand, identifier, price, availability, shipping policy, return policy, and variant details should agree across the visible product page, structured data, Merchant Center feed, and checkout wherever those systems are used.
For Google, page-level structured data and Merchant Center feeds are complementary. Google says using both can maximize eligibility for product experiences, but neither guarantees a product will appear in an AI answer or shopping result.
- Use the real product name, brand, model, and identifiers
- Match price, currency, condition, and availability everywhere
- Describe shipping costs, delivery timing, and return rules accurately
- Give each size, color, material, or configuration the right variant information
- Correct stale feed or page data before adding more marketing copy
Make every important product page reachable
A product cannot be retrieved if the page is blocked, broken, hidden behind a script-only path, or missing from the site's internal navigation. Important product pages should return a successful response, use a consistent canonical URL, appear in the sitemap, and be linked with ordinary HTML links from relevant category pages.
OpenAI documents OAI-SearchBot as the crawler used for ChatGPT search discovery. Its controls are independent from GPTBot, which is used for model training. If ChatGPT search visibility matters to the store, do not accidentally block OAI-SearchBot.
- Use descriptive links from categories, collections, and related products
- Keep canonical URLs, sitemap URLs, and internal links consistent
- Give important variants stable, identifiable URLs when buyers need to reach them directly
- Avoid indexing empty filters or unlimited combinations of faceted URLs
- Check robots rules and crawler access after platform or theme changes
Give buyers the information that decides the purchase
A thin catalog description may identify the item without answering the buyer's real question. Add the specifications, use cases, fit, compatibility, limitations, care instructions, comparisons, and evidence a person needs to choose confidently.
Write for the decision, not for keyword count. A page for a massage chair, for example, should explain body-size fit, room dimensions, feature tradeoffs, warranty, delivery constraints, and who may prefer another model. Avoid unsupported superlatives and repetitive AI-generated filler.
- Who the product is best for and who it is not for
- Dimensions, materials, compatibility, and other decisive specifications
- Meaningful differences between nearby models or options
- Real policies, warranties, testing methods, and limitations
- Original photos, demonstrations, reviews, or questions when available
Use Product and Offer structured data accurately
Product and Offer structured data can help Google understand details such as price, currency, availability, condition, shipping, and returns. The markup must describe the product shown on the page and match the visible information.
Google recommends putting product structured data in the initial HTML when possible, especially for fast-changing price and availability information. Validate the result with Google's Rich Results Test and monitor merchant listing reports in Search Console. Eligibility is not a guarantee of display.
- Mark up the correct product and offer rather than a category page
- Keep structured price and availability synchronized with the page
- Include identifiers and variants only when they are accurate
- Do not use markup to make claims the customer cannot see
- Revalidate after theme, app, or feed changes
Handle variants, filters, and category pages deliberately
Ecommerce sites often create many URLs for the same or nearly identical inventory. Decide which product variants deserve their own indexable URL and keep that decision consistent across navigation, canonicals, and sitemaps.
Category pages should help buyers compare real choices. Keep useful categories internally linked and populated with available products. Avoid creating indexable pages for empty filters, arbitrary sort orders, or combinations that offer no distinct value.
- Use a stable URL structure that people and crawlers can follow
- Make the selected variant clear on the page
- Use self-referencing canonicals on genuinely distinct indexable pages
- Point removed products to the closest useful destination only when it is a true replacement
- Keep out-of-stock information honest and explain whether the item may return
Measure visibility and revenue together
Use Search Console to monitor product rich-result and merchant-listing issues, then connect organic and AI-referred visits to the exact product or category page. Separately test a stable set of non-branded buying questions and record products mentioned, competitors shown, citations used, and the date of each check.
One favorable answer is not a trend. Repeat the same method, compare changes after meaningful page or feed updates, and prioritize the gaps connected to real inventory and profitable customer needs.
- Technical eligibility and structured-data errors
- Product and category landing-page traffic
- AI citations, mentions, and competitor appearances
- Add-to-cart, checkout, and purchase outcomes
- Changes made between comparable measurement periods
Frequently asked questions
Does Product schema guarantee an AI citation?
No. Accurate Product and Offer structured data can help Google understand a product and make the page eligible for supported product experiences, but it does not guarantee a citation, ranking, or AI mention.
Should an ecommerce site allow OAI-SearchBot?
If the store wants its public pages to be eligible for ChatGPT search discovery, OpenAI says OAI-SearchBot should not be blocked. This setting is separate from GPTBot, which relates to model training.
Is a Merchant Center feed enough by itself?
No. Google recommends accurate product data on the website and says structured data and Merchant Center feeds can work together. The landing page, feed, structured data, and checkout details should stay consistent.