Google Merchant Center Setup for AI Mode Shopping

Google AI Mode combines answers with links and shopping information. Google Search Central says a supporting page must be indexed and eligible to appear in Search with a snippet. Those Search fundamentals are the full technical requirement for those links.

For product information, Merchant Center feeds and Product structured data help Google understand what you sell. A supporting web link qualifies on Search eligibility alone. Shopping listings have their own data and policy requirements.

When diagnostics reveal mismatched product information, Paz traces it to the source through the product feeds service.

Google says free listings are turned on by default in most cases. An administrator can view or change the status on the Free listings page in Merchant Center.

1. Check the Free listings status in your account.
2. Review product issues, shipping settings and return policies.
3. Correct the applicable data and policy issues, then check the destination response.

Permission and eligibility make a product available for display, and appearance depends on the question. Paid Shopping campaigns and organic supporting web links have separate requirements.

Core product data

Check id, title, description, link, image_link, availability and price against the current product data specification. Use accurate product descriptions and images that meet the applicable format and size requirements.

Conditional and category attributes

Requirements for condition, brand, identifiers, variant attributes and shipping depend on the product, destination and target country. Check which of color, size, age group and gender your category requires.

Use assigned identifiers

Submit a correct manufacturer-assigned GTIN when available. Where the GTIN is unassigned, provide brand and MPN when applicable. Set identifier_exists to false only for products that genuinely lack assigned unique product identifiers under Google's identifier rules.

Add Schema.org Product structured data to every product detail page. Google can use this markup for merchant listing experiences. Validate it against the merchant listing documentation.

Product and Offer properties to check

• name
• description
• image
• offers.price
• offers.priceCurrency
• offers.availability

Recommended additions

• brand
• gtin / mpn / sku
• aggregateRating (with ratingValue and reviewCount)
• review (sample reviews where available)
• category
• color, size, material when applicable

The consistency rule

Mismatches between the page and Merchant Center data, such as price or availability, can cause product issues or disapprovals. The two sources should pull from the same source of truth in your catalog. Audit periodically - drift happens when product detail pages and feeds are managed by different teams.

Keep product data current

Use supported Merchant API updates, a platform connection or scheduled data-source updates to reflect price and availability changes. Choose the update method for your catalog and account, then check for mismatches after updates.

UCP checkout is separate

Google's UCP documentation describes checkout integration and merchant onboarding. Availability and integration requirements need separate assessment, and agentic checkout has its own onboarding on top of a clean feed.

Paz handles product-data and feed corrections within agreed scope, checks destination responses and follows up on remaining issues. Checkout integration is separate from this feed work.