If you've ever stared at the Merchant Center Diagnostics page wondering what "limited performance: price mismatch" actually means, this article is for you. These 12 errors account for roughly 90% of the disapprovals we see in customer audits. Each one has a specific trigger, a specific diagnostic path, and a specific 30-minute fix.

Google Merchant Center diagnostics dashboard showing product disapprovals and feed errors

Why Merchant Center Errors Cost You More Than You Think

Every unresolved product disapproval is a SKU that cannot appear in Shopping results. At scale, even a 5% disapproval rate across a catalog of 10,000 products means 500 products generating zero paid or organic Shopping impressions.

These 12 errors are the floor, not the ceiling โ€” feed-wide optimization in 2026 now also factors in AI Overview eligibility and quality scoring thresholds that determine whether approved products actually compete for top-of-page placement.

The errors below are ranked by frequency โ€” fix the top ones first and you will recover the majority of lost reach before touching the long tail.

Clearing these errors restores impressions, but if clicks still aren't converting after reapproval, the problem is likely downstream โ€” seven landing-page and feed defects account for the majority of sub-1% conversion rates we see across audited accounts.

If you want to pressure-test everything before touching individual errors, a structured 23-point feed audit surfaces all of the high-impact issues in a single session โ€” stores in our dataset that fixed just three of them moved ROAS by 18โ€“35% within two weeks.

The 12 Most Common Merchant Center Errors and How to Fix Them

1. Missing GTIN

The error: "Missing required field gtin" or "Limited performance due to missing GTIN".

What triggers it: branded products resellers must provide the GTIN (UPC/EAN/ISBN). Private label products can be exempted by setting identifier_exists to false, but most catalogs forget to do this.

Diagnose: Merchant Center โ†’ Products โ†’ Diagnostics โ†’ Filter: Issue = "Missing GTIN"

Fix:

  • Resold branded products: get the GTIN from your supplier or look it up on the manufacturer's site. Add it to the variant's barcode field in Shopify or the equivalent in your platform.

On Shopify, the fastest way to enrich these attributes without touching your theme is via metafields โ€” the Shopify feed optimization walkthrough maps exactly which fields correspond to each Merchant Center attribute and which ones ship raw by default.

  • Private label / handmade: set identifier_exists: false in your feed. In Shopify this is a metafield google.identifier_exists: FALSE.

Leaving GTIN blank without identifier_exists: false is the worst of both worlds โ€” you get a warning and lose the ranking benefit of having one. Set the flag explicitly.

Worth noting: the same GTIN and category attributes you're fixing here carry disproportionate weight inside Performance Max โ€” the 2026 PMax attribute priority guide identifies them as the top two machine-learning signals PMax uses for query matching.

On Shopify specifically, the official Google channel ships a minimal feed by default โ€” the Shopify feed setup guide covers exactly which attributes need to be enriched via metafields to avoid the recurring disapprovals described above.

Google's 2026 enforcement changes mean the identifier_exists: false exemption path is significantly harder to clear โ€” handmade and custom-goods sellers now face a 73% rejection rate on exemption requests that sailed through in 2025. If you sell handmade or custom goods, note that Google's 2026 enforcement has made the GTIN exemption landscape far harsher โ€” a 73% rejection rate on exemption requests means the identifier_exists: false path now requires supporting documentation most sellers don't have ready.


2. Incorrect Google Product Category

The error: "Product category not specific enough" or "Product mismatch with category".

What triggers it: your product is mapped to a too-broad category (e.g. "Apparel & Accessories" instead of "Apparel & Accessories > Clothing > Shirts & Tops > Dress Shirts").

Fix: open the product, set the full 5-level Google Product Category path. The taxonomy is published as a Google Sheet you can browse. Specificity matters โ€” 5-level paths rank 2โ€“3ร— better than 2-level on average.

Beyond individual error fixes, the attributes you enrich directly influence your feed's ranking signal โ€” Google's 2026 quality scoring now weights specificity in ways the feed ranking algorithm breakdown quantifies, including how category depth affects auction eligibility.

If fixing category mappings across hundreds of SKUs inside the primary feed is impractical, a Merchant Center supplemental feed can override the google_product_category attribute without touching your Shopify back-end.

A faster alternative to re-submitting your primary feed is patching these category assignments via a Merchant Center supplemental feed โ€” no back-end code required, and overrides propagate within the next fetch cycle.

One nuance worth flagging: supplemental feeds can accidentally override GTIN values the primary feed already handles correctly โ€” the primary vs. supplemental feed rules spell out exactly which attributes are safe to patch and which ones conflict.


3. Image Quality Issues

The error: "Image quality too low" or "Promotional overlay on image".

What triggers it:

  • Image resolution below 100ร—100 px for non-apparel or below 250ร—250 px for apparel
  • Watermarks, logos, or promotional text overlaid on the main product image
  • Placeholder or lifestyle-only images where a clean product shot is required

Fix:

  • Replace the image with a minimum 800ร—800 px clean product shot on a white or neutral background.
  • Remove all text overlays, badges, and watermarks from the primary image. These elements are permitted only in additional images.
  • Resubmit the feed after updating the image URL; Merchant Center will re-crawl within 24โ€“48 hours.

Example of compliant vs. non-compliant product image for Google Shopping feed


4. Price Mismatch

The error: "Limited performance: price mismatch" or "Mismatched price (page crawl)".

What triggers it: the price in your feed does not match the price Google's crawler sees on your landing page at the time of the crawl. Common causes include currency formatting differences, sale prices not reflected in the feed, and tax-inclusive vs. tax-exclusive discrepancies.

If price mismatches are appearing across multiple currency markets, the root cause is often upstream โ€” a single misconfigured feed pushed to multiple locales is the most common culprit, and multi-currency feed management covers the exact tax-formatting and currency-code rules that prevent cross-market disapprovals.

Fix:

  • Use structured data (schema.org/Offer) on your product pages so Google can read the price programmatically.
  • Ensure your feed price updates trigger a re-fetch โ€” use the Content API or a scheduled supplemental feed rather than waiting for the default 30-day refresh.
  • If you display tax-inclusive prices in certain locales, set price_with_tax alongside the base price attribute.

5. Missing or Invalid Product Title

The error: "Title too short", "Title missing key attributes", or "Title contains promotional text".

What triggers it: titles shorter than 25 characters, titles that omit brand, size, or color for variant products, or titles containing words like "Free shipping" or "Best price".

Fix:

  • Follow the format: Brand + Product Type + Key Attribute (color, size, material). Example: "Nike Air Max 90 Men's Running Shoe โ€“ White โ€“ Size 10".
  • Keep titles between 70โ€“150 characters for maximum indexing coverage.
  • Strip promotional language โ€” move it to the promotion_id attribute if you are running a Merchant Promotions campaign.

6. Unavailable Product Landing Page

The error: "Crawl of the landing page failed" or "Landing page not found (404)".

What triggers it: the link attribute in your feed points to a URL that returns a non-200 HTTP status โ€” most commonly because a product was deleted or unpublished without removing it from the feed.

Fix:

  • Audit your feed for dead links using a crawl tool or Merchant Center's Diagnostics URL report.
  • Implement feed automation that removes out-of-stock or deleted products from the feed within the same publish cycle.
  • Set up 301 redirects for discontinued products pointing to the closest category or replacement product, and update the feed link accordingly.

7. Incorrect Price Currency

The error: "Invalid value for attribute price" or "Currency mismatch".

What triggers it: the currency code in your feed does not match the target country's expected currency, or the price field uses a symbol (e.g. "$") instead of the ISO 4217 code (e.g. "USD").

Fix:

  • Always use ISO 4217 currency codes in feed values: 29.99 USD, not $29.99.
  • Verify that the feed's target country in Merchant Center matches the currency you are submitting.

8. Shipping Configuration Missing

The error: "Missing shipping" or "No shipping service configured for country".

What triggers it: Merchant Center requires at least one shipping service defined for every target country. If your account-level shipping settings are incomplete, all products inherit the error.

Fix:

  • Go to Merchant Center โ†’ Shipping and returns โ†’ Add shipping service.
  • Define carrier, rate table, or flat-rate rules for each target country.
  • Alternatively, pass shipping at the product level using the shipping attribute in your feed, which overrides account-level settings on a per-SKU basis.

9. Out-of-Stock Products Remaining Active

The error: Not a formal disapproval, but products with availability: out of stock that remain in the feed for more than 1 hour will cost you impressions during stock-outs.

Fix:

  • Use the Content API to push real-time availability updates rather than relying on scheduled feed fetches.
  • Set your feed fetch frequency to at least every 4 hours if you have high inventory turnover.
  • Consider temporarily setting excluded_destination for out-of-stock products to prevent impression waste.

10. Prohibited Content

The error: "Prohibited content" โ€” usually triggers on weapons, drugs, counterfeit, adult content, dangerous chemicals, or politically-themed merchandise.

What triggers it: any product touching Google's restricted content policies.

Fix:

  • If false-positive (e.g. a sportswear brand flagged for "weapons" because of a kickboxing glove), file a manual review request through Merchant Center โ†’ Diagnostics โ†’ Request review.
  • If your product genuinely falls in a prohibited category, you cannot advertise it on Shopping. Move it off Shopping and rely on other channels.

11. Missing Tax Configuration

The error: "Tax not configured for destination".

What triggers it: in the US, state-level tax configuration is required for each state where you have tax nexus. Merchant Center does not auto-detect nexus โ€” you must configure it manually or pass tax at the product level.

Fix:

  • Go to Merchant Center โ†’ Tax โ†’ Add tax rule for each applicable US state.
  • For international markets, verify whether the destination country requires VAT to be included in the feed price or declared separately.

12. Mismatched or Invalid Sale Price

The error: "Sale price higher than price" or "Invalid sale price effective date".

What triggers it: the sale_price attribute exceeds the base price, or the sale_price_effective_date range has already expired and was not removed from the feed.

Fix:

  • Always ensure sale_price < price by a meaningful margin โ€” Google's threshold is typically at least 5% below the base price.
  • Remove or update sale_price_effective_date as soon as a promotion ends. Automate this with your promotions calendar if possible.

How to Monitor and Prevent Merchant Center Errors Proactively

Firing fixes reactively after disapprovals accumulate is expensive. The following habits reduce the error rate before it affects campaign performance:

  1. Schedule weekly Diagnostics reviews. Merchant Center โ†’ Products โ†’ Diagnostics gives a filterable breakdown of all active issues by severity. Set a recurring calendar block to review it.
  2. Use feed rules or supplemental feeds for bulk fixes. Rather than editing your Shopify back-end for every attribute gap, use supplemental feeds to patch attributes like google_product_category, identifier_exists, and shipping at scale.
  3. Implement the Content API for real-time updates. Scheduled feed fetches lag by hours. The Content API lets you push price, availability, and attribute changes the moment they happen in your store.
  4. Track disapproval rate as a KPI. A healthy catalog maintains below 2% disapproval rate. If yours exceeds 5%, prioritize a full feed audit before increasing ad spend.

Addressing these 12 Merchant Center errors systematically โ€” rather than one at a time as they appear โ€” is the fastest path to a clean, fully eligible product catalog and maximum Shopping coverage.

Sources & References

  • Google Merchant Center Help โ€” Official documentation on the 'identifier_exists' attribute, supporting claims about when to set it to false for private label or handmade products and GTIN exemption rules.
  • Google Merchant Center Help โ€” Official Google documentation on the GTIN attribute requirements, supporting the article's explanation of when GTINs are required for branded resold products and how missing GTINs trigger disapprovals.
  • Google Merchant Center Help โ€” Official Google documentation on the google_product_category attribute, supporting the article's guidance on using specific 5-level taxonomy paths to avoid 'product category not specific enough' errors.

MagicFeedPro Team

Feed Optimization Practitioners

We're a team of e-commerce and paid-search practitioners who have spent the last decade running Google Shopping campaigns at scale. We write about what actually moves the needle on product feed quality, CTR, and conversion.

Related articles