A useful Shopping feed describes the product the buyer can actually purchase. Start with one item ID and trace its title, variant, price, availability, image and destination through the source data, Merchant Center and live page. Fix mismatches before treating a new title formula as the solution to poor performance.
A fictional color mismatch
Imagine a navy travel bag advertised with a tan image. The landing page opens on the default tan variant while the feed says navy is available. A buyer now has to work out which item the ad represents.
The correction is more than changing the photograph. Check the stable item ID, variant attributes, image, availability and link that selects the intended option. Confirm the cart keeps that option and shows the correct price. Otherwise one part of the mismatch may remain.
This is a fictional diagnostic example, not a report of a Merchant Center decision. A corrected submission still needs provider processing and eligibility readback. A successful file upload is not product approval.
Use the current specification as the checklist
Google’s product data specification explains the required and conditional attributes and the consequences of incorrect or conflicting data. Check the requirements for the actual product, country and destination. Do not invent a GTIN or use a competitor’s identifier to satisfy a field.
Record the product identifier, variant group, relevant size or color, price, availability, image URL and landing URL. Include the applicable shipping and return settings. Read the issue details for the exact item instead of applying a generic fix to the entire catalog.
Describe what is sold in natural language. A title can include verified type and attributes without unsupported performance claims or a string of search modifiers. A useful title should still make sense to someone looking at the product.
Follow the correction through every stage
Keep a row for source value, submitted value, provider-processed value and live-page value. A scheduled feed job can overwrite a manual correction, so identify the authoritative source before editing.
After the update, read the current product status and issue details in Merchant Center. Check the public page again with the relevant option selected. Confirm that mobile controls, stock messaging and cart behavior agree with the feed.
Do not assume an automated update fixes every discrepancy. Keep the exact item, update time and provider status in the receipt. Approval can change and does not prove impressions, clicks or sales.
Prioritize with economics and customer impact
Start with misleading data and blocked items, then prioritize products that matter to the business. Keep margin, stock and fulfillment capacity visible. A product with high click volume but poor contribution may deserve a different decision from a product with little traffic and a correctable data error.
Use labels and campaign groupings only when their definitions are dependable. A “high margin” label that ignores fulfillment or returns can mislead the budget decision it was meant to support.
Your next step is one complete item trace. Save the issue, correction, provider readback and live-page result in a worksheet before expanding the fix. Use the measurement guide to assess commercial results separately.
Editorial revision, October 20, 2026: unsupported impression-share targets, obsolete bidding instructions and universal campaign thresholds have been removed. The bag example is fictional and no approval or performance outcome is promised.