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.
WooCommerce source rows
Use this when product status, variation ID, SKU, GTIN, MPN, brand, barcode, price, stock, catalog visibility, category, or product URL fields need row-level comparison.
Compare source rowsFeed plugin outputUse this when WooCommerce rows look correct but plugin mapping, generated feed output, feed URL, Content API owner, last fetch, or Merchant Center received values do not match.
Compare feed evidenceAffected CSV groupsUse this when Merchant Center affected-products CSV rows need grouping by issue title, affected attribute, severity, destination, offer ID, country, and repair owner.
Group diagnosticsBulk GTIN rowsUse this when WooCommerce GTIN, UPC, EAN, ISBN, barcode, duplicate identifier, nonnumeric value, or check-digit patterns need a fast CSV shape check.
Validate GTIN shapeWooCommerce Feed/GMC owner mapUse this when WooCommerce exports, plugin settings, generated feed rows, Merchant Center diagnostics, affected CSV, and public product URLs disagree before a bulk edit.
Send store URL firstWooCommerce sync answer
WooCommerce-to-GMC sync fails when catalog rows, variations, plugin output, and received attributes disagree.
For WooCommerce source rows, start by separating catalog visibility, variation status, feed plugin mapping, generated feed output, Merchant Center received attributes, affected CSV rows, identifiers, and public product-page proof before changing plugin settings.
Catalog and variation rows come first
Use the product export when missing or stale products involve product status, catalog visibility, variation ID, stock status, price, SKU, GTIN, MPN, brand, category, or product URL fields.
Check source rowsPlugin mapping decides what Google can receiveUse Feed Truth when WooCommerce rows look correct but plugin filters, feed URL output, mapping rules, generation schedule, Content API source, last fetch, or Merchant Center received attributes disagree.
Run Feed Truth reportAffected CSV rows need row-level groupingUse affected CSV routing when diagnostics mention issue title, affected attribute, severity, destination, offer ID, GTIN, MPN, brand, price, availability, image, shipping, tax, link, or landing-page mismatch.
Group affected CSV rowsCross-system conflicts need a Feed/GMC owner mapSend the store URL first when WooCommerce exports, plugin mapping screenshots, generated feed samples, Merchant Center diagnostics, affected CSV rows, and public product URLs disagree before plugin or bulk product edits.
Send store URL firstWho 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
- Store-URL-first Feed/GMC owner map 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.
- Send the store URL first for a 1-page Feed/GMC owner map when WooCommerce rows, feed plugin output, GMC diagnostics, and public product evidence disagree.
Copy-ready WooCommerce feed packet
Package WooCommerce feed evidence before changing plugin settings.
Use this packet when WooCommerce products are missing, stale, rejected, or not updating in Google Merchant Center and the likely owner could be catalog visibility, variation data, plugin mapping, generated feed output, Merchant Center received state, or public product evidence.
WooCommerce product counts, variation rows, stock or visibility state, feed plugin output, Merchant Center item count, affected CSV rows, identifiers, price, availability, image, shipping, or product URL evidence disagree.
WooCommerce product export, feed plugin mapping screenshots, generated feed sample or URL, Merchant Center diagnostics, affected-products CSV, representative product URLs, and recent plugin or product edit timeline.
Decide whether the repair belongs to WooCommerce catalog fields, variation visibility, plugin filters, feed mapping, supplemental feed, Merchant Center rule, identifier cleanup, public product-page proof, or Feed/GMC owner map.
- Product ID, variation ID, SKU, status, catalog visibility, stock status, regular price, sale price, product URL, and category
- GTIN or barcode field, MPN, brand, vendor/manufacturer attribute, product title, image, shipping class, and tax status
- Rows for one missing product, one stale product, one rejected product, and one clean comparison product
- Recent product imports, bulk edits, plugin updates, theme changes, or visibility changes
This proves whether WooCommerce source rows and variations are eligible before plugin mapping or Merchant Center is blamed.
- Plugin name, feed URL or generated file, scheduled generation time, last successful generation, and exclusion filters
- Mapping screenshots for title, link, image, price, sale price, availability, GTIN, MPN, brand, identifier_exists, shipping, and category
- Supplemental feeds, custom attributes, product filters, category filters, and rules that transform or exclude rows
- Generated feed sample rows where values differ from WooCommerce export rows
This separates WooCommerce source data from plugin transformations, scheduled generation, exclusions, and feed URL output.
- Feed name, destination, country, item count, last fetch time, fetch errors, diagnostics date, and affected-products CSV
- Final received attributes for sample products: GTIN, MPN, brand, identifier_exists, price, availability, image, shipping, tax, link, and category
- Issue title, affected attribute, severity, destination, offer ID, and sample row groups
- Merchant Center rules or supplemental feed screenshots if Google rewrites received values
This proves what Google actually evaluated instead of relying on WooCommerce or plugin output alone.
- Sample affected product URLs and clean comparison product URLs
- Visible title, price, stock, variants, image, shipping, returns, brand, product identity, and availability
- Canonical URL, variation URL, redirects, Product/Offer schema, visible policy links, and blocked-resource notes
- Screenshots where the public page contradicts WooCommerce export, generated feed, or Merchant Center received values
This prevents plugin changes or identifier edits when the public product page is the evidence layer Google and shoppers can observe.
WooCommerce feed sync evidence packet:
Catalog: product ID, variation ID, SKU, visibility, status, stock, price, sale price, GTIN/barcode, MPN, brand, category, product URL.
Plugin/feed: plugin name, feed URL/file, mappings, exclusions, custom attributes, scheduled generation, last generation, supplemental feeds.
Merchant Center: feed name, destination, item count, last fetch, diagnostics date, affected CSV, issue title, affected attribute, final received values.
Public proof: sample URLs, visible title/price/stock/shipping/returns/images, canonical/variation URL, Product/Offer schema, policy links.
Decision needed: WooCommerce catalog fix, variation visibility, plugin mapping, feed generation, GMC rule, identifier checker, Feed Truth report, suspension pack, 1-page Feed/GMC owner map.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 Feed/GMC owner map
Use the free tools when the evidence is visible in CSV rows. Send the store URL first for a Feed/GMC owner map 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 Feed/GMC owner map
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 |
| Feed/GMC owner map | Cross-system evidence conflict before plugin changes or support handoff | CSV rows, plugin screenshots, generated feed file, GMC diagnostics, product URLs | Send the store URL first 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.
Send the store URL first for a Feed/GMC owner map 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.