Google Merchant Center errors stop your products from appearing in Google Shopping, suppress impression share across active campaigns, and in serious cases suspend your entire account. Every disapproved product is a product that earns zero impressions and zero revenue from Google’s paid and organic surfaces. The good news is that most errors follow predictable patterns with clear fixes. This guide covers how to diagnose errors in Merchant Center Next, the most common disapproval causes, and exactly what to do to resolve them and prevent them from recurring.
Merchant Center errors costing you impressions you should be winning?
We audit Google Shopping feeds and Merchant Center accounts for ecommerce brands and resolve feed errors before they compound into account-level problems.
The Quick Take
| Error Severity | What It Means and What Happens |
|---|---|
| Critical (Red) | Product or account disapproved due to policy violation. Zero impressions until fixed and reviewed. |
| Warning (Yellow) | Products continue serving but performance is limited. Unresolved warnings escalate to disapprovals. |
| Informational (Blue) | Status updates and improvement suggestions. No immediate action required but worth monitoring. |
| Account Suspension | All products disabled across Google. Requires policy fix plus manual review request to reinstate. |
| Preemptive Item Disapproval (PID) | Google proactively disapproves products when feed data likely mismatches website. Requires review to resolve. |
The Takeaway: Merchant Center errors exist on a severity spectrum — the faster you catch and fix warnings, the less likely they escalate into disapprovals or account suspensions that take days to recover from.
💡 Pro Tip: Do not trust the top-level disapproval count in Merchant Center without clicking through to individual products. Google sometimes resolves issues behind the scenes while the dashboard still shows the original error count. Dig into each flagged product individually before making feed changes or contacting support — many reported disapprovals are already resolved.
Table of Contents
→ How to Diagnose Merchant Center Errors
→ Price and Availability Mismatch Errors
→ Image Errors and How to Fix Them
→ Missing Required Attribute Errors
→ Policy Violation Disapprovals
→ Shipping and Tax Errors
→ Account Suspension: What to Do
→ How to Prevent Merchant Center Errors Going Forward
→ The Bottom Line on Fixing Google Merchant Center Errors
→ FAQ: Common Questions About Google Merchant Center Errors
How to Diagnose Merchant Center Errors
Every Merchant Center error lives in the Diagnostics tab, and that is always the first place to go when campaign performance drops without an obvious cause. In Merchant Center Next, navigate to Products and select the Needs Attention tab. This view shows every product with an active issue, filterable by impact level, status, and issue type. Google also provides an Issue Details Page for each error type that shows affected products, estimated lost click potential, and specific resolution steps.
Download the full affected items list as a CSV before making any changes. This gives you a complete picture of scope before you start fixing. A single feed error often affects hundreds of products simultaneously, and knowing the full count before you begin helps you prioritize by revenue impact rather than fixing errors randomly.
One critical workflow note: turn off the Prioritized Fixes toggle in the Needs Attention view to see all issues. By default, Merchant Center hides low-impact issues and only surfaces the highest-priority problems. That default is useful for triage but creates blind spots for accounts that want complete feed health visibility. Turn the toggle off periodically to catch smaller issues before they compound. After fixing any error, resubmit your feed and allow 24 to 72 hours for Google to process and review the changes before checking whether the disapproval cleared.
Price and Availability Mismatch Errors
Price and availability mismatches are the most common disapproval trigger in Google Merchant Center, and they are entirely preventable with proper feed sync. Google’s crawler compares your feed data against your live product pages continuously. When the price in your feed differs from the price on your website, or when your feed shows a product as in stock while your page shows it as sold out, Google flags the mismatch and disapproves the product.
The most dangerous version of this error is Preemptive Item Disapproval (PID), where Google proactively disapproves products it predicts will have a mismatch based on historical patterns in your account. PID disapprovals require a manual review request to resolve, even after you fix the underlying data issue. Accounts with repeated price mismatch history trigger PID more easily, which is why keeping feed data consistently accurate matters for account health beyond individual product disapprovals.
| Mismatch Cause | Fix |
|---|---|
| Sale ended but sale_price still in feed | Always pair sale_price with sale_price_effective_date so expired sales auto-remove. Never leave stale sale prices in the feed manually. |
| Feed price differs from schema markup price on page | Match feed price, on-page displayed price, and structured data schema markup exactly. All three must agree. |
| Availability value not recognized by Google | Google accepts only: in stock, out of stock, preorder, backorder. Any other value causes disapproval. Map all custom inventory statuses to these four values. |
| Feed refreshes too slowly for fast-moving inventory | Enable automatic item updates in Merchant Center settings. This allows Google to update price and availability from your page directly when feed data lags. |
💡 Pro Tip: Enable automatic item updates in Merchant Center as a safety net, but do not rely on it as your primary sync method. Automatic updates reduce disapprovals from temporary mismatches, but they introduce a dependency on Google’s crawler being able to read your page correctly. A properly structured feed with daily or real-time sync is still the most reliable foundation.
Image Errors and How to Fix Them
Image errors are the second most common cause of product disapprovals and one of the most avoidable with a proper image hosting setup. Google requires product images that accurately represent the item, meet minimum resolution standards, and contain no promotional overlay text, watermarks, or placeholder graphics. The recommended image size is 1,500 by 1,500 pixels. Images smaller than 100 by 100 pixels trigger automatic disapproval.
The most frustrating image error is a broken image URL, where the image_link attribute points to a file that returns a 404 or has moved. This happens silently after site migrations, CDN changes, or product catalog restructures. Test every image URL before launching any campaign and run a periodic audit using an HTTP status checker to catch broken links that develop after initial setup. A broken image URL disapproves the product immediately with no warning period.
| Image Error | Fix |
|---|---|
| Promotional text overlay on image | Enable automatic image improvements in Merchant Center. Google will attempt to remove overlays automatically. Replace manually if the automatic fix fails. |
| Image URL returns 404 or error | Host images on a reliable CDN. Run HTTP status checks on image URLs monthly. Update the feed immediately after any site migration that moves image file locations. |
| Image too small or low resolution | Replace with a minimum 250 by 250 pixel image. Target 1,500 by 1,500 for best ad placement eligibility. Never use placeholder or development images on live products. |
| Generic or non-representative image | Use a product-specific image for every SKU. A lifestyle image shared across variants that look different will trigger disapproval for misrepresentation. |
💡 Pro Tip: Use the lifestyle_image_link attribute to add a secondary contextual image alongside your primary white-background product shot. This does not affect disapproval risk and boosts CTR in competitive categories. The primary image_link must remain a clean product shot. The lifestyle image goes in the separate attribute field.
Missing Required Attribute Errors
Missing required attributes generate immediate product disapprovals with no warning period. Google requires a specific set of attributes for every product before it enters the Shopping auction. If any required field is absent or formatted incorrectly, the product earns zero impressions regardless of how well everything else in the feed is optimized.
The most commonly missing required attributes are not the obvious ones like title and price. They are the ones brands forget to map in their platform integrations: condition, google_product_category, and GTIN. Condition defaults are often not set correctly in Shopify or WooCommerce Google channel integrations, leaving the field blank for products that should be marked as new. Google product category selections default to broad categories when merchants skip the taxonomy step, which reduces matching precision without triggering an outright disapproval but silently limits reach.
| Missing Attribute Error | Fix |
|---|---|
| Missing GTIN for branded product | Add the manufacturer barcode. For custom or private label products with no GTIN, set identifier_exists to false to signal the omission is intentional. |
| Missing or invalid condition value | Set condition to new, refurbished, or used for every product. Map your platform’s condition field to one of these three accepted values. |
| Missing shipping configuration | Configure shipping at the account level in Merchant Center first. Override at the product level using the shipping attribute only where specific products have different requirements. |
| Missing return and refund policy | Add a clearly accessible return and refund policy to your website footer and product pages. If you do not accept returns, state that explicitly. Missing policy causes account-level warnings. |
| Brand mismatch between feed and website | Ensure the brand attribute in your feed exactly matches the brand shown in your website metadata and product pages. For private label products, use your store name as the brand value. |
💡 Pro Tip: Use supplemental feeds to fix missing attributes across large catalogs without rebuilding your primary feed. A supplemental feed lets you override specific attribute values for targeted products — adding GTINs, correcting condition values, or updating google_product_category — without touching your main feed structure. This is the fastest way to fix attribute gaps at scale.
Policy Violation Disapprovals
Policy violation disapprovals are the most serious category of Merchant Center errors because they can escalate from individual product disapprovals to full account suspension. Google enforces strict policies around product content, business practices, and website transparency. Policy violations include prohibited products, misrepresentation of self or product, and misleading business practices. These errors require both a content fix and a manual review request before the disapproval clears.
The misrepresentation policy is the most commonly misunderstood. Google does not just flag false claims — it flags incomplete disclosure. A brand that does not clearly display contact information, a physical business address, return policies, and accurate delivery timelines on its website can receive a misrepresentation flag even if the products themselves are legitimate. Google treats unclear or inaccessible business information as a trust signal failure, and it disapproves the account rather than individual products in those cases.
For products in sensitive categories (supplements, skincare with health claims, certain electronics), review your product descriptions carefully. Language that implies medical benefits, exaggerates performance claims, or uses terminology Google associates with restricted categories can trigger policy disapprovals even on products that are entirely legal to sell. Rewrite descriptions to focus on product features and specifications rather than outcome claims, and remove any language that could be read as a health or safety claim.
After fixing a policy violation, navigate to the Needs Attention tab, find the affected products or account issue, and use the Request Review option. Google limits the number of reviews you can request per issue type, so fix the underlying problem completely before submitting. Submitting a review before the fix is in place wastes one of your review attempts. The review process typically takes three to five business days for product-level issues and longer for account-level suspensions. For a broader look at how feed quality connects to your Google Shopping strategy, see our complete Google Shopping strategy guide.
Shipping and Tax Errors
Shipping and tax errors are account-level issues that block all products from serving until resolved, not individual product disapprovals. Google requires that your shipping configuration in Merchant Center accurately reflects what shoppers see at checkout. Mismatches between the shipping costs shown in your ads and the costs presented at checkout violate Google’s accuracy policies and trigger account-level warnings that escalate to suspension if not resolved within the warning period.
The most common shipping error is missing shipping information entirely, which happens when brands launch campaigns without completing the account-level shipping setup in Merchant Center. Configure shipping at the account level first under Your Business, then Shipping and Returns. Changes take 24 to 72 hours to reflect across your account. Only after account-level shipping is configured should you use the shipping attribute in your feed to override costs for specific products with non-standard shipping requirements.
For US-based ecommerce brands, tax configuration in Merchant Center must reflect your actual tax collection practices by state. For brands selling internationally, the rules shift: EU and UK feeds require prices that include VAT, and the tax attribute itself has been phased out for those regions as of Google’s 2025 policy updates. If you sell across multiple regions, verify your regional pricing and tax setup matches current Merchant Center requirements for each market.
Account Suspension: What to Do
A Merchant Center account suspension disables every product across all Google surfaces simultaneously. Suspensions happen when Google determines that account-level policy violations are severe enough that individual product fixes are insufficient. Common suspension causes include widespread misrepresentation, repeated policy violations after previous warnings, and significant checkout or website trust issues that Google’s crawler identifies.
When your account is suspended, Google sends a notice identifying the violation category. Read that notice carefully before making any changes. The most common mistake after a suspension notice is making surface-level fixes — updating a few product descriptions or adding a return policy link — without addressing the root cause Google identified. Submitting a review before the fix is complete wastes a review attempt and delays reinstatement.
The reinstatement process requires fixing every flagged issue completely, then submitting a manual review request through the Merchant Center interface. Suspension reviews take longer than product-level reviews and Google does not provide specific timelines. While waiting, audit your website for transparency signals: visible contact information, accessible return and refund policies, accurate delivery timeframes, and checkout flows that match what your Shopping ads promise. These are the elements Google’s reviewer checks during reinstatement evaluation.
If you use a programmatic API connection to Merchant Center, also verify that your API integration is current. Brands still running on the legacy Content API should review their migration status given the August 18, 2026 shutdown deadline. Our Google Merchant API migration guide covers what that transition requires and how to check your current API status in Merchant Center.
How to Prevent Merchant Center Errors Going Forward
Most Merchant Center errors are preventable with three habits: weekly diagnostics checks, automated price and availability sync, and a feed quality audit cadence. Brands that check Merchant Center diagnostics once a month discover problems after they have suppressed impressions for weeks. Brands that check weekly catch disapprovals within days of them triggering and resolve them before they affect campaign performance significantly.
Set up automated price and availability sync through your platform integration or a supplemental feed that refreshes at least daily. Enable automatic item updates in Merchant Center as a backup layer. Neither replaces a properly maintained primary feed, but together they reduce the gap between your live website data and what Google’s systems see between scheduled feed refreshes.
Build a quarterly feed audit into your Google Shopping workflow. Review your top 50 products by revenue for title quality, attribute completeness, GTIN coverage, and image quality. Check for any new warnings in the Diagnostics tab that have not yet escalated to disapprovals. Verify that your shipping configuration and return policy pages still match what Merchant Center has on record. Catching small issues quarterly prevents the compounding effect of multiple minor problems combining into an account-level flag that triggers suspension.
The Bottom Line on Fixing Google Merchant Center Errors
Google Merchant Center errors are not random — they follow patterns, and fixing them permanently requires addressing the data quality and policy compliance issues that cause them, not just clearing the individual flags. Price and availability mismatches come from inadequate feed sync. Image errors come from poor hosting and missing audit routines. Policy violations come from website transparency gaps. Each category has a root cause, and the root cause is what needs fixing.
The urgency of resolution scales with severity. A warning gives you time to fix before escalation. A product disapproval costs you impressions daily until resolved. An account suspension costs you every product across every Google surface until Google completes its review. The fastest path to recovery is always fixing the underlying problem completely before requesting a review, not submitting an incomplete fix and hoping Google approves it.
Treat Merchant Center diagnostics as a weekly KPI alongside campaign performance metrics. Feed health is not a setup task — it is an ongoing operational discipline that directly determines how much of your campaign budget converts to actual impressions and revenue. The brands that run clean feeds consistently outperform brands with better bids and worse data.
🎯 Merchant Center Errors Suppressing Your Google Shopping Performance?
We audit Google Shopping feeds and Merchant Center accounts for ecommerce brands, identify every active error and root cause, and resolve them before they compound. Book a free 30-minute strategy call.
→ Book Your Free Feed Audit Call
Every disapproved product is impressions and revenue you are not capturing. Let’s fix that.
Frequently Asked Questions About Google Merchant Center Errors
What are Google Merchant Center errors?
Google Merchant Center errors are issues in your product feed or account that cause Google to disapprove products, limit their visibility, or suspend your account. They range from warnings that limit performance to critical errors that remove products from all Google surfaces entirely.
Where do I find Google Merchant Center errors?
In Merchant Center Next, navigate to Products and select the Needs Attention tab. This shows every product with an active issue. Turn off the Prioritized Fixes toggle to see all issues, not just the highest-priority ones. Download the full affected items list as a CSV to understand the full scope before making changes.
How do I fix a price mismatch error in Google Merchant Center?
Ensure that the price in your feed exactly matches the price displayed on your product page and in your website’s structured data schema markup. All three must agree. Enable automatic item updates in Merchant Center as a safety net, and set up daily or real-time feed sync to prevent future mismatches.
Why are my products disapproved in Google Merchant Center?
Products are disapproved when they violate Google’s Shopping policies or contain data errors. The most common causes are price or availability mismatches, image errors, missing required attributes like GTIN or condition, and policy violations related to product content or website transparency.
How long does it take Google to review a Merchant Center fix?
After submitting a fixed feed, allow 24 to 72 hours for Google to process and review the changes. Policy violation reviews and account suspension reinstatement reviews take longer and do not have a guaranteed timeline. Fix the underlying issue completely before requesting a review.
What is a Preemptive Item Disapproval in Merchant Center?
Preemptive Item Disapproval (PID) occurs when Google proactively disapproves products it predicts will have a price or availability mismatch based on historical patterns in your account. PID requires a manual review request to resolve even after fixing the underlying data issue.
How do I fix a Google Merchant Center account suspension?
Read the suspension notice carefully to identify the specific violation. Fix every flagged issue completely before submitting a review request. Common fixes include improving website transparency with clear contact information, return policies, and accurate delivery timeframes. Submit a review only after all issues are resolved.
What image requirements does Google Merchant Center have?
Google requires product images that accurately represent the item, contain no promotional text overlay or watermarks, and meet minimum size requirements of 250 by 250 pixels. The recommended size is 1,500 by 1,500 pixels. Images smaller than 100 by 100 pixels trigger automatic disapproval.
How do I fix missing GTIN errors in Google Merchant Center?
For branded products, add the manufacturer barcode as the GTIN value. For custom, handmade, or private label products that genuinely have no GTIN, set the identifier_exists attribute to false. This tells Google the omission is intentional and prevents the disapproval.
How often should I check Google Merchant Center for errors?
Check the Diagnostics tab weekly as a minimum. Brands that check monthly discover problems after they have suppressed impressions for weeks. Weekly checks catch disapprovals within days and allow resolution before errors compound into account-level issues.