Yes, product feeds can affect whether AI shopping assistants show your products, but only on platforms that actually take feed data. OpenAI and Microsoft both document merchant feeds as an input for their AI shopping experiences. Google accepts feeds and on-page structured data side by side. No platform in our source set says a feed alone guarantees a recommendation.
This guide covers the feed and data layer only: price, availability, identifiers and attributes. Page copy is a separate input. We cover it in our guides to het optimaliseren van productpagina’s voor AI-winkelassistenten en category page optimization.
Do AI shopping assistants use feeds, pages, or both?
It depends on the platform. There is no single answer that covers every assistant, so look at what each one documents.
ChatGPT: a merchant feed
OpenAI’s commerce documentation describes a feed that merchants share so ChatGPT can surface their products in search and shopping experiences. According to OpenAI’s key concepts guide, merchants provide a secure, regularly refreshed feed in CSV or JSON. It contains identifiers, descriptions, pricing, inventory, media and fulfillment options. Integration starts with a sample feed for validation, followed by daily snapshots.
Google: structured data, Merchant Center, or both
Google Search Central says you can provide product data through structured data on your pages, through Merchant Center feeds, or both. Google states that supplying both increases your eligibility for its experiences and helps it understand and verify your data. Some experiences combine the two. Product snippets, for example, may use pricing from your feed when it is missing from the page’s structured data.
Note the scope. That documentation is about Google Search and the Shopping tab. Our source set does not confirm how Gemini uses Merchant Center data, so treat any claim about that link as unverified.
Microsoft Copilot: Microsoft Merchant Center
Microsoft describes “trusted product truth” as the foundation of agentic commerce. On its agentic commerce page, the first step it lists for product visibility in Copilot is a UCP-ready feed in Microsoft Merchant Center. Microsoft says Merchant Center will support the Universal Commerce Protocol, with richer signals such as return and support policies so AI can assess products with confidence.
| Platform | Documented product data input | Scope of the documentation |
|---|---|---|
| ChatGPT (OpenAI) | Merchant feed in CSV or JSON, refreshed with daily snapshots | ChatGPT search and shopping experiences |
| Product structured data, Merchant Center feed, or both | Google Search and Shopping tab; not confirmed for Gemini in our sources | |
| Microsoft Copilot | UCP-ready feed in Microsoft Merchant Center | Copilot shopping and Copilot Checkout; UCP support announced as upcoming |
Which feed attributes matter most in a comparison?
No platform in our source set publishes a universal ranking of attributes. What the documentation does give you is a split between fields that are required and fields that are recommended for better visibility.
Start with the basics: price and availability
The platforms describe these basics differently. Google’s Merchant Center specification lists price as a required attribute. OpenAI says its required fields ensure correct display of price and availability. Neither statement makes both fields universally required on every platform. As a practical step, check that price and availability are correct in your feed before you work on anything else, because a comparison can only show the facts you supply.
Recommended signals that support ranking
OpenAI states that recommended attributes such as rich media, reviews and performance signals “improve ranking, relevance, and user trust.” That is the clearest statement in our sources that optional fields can change how a product is surfaced. If you want the review side explained further, read hoe klantbeoordelingen de productaanbevelingen van AI beïnvloeden.
Trust and checkout signals
Microsoft lists return policy and customer support as store settings, and names extra feed attributes for UCP: native checkout eligibility, product warnings where needed, and a unique Merchant Item ID. These describe whether a product can be bought and supported, not only what it costs.
A practical way to prioritise, as advice rather than a measured ranking:
- Unique identifiers on every item, so products are not confused with each other.
- Price and currency, matching your site and checkout.
- Availability and inventory, refreshed as often as the platform expects.
- Fulfillment, returns and support details.
- Rich media and reviews, where the platform accepts them.
Does feed data need to match your pages exactly?
For price, Google is explicit. The Merchant Center product data specification asks you to submit the correct price and currency and to match it with your landing page, structured data and checkout. Any customer must be able to buy the product online for the submitted price without joining a membership program, free or paid.
Our sources do not spell out how each AI assistant treats a mismatch, so we won’t claim a specific penalty. The direction is clear, though. Google says feed plus structured data helps it verify your data, and Microsoft frames the whole system around trusted product truth. A feed that contradicts your page gives a system two answers to the same question.
Matching does not mean your feed description must copy your page word for word. The documented requirement is about facts: price, currency, purchasability. Treat stock, shipping and return terms the same way, as advice.
A feed audit you can run this week
- Pick ten products you most want recommended and compare feed price, page price, structured data price and checkout price.
- Check that each item has a unique identifier and that variants are not merged.
- Confirm how often your feed refreshes, and whether that keeps pace with stock changes.
- List which recommended fields you leave empty, such as media, reviews or return details.
- Review which merchant programs you are in: Google Merchant Center, Microsoft Merchant Center, or OpenAI’s commerce program.
- Check your product structured data against the visible page, using our handleiding voor gestructureerde gegevens.
As a practical starting point, check price and availability gaps first. Google lists price as required, and OpenAI ties its required fields to correct display of price and availability.
Where the feed stops and content takes over
A clean feed gets your facts into the system. It does not explain why your product suits a specific buyer. That reasoning lives in your pages, buying guides and the wider authority your brand builds across Google and AI chatbots. Our guide on hoe je producten kunt krijgen die door ChatGPT en Gemini worden aanbevolen shows how those layers fit together.
Feeds are work for your platform or developer. The content layer around them is steady, repeatable publishing. If you would rather have that authority built for you without hiring an SEO team, hoe de AI-motor voor organische groei van Authora werkt and claim your product positions before a competitor does.