Audit Google Shopping feed evidence across Shopify, WooCommerce, feed apps, Merchant Center diagnostics, Shopping ads eligibility, affected-products CSV rows, GTIN, price, stock, shipping, and landing page mismatches.
Use this when Shopping diagnostics, affected CSV rows, source exports, generated feed output, campaign symptoms, and product URLs already conflict and need a repair-owner boundary.
Send store URL for the 1-page Feed/GMC owner mapFeed Truth reportUse this when source counts, generated feed rows, Shopping destination counts, last fetch, Content API owner, or Merchant Center received attributes do not line up.
Compare feed evidenceAffected CSV owner mapUse this when Merchant Center affected-products CSV rows need grouping by issue title, affected attribute, severity, destination, country, offer ID, and repair owner.
Map CSV repairsIdentifier checkerUse this before barcode, GTIN, MPN, brand, identifier_exists, duplicate identifier, custom product, or product identity bulk edits.
Check row identityProduct feed auditUse this when Shopping symptoms cross multiple destinations, marketplaces, source catalogs, feed apps, WooCommerce, Shopify, public product pages, or channel mappings.
Broaden audit scopeA useful Google Shopping feed audit separates Shopping destination eligibility, Merchant Center received attributes, affected CSV row groups, source catalog ownership, feed app mapping, and public landing-page proof before bids, product groups, or feed rules are changed.
Use Feed Truth when source product counts, generated feed rows, Google channel state, last fetch time, final received values, or eligible Shopping items do not match.
Run Feed Truth reportGroup affected CSV rows before assigning repair ownershipUse affected CSV routing when issue title, affected attribute, severity, destination, country, offer ID, price, availability, shipping, image, link, or landing-page proof needs owner mapping.
Map affected rowsRun identifier checks before barcode or GTIN bulk editsUse the identifier checker when the audit touches GTIN, MPN, brand, identifier_exists, duplicate barcode, invalid GTIN, custom product flags, or product identity proof.
Check identifiersUse the owner map when Shopping feed evidence conflicts across systemsSend the store URL first when Merchant Center diagnostics, affected CSV rows, Shopify or WooCommerce exports, generated feed output, app mapping screenshots, campaign symptoms, and product URLs disagree; CSVs and screenshots can wait for the reply thread.
Send store URL for owner mapGoogle Shopping feed audit intent sits close to Merchant Center cleanup, Shopping ads eligibility, feed app support, and product feed audit work. The useful page should separate Shopping destination eligibility and Merchant Center received state from generic feed management advice.
Shopify, WooCommerce, DTC, and agency teams responsible for Google Shopping ads, Merchant Center feeds, diagnostics, product eligibility, feed apps, and source catalog repairs.
A Google Shopping feed audit should decide whether the problem belongs to product eligibility, source catalog data, feed generation, Merchant Center rules, identifier cleanup, campaign surface, or a broader product feed audit.
Google Shopping destination item count, eligible item count, generated feed rows, source catalog count, or last fetch time does not line up.
Run the Feed Truth reportIdentifier or item row cleanupAffected-products CSV rows mention GTIN, MPN, brand, identifier_exists, invalid GTIN, duplicate barcode, price, stock, image, or landing page mismatch errors.
Group rows in the identifier checkerShopify Google Shopping sync issueShopify product status, Google & YouTube app state, feed app ownership, Content API source, product groups, and Merchant Center item counts disagree.
Open the Shopify sync pathBroader product feed auditThe Shopping symptom also touches WooCommerce, a feed app, supplemental feed, product URL evidence, shipping, public trust, or several marketplaces.
Open the product feed audit routeSuspension or account review overlapShopping feed diagnostics appear beside account review, misrepresentation, policy, appeal, business identity, or merchant trust symptoms.
Build the suspension evidence packThe report connects each visibility problem to crawl evidence, AI answer samples, competitor risk, and a concrete repair step.
A zero-impression or limited-performance product group may trace back to source catalog fields, generated feed mapping, Merchant Center received attributes, public product-page mismatch, or policy evidence rather than campaign settings.
The query sits near Shopping ads, Merchant Center cleanup, feed app support, and product feed audit demand, so the page should convert to evidence intake instead of chasing broad feed management traffic.
Start by proving what Google received for the Shopping destination before changing campaigns, bids, feed rules, or app settings. The free Feed Truth workflow helps separate source catalog, generated feed, Merchant Center diagnostics, and public product-page evidence.
Use this packet when a Google Shopping feed audit needs to prove the repair owner across Shopping eligibility, Merchant Center received attributes, affected-products CSV rows, source catalog data, generated feed output, public landing pages, and campaign symptoms.
Shopping destination eligibility, disapproved products, limited performance, stale fetches, affected CSV rows, received attributes, product groups, or landing-page proof disagree across systems.
Merchant Center diagnostics, affected-products CSV, Shopping destination counts, source export, generated feed sample, mapping screenshots, sample product URLs, and campaign/product group screenshots.
Decide whether the repair belongs to source catalog data, feed app mapping, Merchant Center rules, identifier cleanup, landing-page proof, Shopping campaign review, broader product feed audit, or the 1-page Feed/GMC owner map.
This defines whether the audit is about Shopping eligibility and serving scope instead of generic catalog optimization.
This proves what Google evaluated and keeps the audit anchored in received attributes, not assumptions from the ecommerce platform.
This separates source catalog repairs from feed transformation, app ownership, Content API, and Merchant Center rule repairs.
This prevents the audit from recommending campaign or feed edits while public product evidence contradicts what Google can crawl.
Google Shopping feed audit evidence packet:
Scope: Shopping destination, country, active/eligible/pending/limited/disapproved counts, diagnostics date, issue names, product status groups.
Merchant Center: affected CSV, issue title, affected attribute, severity, final received attributes, feed name, Content API source, last fetch.
Source/feed: platform export, generated feed sample, feed app/API owner, mappings, exclusions, supplemental feeds, recent bulk edits.
Public proof: sample URLs, visible title/price/stock/shipping/returns/images, canonical/variant URL, Product/Offer schema, policy links.
Decision needed: source repair, feed mapping, Merchant Center rule, identifier cleanup, landing-page fix, Shopping campaign review, product feed audit, 1-page Feed/GMC owner map, or Fix Pack.Shopping ads teams often change bids or campaigns when the issue is actually item eligibility, feed source ownership, Merchant Center received attributes, or public landing page evidence. Keep those layers separate before making bulk edits.
Capture eligible, limited, disapproved, and pending item counts for the Shopping destination before changing campaign structure or product groups.
Use diagnostics, affected-products CSV, final item attributes, fetch time, and destination to see what Google evaluated.
Compare ecommerce platform exports with generated feed rows, feed app mappings, supplemental feeds, Content API source, and Merchant Center rules.
Verify visible price, stock, shipping, returns, product identity, merchant trust, and page availability before appealing or editing feed values.
The free route is enough when the source owner is visible. A reviewed snapshot is useful when private screenshots, affected CSV rows, feed app settings, Merchant Center diagnostics, campaign symptoms, and public product pages disagree.
Best for count mismatch, stale fetch, source owner checks, destination state, and a first-pass path before feed edits.
Best for GTIN, MPN, brand, identifier_exists, invalid GTIN, duplicate barcode, and row-level cleanup from affected-products CSV exports.
Use this when the evidence spans campaigns, Merchant Center, feed app settings, source catalog rows, and public product pages, and the first decision is which layer owns the fix.
This page targets Shopping and Merchant Center evidence. The broader product feed audit handles cross-channel feed ownership, and feed management software handles ongoing catalog syndication.
| Workflow | Best for | Evidence required | Next action |
|---|---|---|---|
| Google Shopping feed audit | Shopping ads eligibility, Merchant Center diagnostics, affected rows, and product status mismatches | GMC diagnostics, affected-products CSV, Shopping destination, source export, feed output, public product URLs | Send store URL for Feed/GMC owner map |
| Product feed audit | Broader source catalog, generated feed, Merchant Center, feed app, WooCommerce, Shopify, and public evidence ownership | Platform export, generated feed, feed app mapping, diagnostics, affected rows, product URLs | Open /audit/product-feed-audit |
| Identifier checker | GTIN, MPN, brand, identifier_exists, invalid GTIN, duplicate barcode, and affected CSV row grouping | GMC affected-products CSV plus platform product export | Open /tools/gmc-product-identifier-error-checker |
| Feed management software | Ongoing feed generation, mapping, marketplace syndication, and catalog operations after the evidence owner is known | Platform access, feed provider setup, channel mappings, and ongoing operations budget | Use only after the audit proves the owner |
This is an evidence routing page for Shopping feed problems. It does not replace ad management, platform access, feed provider support, or Google decisions.
A Google Shopping feed audit compares source product data, generated feed output, Merchant Center received attributes, Shopping destination eligibility, affected-products CSV diagnostics, and public product page evidence before changing campaigns or feed rules.
The Google Shopping feed audit focuses on Merchant Center and Shopping ads eligibility. The broader product feed audit covers cross-channel feed ownership across Shopify, WooCommerce, feed apps, supplemental feeds, product pages, and reviewed snapshot routing.
If eligible item count, disapprovals, affected CSV rows, or Merchant Center received attributes are unclear, audit the feed evidence first. Change campaigns only after the feed owner and item state are known.
Yes. Start with the free Feed Truth report and identifier checker. Request a reviewed snapshot only when diagnostics, CSV rows, feed output, source exports, and public product pages disagree.
Start by proving what Google received for the Shopping destination before changing campaigns, bids, feed rules, or app settings. The free Feed Truth workflow helps separate source catalog, generated feed, Merchant Center diagnostics, and public product-page evidence.