VizupCommerce
shopify

Shopify Google Merchant Center Feed Audit: Fix Product Data Before You Advertise

Tej•
#shopify#google merchant center#product feed#google shopping#product data

Shopify brands can reduce avoidable Merchant Center feed failures by reconciling product data, landing pages, variants, prices, availability, shipping, and policies before promoting a catalog.

Google Merchant Center is not only a connection between Shopify and Google Ads. It is another representation of your catalog, and Google compares important parts of that representation with the product page shoppers reach. A feed that synchronizes successfully can still contain incomplete identifiers, an unavailable variant, an incorrect price, or a shipping promise your checkout cannot support.

This audit is for Shopify performance and social-commerce leads who need to decide whether a product set is ready for Google Shopping, free listings, or a Performance Max campaign. It is not a promise that approved products will receive traffic or sales. The goal is a defensible product-data handoff that gives shoppers the same offer wherever they encounter it.

If the audit exposes a product-page clarity problem, continue with the Shopify product-description workflow. If the feed is ready but campaign measurement is not, use the Shopify Meta Pixel setup guide as a separate tracking check.

What the audit should decide

By the end, each in-scope product or variant should have one clear status:

Shopify’s Google & YouTube channel syncs eligible products and relevant store information with Google Merchant Center, but products still need the required product data before they can be published on Google.[1][2] Treat the channel as a delivery path, not as a substitute for catalog governance.

Start with one commercial scope

Do not begin by exporting the entire catalog and trying to fix every row at once. Define a bounded scope that has a real commercial job:

Record the scope before making changes:

FieldMerchant decision
MarketWhich country or region should this offer serve?
Product setWhich products, variants, or collection are included?
Commercial jobFree listing discovery, Shopping ads, or a named campaign?
Price conventionWhich currency and tax-display convention should shoppers see?
Fulfillment promiseWhich shipping service, cost, and delivery expectation is actually available?
OwnerWho fixes Shopify data, channel settings, pages, and approvals?
Decision dateWhen will the team decide ready, fix, hold, or monitor?

A narrow scope makes it possible to compare the source product, the submitted data, the rendered page, and the customer-facing checkout without hiding exceptions in a catalog average.

Build a product-data handoff

Create one row per promoted variant when the offer, price, availability, color, size, or landing page can differ. The row should point to the source of truth rather than becoming a second catalog maintained in a spreadsheet.

CheckShopify source to inspectCustomer-facing result
IdentityProduct title, vendor, SKU, barcode, and variant IDThe product and exact variant are unambiguous
ClassificationShopify product category and relevant category attributesThe item can be classified for its intended Shopping surface
DescriptionProduct description and channel preferencesThe ad or listing describes the same item as the landing page
MediaFeatured image and variant mediaThe image shows the product the shopper will receive
OfferPrice, compare-at price, sale state, currency, and quantity rulesThe displayed price is understandable and available to the intended shopper
AvailabilityInventory by variant and sales-channel availabilityThe page does not advertise an unavailable option
DeliveryShipping zones, profiles, rates, handling, and transit settingsThe delivery promise matches checkout and the channel
TrustContact details, refund policy, terms, and relevant product policiesA shopper can verify who sells the item and what happens after purchase

Shopify identifies Google product category and unique product identifiers as core product requirements. Products with a GTIN need that identifier; products without one may need a brand and MPN instead.[1] For apparel and accessories, additional fields such as age group, gender, color, and size may apply.[1]

Do not fill missing values with guesses. A barcode field is not automatically a valid GTIN, a supplier name is not necessarily the customer-facing brand, and an internal color nickname may not match the value shown on the product page. If the team cannot establish the value, mark the row for review instead of creating a plausible-looking feed.

Reconcile the landing page, not only the export

Open representative product URLs from the feed or channel export and compare them with the submitted rows. The important question is not “did the sync run?” but “what will Google and the shopper see when the link opens?”

Check each sampled page for:

Google says it crawls landing pages and compares the submitted price with the page or structured data. If the values do not match, the product may be disapproved.[3] It also documents price and availability mismatches between product data and landing pages as a reason for preemptive item disapproval.[4]

This is where many Shopify-specific failures become visible. A sale can change the storefront before the feed updates. A theme or app can expose stale structured data. A variant can be present in the feed while the landing page opens with a different option. A geo or currency rule can cause Googlebot to receive a different price from the one used in the data source.

When the page and feed disagree, keep the product on hold until the source of truth is clear. Do not “solve” a price mismatch by editing only the downstream listing if Shopify will overwrite it on the next sync.

Audit price and availability as one promise

Price and stock are not independent metadata fields. Together they answer whether a shopper can buy the advertised offer under the terms shown.

Price checks

Compare the price in Shopify, the submitted price, the visible page price, structured data, and checkout conditions. Pay special attention to:

Google recommends matching product data to the landing page and keeping price and availability current through automated delivery, the Merchant API, or structured data where appropriate.[7] Automatic item updates can help with some discrepancies, but they are a safety net, not a replacement for one reliable source of truth.[4]

Availability checks

For each promoted variant, record:

  1. the inventory state in Shopify;
  2. the value sent to Merchant Center;
  3. the state shown on the landing page;
  4. the state available at checkout; and
  5. the owner of the next inventory or sync check.

For fashion, a product can be in stock while the advertised size and color are not. For beauty, a shade can sell out while the parent product remains available. For made-to-order goods, “available” may be accurate only when the delivery promise and production capacity are represented honestly.

Do not use a parent-product stock state as proof that every advertised variant can be purchased. The landing page should make the selected offer understandable before the shopper commits.

Check shipping, tax, and policy readiness

A product can have complete product attributes and still fail the customer-facing promise because delivery or business information is incomplete. Shopify requires store policies and visible contact information for the Google & YouTube channel, and shipping information can be required for offers in supported markets.[1]

Review the shipping path at the same market and product scope you chose at the start:

Shopify documents automatic shipping import when the store meets the channel’s conditions; otherwise, merchants may need to configure shipping manually in Merchant Center.[1] Google also instructs merchants to reconcile shipping costs when the submitted amount differs from checkout.[6]

Keep the product on hold when the only way to make the feed look attractive is to promise a lower shipping cost or faster delivery than the store can fulfill. A compliant listing that sends a shopper into a contradictory checkout is not a successful handoff.

Triage diagnostics by owner

Use the diagnostic reason and affected product rows to assign the next action. Avoid treating the top-level error count as the diagnosis.

Diagnostic signalFirst questionLikely next action
Missing GTIN or MPNIs the product identifier known and valid for this item?Add the verified identifier or document the brand/MPN path in Shopify or the channel
Price mismatchWhich value differs: Shopify, feed, page markup, visible page, or checkout?Fix the source and sync timing, then recheck the rendered page
Availability mismatchIs the promoted variant actually purchasable?Reconcile inventory, variant selection, and channel availability
Missing shippingIs shipping configured for the target country and product?Import supported settings or configure Merchant Center deliberately
Landing-page errorDoes the submitted URL resolve to the exact product?Fix the URL, availability, redirect, crawl, or page-load issue
Policy or trust issueCan the store show clear contact and customer-policy information?Fix the customer-facing page and review the applicable policy before requesting review
Warning without disapprovalWhat could become an item-level or account-level problem if ignored?Assign an owner and monitor the affected product group

Google distinguishes warnings, disapprovals, and preemptive item disapprovals. Disapproved products stop showing across Google surfaces, while warnings can limit performance and may lead to disapprovals if unresolved.[5] Use that distinction to prioritize, but do not ignore warnings simply because a product is still visible.

Fix the underlying source before requesting a review. Google’s troubleshooting guidance expects merchants to correct the product data or landing page and then submit the relevant review or website check.[3][4]

Use a repair record

A repair record keeps the team from repeatedly fixing symptoms in the wrong system. For every issue, capture:

For a fashion campaign, the record might show that the feed contained a black medium jacket while the landing page opened on a sold-out blue small variant. For a beauty campaign, it might show that a shade-specific image and price were submitted while the page defaulted to the parent product. For a broader merchant, it might show that a free-shipping threshold was available in Shopify but absent from the submitted shipping configuration.

The examples are not universal failure rates or platform benchmarks. They are prompts for finding the mismatch that a shopper would experience.

Measure readiness with guardrails

Choose one primary readiness metric before you change the catalog. A useful internal metric is the number of in-scope offers with a verified status and a named owner, divided by the total number of in-scope offers. Record the denominator, market, product set, and date so the result can be compared after the repair work.

Pair that measure with protective checks:

Do not use approval status as a proxy for revenue. A product can be technically eligible and still have weak demand, an uncompetitive offer, poor creative, or a page that does not answer the shopper’s question. Conversely, a product with a feed error should not be judged by campaign performance until the data issue is understood.

Before launching the campaign

Before sending the product set to a campaign or expanding the sync, confirm:

Use a shared agreement between the Shopify catalog, the customer-facing product page, the fulfillment promise, and the channel that distributes the offer to judge feed audit; a one-time export cleanup alone is not enough. Start with the products that have a clear commercial job, fix the source that owns each mismatch, and expand only when the handoff remains truthful under real shopper conditions.

Sources

[1] https://help.shopify.com/en/manual/online-sales-channels/marketplaces/google/requirements [2] https://help.shopify.com/en/manual/promoting-marketing/create-marketing/google/syncing-products [3] https://support.google.com/merchants/answer/12159029?hl=en [4] https://support.google.com/merchants/answer/9773429?hl=en [5] https://support.google.com/merchants/answer/13693497?hl=en [6] https://support.google.com/merchants/answer/10248678?hl=en [7] https://support.google.com/merchants/answer/7380908?hl=en

← Back to Blog