Why this page exists
The opportunity library contains repeated Shopify-to-Google sync problems, while exact search demand is fragmented. This page turns the problem into a count and source-path diagnosis instead of a generic feed article.
Diagnose Shopify products not syncing to Google Merchant Center by comparing product count, variant count, channel inclusion, Google & YouTube app status, feed app exports, affected rows, and last fetch evidence.
Products are active or eligible in Shopify, but Merchant Center has no matching items, no Content API data source, or a lower item count.
Send store URL firstPresent but disapprovedThe product exists in Merchant Center, but diagnostics mention disapproval, limited performance, price, availability, image, link, identifier, or policy issues.
Group diagnosticsAffected CSV rowsYou have a Merchant Center affected-products CSV and need row-level routing before bulk edits.
Group affected rowsBarcode to GTIN mismatchShopify variant barcode is filled, but Merchant Center still reports missing GTIN, invalid GTIN, duplicate identifier, or identifier_exists issues.
Open barcode evidence routeFeed/GMC owner mapShopify rows, feed app mappings, diagnostics, and public product URLs disagree, but you want to start with store URL before sending private exports.
Send store URL firstThe opportunity library contains repeated Shopify-to-Google sync problems, while exact search demand is fragmented. This page turns the problem into a count and source-path diagnosis instead of a generic feed article.
Shopify merchants, agencies, and store operators using Google & YouTube, Content API, supplemental feeds, or feed apps for Merchant Center.
A Shopify-to-GMC sync problem can belong to channel inclusion, feed ownership, identifier rows, public product proof, or account-level evidence. Pick the path that matches the mismatch you can prove.
Shopify active products, eligible variants, Google channel state, GMC item count, and last fetch timing do not line up.
Send store URL firstIdentifier row cleanupThe affected-products CSV mentions invalid GTIN, missing identifiers, MPN, brand, barcode, duplicate identifiers, or identifier_exists.
Group identifier rowsGCR or merchant trust contextFeed sync is not the only Google channel issue: GCR program state, checkout trigger, policy pages, or merchant proof also look unclear.
Check Google channel trust evidenceSuspension or appeal overlapThe sync problem appears beside account review, disapprovals, policy warnings, appeal history, or merchant trust evidence.
Build the suspension evidence packFeed/GMC owner mapShopify export, feed mapping, GMC diagnostics, affected CSV rows, and public product URLs give different answers.
Send store URL firstThe report connects each visibility problem to crawl evidence, AI answer samples, competitor risk, and a concrete repair step.
If Shopify and GMC counts disagree, the first repair is source inclusion and feed ownership, not item-level copy changes.
Merchant Center rules and supplemental feeds can override correct Shopify data, so every mismatch needs a source-path note.
Start with the Shopify-to-GMC feed truth report. It compares Shopify catalog count, eligible variants, Google channel inclusion, GMC item count, affected-products CSV rows, feed app ownership, and last fetch timing before you edit product identifiers or Merchant Center rules. No private product export, feed screenshot, or affected CSV is required for the first store-URL pass.
Use this packet when products are missing, stuck pending, stale after edits, or counted differently between Shopify and Merchant Center. The goal is to prove the owner before changing identifiers, feed rules, or app mappings.
Shopify source catalog, Google & YouTube app, feed app, Content API, GMC rule, or public product proof
Run the Feed Truth report and identifier checker when the evidence is public or easy to export
Use the 1-page Feed/GMC owner map when screenshots, CSVs, feed mappings, and product URLs disagree
This proves whether the product should be eligible before Google or a feed app receives the row.
This proves what Google received, not just what Shopify says should exist.
This prevents editing Shopify fields when a downstream mapping or override owns the submitted value.
This captures buyer-visible evidence Google may use for product, trust, or policy interpretation.
Store URL:
Primary symptom: products missing / stale after edits / pending / count mismatch / affected CSV rows
Date range or last edit window:
Shopify active product count:
Shopify eligible variant count:
GMC total items / active items / disapproved items:
Feed owner: Google & YouTube app / feed app / Content API / scheduled feed / unknown
Last feed fetch time:
Content API or data source present?:
Affected-products CSV issue groups:
Sample offer_id or SKU rows:
Public product URLs that disagree:
What changed recently: app, market, feed rule, product edit, theme, checkout, policy, or account reviewShopify community threads often describe the same problem with different words: missing products, pending Google channel rows, stale Merchant Center values, or a count mismatch. Treat each wording as a routing clue before editing barcodes, titles, or feed rules.
First compare Shopify active products, eligible variants, Google channel inclusion, Content API or data source presence, GMC total items, and last fetch. If the count path disagrees, use the Feed Truth reviewed intake before item-level edits.
If the product exists in Merchant Center, this is not a pure sync problem. Export affected-products rows and group the exact diagnostics before changing Shopify source fields.
Treat this as a connection and ownership problem first: confirm the expected Merchant Center account, Google & YouTube app connection, data source, destination country, and whether another feed app owns the submitted rows.
Check Google & YouTube app status, market eligibility, publication errors, Content API ownership, and whether a feed app has taken over submitted rows.
Compare last product edit time, feed fetch time, supplemental feed overrides, Merchant Center rules, and feed app mapping before assuming Shopify failed to sync.
Move affected rows into the GMC identifier checker when the evidence mentions GTIN, MPN, brand, barcode, duplicate identifiers, or identifier_exists.
Treat this as a mapping proof problem, not a promise that Shopify failed. Compare variant barcode, Google & YouTube app status, feed app GTIN mapping, Merchant Center final attribute, and one public product URL before bulk editing barcodes.
The reliable order is source catalog, channel eligibility, feed owner, Merchant Center received state, then item-level diagnostics. If that order is skipped, teams often rewrite GTIN or feed rules while the product never reached GMC correctly in the first place.
Start with Shopify product status, active variants, markets, product URLs, barcode, vendor or brand, inventory, and whether the product is eligible for Google.
Check Google & YouTube app status, sales-channel inclusion, app errors, product approval state, and whether a third-party feed app or Content API owns the submitted row.
Compare GMC item count, active items, disapproved items, limited-performance rows, feed name, destination, countries, and last fetch time against Shopify.
Only then group invalid GTIN, missing identifiers, MPN, brand, identifier_exists, price, image, availability, and link problems.
Use the free tools when the evidence is visible and structured. Move to a reviewed snapshot when private screenshots or CSV rows need a second pass before bulk edits, support escalation, or a focused audit.
Good enough when the question is count gap, channel inclusion, feed app owner, last fetch timing, or obvious feed source mismatch.
Best when the sync issue narrows to affected-products rows with GTIN, MPN, brand, barcode, or identifier_exists decisions.
Useful when Shopify export rows, feed app mapping, GMC diagnostics screenshots, and public product pages disagree.
Needed when sync mismatch overlaps with Merchant Center account review, policy warnings, misrepresentation evidence, or appeal history.
Use the smallest workflow that can prove the owner. A count issue should not become a bulk identifier rewrite unless the source path has already been checked.
| Workflow | Best for | Evidence required | Next action |
|---|---|---|---|
| Feed sync fix page | Understanding whether a missing product problem is count, channel, feed owner, or item-level | Visible symptoms, broad count gap, app state, affected issue names | Choose the matching route |
| Feed Truth report | Product count mismatch, stale fetch, feed app ownership, Content API source conflict | Shopify export, GMC item count, feed name, last fetch time, diagnostics screenshot | Open /tools/shopify-to-gmc-feed-truth-report |
| Identifier checker | Invalid GTIN, missing identifiers, MPN + brand, duplicate barcode, identifier_exists | GMC affected-products CSV plus Shopify product or variant export | Open /tools/gmc-product-identifier-error-checker |
| Reviewed Google Truth Snapshot | Cross-system evidence conflict before bulk edits or support handoff | CSV rows, diagnostics screenshot, feed mapping screenshot, product URLs, policy proof | Request review from the Feed Truth tool |
The page organizes evidence and likely ownership. Google and the feed provider still control processing, policy status, and final item eligibility.
Common causes include products not published to the Google channel, unsupported markets, variant mapping gaps, Google & YouTube app errors, feed app filters, supplemental feed overrides, or Merchant Center diagnostics.
Only after the product count path is explained. If hundreds of eligible products never reach Merchant Center, fix sync ownership before item-level GTIN, MPN, or brand cleanup.
Collect Shopify product and variant exports, Google channel status, GMC item count, affected-products CSV, feed name, last fetch time, and any feed app mapping or rule screenshots.
Use a reviewed snapshot when Shopify exports, feed app mappings, Merchant Center diagnostics, and public product URLs disagree, or when the next step affects many products.
Start with the Shopify-to-GMC feed truth report. It compares Shopify catalog count, eligible variants, Google channel inclusion, GMC item count, affected-products CSV rows, feed app ownership, and last fetch timing before you edit product identifiers or Merchant Center rules. No private product export, feed screenshot, or affected CSV is required for the first store-URL pass.