Product feed grader

Find missing product facts and feed errors before you supply your catalogue to an agent. Your file stays in your browser.

Choose your feed

UTF-8, comma-separated CSV. Up to 5 MiB, 10,000 product rows and 100 columns.

Google’s product fields, or id, title and your chosen agent fields.

Use an amount and currency, such as 39.95 AUD or 25.00 USD.

Map your columns

The sample uses matching field names. Enable JavaScript to change mappings.

Require extra attributes

Sample requirement: color.

Local feed report

2 of 2 rows need attention

Required values filled

14 of 16

Issues to repair

6

A filled value can still be invalid. This report checks the supplied file and does not certify Google approval or live stock accuracy.

2 product rows checked in full. 14 of 16 required values filled. 6 issues.

Field completeness

Filled values for each required field
Required fieldFilled
id2 of 2
title2 of 2
description1 of 2
link2 of 2
image_link2 of 2
availability2 of 2
price2 of 2
color1 of 2

Rows to repair

Issues to repair by CSV record
CSV recordFieldRepair
2idGive each product variant its own unique ID. A shared item_group_id is allowed.
3descriptionSupply a value for description. Map its column if it is already in the file.
3colorSupply a value for color. Map its column if it is already in the file.
3priceUse a non-negative amount with at most two decimal places, a space and a currency code. Example: 39.95 AUD.
3availabilityUse in_stock, out_of_stock, preorder or backorder.
3idGive each product variant its own unique ID. A shared item_group_id is allowed.

Showing all 6 issues.

What the feed grader checks

The product feed grader reports missing required values separately from malformed values. It also flags every row that shares a product ID. Variants can share an item_group_id while keeping different product IDs.

For a free Google Shopping feed audit, choose Google basic fields to check the supplied CSV against the rules below.

The Google basic profile checks id, title, description, link, image_link, availability and price. It uses the plain-text fields in Google’s product data specification. IDs have a 50-character limit, titles 150 and descriptions 5,000.

Mapped URLs need http or https. Availability accepts in_stock, out_of_stock, preorder or backorder. Preorder and backorder need an availability_date. Dates receive a calendar-format check, without a delivery-date or future-window assessment.

The agent profile requires id and title, plus the extra attributes you select. Mapped prices and availability values use the same format checks in either profile. This is a store-selected convention, not a universal agent-feed standard.

The local price format accepts a non-negative amount with up to two decimal places and the expected currency code. In the Google profile, a zero price raises an eligibility review because its permitted uses depend on the product.

No conversion is performed.

Each required field counts once per relevant product row. Preorder and backorder rows add a date requirement. Extra attributes count on every row. Format errors do not reduce the filled count.

Choose the source column for each field. Matching headers are mapped automatically. Unmapped required fields count as missing.

Read and repair a sample feed

The fictional sample has a blue tee and a red tee, both assigned SKU-1 and the variant group TEE. The blue tee has a price of 39.95 AUD. The red tee has the price free and availability available. Its description and color are empty.

With the Google basic profile and color selected, 14 of 16 required values are filled. Both rows need attention. Six issues appear because the repeated ID affects both rows, alongside the price and availability errors and two missing values.

Keep SKU-1 for the blue tee and assign SKU-2 to the red tee. Replace free with the actual selling price, such as 39.95 AUD. Use in_stock only if the red tee is available to buy. Add its description and red colour value. Both variants can keep TEE as their item_group_id.

Export the repairs, correct your original feed and load it again. The repair list does not change your source file. For recurring catalogue issues, use the guide to improving your product feed.

The CSV contains every issue, its product ID and the supplied value. Formula-like values receive a protective apostrophe for spreadsheet use.

CSV record 1 is the header. A quoted description with line breaks remains one record. Several issues can refer to the same product.

Select source columns that your store requires on every row. These are your rules. The sample requires color.

The starting report uses a fictional two-product feed. Loading your file replaces it. Closing or reloading the page clears your file.

What a local feed check cannot confirm

The report checks values in one supplied file. It cannot confirm live inventory, open product or image URLs, inspect image quality or compare prices with your checkout. A correctly formatted stock value can still be outdated.

The Google profile covers a limited set of plain-text fields. It does not validate structured titles or descriptions, GTINs, brand and MPN rules, category-specific variant attributes, shipping, tax or policy requirements. Product-group consistency beyond unique product IDs is outside these checks.

Google Merchant Center also applies account and destination requirements. A report with no issues does not approve a listing. Complete the channel’s own checks, and compare repaired records with the products customers can actually buy.

Larger files are refused, never sampled.