Free · without registration
Checking product feed for specific data errors
Check your product feed before importing it to the Merchant Center. The evaluation indicates missing information, invalid values and duplicate IDs directly on the affected product.
Insert product data or select file
Feed Diagnosis by Product
- Products
- –
- Data errors
- –
- Products with errors
- –
The test covers selected data rules. Account settings, target market, shipping, tax, policies, image quality and compliance with your product pages must be checked separately. No proof of release for the Merchant Center.
Finding product defects before the feed import
A feed can be technically readable and still contain conflicting product data. Missing IDs, duplicate products or a misspelled availability feature can often be corrected directly in the export logic. Download the find list as CSV and assign the errors based on product ID and row or XML product position.
This information is evaluated
The checker investigates among other things id, title, description, link, image_link, price and availability. Structured titles and descriptions are considered as an alternative. For existing information, checks of offer price, condition, product identifiers and selected variant characteristics are carried out.
“Error” means a breach of a data rule checked here. “Testing” marks conditional requirements: for example, whether a manufacturer identifier is required depends on the product. Indications provide further starting points without predicting a rejection. They will remain decisive. Current product data specifications from Google.
Fixing Typical Feed Problems Targeted
- Duplicate ID: Check whether variants or export joins generate the same product identifier multiple times. IDs should be permanent and unique.
- Invalid price: Use the expected machine format with decimal point and currency, for example
19.90 EUR. A German formatted19,90 €It is not a suitable feed value. - Availability: Export the intended English values, not your visible shop labels. For pre-order and subsequent delivery, the associated date is relevant.
- GTIN test digit: Check the original identifier at the manufacturer. A self-invented number with a suitable check digit does not become a valid product identifier.
- Missing description: Check the language version and the mapping of the export fields. A text visible in the shop does not have to be automatically included in the feed file.
File formats and limits
XML is used as RSS item or atom with entry Read; the Google namespace prefix is recognized. CSV and TSV require a header, for example id,title,description,link,image_link,price,availability. Comma, semicolon and tab are supported. DTD and entity declarations are excluded.
The check does not load any product pages or images. It can therefore neither confirm image quality nor actual prices, stocks or delivery conditions in the shop. Even a technically inconspicuous file can receive further information in the Merchant Center. After import, check the product- and account-related diagnoses.
Frequent questions
Will my product feed be uploaded?
No. Parsing, testing and CSV export are done locally in the browser.
Does zero error mean that Google releases all products?
No. No violations of the selected local data checks were then found. Policies, account settings and matching with your product pages are not part of this check.
Why are brands and identifiers partly only test instructions?
Requirements depend on the product and available manufacturer identifiers. The tool cannot safely determine these product circumstances and therefore does not require invented identifiers.
How are XML references specified?
As the position of the product in the feed. In the case of CSV/TSV, the data row shall be the same as the header row; embedded row breaks in fields shall be treated as one record.
Does the tool check a feed directly via URL?
No. Open the exported feed as a file or paste its contents. As a result, confidential product data also remains local.