Run a product feed audit evidence workflow for Shopify, WooCommerce, feed apps, GMC affected-products CSV rows, GTIN, MPN, brand, price, stock, shipping, and product URL mismatches.
Use this when the audit already involves Merchant Center diagnostics, generated feed output, screenshots, affected rows, or sample product URLs and needs a repair-owner boundary.
Send store URL for the 1-page Feed/GMC owner mapFree Feed Truth reportUse this first when product counts, last fetch time, Google channel state, GCR, feed app mapping, or generated feed rows do not line up.
Build feed source snapshotAffected CSV and identifiersUse this when the product feed audit starts from GMC affected-products CSV rows, GTIN, MPN, brand, identifier_exists, SKU, price, or availability fields.
Group row errorsProduct feed checklistUse this when the audit needs a field coverage pass before deciding whether the issue is source data, mapping, received state, or public page evidence.
Package field evidenceFor product feed audit searches, the first useful answer is not a feed score. It is whether the repair owner is the source catalog, feed app mapping, Merchant Center received state, public product page evidence, or a reviewed Feed/GMC snapshot.
Start here when Shopify or WooCommerce product counts, generated feed rows, Merchant Center item counts, last fetch time, GCR state, or feed app ownership disagree.
Run Feed Truth reportUse the identifier checker for affected-products CSV rowsUse this path when the audit problem mentions GTIN, MPN, brand, identifier_exists, invalid GTIN, duplicate barcode, price, stock, or affected-products CSV row groups.
Group identifier rowsUse the owner map when feed audit evidence conflictsSend the store URL first when private screenshots, generated feed files, Merchant Center diagnostics, affected CSV rows, feed app mappings, and public product URLs point to different repair owners.
Send store URL for owner mapProduct feed audit intent is commercial because the visitor already has catalog, Merchant Center, feed app, or Shopping evidence to reconcile. The useful page is not a generic feed management article; it should route the visitor into CSV evidence, feed ownership, and reviewed snapshot decisions.
Shopify, WooCommerce, DTC, and agency teams dealing with Merchant Center diagnostics, feed app mappings, product identifiers, price, stock, and product URL evidence.
A product feed audit should not end in a vague score. Route each finding to count mismatch, identifier cleanup, WooCommerce plugin mapping, Shopify sync ownership, suspension evidence, or reviewed snapshot.
Platform product count, generated feed rows, GMC item count, last fetch time, or feed app ownership does not line up.
Run the Feed Truth reportIdentifier row cleanupThe affected-products CSV mentions GTIN, MPN, brand, identifier_exists, invalid GTIN, missing identifiers, duplicate barcode, price, or availability rows.
Group product identifier rowsWooCommerce feed plugin issueWooCommerce product export, feed plugin mapping, generated feed file, and Merchant Center received state disagree.
Open WooCommerce feed evidence pathShopify sync owner issueShopify product status, Google channel inclusion, feed app ownership, Content API source, and GMC item counts disagree.
Open Shopify feed sync pathSuspension or policy overlapFeed audit findings appear beside account review, disapprovals, appeal timeline, misrepresentation, policy, or merchant trust evidence.
Build the suspension evidence packThe report connects each visibility problem to crawl evidence, AI answer samples, competitor risk, and a concrete repair step.
The same Merchant Center warning can be caused by platform data, feed app mapping, supplemental feeds, Merchant Center rules, or visible product-page contradictions.
The query is narrow, but it signals a buyer who may need a reviewed snapshot or focused Fix Pack once evidence conflict is proven.
Start with the free Feed/GMC evidence workflow. Compare platform exports, generated feed rows, Merchant Center diagnostics, affected-products CSV, and public product pages before buying feed management or rewriting rules.
Use this packet when a product feed audit crosses Shopify, WooCommerce, feed apps, Merchant Center diagnostics, affected-products CSV rows, public product pages, or Shopping destination evidence. It keeps the audit focused on repair ownership instead of generic optimization advice.
Feed item counts, affected rows, identifiers, price, stock, shipping, image, product URL, or public product evidence disagree across systems.
Platform export, generated feed URL or file, feed app mapping screenshots, Merchant Center diagnostics, affected-products CSV, and sample product URLs.
Decide whether the next owner is source catalog data, feed app mapping, supplemental feed, Merchant Center rule, public product page, the 1-page Feed/GMC owner map, or Fix Pack.
This proves whether the source catalog is already wrong before feed app or Merchant Center rules are blamed.
This separates feed transformation problems from platform data and Merchant Center received-state problems.
This proves what Google evaluated, not just what the ecommerce platform or feed app claims to send.
This prevents feed values from contradicting the landing page evidence Google and shoppers can see.
Product feed audit evidence packet:
Source catalog: platform export, product/variant IDs, SKU, barcode, GTIN, MPN, brand/vendor, price, availability, image, product URL, channel inclusion.
Generated feed: feed app or Content API owner, generated feed URL/file, mapping screenshots, exclusions, supplemental feeds, last generation time.
Merchant Center: diagnostics screenshot, affected-products CSV, feed name, destination, item count, last fetch, final received attributes.
Public proof: sample product URLs, visible price/stock/shipping/returns/brand, Product/Offer schema, policy or trust evidence if relevant.
Decision needed: source catalog, feed mapping, supplemental feed, Merchant Center rule, public product page, 1-page Feed/GMC owner map, or Fix Pack.A product feed audit becomes useful when it separates the source catalog, generated feed, Merchant Center received attributes, and public product evidence. Otherwise teams often edit the wrong system.
Export Shopify or WooCommerce rows for product ID, variant or variation ID, title, SKU, GTIN, MPN, brand, price, stock, image, category, visibility, and URL.
Inspect the feed app or generated feed file for mappings, transformations, excluded rows, supplemental feeds, and scheduled generation time.
Use Merchant Center diagnostics, affected-products CSV, item counts, destination, final attributes, and last fetch time to confirm what Google actually received.
Compare visible product title, price, stock, shipping, return policy, brand, and identifiers against the submitted feed before appealing or bulk editing.
Free tools can group obvious rows. A reviewed snapshot is useful when private screenshots or CSVs need a second pass. A focused Fix Pack is only justified when the repair crosses platform fields, feed app rules, Merchant Center state, and public product evidence.
Best for first-pass count mismatch, identifier groups, GTIN validation, and route selection before editing feed rules.
Useful when CSV rows, feed app mapping, diagnostics screenshots, and product pages disagree about the repair owner.
Use this only when the snapshot proves the fix requires cross-system changes across catalog data, feed mapping, Merchant Center rules, and public evidence.
The audit page is the commercial routing layer. It should help the visitor pick the smallest workflow that can prove the feed repair owner.
| Workflow | Best for | Evidence required | Next action |
|---|---|---|---|
| Product feed audit page | Understanding whether the feed issue is source data, generated feed, Google received state, or public product evidence | Visible symptom, platform, feed app, affected issue names | Choose a route |
| Feed Truth report | Product count mismatch, generated feed ownership, stale fetch, Google channel state, or feed app conflict | Platform export, feed URL, diagnostics screenshot, item count, last fetch time | Open /tools/shopify-to-gmc-feed-truth-report |
| Identifier checker | GTIN, MPN, brand, identifier_exists, invalid GTIN, duplicate barcode, and missing identifier rows | GMC affected-products CSV plus product export | Open /tools/gmc-product-identifier-error-checker |
| Reviewed Feed/GMC Truth Snapshot | Cross-system evidence conflict before support handoff or paid repair work | CSV rows, screenshots, generated feed file, product URLs, policy proof | Request review before a focused Fix Pack |
This page routes feed evidence into the right tool, snapshot, or focused audit. It does not replace platform access, feed provider support, or Google decisions.
A product feed audit compares source catalog rows, generated feed output, Merchant Center received attributes, affected-products CSV diagnostics, and public product page evidence to decide where feed repair should happen.
Yes. Start with the free Feed Truth report and identifier checker. Request a reviewed snapshot only when CSV rows, feed mapping, diagnostics screenshots, and public product pages disagree.
No. This is an evidence audit and repair routing workflow, not ongoing feed management software or managed feed operations.
Prepare Shopify or WooCommerce product export, generated feed file or URL, GMC affected-products CSV, diagnostics screenshots, feed app mapping screenshots, and sample public product URLs.
Start with the free Feed/GMC evidence workflow. Compare platform exports, generated feed rows, Merchant Center diagnostics, affected-products CSV, and public product pages before buying feed management or rewriting rules.