How to validate a Google Shopping feed before submitting it

A useful validation workflow separates file parsing, attribute rules and live/account checks. Passing a CSV or XML parser alone does not mean Google will approve the offers.

Reviewed October 4, 2026 · Independent guidance · Static feed check with contextual limitations

What does this issue mean?

Start by confirming that the export is an actual Google product feed rather than a platform-native catalog dump. Then review required attributes, accepted values and identifier logic. Finally verify the website, shipping and account context that a standalone file checker cannot observe. Each layer catches a different class of failure.

Why this happens

Merchants often jump directly to individual disapproval messages while the source file has broken quoting, inconsistent headers or variant exports. Others trust a perfect health score without checking price matching or account eligibility. A repeatable workflow uses a known feed snapshot, stable IDs and a documented list of checks that were and were not performed.

How to diagnose and fix it

1. Validate encoding, delimiter or XML structure and confirm the parsed product count matches your expected offers.
2. Check IDs, titles, descriptions, links, images, availability and amount/currency syntax across every product.
3. Review conditional identifiers, variant grouping and shipping applicability with the appropriate source facts.
4. Inspect public pages and Merchant Center account diagnostics separately before relying on any static report.

Before and after example

The examples are illustrative. Replace them with verified information for your own offer; copying an example identifier, amount or URL would introduce incorrect data.

Before

Parser pass → assume approval

After review

Parser pass → static checks → contextual review → live/account checks

Feed Doctor evaluates all parsed products within its limits, but its score covers only implemented rules. It is independent of Google and does not replace Merchant Center’s own processing or policy review.

Shopify fix

Find the affected product and exact variant in your Shopify catalog, then identify which product field or Google & YouTube channel setting supplies feed. If a separate feed app generates your export, inspect its mapping instead of assuming the channel settings control that file. Change verified source data, save it, and obtain a fresh export.

Compare one affected variant and one previously correct offer before making a bulk change. Do not change stable IDs just to improve a report score. If the issue involves identifiers, verify whether the connector reads barcode, brand or manufacturer reference data. If it concerns a live page or shipping account setting, a feed-column edit alone may not resolve it.

WooCommerce fix

Open the relevant product or variation and inspect the attribute consumed by your Google feed integration. Google for WooCommerce can map product attributes into feed attributes; third-party feed generators may use different mappings. Check both the stored value and the exported result, especially when parent attributes are inherited by variations.

Update the source value or mapping deliberately and regenerate the feed. Keep product identity, currency and variant relationships consistent. Avoid editing only a downloaded snapshot if a scheduled exporter will replace that change. For an account or website issue, repair the effective configuration and public offer as well as reviewing the file.

Verify the repair before submitting

Keep the original feed as a backup and compare the same affected product IDs in the regenerated file. Confirm that the expected product count remains unchanged and that no unrelated fields disappeared. If you applied a bulk rule, inspect offers outside the original affected set as a control; an overly broad mapping can fix one problem while creating another.

Run a new static scan, then separately check live product information and your Merchant Center diagnostics. File format validation cannot determine every policy, account, image or website condition. Processing and recrawling take place in Google’s systems, so a corrected file is not an immediate promise of approval. Use the actual updated diagnostics to decide whether additional investigation is required.

Frequently asked questions

Related feed issues

• How to fix invalid GTIN format and check digits
• How to fix duplicate product IDs in a Google feed
• How to investigate price mismatch in Merchant Center

Official references: Google product data specification, Shopify Google & YouTube requirements, WooCommerce attribute mapping. Requirements can vary by product, country and account setup.