When the AI Assistant Recommends Your Competitor: The Feed Fields That Decide It

A shopper asks an AI assistant for a waterproof hiking boot under $150, and it recommends your competitor's boot. Your boot is waterproof, it costs $140, and it is in stock. The assistant did not read your store. It read your feed, and your feed did not say waterproof.

The assistant reads the feed, not the store

AI shopping assistants, the chatbots and answer engines that now sit between the shopper and the store, do not browse your site the way a person does. They read structured data: the product feed you send to Google Merchant Center, and the Schema.org Product markup on your pages. The feed is the structured source, and it is the one the assistant trusts, because it is standardized, validated, and machine-readable. Your product page is the second source, and when the two disagree, the feed wins.

The fields that decide the recommendation are specific. A structured title that names the product and its key attribute. A complete description that states the material, the fit, and the use case. An accurate price and availability, because an assistant will not recommend a product it cannot confirm is in stock. A product type that places the item in the right category. And a GTIN or MPN where one exists, because the identifier is what lets the assistant match the product across surfaces and confirm it is the same item. A feed that is missing those fields does not get ranked lower. It gets skipped, because the assistant cannot describe a product it cannot identify.

The failure is silent. There is no error, no warning, and no report that says your product was skipped. The assistant recommends the competitor, the shopper buys, and the store sees a conversion it never had. The structured data post covers the page side of this: the fields the markup carries, and the ones it drops. The feed side is the same problem with higher stakes, because the feed is the source the assistant reads first, and the page is the source it reads to confirm.

The three fields that lose the sale

First, the title. A title that says Hiking Boot, Men's, Size 10 tells the assistant nothing about waterproofing, and the assistant will not guess. A title that says Waterproof Hiking Boot, Men's, Size 10 tells it everything. The title is the field the assistant quotes, and the shopper reads, so the attribute that decides the purchase has to be in the title, not buried in the third paragraph of the description.

Second, the description. An AI-generated description that invents a feature is a feed problem, not a chatbot problem: the description field in the feed is the source, and the assistant repeats what the feed says. The AI images post is the same lesson about a different field: the generated asset is only as accurate as the data behind it, and the data behind it is the feed. A description that says waterproof when the product is water-resistant will produce a return, and the return will be yours, because the assistant quoted your feed.

Third, the identifier. A product without a GTIN or MPN is a product the assistant cannot match across surfaces, and it will prefer the product it can match, because the match is what lets it confirm price, availability, and reviews. The identifier is not bureaucracy. It is the key that lets the assistant trust the product, and a feed without it is a feed the assistant treats as unverified.

The audit that takes an afternoon

Export the feed and read it as the assistant does. For the ten products that matter most, check the title, the description, the price, the availability, the product type, and the identifier. Ask the question a shopper would ask, waterproof, under $150, in stock, and see whether the feed answers it. If the feed does not answer it, the assistant cannot answer it either, and the competitor whose feed does answer it gets the recommendation.

Then fix the feed before the page. The feed is the structured source, and it is the one the assistant trusts. A corrected page with an uncorrected feed leaves the assistant reading the wrong data, and the wrong recommendation follows. The AI crawler post is the companion check: the crawlers that read the feed are the same ones that build the assistant's index, and the feed they read is the feed you sent, not the page you designed.

Frequently asked questions

Which feed fields does an AI shopping assistant actually use?

The fields the assistant uses to decide: a structured title, a complete description, an accurate price and availability, a product type, and a GTIN or MPN where one exists. A feed that is missing those fields does not get ranked lower. It gets skipped, because the assistant cannot describe a product it cannot identify.

Does the assistant read my product pages or my feed?

Google Merchant Center is the feed most AI shopping surfaces read first, because it is structured, standardized, and already validated. Schema.org Product markup on the page is the second source, and the two should agree. When they disagree, the feed wins, because it is the one the platform trusts.

Can an AI assistant invent a feature my product does not have?

It can, and it does, through the same mechanism. An AI description that invents a feature is a feed problem: the description field in the feed is the source, and the assistant repeats what the feed says. If the feed description is wrong, the assistant will be wrong, and the return will be yours.

Should I fix the product page or the feed first?

Fix the feed first, then the page. The feed is the structured source, and it is the one the assistant trusts. A corrected page with an uncorrected feed leaves the assistant reading the wrong data, and the wrong recommendation follows.