Google AI Mode shopping prices: compare offers, not just products
A Productrise study finds different shopping prices and sellers. Use our offer-comparison worksheet to separate real price gaps from mismatched products.
A September 1 Productrise study found different prices and sellers for products appearing in both Google AI Mode and traditional shopping results. Before treating that as a price penalty, retailers need to check whether the two results represent the same offer, not just the same product.
What the shopping study measured
Productrise’s study covered August 9–31, 2026, using more than two million listings from over 100,000 search results and AI Mode responses in the US and UK. It matched Google product IDs for the same query and day, then compared first-listed offers. Traditional search sampling used the Popular products carousel; AI Mode sampling included tracked product cards.
Among matched products, the first seller differed in 49.6% of cases and the price differed in 38.1%. Within the price-different subset, AI Mode was higher 68.4% of the time. Productrise reported a 21.6% average premium across matched pairs, but condition differences and outliers complicate that average.
This is a commercial tracking vendor’s observational sample, not a random sample of all shopping searches. It does not establish purchases, clicks, or Google’s ranking mechanism. SearchEngineAnswer has not independently reproduced the dataset.
Product identity is only the first check
Consider a hypothetical kettle with the same model number in two results. One leads to a used unit for $80; the other leads to a new unit for $100. The displayed difference is 25%, calculated against $80. Calling it a 25% markup on an equivalent offer would hide the condition difference.
Now consider two new units at $100 and $105. If the first seller charges $15 shipping and the second includes delivery, the displayed item-price comparison and the delivered-price comparison point in opposite directions. These are illustrative arithmetic examples, not observations from Google’s results.
For a retailer, those distinctions determine the next action. A wrong condition deserves a data correction. A valid competing offer deserves a commercial review. Neither justifies changing every product price because of an aggregate headline.
Classify the discrepancy before escalating it
| Finding | Comparison status | Next check |
|---|---|---|
| Same model, used versus new | Not equivalent | Condition and landing-page accuracy |
| Same variant, different delivery fees | Item prices only | Delivered total for one destination |
| Different bundle or pack size | Not equivalent | Units, accessories, and variant identifiers |
| Equivalent offer, same currency and time | Eligible comparison | Seller selection and repeated observations |
Build a small, reviewable offer record
Start with products for which your team can verify stock, variants, and delivery terms. Record the exact query, country, time, surface, product identifier, seller, condition, currency, displayed price, and destination URL. Open the destination and record whether the advertised variant is actually available.
Save both result captures together. Mark shipping or tax as unknown when it cannot be verified without an address or checkout. Do not fill unknown fields with zero. A zero shipping charge is a claim about the offer; a blank field is a limit of the observation.
Download the offer-comparison worksheet (CSV). Its example pairs are explicitly labeled EXAMPLE-REMOVE. Replace them with dated observations. The worksheet separates item-price differences from delivered totals and includes a reason to reject an invalid match.
Separate visibility from the checkout outcome
Repeat the same product-query pairs before deciding that a seller change is persistent. Count comparable pairs separately from all captured pairs. If ten of twenty captured pairs have unresolved variant or delivery differences, your equivalent-offer analysis has ten observations, not twenty.
Track product presence, seller presence, displayed price, landing-page consistency, and attributed orders separately. A screenshot can establish what appeared at that moment. It cannot tell you which seller the shopper ultimately chose.
Our Google AI Mode checkout explainer covers a later part of that journey. The visibility and referral-traffic framework explains why appearances should not be reported as visits or sales.
What to change now
Use the worksheet to create an exception list: wrong condition, wrong variant, stale price, unavailable offer, incomplete delivery information, or a valid alternative seller. Assign each exception to the person who can resolve it. Preserve a before-and-after capture when a correction is made.
The useful conclusion is narrower than “AI Mode prefers expensive products.” Retailers now have a reason to inspect which offer represents their product on each surface. Our contribution is that offer-level review process; it is not a new measurement of Google’s behavior.
Keep learning
Continue this topic
Next in this topic
Microsoft’s holiday AI shopping survey measures plans, not purchases
Earlier in this topic
DOJ Backs OpenAI in The New York Times AI Copyright Case
AEO & AI Search
Ask a question or join the discussion