Before you debug the feed
Google Merchant Center Product Data Checklist
Merchant Center diagnostics are the final authority. This checklist helps you fix the underlying Shopify product record first so feed troubleshooting starts with cleaner, more consistent data.
What to remember
Keep feed values aligned with the landing page.
Use stable product IDs and accurate variant-level identifiers.
Treat structured data as confirmation, not a substitute for the feed.
Step 1
Verify the core offer data
Start with the values a shopping destination needs to identify the item and show an accurate offer.
Stable ID and product link
Each product or variant needs a stable identifier in the feed and a working landing-page URL. Avoid reusing an old ID for a different item.
Action: Compare the current feed ID and link with the Shopify product and variant record.
Title and description
Use factual, specific copy that describes the item. Include distinguishing attributes naturally and keep promotional phrases out of the product title.
Action: Check that the feed and landing page describe the same product and variant.
Price and availability
The feed, structured data, and visible landing page should agree on price, currency, availability, and the selected variant. Mismatches create avoidable diagnostics and buyer confusion.
Action: Open the landing page in a private window and compare it with the submitted values.
Primary image
Use a clear image of the actual product without placeholders or misleading overlays. Additional images should clarify angles, scale, variants, or use.
Action: Test the image URL and confirm that it matches the exact product or variant.
Step 2
Verify classification and identity
Accurate classification and identifiers help systems match the offer to the right product concept.
Product category and type
Set an accurate Shopify product category and keep custom product types consistent. Shopify notes that product data can be imported when channels sync with the store.
Action: Correct obvious category errors before troubleshooting downstream mappings.
Brand, GTIN, and MPN
Provide legitimate unique product identifiers when they exist. Do not guess or copy identifiers from similar products; follow Merchant Center guidance for products without assigned identifiers.
Action: Create a source column in your cleanup sheet for every identifier you change.
Variant attributes
Make color, size, material, pattern, age group, gender, or other relevant variant attributes explicit when they apply. Keep each variant's values internally consistent.
Action: Review the feed at the variant level and look for duplicated or contradictory rows.
Step 3
Confirm the landing page
The landing page should support the offer data and make the purchase conditions understandable.
Product and Offer structured data
Google supports Product and Offer structured data for merchant listing experiences. Recommended properties can add useful context, but eligibility does not guarantee display.
Action: Test a representative product URL with Google's Rich Results Test and review errors and warnings.
Shipping and returns
Keep shipping cost, timing, return window, and important conditions easy to find and consistent with what is configured in the destination.
Action: Follow each policy link from the product page and verify that it is current.
Destination diagnostics
A preflight score cannot replace Merchant Center. Review item-level diagnostics after the feed refreshes and use the exact issue details to confirm the result.
Action: Record the original diagnostic, the change made, and the status after reprocessing.
Frequently asked questions
Does passing this checklist mean Merchant Center will approve every product?
No. Merchant Center applies current data, destination, policy, and account requirements. The checklist reduces common product-record problems but cannot guarantee approval or placement.
Is structured data enough without a product feed?
Structured data can support Google merchant listing experiences and help confirm landing-page values, but it is not a universal replacement for a configured Merchant Center data source.
Where should I start when hundreds of products have warnings?
Start with a representative sample and group repeated issues by field and owner. Fix the highest-impact shared problem first, then confirm the destination reprocessed the change before scaling it.
Primary references
This guide summarizes practical checks and links to the destination documentation that should remain the authority when requirements change.
Check your Shopify sample
Run the read-only scan to turn repeated product-data gaps into an explainable worklist.
Install free on ShopifyFeedSnapshot AI provides directional product-data readiness checks. It does not guarantee Merchant Center approval, search rankings, AI mentions, traffic, or revenue.
Read another guide