April 17, 20266 min read

Merchant Center, Product Markup, and Shipping for AI Search: How to Keep Price, Availability, and Returns Aligned

A practical guide to Google merchant listing/Product markup, Merchant Center, shipping policy, and return policy setup for AI search. Focus on price, availability, shipping, returns, and alignment between structured data and visible content.

Vladislav Puchkov

Founder of GEO Scout, GEO optimization expert

If you want to see whether cleaner commerce data is changing which product URLs AI systems rely on, GEO Scout helps track prompt-level mentions, cited sources, and competitive shifts across commercial queries.

Teams often ask how to “optimize for Google AI” on product pages. The official Google docs point to a more practical answer: make the offer unambiguous.

In AI features and your website, Google says AI Overviews and AI Mode do not require extra technical rules or special markup. Instead, Google recommends keeping important content available in text, making structured data match visible content, and keeping Merchant Center up to date.

For ecommerce, that means AI search is not a separate markup project. It is a data-consistency project.

Where Product markup belongs

In Google’s merchant listing structured data documentation, merchant listing markup is meant for pages where a shopper can purchase a product. Google also says product rich results support pages focused on a single product or its variants, not category pages.

That means Product markup belongs on:

• a product detail page
• a variant URL when the variant changes the offer materially
• a page with a visible, purchasable offer

It does not belong on:

• a category grid
• a “best products” page
• a page that only links out to other sellers

If Google cannot tell what exact offer is attached to the URL, the page is less useful for merchant listings and less reliable for AI answers.

The signals that cannot drift

1. Price

On the Mismatched product price help page, Google explains that Googlebot compares the price in Merchant Center with the landing page and, when present, with structured data. Google also notes that the price in the HTML should exactly match the price uploaded in Merchant Center.

In practice:

• show the live selling price in HTML
• keep Offer.price and Offer.priceCurrency aligned with the visible page
• update the page and Merchant Center on the same cadence
• avoid price logic that appears only after JavaScript, login, or region popups

2. Availability

Google’s Mismatched product availability guidance is equally strict: the value in product data should match the landing page.

That means:

• stock state should be visible near the buy box
• Offer.availability should reflect the real status
• selected variants should expose their own stock state
• “in stock” should never survive after the product is effectively unavailable

3. Shipping

Google’s merchant shipping policy documentation recommends putting your standard shipping policy on a dedicated page using ShippingService under Organization. If a specific product has different shipping terms, use OfferShippingDetails under the product’s Offer.

For most stores, the clean pattern is:

• one sitewide shipping policy page
• a short shipping summary on the product page
• product-level shipping markup only for exceptions

The visible product page should still answer the real buyer questions: shipping cost, destination, delivery timing, and any oversized or special-case restrictions.

4. Returns

Google’s merchant return policy documentation follows the same logic. Standard returns belong on a dedicated page under Organization. Product-level return policy data under Offer is for products that differ from the default rule.

On the product page, do not rely on a vague badge like “easy returns.” State the actual terms:

• return window
• return fee or free return
• return method
• exclusions, if any

Structured data must match the visible page

Google’s AI-features guide says structured data should match the visible text on the page. Google’s general structured data guidelines also say not to mark up content that users cannot see. Merchant Center’s Unclear value on your website diagnostic points to the same problem when price, availability, or condition cannot be verified clearly from the landing page.

In practice, that means:

• do not mark up free shipping if the page does not clearly show the rule
• do not mark up a 30-day return window if the page never states it
• do not mark up InStock when the selected variant is on backorder
• do not hide key values inside images or icons without text labels

For Google AI, there is no second version of your product facts. There is only the version Google can verify.

Merchant Center is part of the trust layer

Google’s structured data guidance for Merchant Center explains that on-site structured data can help Google retrieve up-to-date product data and support automatic item updates. That is useful, but it does not replace a clean landing page.

The strongest setup is:

1. A product page with visible price, stock, shipping summary, and return summary.
2. Product and Offer markup describing the same offer.
3. Dedicated shipping and return policy pages under Organization markup.
4. Merchant Center data that updates in sync with the site.

Pre-publish checklist

• Product markup is on a real purchasable product page
• Price matches in HTML, structured data, and Merchant Center
• Availability matches in HTML, structured data, and Merchant Center
• Shipping and return terms are visible to users
• Sitewide policies live on dedicated pages
• Product-level shipping or return markup is used only for true exceptions
• Important values are in text, not just in JavaScript states or images
• Rich Results Test and URL Inspection show the page correctly

For page structure, pair this with How to Optimize Product Pages for AI Answers and FAQ and Schema.org for Getting Into AI Responses.