Why this page exists
WooCommerce feed issues are usually evidence routing problems: catalog fields, product variations, plugin mappings, generated feed rows, Merchant Center received attributes, and public product pages can all disagree.
Google Truth fix page
WooCommerce Products Not Syncing to Google Merchant Center
Diagnose WooCommerce products not syncing to Google Merchant Center by comparing product CSV rows, variation status, feed plugin mapping, GTIN fields, GMC diagnostics, fetch timing, and public product evidence.
Who it is for
WooCommerce store owners, WordPress agencies, and ecommerce operators using Google Listings & Ads, product feed plugins, supplemental feeds, or Merchant Center rules.
WooCommerce feed evidence route
Choose the WooCommerce feed sync owner before changing products
A WooCommerce-to-GMC sync problem can belong to catalog visibility, variation data, plugin mapping, generated feed rows, product identifiers, Merchant Center rules, or public-page evidence. Pick the smallest route that proves the owner.
Identifier and affected row cleanup
GMC affected-products CSV mentions GTIN, MPN, brand, identifier_exists, price, stock, image, or landing page errors that need row-level grouping.
Group WooCommerce and GMC rowsBulk GTIN shape checkThe immediate question is whether UPC, EAN, ISBN, or GTIN-14 values have valid length, numeric shape, check digit, or duplicate rows.
Run the GTIN validator CSV toolFeed owner conflictWooCommerce export rows look correct, but the generated feed, plugin mapping, Merchant Center final attributes, and last fetch time do not agree.
Compare feed source ownershipSuspension or policy overlapThe WooCommerce feed issue appears beside Merchant Center review, disapprovals, appeal timeline, misrepresentation, policy, or trust evidence.
Build the suspension evidence packWhat the audit checks
The report connects each visibility problem to crawl evidence, AI answer samples, competitor risk, and a concrete repair step.
Sample report evidenceChargeable audit v0.2
Plugin mappings can rewrite correct catalog data
A WooCommerce product export can look correct while the generated feed sends blank, stale, or transformed identifiers to Merchant Center.
Variation rows need separate evidence
Parent products, variations, hidden products, and excluded categories can create count gaps that are not solved by editing GTIN values.
GMC diagnostics prove received state, not source ownership
Merchant Center warnings show what Google received. They do not prove whether the repair belongs in WooCommerce fields, plugin mapping, supplemental feeds, or rules.
Queries and diagnostic phrases
Turn vague store symptoms into repeatable checks.
WooCommerce products not syncing Google Merchant CenterWooCommerce Google Merchant Center products not showingWooCommerce product feed not updating Google Merchant CenterWooCommerce GTIN not syncing Google Merchant CenterWooCommerce Google feed plugin product count mismatch
- WooCommerce feed evidence packet
- Likely sync owner: WooCommerce catalog field, product variation, feed plugin, supplemental feed, Merchant Center rule, or public product page
- CSV and screenshot list for Google channel evidence
- Identifier row groups for GTIN, MPN, brand, identifier_exists, price, stock, and link mismatches
- Reviewed 1-page Google Truth Snapshot boundary when plugin mapping and Merchant Center evidence conflict
Free precheck
Free WooCommerce feed evidence intake before changing plugin settings
Start with the product and identifier CSV evidence. Compare WooCommerce catalog rows, feed plugin mapping, generated feed rows, Merchant Center affected-products CSV, and public product URLs before editing plugin rules or product identifiers.
- Export WooCommerce product CSV rows with product ID, variation ID, SKU, GTIN, MPN, brand, price, stock, visibility, and product URL.
- Capture feed plugin mapping, product exclusion filters, scheduled generation time, feed URL, and any supplemental feed or Merchant Center rule.
- Compare GMC item count, affected-products CSV, diagnostics date, destination, and last fetch time against the generated feed.
- Request a reviewed Google Truth Snapshot only when WooCommerce rows, feed plugin output, GMC diagnostics, and public product evidence disagree.
Evidence owner
Diagnose WooCommerce-to-GMC sync by evidence owner
WooCommerce stores often route product data through plugins before Google receives it. Check the evidence in order: source product rows, variation fields, plugin mapping, generated feed output, Merchant Center received state, then public product page proof.
Start with product status, catalog visibility, variation IDs, stock, price, SKU, brand, GTIN, MPN, category, and product URL in the exported product CSV.
Check which WooCommerce field is mapped to GTIN, MPN, brand, price, sale price, availability, shipping, image, and link, plus filters that exclude products.
Compare the generated feed URL or downloaded feed file against the WooCommerce export before assuming Merchant Center transformed the data.
Use GMC item counts, destination, affected-products CSV, diagnostics date, last fetch time, and final attributes to prove what Google actually received.
Snapshot handoff
When WooCommerce feed sync needs a reviewed Google Truth Snapshot
Use the free tools when the evidence is visible in CSV rows. Move to a reviewed snapshot when private plugin screenshots, feed output, Merchant Center diagnostics, and public product pages need a second pass before bulk edits or support handoff.
Best when affected rows mention GTIN, MPN, brand, identifier_exists, price, stock, image, or landing page attributes.
Best when the row issue is only GTIN length, check digit, non-numeric values, duplicate barcode, or UPC/EAN shape.
Useful when WooCommerce CSV rows, plugin field mapping, generated feed rows, Merchant Center diagnostics, and public product URLs disagree.
Needed when feed mismatch overlaps with Merchant Center account review, policy warnings, misrepresentation, or an appeal timeline.
Audit scope
WooCommerce feed fix vs identifier checker vs reviewed Google Truth Snapshot
Use the smallest workflow that proves the repair owner. Do not rewrite plugin mappings until the WooCommerce export, generated feed, and GMC received rows have been compared.
| Workflow | Best for | Evidence required | Next action |
|---|---|---|---|
| WooCommerce fix page | Understanding whether the blocker is catalog visibility, variation data, plugin mapping, or Merchant Center fetch | Visible symptom, product count gap, feed plugin name, affected issue names | Choose the matching evidence route |
| Identifier checker | GTIN, MPN, brand, identifier_exists, price, stock, image, and landing page row conflicts | WooCommerce product CSV plus GMC affected-products CSV | Open /tools/gmc-product-identifier-error-checker |
| Bulk GTIN validator | UPC, EAN, ISBN, or GTIN-14 length, check digit, duplicate, and non-numeric checks | CSV column with GTIN or barcode values | Open /tools/bulk-gtin-validator |
| Reviewed Google Truth Snapshot | Cross-system evidence conflict before plugin changes or support handoff | CSV rows, plugin screenshots, generated feed file, GMC diagnostics, product URLs | Request review from the Feed/GMC evidence path |
What this WooCommerce sync diagnosis cannot guarantee
This page organizes evidence and likely ownership. Google, WooCommerce, WordPress plugins, and feed providers still control processing, eligibility, and support outcomes.
Public-page boundary
- This page does not guarantee Merchant Center approval.
- This page does not guarantee Shopping ads recovery.
- This page does not replace WooCommerce, WordPress plugin, or Google support access.
- This page does not verify official GS1 ownership.
FAQ
Questions store owners ask before ordering an audit.
Common causes include hidden products, variation data gaps, feed plugin filters, unmapped GTIN or brand fields, stale generated feeds, Merchant Center fetch delays, supplemental feed overrides, or item-level diagnostics.
Start with product ID, variation ID, SKU, GTIN or barcode field, MPN, brand, title, product URL, stock status, regular price, sale price, catalog visibility, and product category.
Not until you compare the WooCommerce product export, generated feed row, Merchant Center affected row, and public product URL. Plugin changes can affect many products at once.
Use a reviewed snapshot when WooCommerce CSV rows, feed plugin mappings, generated feed files, Merchant Center diagnostics, and public product pages disagree or the next change affects many products.
Free WooCommerce feed evidence intake before changing plugin settings
Start with the product and identifier CSV evidence. Compare WooCommerce catalog rows, feed plugin mapping, generated feed rows, Merchant Center affected-products CSV, and public product URLs before editing plugin rules or product identifiers.