Google Shopping Feed Errors: A Practical Diagnostic Workflow
A rejected product and a malformed spreadsheet are different problems. Start by finding out whether your source file can be read, whether its values are usable, and whether the remaining problem depends on the store or Merchant Center account.
1. Separate a file error from an account decision
FeedDoctor reads CSV and XLSX product feeds. A damaged workbook, an empty upload or ambiguous duplicate headers prevents a reliable analysis. Export a fresh values-only copy before changing product information. If the file opens successfully, the report contains row-level errors, review warnings and optional improvements. These labels describe the file checks; they do not reproduce every Merchant Center account diagnostic.
Keep the exact Merchant Center issue message beside your FeedDoctor report. An account suspension, shipping configuration problem or policy decision needs a different investigation from a missing title. A clean file cannot establish compliance with every country, category or destination requirement.
2. Work through a concrete example
| Input | Finding | Next action |
|---|---|---|
| Two rows both use SKU-001 | Duplicate ID error | Check whether they are duplicate records or distinct variants. Assign genuine stable IDs manually. |
| title is blank | Missing value error | Recover the product title from your source catalog. |
| availability is In stock | Unsupported spelling with a safe proposal | Preview in_stock and confirm it represents the same actual stock state. |
| price is 1,234 USD | Ambiguous price | Check the actual amount. The tool does not choose between a decimal and a grouping separator. |
3. Diagnose prices without changing their meaning
The tool checks that a supplied amount has an explicit recognized currency. An input such as 19,95 usd has an unambiguous formatting proposal in this validator. A value such as $19.95 does not tell the tool which dollar currency you intend, so it needs manual attention. Review the product page and checkout as well; FeedDoctor does not visit either page.
Download the original file before working outside the browser. The original upload and corrected export are separate files. If a spreadsheet editor has already removed leading zeroes from a barcode, neither a checksum test nor a formatting change can reconstruct the lost digits reliably.
4. Treat identifier warnings as questions
A GTIN check can detect a length or check-digit problem. It cannot establish that the identifier was assigned to your product. Missing brand and GTIN information is therefore presented with context rather than filled with invented values. Consult packaging, manufacturer data and the applicable exceptions. Do not mark identifier_exists as false merely to remove a warning.
5. Build a repeatable resolution list
- Filter errors first and search by product ID or field.
- Resolve missing factual information in the source system.
- Review safe proposals individually before applying them.
- Download the CSV or XLSX diagnostic report, including suggested solutions and applied status.
- Re-analyze the revised feed and compare current issues with resolved findings.
- Submit through your actual Merchant Center data source and review its own feedback.
If many rows share one problem, check the export mapping before editing each row. A missing price column can affect every product, even when the product IDs are present. Header-level errors therefore count all product rows as affected in FeedDoctor's summary.
References and next steps
These instructions describe the current FeedDoctor implementation. Check the official requirements for your product, target country and destination before submitting data.