Your feed validates. That does not mean it is right.
- Generates XML, TSV or CSV on your own server
- Audits the catalogue in a full-width table you can act on
- Rules rewrite fields without editing product pages
No card charged until day 8 · 30-day money-back guarantee · Works with any WooCommerce store
Free check
Paste a feed URL or your store address.
We hunt the common Woo feed plugins, the homepage, robots.txt and sitemaps. Five free checks a day. Nothing is stored.
The expensive failures are the ones that look fine
Every problem below came out of generating a real 7,000-item catalogue and comparing it product by product against another feed plugin's output. Each one produced a feed that validated cleanly and was wrong.
Descriptions double-escaped
Tags stripped but entities left alone, then escaped a second time on the way out. M&M SCRUBS reaches Google as M&M SCRUBS.
Colour and size sent as slugs
WooCommerce returns xx-small where Google expects XX-Small. Google matches apparel size and colour against its own vocabulary, and a hyphenated slug matches nothing.
Offer ids silently collapsing
Ids built from a SKU that is not unique per variation turned 6,214 items into 4,075 ids. Google keeps performance history against the id, so this is not a cosmetic bug.
Every product type
Simple, variable, grouped and downloadable, with variations sharing an item_group_id. Nothing is dropped silently: everything excluded is reported with its reason.
Rules, not silent guesses
Set Google category, gender or age with an if/then rule (all products, or category contains “scrubs”). A store-wide fallback is last resort. Nothing is invented when there is no signal.
Google's taxonomy, built in
All 5,595 categories ship with the plugin. Your categories are matched against them and every proposal carries a confidence, so you can see which were obvious and which need a look.
Large catalogues
Generation streams instead of loading the catalogue into memory. A 7,000-item feed and a 100,000-variation catalogue use about the same amount of it.
Never touches your products
Feed-level corrections live beside your catalogue, not inside it, and are removed cleanly if you uninstall. Title casing is off by default.
WP-CLI
status, doctor, generate, audit, fix, explain, map-categories. Script it across every client site.
The audit
Every finding, counted and explained
How it works
Three steps, no Google login
Generate
Install, activate, generate. Every product type, one feed item per buyable variation, published atomically so a Google fetch never reads half a file.
Audit
A table of every gap: severity, count, how to fix, one-click apply. Mechanical fixes write feed overrides only. Product pages stay as they are.
Fix and publish
Apply the safe fixes in bulk, approve the rest yourself, then hand Merchant Center your feed URL and let it fetch on a schedule.
Editions
Free forever, and a paid edition
The free edition on WordPress.org is not a trial and does not expire.
Free
Feed generation in XML, TSV and CSV. Scheduled regeneration. Attribute derivation. Category mapping. The full exclusion report. No feature nag in the middle of your catalogue.
Paid
Included AI rewrites (no site API key, capped by plan), the hosted 83-point audit, per-product overrides, and the Merchant Center connection.
Questions
Do I need to connect my Google account?
No. The default workflow generates a file and gives you a URL that Merchant Center fetches on a schedule. Connecting Google is optional and adds account-aware features.
Does my catalogue leave my site?
Feed generation runs on your own server. The audit is opt-in: when you turn it on the plugin sends the feed's URL and our service fetches it. With the audit off, nothing leaves your site.
I already use another feed plugin. Can I switch?
Yes, and one thing is worth checking on any plugin before you do: offer ids. Google accumulates performance history against the id in your feed, so a plugin that derives ids differently resets it. This one uses the product id, which is what most feed plugins emit.
Will it work for apparel?
Apparel is the case it was built against. Google requires gender, age group, colour and size, and WooCommerce stores none of them in a form Google accepts. Variation attributes are resolved to their proper labels and the rest is derived from real signals, or left out.
Find the problems before Google does
Start with the free edition on WordPress.org, or take the trial and run the audit on your real catalogue.
No card charged until day 8 · 30-day money-back guarantee · Works with any WooCommerce store