Playbook

Playbook: products disapproved in Google Merchant Centre

Fix products that show disapproved status in Google Merchant Centre by diagnosing the specific rejection reason, correcting source data or feed rules, and implementing validation checks to prevent recurrence.

6 min read 22 views Updated 19 Jul 2026

No results found

Try different keywords or browse all help articles.

    Symptom: products showing disapproved status

    Your products were exporting to Google Merchant Centre successfully, but now one or more show a disapproved status. Alternatively, a newly exported product is immediately disapproved upon arrival at Google.

    When a product is disapproved, Google will not display it in Shopping results. This blocks visibility and prevents sales, even though the product exists in your feed and the export completed without errors.

    Disapproval is different from a feed import failure. Your feed is importing correctly, but Google's review process has rejected individual products for policy or data quality reasons.

    Diagnosis: common causes of product disapproval

    Use this checklist to identify which issue is affecting your products.

    Missing or invalid GTIN

    Many product categories require a GTIN (Global Trade Item Number), also known as a barcode, UPC, or EAN. If the GTIN field is empty, invalid, or incorrectly formatted, Google will disapprove the product. Check whether your product category mandates a GTIN and whether your source data contains a valid code.

    Image fails Google's requirements

    Product images must meet specific technical standards. Google rejects images that are too small (below 100 x 100 pixels), too large (above 64 megapixels), in unsupported formats, or contain watermarks or logos that obscure the product. Images must also show the product clearly without excessive text or promotional overlays. See playbook-product-images-rejected-by-a-channel for full requirements.

    Price or availability mismatch

    Google compares the price and availability in your feed against what appears on your landing page. If the feed states a price of £25 but your website shows £30, or if the feed says the product is in stock but your page says it is out of stock, Google will disapprove the product to protect user trust.

    Policy violation for the product category

    Some product categories have strict policies. For example, certain health, beauty, financial, or restricted goods categories prohibit specific claims, images, or descriptions. If your product data violates these category rules, Google will reject it.

    Broken or non-resolving product URL

    The link field in your feed must point to a valid, accessible product page. If the URL is broken, returns a 404 error, redirects incorrectly, or requires authentication to view, Google cannot verify the product details and will disapprove it.

    Fix: step-by-step resolution

    Step 1: Access the diagnostics view

    Log into Google Merchant Centre. Navigate to the Products section and select the destination (Google Shopping, Google Ads, or whichever channel is showing disapprovals). Click on the Diagnostics tab.

    The Diagnostics view lists all disapproved products and shows Google's specific rejection reason for each one.

    Step 2: Note the disapproval reason

    Read Google's message carefully. It will state the exact reason, such as 'Missing GTIN', 'Image too small', 'Price mismatch', 'Policy violation', or 'Landing page not accessible'.

    If multiple products are disapproved, you may see several different reasons. Note each one.

    Step 3: Cross-reference against the diagnosis checklist

    Match Google's stated reason against the checklist above. This confirms which source data field is causing the problem.

    Step 4: Correct the source data or apply a feed rule

    You have two options.

    Option A: Fix the source data directly. Open your product database or spreadsheet. Locate the affected product and correct the field that Google identified. For example, add a valid GTIN, replace the image with one that meets Google's size requirements, update the price to match your website, or fix the product URL. Re-export the feed.

    Option B: Apply a targeted feed rule. If you cannot change the source data immediately, use your feed management tool's rule engine to fix the field at export time. For example, you can create a rule that appends a GTIN from a lookup table, resizes or swaps out an image, adjusts a price, or rewrites a URL. This approach is useful if your source data is correct but needs transformation for Google's specific requirements.

    Many merchants use Option B as a temporary measure while Option A (fixing the source) is being implemented.

    Step 5: Trigger a fresh export

    After you have corrected the data or applied the rule, initiate a new feed export. Do not wait for a scheduled export; export manually to speed up the fix cycle.

    Step 6: Confirm the disapproval has cleared

    Return to the Diagnostics view in Google Merchant Centre. The product should no longer appear in the disapproved list.

    Note that Google has its own review timeline. In most cases, the product will be re-evaluated within 24 to 48 hours. During peak periods, review may take longer. Do not re-export repeatedly; one fresh export is sufficient.

    Once Google approves the product, it will become eligible for Shopping ads and organic Google Shopping results.

    Prevention: avoid disapprovals in future

    Enable feed validation

    Configure your feed management tool to validate products against Google's requirements before export. Validation rules should check for missing or invalid GTINs, image dimensions and format, price format, URL accessibility, and category-specific policies.

    Validation catches errors before they reach Google, allowing you to fix them locally. Many merchants use validation to quarantine non-compliant products and alert the team to review them.

    Review product quality scores regularly

    Most feed tools provide a product quality score or health dashboard. This shows which products have missing fields, invalid data, or potential policy issues. Review these scores weekly or monthly. Fix low-scoring products proactively rather than waiting for Google to disapprove them.

    A product with missing GTIN or a broken URL will show a low quality score long before it reaches Merchant Centre. Addressing these gaps early prevents disapprovals.

    Audit landing pages for price and availability accuracy

    Set a schedule to spot-check your website. Pick a sample of products and verify that the price and availability shown on your landing page match what is in your feed. If your e-commerce platform updates prices or stock levels dynamically, ensure your feed export captures the current state.

    Maintain a policy compliance checklist

    For each product category you sell in, document Google's policies. Keep a checklist of prohibited claims, restricted images, or content rules. Review new products against this checklist before they are added to the feed.

    Summary

    Products disapproved in Google Merchant Centre are blocked from Shopping visibility until the underlying issue is resolved. The fix starts with reading Google's specific disapproval reason in the Diagnostics view, identifying which source data field is at fault using the diagnosis checklist, correcting that field or applying a feed rule, exporting again, and confirming the disapproval has cleared.

    Prevention relies on feed validation to catch errors before export and regular product quality reviews to surface gaps early. These practices reduce the frequency of disapprovals and keep your product feed healthy.