PRODUCT DATA & MERCHANT CENTER

Google Shopping Feed Readiness Checker

Check required Google Shopping fields, common CSV or TSV formatting issues and manual Merchant Center checks before upload.

US workflow. UTF-8 CSV/TSV only, up to 5 MiB and 10,000 product rows. Local advisory checks do not confirm approval.

Google Shopping feed checker

US workflow · UTF-8 CSV/TSV · up to 5 MiB and 10,000 product rows.

Your file and pasted content stay in this browser. Nothing is uploaded or saved.

Feed contents stay in this browser. Nothing is uploaded or saved.

Check a Google Shopping product feed before upload

Review common US product data fields in a CSV or TSV file. The checker runs locally and separates format findings from checks that need Merchant Center or the live product page.

What this checker covers

It checks file structure, required columns, row values, duplicate IDs within the file, basic URL and price shapes, and selected optional attributes. It supports UTF-8 CSV/TSV up to 5 MiB and 10,000 product rows.

A valid-looking value does not establish that a product meets Google policy or that an account is configured correctly.

How to use the results

Upload a feed export or paste delimited text. Review missing and malformed fields first, then suspicious values. The separate manual-check findings identify live price, inventory, image, landing-page, identifier and account shipping checks.

The downloadable report contains row numbers and findings only; it excludes product cell contents. Reset clears the current data from this page.

US market limits

Rules and required attributes can vary by country, product category and account configuration. This v1 does not calculate tax or shipping, fetch URLs or images, verify GTIN ownership, or predict approval. Confirm current requirements in Merchant Center.

What a clean row looks like

A minimal US row needs id, title, description, link, image_link, availability, and price. Use a stable ID, a title that identifies the product, a description that matches the landing page, absolute http(s) URLs, a supported availability value such as in_stock, and a price in the form 24.99 USD.

Optional columns such as condition, brand, gtin, mpn, identifier_exists, and item_group_id are checked only when a value is present. A blank optional item_group_id is allowed for a standalone product; use a shared group ID only when variants should be linked.

How to read the four status groups

Missing means a required column or value is absent. Malformed means the value does not match the checker's supported shape, such as a non-http URL or a price without a currency. Suspicious means the value may be valid but needs a second look, such as a duplicate ID or an all-caps title.

Manual check is not an error. It marks a live condition the file cannot prove: whether the landing page, image, price, inventory, identifiers, shipping settings, or account status match Merchant Center. Fix missing and malformed findings first, then verify the manual-check list against the live store.

Rules reviewed October 25, 2026. Verify live country, category, account, shipping and policy requirements in Merchant Center. Google product data specification · Google shipping settings · Google product image requirements

Frequently asked questions

Does this checker tell me whether Google will approve my products?+

No. It checks selected local file patterns and highlights checks that require Merchant Center, the product page, or category-specific guidance.

Are my feed contents uploaded?+

No. Parsing and checks run in your browser. The issue report is generated locally and does not include source cell values.

Which files and markets are supported?+

This version accepts UTF-8 CSV or TSV for a US workflow, up to 5 MiB and 10,000 product rows. XML, API feeds, nested attributes and other market-specific rules are outside its scope.

Is a blank item_group_id an error?+

No. item_group_id is optional. Leave it blank when a product has no variants; use a shared group ID only when separate offer rows should be linked as variants.

Why does a valid row still show manual-check findings?+

Manual-check findings describe facts outside the file, such as a live landing page, inventory, image, price, identifier, or Merchant Center shipping setting. They are prompts to verify, not proof that the row is wrong.

NEXT STEP

Use the report as a preflight, then verify in Merchant Center.

Local format checks cannot replace live account diagnostics or product policy review.Check a feed