Fixing Merchant Center Errors: Diagnosis and Solutions

by Francis Rozange | Apr 4, 2026 | Google Ads

erreurs-merchant-center-diagnostic-solutions-1

Fixing Merchant Center errors: diagnosis and solutions

A Google Ads account can be perfectly architected, well-funded, and aimed at the right audience, and still produce zero impressions on Shopping or Performance Max. The reason is rarely the bid strategy. It is the feed. When Merchant Center decides that a product is disapproved, an account is at risk, or a data source is stale, that decision propagates instantly to every downstream campaign. No feed, no Shopping. No clean feed, no Performance Max retail delivery. The lever is upstream of media buying.

This guide treats Merchant Center as the first system to debug when revenue collapses, not the last. It walks through the diagnostics dashboard structure, the item-level errors that appear in 80% of accounts, the account-level suspensions that take weeks to recover, the appeal process, and a practical priority order for fixing issues without burning a week on warnings that do not block delivery.

Why Merchant Center health gates everything else

Performance Max for retail, Shopping ads, free listings on the Shopping tab, YouTube Shopping, and the merchant knowledge panel all read from the same source: a Merchant Center feed in good standing. Google’s own documentation is explicit on this point. A disapproved product is not eligible to serve in any of those surfaces, regardless of campaign budget, bid, or creative quality.

The most common diagnostic mistake is to look at the Google Ads interface first when impressions drop. Performance Max in particular hides this trap well: the campaign keeps spending on text and asset combinations while the product feed is silently disqualified, so total spend looks normal while retail revenue collapses. Tinuiti’s analysis of disapproval recoveries shows that the average enterprise account loses 8 to 12 days of revenue before the team realizes the bottleneck is in Merchant Center, not in Ads.

The rule is simple: if Shopping impressions drop more than 20% in 24 hours, open Merchant Center before you open Google Ads. The diagnostic dashboard there will tell you in 90 seconds what an Ads-side investigation will not surface in three hours.

The diagnostics dashboard structure

Inside Merchant Center, the Diagnostics report is split into three tabs that each carry a different blast radius. Understanding the split is half the work.

Item issues

Item issues affect specific products, not the account as a whole. The dashboard shows the affected product count, the destination (Shopping ads, free listings, Buy on Google, local), and the country of sale where the issue applies. A single product can have multiple issues across multiple destinations, which is why the affected-item count rarely equals the disapproved-product count.

The granularity matters: a price mismatch on 2,000 SKUs in France is a feed problem, while a price mismatch on 4 SKUs is almost always a manual pricing edit that did not propagate. The first needs an integration fix, the second needs an inventory team email.

Account issues

Account issues affect the entire merchant account. They are the high-stakes column. Misrepresentation suspensions, suspicious payment behavior flags, untrusted business operation status, and unverified contact information all live here. A single account issue can suspend every product on every destination, instantly.

According to Search Engine Land’s coverage of suspension trends, the share of suspensions classified as “misrepresentation” rose sharply between 2022 and 2024 as Google tightened automated review thresholds. That category is now the single largest source of permanent merchant offboarding for small and mid-sized retailers.

Data quality

The data quality tab tracks structured issues that do not always block serving but degrade matching, ranking, and eligibility for enhanced placements. Missing GTINs on branded products, low-resolution images, generic titles, missing brand attributes, and unspecified product types appear here. Most are warnings rather than blocking errors. They will not stop your products from serving, but they will throttle the volume your products earn relative to a clean catalog.

The cost of ignoring data quality is invisible in any single report. DataFeedWatch’s annual feed benchmarks consistently show 20 to 40% impression uplift for catalogs that resolve all warnings versus catalogs that only resolve hard errors. The warnings tab is where the unglamorous, compounding gains live.

Item-level errors that appear in 80% of accounts

The same dozen errors generate most of the volume in Merchant Center support forums. Recognizing them on sight cuts diagnosis time from hours to minutes.

Price mismatch (price_microconsistency)

Google’s crawler scrapes your product page, extracts the price visible to a user (typically from JSON-LD structured data or visible price tags), and compares it to the price submitted in your feed. If the difference exceeds a tolerance threshold, the product is disapproved with the “Mismatched value” or “Price not consistent” error.

The frequent root causes: a price changed on the website but the feed sync runs every 24 hours, a discount applied at checkout is not reflected in the feed, a price displayed in the wrong currency, or VAT inclusion logic that differs between the page and the feed. The fix is to enable Automatic Item Updates in Merchant Center settings, which lets Google self-correct the feed price using the page price within a delta you authorize. Combined with a near-real-time inventory feed, this eliminates 90% of mismatch disapprovals.

Image issues (image_link_broken, image_too_small, promotional_overlay)

Image errors fall into three buckets: the URL does not return an image (404, 403, or non-image MIME type), the image is below the 100×100 pixel minimum (250×250 for apparel), or the image contains promotional overlays (text like “50% OFF”, watermarks, badges). The third is the most often overlooked because the image renders correctly on the website but violates the no-overlay policy.

Google’s image policy explicitly prohibits text overlays advertising prices, percentages, free shipping, or borders that frame the product. Many shops generate sale-banner images dynamically through their CMS or a marketing app, and those images become the primary product image without the merchandiser realizing it. Audit by spot-checking 20 random product image URLs from the feed in an incognito browser.

GTIN required (gtin_missing)

For products from a brand that exists in Google’s catalog database, GTIN is mandatory. The disapproval triggers when the brand attribute matches a known manufacturer (Nike, Apple, Sony, Bosch, etc.) but the gtin attribute is empty. Submitting a wrong GTIN is treated as harshly as omitting it: a 13-digit string that does not validate against the GS1 checksum will be rejected.

For private-label products, handmade items, vintage goods, and custom configurations, the gtin attribute can be omitted, but you must then submit identifier_exists set to false. The most common failure mode is leaving identifier_exists at its default while also leaving gtin empty, which Google interprets as a missing GTIN rather than as a no-GTIN-applicable case.

Product disapproved as misrepresentation (item-level)

Item-level misrepresentation flags trigger when Google’s automated review detects that the product page contradicts the feed. The classic patterns: a product titled “Authentic Apple AirPods” sold by a non-authorized reseller, a “free shipping” claim in the feed contradicted by a shipping fee at checkout, a price that requires email signup to unlock, or a product that requires multiple add-ons to function but is marketed as standalone.

This category is the slippery one. The error message is identical to account-level misrepresentation, but the consequence is local: only the affected products are disapproved, the account remains active. Catching item-level misrepresentation early matters because clusters of item-level flags are the precursor to an account-level suspension.

Missing identifiers (mpn_missing, brand_missing)

For products without a GTIN, Google still requires identifier_exists set to false, plus a brand and an MPN (manufacturer part number) when those are knowable. The fallback chain is: GTIN preferred, brand+MPN second, brand alone third for some categories. Generic titles like “T-shirt blue medium” with no brand and no MPN trigger reduced visibility flags rather than outright disapprovals, but the impression delta is significant.

Invalid landing page (link_broken, redirect_loop)

The crawler tries to fetch the URL submitted in the link attribute. It expects a 200 response within a reasonable time, with a product detail page rendered. Broken links produce immediate disapprovals. More subtle: redirects that loop, redirects to category pages instead of product pages, soft 404s (200 status with “product not found” content), and pages that require cookie acceptance before content renders.

The diagnosis tool: paste the link into the URL inspection feature inside Merchant Center, which will show what the crawler actually fetched. A page that renders fine in your browser but fetches as a soft 404 for Googlebot is the typical failure mode for sites with aggressive anti-bot rules.

Mobile landing page issues (mobile_landing_page_error)

Google fetches the product page with a mobile user agent independently of the desktop crawl. A site that renders correctly on desktop but throws a JavaScript error, an unhandled redirect, or a blocked viewport on mobile will be disapproved for mobile devices specifically. Store Growers’ troubleshooting series highlights this as the single most-overlooked error in 2024 audits, because the desktop preview in Merchant Center looks fine and the merchant assumes the page is healthy.

The fix uses the same URL inspection tool, with the device toggle set to mobile. If the rendered HTML differs significantly between desktop and mobile fetches, the issue is in the responsive layer, not in the feed.

Deprecated GTIN (gtin_obsolete)

A GTIN that was valid five years ago but has since been retired by GS1, reassigned, or marked obsolete will trigger a disapproval. This happens with products that have been on the catalog for a long time, especially in categories where manufacturers cycle through SKU numbers. The fix is to refresh the GTIN against the manufacturer’s current catalog, not to invent a replacement.

Sale price effective date issues

The sale_price_effective_date attribute uses an ISO 8601 interval format. Submitting a sale that ended yesterday, a sale that starts in 2027, or an interval with malformed timestamps will disapprove the product or strip the sale_price entirely. The merchandising team often sets these dates manually and forgets to remove them after a campaign, leaving stale dates that Google flags.

Shipping policy mismatches

If the shipping cost in the feed exceeds the shipping cost displayed at checkout by more than a small tolerance, Google flags it as misrepresentation. The reverse (feed shows free shipping, checkout charges) is treated more harshly because it surprises the consumer. Search Engine Journal’s deep dive on shipping configuration documents how flat-rate shipping, table-rate shipping, and carrier-calculated shipping each have to be configured in account-level shipping services to match the checkout reality.

Tax configuration errors

For US sellers, missing tax registrations or incorrect tax-on-shipping settings produce disapprovals at the state level. For EU and UK sellers, VAT-inclusive vs VAT-exclusive feed prices must match the page rendering. A feed submitting VAT-exclusive prices to a country expecting VAT-inclusive (or vice versa) will mass-disapprove.

Energy efficiency labels (EU)

For appliances and electronics in the EU, the energy_efficiency_class, min_energy_efficiency_class, and max_energy_efficiency_class attributes are mandatory for many product types. Missing or incorrect energy class data triggers disapprovals specific to the EU market while products continue serving in the US.

Account-level errors and recovery

Account-level issues are the ones that ruin a Black Friday. They are also the ones merchants most often misdiagnose, because the symptoms (no impressions, no clicks) are identical to bid issues, budget issues, or Performance Max algorithmic learning resets.

Suspicious payment behavior

This flag triggers when Google detects payment patterns it considers high-risk: unusually high refund rates, chargebacks above industry norms, declined transactions clustered in a way that looks fraudulent. The error message is generic, the resolution path is not.

The fix is procedural. Submit a request for review through the Merchant Center help center, attach evidence of legitimate operations: business registration, recent invoices, customer service logs, refund policy documentation. Google’s payment review team manually reviews. Average resolution time is 5 to 7 business days when the documentation is complete on first submission, longer when documents are missing.

Account suspension for misrepresentation

Misrepresentation is the hardest category to recover from. Once an account is suspended for misrepresentation of self or product, the typical path is: submit an appeal, get rejected, submit a more detailed appeal, get rejected again, work with a Google partner agency to escalate. Tinuiti’s recovery guide reports that fewer than 40% of misrepresentation suspensions are reversed on the first appeal, and roughly 15% are never reversed.

The triggers for misrepresentation are layered. Pricing pages that hide fees until checkout. Promotional claims that cannot be substantiated. Branded product sales by non-authorized resellers. Phone numbers that do not connect to a human. Business addresses that do not match the legal entity registration. Return policies that contradict the displayed information. Any of these can trigger the suspension, and the appeal must address all suspected causes, not just the one the merchant suspects.

Untrusted reputation

Google maintains a separate reputation signal that aggregates user feedback, third-party review platforms, BBB complaints, and consumer protection bureau filings. An account in good standing on technical attributes can still be flagged for untrusted reputation if external signals deteriorate. Recovery requires addressing the underlying reputation signals, not just submitting paperwork.

Invalid contact information

The business name, address, phone number, and email submitted to Merchant Center must match the public information on the website. Mismatches trigger an account-level flag. The fix is to align both sources: update the website footer, the contact page, the legal pages, and the Merchant Center business information settings to the same data.

Business operation verification

Newer accounts and accounts that change their business profile are required to verify business operations: phone verification, video verification of physical location, document verification of business registration. Verification timelines run 1 to 3 weeks. Accounts that fail to complete verification within the window are suspended for unverified business operation, which is recoverable but adds delay.

Suspicious payment, in detail

Suspicious payment deserves its own treatment because it is the most opaque suspension type. Google’s signal is composite: it considers chargeback rate, refund rate, dispute rate, transaction velocity, geographic distribution of buyers, payment method mix, and historical disputes against the merchant or the merchant’s processor.

The recovery checklist that produces the highest reinstatement rate, in observed practice: a clear PDF of the business registration, recent payment processor statements showing chargeback rates below the threshold the processor uses for high-risk classification, three months of customer service email logs showing how disputes are handled, and a refund policy document that matches what is published on the site. Submitting all of these in a single appeal, with a written narrative that walks through the policies and the evidence, doubles reinstatement probability versus submitting documents alone.

Misrepresentation suspension: the hardest to recover

The single most important rule: do not submit a casual appeal. Misrepresentation appeals are reviewed by humans, and they read every word. An appeal that says “I do not understand why I was suspended, please review” closes the case faster than an appeal that addresses every plausible cause.

The framework that wins: identify every possible misrepresentation trigger in the account (audit pricing transparency, promotional claims, business identity disclosure, return policy clarity, contact reachability), document remediation for each, and submit the audit with the appeal. The reviewer is looking for evidence that the merchant understood the policy, identified the issue, and fixed it. They are not looking for an explanation of why the suspension was unfair.

What loses appeals: blaming Google’s automation, claiming the suspension is a mistake without evidence, asking for clarification of the specific reason, sending the same appeal twice with different wording, escalating through an agency partner before exhausting the standard appeal process. What wins: a structured remediation document, before-and-after screenshots of the policy pages, a brief statement of accountability, and patience for the 5 to 14 day review window.

Warnings vs errors: the prioritization difference

Errors block serving. Warnings degrade serving. The difference matters because resolving a warning when a hard error exists is wasted time.

An error means the affected products will not serve in the affected destinations. Disapproved status, hard policy violation, missing required attribute. Until the error is resolved, those products generate zero impressions. Errors are urgent.

A warning means the products will serve, but with reduced visibility, lower ranking, or limited eligibility for enhanced placements. Missing GTIN, low-resolution image (above the minimum but below the recommended), short title, missing product type. The product still appears, it just appears less often or less prominently.

The math: an account with 200 errors and 5,000 warnings should fix the 200 errors first, even though the warning count is 25 times larger. Recovering one disapproved product to active is worth more than tightening data quality on 25 products that are already serving. The exception: if the warnings include conditions that are precursors to errors (like trending image quality issues that will eventually trip the policy threshold), preempting them has a payoff.

Feed health and Performance Max delivery

Performance Max for retail uses the Merchant Center feed as the primary asset source. Disapproved products do not enter the asset pool. Products with warnings are eligible but compete at a disadvantage. Search Engine Land’s reporting on Performance Max feed dependencies shows that accounts with disapproval rates above 5% see Performance Max delivery drop disproportionately, because the algorithm allocates spend to product groups that have enough eligible inventory to learn against.

The practical implication: a Performance Max campaign that loses delivery is often debugged in Merchant Center, not in the campaign settings. Check the disapproval rate by product group, identify groups where the disapproval rate exceeds 20%, and resolve those before adjusting bids or budgets.

Structured data debugging

When a price mismatch, availability mismatch, or product identifier issue persists after the feed has been corrected, the cause is typically structured data on the product page. Google reads JSON-LD product schema, OpenGraph tags, and microdata, and the data extracted from those sources can override or contradict the feed.

Rich Results Test

Google’s Rich Results Test renders the product page with a Googlebot user agent and shows the structured data that the crawler extracts. If the price field in the rendered structured data differs from the feed price, the page is the source of truth from Google’s perspective. The fix is on the page, not in the feed.

Schema.org Validator

The schema.org Validator checks the syntactic validity of the structured data. It catches missing required properties, malformed dates, currency codes that do not match ISO 4217, and product IDs that do not validate against expected formats. Pages that pass the validator but still produce mismatches are usually a content issue (e.g., the schema lists the regular price but not the sale price), not a syntax issue.

Manual feed-vs-page comparison

For stubborn cases, the diagnostic of last resort: open the product page in a browser, view the rendered HTML, find the structured data block, copy the price, availability, and identifier values into a spreadsheet next to the corresponding feed values, and look for differences. The mismatches that survive automated tools are often whitespace differences (a non-breaking space inside the price), encoding differences (a comma vs a period as the decimal separator), or unit differences (price per kilogram vs price per unit).

Priority order for fixes

The triage that minimizes recovery time, in order:

Account-level issues first. A single account-level suspension is worth more lost revenue than 10,000 item-level errors. Always.
High-volume item-level errors second. If 30% of the catalog is disapproved for a single error type, fixing the integration that produces it recovers more revenue than triaging individual SKUs.
High-margin item-level errors third. A disapproved bestseller is worth more than a disapproved long-tail product.
Long-tail item-level errors fourth. Bulk-fix what can be bulk-fixed, accept that some products will remain disapproved.
Warnings last. Resolve them in batches during slow periods. Never let warnings preempt error work.

The discipline that breaks this priority order: a stakeholder asks why a specific product is not appearing, and the team spends three hours on one SKU while the account-level issue continues to bleed revenue. Stay structural.

A 7-day diagnostics workflow for new accounts

For an account that has just been connected to Merchant Center, or for an audit of an account inherited from a previous agency, the workflow that surfaces all material issues in one week:

Day 1. Account-level issues review. Confirm verification status, contact information, business identity, payment configuration, shipping services, tax services. Resolve anything that is not green.
Day 2. Feed configuration audit. Confirm feed schedule, sync frequency, country and language targeting, primary feed vs supplemental feed structure. Confirm Automatic Item Updates is enabled if appropriate.
Day 3. Item-level error review. Sort by affected-item count, descending. Document the top 10 errors and their root causes.
Day 4. Sample URL inspection. Pick 20 disapproved products spanning the top errors and run each through the URL inspection tool. Identify whether the issue is feed-side or page-side.
Day 5. Structured data audit. Run the Rich Results Test on 10 representative product pages. Document any mismatches between page schema and feed.
Day 6. Warnings triage. Identify warning types affecting 10% or more of the catalog. Build a remediation plan.
Day 7. Documentation and ownership. Write a one-page summary of the issues, the fixes, and the responsible team for each. Schedule the recurring monthly check.

Recurring monthly check

Once an account is healthy, the cadence to keep it healthy is monthly, not weekly. Weekly creates noise; quarterly misses the slow-developing issues. The 30-minute monthly check:

Account issues tab. Confirm zero open issues. If new ones have appeared, treat as urgent.
Item issues tab. Review affected-item count by issue type. Compare to last month. Investigate any issue type with more than 50% growth in affected items.
Disapproval rate by product group. If any group exceeds 5%, drill in. If any group exceeds 20%, treat as a priority fix.
Feed sync log. Confirm the feed has refreshed on schedule. Look for skipped syncs.
Performance Max retail delivery. Compare current delivery to last month. If delivery is down 15% or more without a corresponding budget change, the cause is often feed health.

Documenting the monthly check in a shared report, with the same metrics each time, surfaces trends that a one-off audit will miss.

Common mistakes

The patterns that consume time and produce no recovery:

Treating Merchant Center as a Google Ads sub-feature. It is a separate product with separate policies, separate review processes, and separate support. Triaging Merchant Center issues from inside Google Ads diagnostics misses the relevant detail.

Submitting the same appeal twice. Reviewers see the duplicate. The second appeal is treated as a lower priority, not a higher one.

Fixing warnings while errors are open. The math is wrong. Errors block delivery, warnings degrade delivery.

Believing the feed is the source of truth when the page contradicts it. Google’s automated review treats the page as authoritative for price, availability, and identifier. Aligning the feed to a wrong page does not resolve the issue.

Disabling Automatic Item Updates because of a single bad correction. The feature recovers more revenue than it loses across any reasonable time window. The exception is high-velocity flash sales where price changes faster than the crawler can keep up; in those cases, a near-real-time inventory feed is the cleaner solution.

Ignoring mobile landing page errors because the desktop site looks fine. Mobile traffic is the majority of Shopping clicks for most categories. A mobile-only disapproval cuts the addressable audience by more than half.

Treating misrepresentation appeals as routine paperwork. Each appeal that fails reduces the probability the next one succeeds. The first appeal must be the strongest one.

Conclusion

Merchant Center is the substrate. The campaign architecture, the bid strategy, the creative work, the audience targeting all sit on top of it. When the substrate cracks, none of the work above it functions. The teams that win in retail Google Ads are the ones that treat feed health as a daily operational discipline, not as a quarterly hygiene exercise.

The diagnostic instinct to develop: when something stops working, open Merchant Center first. Account issues second. Item issues third. The cause is upstream of the symptom 80% of the time.