Google Merchant Center errors in 2026: how to fix suspensions and save Shopping ROAS

If your Shopping campaigns are underperforming, the problem is often not the campaign at all. It starts in Google Merchant Center: bad identifiers, policy flags, inconsistent prices, weak shipping data or a site that looks untrustworthy to Google’s reviewers. In our audits, feed and policy issues explain roughly 60–70% of poor Shopping results before bidding strategy even becomes the bottleneck.

The three disapprovals that hurt most

In 2026, the most expensive Merchant Center problems are still the same three: invalid or missing GTINs, misrepresentation, and price mismatch between feed and landing page. GTIN issues suppress product visibility. Price mismatches trigger item disapprovals and can escalate to account-level warnings. Misrepresentation is the dangerous one: if Google believes your site hides key business information, exaggerates claims or shows inconsistent checkout terms, suspension can happen fast and appeals get harder.

• GTIN problems: wrong code length, reused identifiers, fake placeholders like 0000000000000;
• Misrepresentation: missing contact details, unclear returns, impossible claims, hidden fees, inconsistent domain branding;
• Price mismatch: feed says €49.99, landing page shows €54.99 after variant selection, geo change or structured-data lag;
• Shipping/tax gaps: final cost in checkout differs from Merchant Center settings;
• Availability mismatch: feed says in stock, page says out of stock or backorder.

Why Shopping ROAS starts in the feed, not the campaign

A clean feed improves more than approval rate. It affects query matching, auction confidence and click quality. Titles with brand + product type + core attribute usually outperform generic titles by 10–25% on click-through rate in catalog accounts. Correct GTINs help Google map products to the right knowledge graph entities, which improves relevance. Accurate price, shipping and availability reduce wasted clicks from users who bounce when checkout reality differs from the ad. That is why two stores with the same bids can have very different ROAS: one is buying traffic to a trustworthy product record, the other is paying to expose inconsistencies.

The fastest way to improve Shopping performance is often not raising bids — it is removing reasons for Google to distrust your catalog.

How to fix a suspension without making it worse

The common mistake is appealing too early. If you request a review before the root cause is fixed everywhere, you waste reviewer trust and often lock yourself into a slower second review cycle. A better process is: identify the exact policy in Diagnostics, audit the full site and feed against that policy, document every fix, then appeal once with evidence. For misrepresentation, reviewers check business identity signals across the whole site: company name, address, phone, returns, delivery times, payment methods, refund terms, and whether promotions look realistic. We tell clients to assume a human reviewer will compare homepage, product page, checkout and policy pages in under five minutes.

• Step 1: export Diagnostics issues by item and by policy, not just screenshots;
• Step 2: fix sitewide trust signals first — contact page, legal entity, returns, shipping, payment, refund policy;
• Step 3: fix feed-level errors in primary feed and resubmit;
• Step 4: recrawl key landing pages and test final price/availability as a normal user;
• Step 5: appeal once, with a concise summary of what changed and where.

Feed hygiene rules that prevent repeat disapprovals

Good Merchant Center accounts run on routine, not heroics. Schedule feed fetches at least daily if price or stock changes often; high-turnover catalogs may need 2–4 updates per day. Use automatic item updates where possible, but do not rely on them as a substitute for feed accuracy. Keep structured data aligned with the feed, especially price, currency and availability. Standardize titles, product types and image rules. If variants exist, make sure color, size and item group IDs are consistent. For branded products, GTIN should be present whenever it exists; setting identifier_exists to no for products that clearly have a GTIN is one of the easiest ways to trigger avoidable issues.

When supplemental feeds save the account

Supplemental feeds are underused. They are ideal when the main ecommerce platform cannot easily enrich titles, custom labels, sale prices, shipping attributes or excluded destinations. Instead of rebuilding the primary feed, you can patch weak fields on top of it. In practice, we use supplemental feeds to add margin tiers, seasonality labels, title improvements, and temporary corrections while a development fix is pending. That reduces time-to-recovery from weeks to days. Just remember: supplemental feeds can improve data, but they cannot hide policy violations on the site itself.

• Use supplemental feeds for title rewrites, custom labels, sale windows and missing attributes;
• Do not use them to mask landing-page problems Google can still crawl;
• Map by stable ID and document ownership so fixes do not get overwritten by the platform;
• Review merge rules after every catalog update or migration.

The 2026 prevention checklist

Before scaling Shopping spend, run a monthly prevention check. Verify that legal business details are visible and match payments and invoices. Test five random products from ad click to checkout and compare feed price, shipping and availability with what a user sees. Validate GTIN format and uniqueness. Check image quality and policy compliance. Review Diagnostics trends, not just current errors: repeated warnings are often the precursor to suspension. For stores above 1,000 SKUs, assign one owner for feed quality and one for site policy compliance; when nobody owns both, issues bounce between teams and stay unresolved.

• Business identity visible: company name, address, email, phone, returns, shipping, refund policy;
• Feed synced daily or more often if prices/stock change quickly;
• Structured data matches landing pages and Merchant Center attributes;
• GTINs valid where available; no fake placeholders;
• Random checkout tests passed for price, shipping and availability;
• Supplemental feed used for controlled enrichment, not emergency chaos;
• Appeals submitted only after fixes are fully live.

The practical rule for 2026 is simple: treat Merchant Center as a compliance and data-quality system first, an ad channel second. If the feed is clean and the site is credible, Shopping usually becomes easier to scale. If not, no bidding strategy will rescue ROAS for long. The survival guide is boring on purpose: accurate identifiers, consistent prices, transparent policies, disciplined feed updates and one clean appeal when needed. That is what keeps products serving and revenue stable.