Google Merchant Feed Validator
Google Merchant Feed Validator: fix product-feed errors before you upload to Google.
Find blocked products, understand each fix and export a corrected feed.
START HEREChoose data filesCSV, TSV, TXT, XML, XLSX
- Maximum
- 50 MB · 100,000 products · 250 columns
- File handling
- 24 hours
FREE3 jobs a dayFiles up to 10 MB
PROUp to 200 jobs a day€12.99/month or €89.99/year
See plansLarger files need Pro. Failed jobs are never counted.
- Prepared example is free
- 3 free jobs a day
- Cancel anytime
EXAMPLE RESULTSample data
Products checked · 12
Fix before upload4
Review to improve5
Safe fixes applied2
XLSX audit · corrected TSV
- Products checked
- 12
- Findings
- 9
- Safe fixes
- 2
Formats, limits & file handling
- Works with
- CSV, TSV, TXT, XML, XLSX
- Limit
- 50 MB · 100,000 products · 250 columns
- You receive
- Prioritised XLSX, issues CSV and corrected TSV
- File handling
- 24 hours
Upload one feed and get a fix-first worklist with affected example products, plain-language repair steps and a corrected TSV containing only the safe changes you approve.
THREE CLEAR STEPS
From your files to a usable result.
- 01Add your input
Limits and supported formats are visible before you begin.
- 02Review the result
Errors are grouped by fix, each with an example product and a plain-language repair step. Safe changes go into the corrected TSV only if you approve them.
- 03Download
Use your free job, plan or credits. Failed jobs are never counted.
Interactive synthetic catalogue
See the exact repair, not just an error code.
The twelve sample products use fixed, versioned data. Run the example to see why an issue matters, what to change and which product proves it.
✓
No upload in this demo12 synthetic products · grouped worklist
No findings match this filter.
Important: This example cannot see your Merchant Center account, landing pages or Google's policy decisions.
One short, controlled audit
From feed file to an ordered correction package
- Add one feed.Upload CSV, TSV, TXT, XML or XLSX. Content, extension, size and structure are checked before processing and before a job is counted.
- Confirm the important columns.Required attributes stay visible first; identifiers, variants, apparel and optimisation fields are grouped separately.
- Approve safe formatting only.Whitespace, unambiguous price syntax and recognised availability spellings can be selected independently.
- Start with blockers.Repeated findings are grouped into one card with affected counts, example products, why it matters and the concrete next step.
- Download the evidence.The XLSX starts with priorities, while CSV keeps every row-level issue and the TSV contains only approved deterministic changes.
What the rules cover
Required attributesID, title, description, link, image link, price and availability.
IdentifiersDuplicate IDs, GTIN length and check digit, brand/MPN combinations and identifier_exists.
Commerce valuesPrice, sale price, condition, availability and ISO availability dates.
Variants and apparelItem groups plus visible color, size, age-group and gender gaps where apparel data is detected.
Clear audit boundary
This is a file-level product-data preflight. It does not log in to Google Merchant Center, crawl the destination website, compare landing-page price or stock, verify checkout or shipping settings, review policies, inspect account diagnostics or guarantee that Google will approve an item.
One organised ZIP
Start with priorities, keep every underlying row.
No silent bulk rewrite. The source hash, ruleset, settings and selected fixes stay documented.
Feed audit questions
Google Merchant Feed Validator FAQ
Exact answers about file checks, automatic corrections and the boundary to Merchant Center.
What does the Google Merchant Feed Validator check?
It checks product-data structure, required values, identifiers, prices, availability, URLs and selected variant relationships using a versioned ruleset.
Does it connect to my Merchant Center account?
No. It audits the uploaded feed file only. It cannot see account diagnostics, item history, landing-page crawls, policy reviews or live approval status.
Which feed formats are supported?
The tool accepts UTF-8 CSV, TSV and TXT files, RSS or Atom XML product feeds, and XLSX workbooks.
Will WoluTools invent missing values?
No. It never creates GTINs, brands, MPNs, prices, stock states, URLs or product descriptions. Missing business data remains an issue for a human to resolve.
Which corrections can be applied automatically?
Only deterministic corrections selected by the user, such as trimming whitespace and normalising unambiguous price or availability formatting.
Does a clean report guarantee Google approval?
No. Google may use account, website, policy, crawl and market information that a file-only validator cannot inspect.
What is included in the download?
The ZIP contains report.xlsx, issues.csv, corrected-feed.tsv, manifest.json and a README explaining the audit boundary.
How large can a feed be?
The initial service limit is 50 MB, 100,000 product rows and 250 columns per audit.
What happens to uploaded feeds?
Originals are deleted after processing. The generated audit package expires after 24 hours and is physically removed in the recurring cleanup.
Can I upload a real feed publicly now?
Yes. Upload a real catalogue and use 3 free jobs a day without an account, or up to 200 a day with Pro.
Try it free
Inspect the audit before sharing a real catalogue.
Use the synthetic feed now. Your own files run here without an account.