10 Common Google Merchant Center Errors and How to Fix Them

Issue 1

Products pending initial review.

Products can sit in pending initial review when Google is checking the item, landing page, website, account, and product data. This is especially stressful because the product may look technically correct in the feed but still not be eligible to show.

Why it happens

• The Merchant Center account is new or recently changed.
• The product, feed, landing page, or website has changed materially.
• Google needs to review policy, shipping, price, availability, or destination settings.
• The landing page is blocked, slow, inconsistent, or difficult for Google to crawl.

How to fix it

Check that the product page is live, crawlable, consistent with the feed, and clear about price, availability, shipping, returns, and product claims. Avoid repeatedly resubmitting low-quality changes. If the account and product data are clean, use the relevant Merchant Center guidance on product data requirements to confirm the basics, then wait for review or request help when the delay is outside the normal review window.

Do not keep changing product titles, descriptions, or feed settings just because the status feels stuck. That can reset your own troubleshooting trail and make it harder to know which change actually helped. Instead, check the product page, shipping, account settings, policy information, and feed diagnostics in a structured order. If several new products are pending at once, look for an account-level or feed-level pattern before treating each product as a separate problem.

Issue 2

Missing or invalid GTIN.

GTIN problems are one of the most common Google Shopping feed errors. If a product has a manufacturer-assigned GTIN, it should be submitted accurately. Missing, made-up, reused, or incorrectly formatted identifiers can limit visibility or create warnings.

How to fix it

• Use the real GTIN from the manufacturer, barcode, supplier data, or product database.
• Do not invent GTINs or reuse the same identifier across unrelated products.
• Check that variants use the correct identifiers for the exact product.
• Use MPN and brand where GTIN is not available but the product still has manufacturer identifiers.

GTIN cleanup should be based on the best source data available, not guesswork. For brand-name products, the correct identifier usually comes from the manufacturer, supplier feed, product packaging, or an internal product information system. For multipacks, bundles, refurbished products, and variants, check that the identifier describes the product being sold on the landing page, not a related parent item or a different pack configuration.

Google's GTIN attribute documentation is worth linking because it explains why valid identifiers help Google understand and classify products. It also makes clear that merchants should not submit invented identifiers.

Issue 3

Incorrect identifier_exists.

The identifier_exists attribute tells Google whether a product has unique product identifiers such as GTIN, brand, or MPN. It should not be used as a shortcut to hide missing identifiers when the product actually has them.

When identifier_exists = no makes sense

• Custom-made goods.
• Private label products with no manufacturer-assigned identifiers.
• Vintage, handmade, or one-off products where standard identifiers genuinely do not exist.

How to fix it

Audit products where identifier_exists is set to no. If the product has a valid GTIN, brand, or MPN, submit the identifier instead. Keep identifier_exists = no for products where identifiers genuinely do not exist.

This is one of the easiest errors to make during a rushed feed cleanup. If identifier_exists is set to no across a large catalogue, Google may receive the wrong signal for products that do have real identifiers. Use Google's identifier_exists documentation to confirm when the attribute is appropriate, then build a rule that separates custom or private-label products from products with manufacturer identifiers.

Issue 4

Price mismatch.

Price mismatch happens when the price in the feed does not match the price Google finds on the landing page. It can come from sale prices, variant pages, currency differences, tax handling, structured data, or delayed feed updates.

How to fix it

• Make sure the feed price and landing page price match for the exact variant.
• Check sale_price, sale dates, currency, tax, and regional pricing.
• Update the feed more often if prices change frequently.
• Check structured data so Google sees the same price as shoppers.

Price mismatch is often a timing problem rather than a simple typo. A promotion may start on the website before the feed updates, a sale may end in the feed before the landing page changes, or a variant selector may show a different default price from the item submitted to Merchant Center. For stores with frequent promotions, compare your feed against Google's product data specification, then fix the issue with cleaner sale_price rules, faster feed refreshes, and better structured data.

Issue 5

Availability mismatch.

Availability mismatch means the feed says one thing and the product page says another. A common example is a feed marking an item as in stock while the website shows out of stock.

How to fix it

Synchronise inventory updates between the ecommerce platform, product feed, and website. Pay special attention to variants, low-stock products, preorders, backorders, and products with multiple fulfilment locations. If stock changes quickly, update the feed more often.

For fast-moving catalogues, availability errors can keep returning even after individual products are fixed. The better fix is to shorten the gap between inventory changes and feed updates, especially for high-volume products, clearance items, and products fulfilled from multiple locations. Also check Google's availability and product data rules against how preorder and backorder states appear on the website, because those statuses need to be represented consistently in the feed and on the landing page.

Issue 6

Missing shipping settings.

Google needs to understand delivery cost and shipping eligibility before it can confidently show products. Missing shipping settings can block products or reduce listing quality in markets where shipping data is required.

How to fix it

• Set up account-level shipping settings in Merchant Center where possible.
• Use shipping attributes when product-level shipping differs by item, weight, location, or service.
• Check country, currency, delivery service, delivery time, and minimum order thresholds.
• Review shipping after changing warehouses, carriers, markets, or ecommerce platforms.

Shipping errors become more likely when a store sells bulky items, regional products, restricted products, or products with different delivery services. Account-level rules are easier to maintain, but product-level shipping data may be needed when some items have different rates, countries, delivery times, or service requirements. Google's shipping attribute documentation is a useful reference when product-level shipping needs to be submitted in the feed.

Issue 7

Missing required attributes.

Missing required attributes can stop products from showing. Missing recommended attributes can also reduce data quality, filtering, matching, and performance, especially in categories like apparel, homewares, electronics, and auto parts.

Attributes to check

• Core fields such as title, description, link, image_link, price, availability, brand, and identifiers.
• Variant fields such as item_group_id, color, size, material, pattern, gender, and age_group.
• Category-specific fields such as capacity, dimensions, condition, energy efficiency, or compatibility.

Use the Google Merchant Center product data specification as the source of truth, but prioritise the attributes that matter most to your categories and your performance gaps. The goal is not to fill every optional field for every product at once. Start with required attributes, then add recommended attributes that improve product matching, filtering, variant clarity, and shopper confidence.

For example, apparel feeds usually need stronger variant data than a simple homewares catalogue. Electronics may need model, compatibility, condition, and technical detail. Furniture may need material, dimensions, colour, and delivery information. The product data specification tells you what Google expects; your category strategy tells you which attributes are worth fixing first.

Issue 8

Poor product titles.

Poor product titles can make eligible products harder to match and less attractive to click. Many ecommerce titles are written for product pages, not Shopping results, so they miss product type, brand, material, size, colour, model, compatibility, or pack size.

How to fix it

• Put the product type or main search term near the front.
• Add important attributes where they help shoppers choose.
• Keep titles readable and accurate.
• Avoid stuffing, promotional text, all caps, and unsupported claims.

For deeper examples, use the Google Shopping Title Optimization Guide.

Issue 9

Wrong Google product category or product type.

Google can classify products automatically, but weak product data can make classification harder. Poor product types can also make reporting, segmentation, and campaign management messier.

How to fix it

Review the highest-value categories first. Improve titles, descriptions, product types, brand, GTIN, and category signals before manually overriding every Google Product Category. Use product_type to describe your catalogue in a way that is accurate, consistent, and useful for reporting.

A messy product_type structure can also make performance analysis harder. If one product group uses Shoes > Running, another uses Footwear > Trainers, and another uses only Sale, campaign and reporting decisions become less reliable. Keep product_type values consistent enough to support segmentation, but specific enough to describe how shoppers actually compare the products. For the broader cleanup process, use the Google Shopping Feed Optimization Guide.

Issue 10

Misrepresentation or account suspension.

Misrepresentation is more serious than a normal feed warning. It usually means Google sees a trust, transparency, policy, or claims problem. This can affect the whole account, not just one product.

What to check

• Clear business identity, contact details, and customer support information.
• Transparent returns, refunds, shipping, payment, and checkout information.
• Product claims, pricing, promotions, and availability that match the website.
• No misleading urgency, unsupported health claims, fake trust badges, or unclear ownership.

Fix the underlying issue before requesting a review or appeal. If the same policy warning comes back, look beyond the feed and review the full site experience. Google's misrepresentation policy guidance is especially useful here because the fix may involve business transparency, checkout clarity, product claims, or customer support information rather than a normal feed attribute.

Prioritise fixes

Fix blocking Merchant Center errors before optimisation work.

Not every Google Merchant Center error has the same commercial impact. Some errors stop products from showing at all. Others reduce data quality, limit matching, or make Shopping ads less competitive. A good troubleshooting process fixes eligibility first, then moves into product data quality and performance improvement.

Use this order of operations

• Blocking errors: Fix disapprovals, policy warnings, account suspension, crawl problems, missing shipping, and product review delays first.
• Mismatch errors: Fix price, availability, landing page, and structured data mismatches next because they can keep coming back if the feed and website update at different speeds.
• Identifier errors: Clean up GTIN, brand, MPN, and identifier_exists values so Google can understand the exact products you sell.
• Attribute gaps: Fill required and commercially useful recommended attributes by category, especially for variant-heavy products.
• Performance improvements: Improve product titles, product types, descriptions, and category signals after the products are eligible and stable.

This sequence matters because fixing product titles will not help much if the product is disapproved, pending review, missing shipping, or showing the wrong price. Eligibility creates the floor. Feed quality creates the upside.

Use Google Help docs as the rulebook, then diagnose your actual feed. The docs explain what Google expects; your feed audit shows which products are affected, which source system is sending the wrong value, whether the ecommerce platform or feed app is overriding it, and whether the error will return after the next sync.

Checklist

Google Merchant Center error checklist.

1. Check whether the issue is product-level, feed-level, website-level, shipping-related, or account-level.
2. Confirm that price and availability match the exact landing page variant.
3. Review GTIN, brand, MPN, and identifier_exists values.
4. Check required and recommended attributes by category.
5. Review shipping settings and product-level shipping attributes.
6. Improve weak product titles, product types, and category signals.
7. Check landing page crawlability, structured data, and policy information.
8. Fix trust and transparency gaps before requesting policy review.
9. Increase feed update frequency for fast-changing price or inventory data.
10. Run regular feed audits so recurring issues are caught earlier.

Related guides

Use these guides when the error points to a deeper feed quality or Shopping performance problem.