Fixing Merchant Center Errors: The Most Common Causes and Their Solutions

Understand Error Classes Before You Change Anything

The Merchant Center displays problems in three severity levels. They look similar but have completely different consequences – and confusing them leads to incorrect prioritization.

• Rejection. The product cannot be delivered. It does not appear in Shopping results and generates no impressions. Highest priority.
• Warning. The product continues to run, but loses quality: poorer categorization, missing formats, restricted placements. Medium priority, but often the bigger lever in the aggregate.
• Limitation. The product is only approved for certain target markets, programs, or formats. Important if you are advertising cross-border.

Equally important is the level at which a problem arises:

• Account level. Website requirements, return and contact information, policy violations. A single account problem can shut down the entire product range – so always check this first.
• Feed or product level. Missing attributes, invalid values, price or availability discrepancies. Affects individual products or product groups.

The Most Common Errors – Cause, Fix, Control

The following eight cases cover most messages in practice. For each point, you'll find what the real cause usually is, what you need to change, and how to verify that the fix has taken effect.

1. Missing or Invalid GTIN, MPN, or Brand

Cause: For branded products, Google expects a valid GTIN. Often, the EAN is in the wrong field, contains spaces or hyphens, has an incorrect checksum, or the GTIN of the manufacturer's carton is submitted instead of the sales unit.

Fix: Submit the GTIN as a pure sequence of digits (8, 12, 13, or 14 digits). For private label and handmade products without a barcode, provide `brand` plus `mpn` and set `identifier_exists` to false – but only where applicable, not across the entire feed.

Control: After the next feed fetch, the number of affected items will decrease; in the product view, the GTIN will be marked as valid.

2. Price Does Not Match Landing Page

Cause: The most common reason for rejection. Typical triggers: the feed is older than the last price change, discounts only apply in the shopping cart, the feed contains a net price and the page shows a gross price, or currency and target market do not match.

Fix: Always provide the final price including taxes, in the currency of the target market, and update the feed more frequently than you change prices. Sale prices belong in `sale_price` with a period, not as an overwrite of the regular price. Discounts only visible at checkout are not a price for Shopping.

Control: Open the product URL in an incognito window and compare the price displayed there with the feed value – including the target country and language.

3. Availability Discrepancy

Cause: The feed reports `in_stock`, but the page shows “unavailable” – or vice versa. This is often due to infrequent inventory synchronization, variants that are individually sold out, or structured data on the page containing an old status.

Fix: Update inventory at least daily, more frequently for fast-moving assortments. Structured data on the product page must show the same status as the feed. Report sold-out variants correctly as `out_of_stock` instead of removing them.

Control: Sample five high-demand items: feed status, page display, and structured data must match.

4. Missing Shipping Costs and Delivery Times per Target Market

Cause: When selling to multiple countries, often only the home market is fully configured. Missing shipping information does not always lead to rejection, but it reduces visibility – and if the displayed costs differ from checkout, rejection follows.

Fix: Store shipping costs, handling, and transit time for each target country. Accurately represent free shipping above a minimum order value instead of generally providing 0. For highly divergent items, set `shipping` at the product level.

Control: For each target market, run a test item through checkout and compare the displayed shipping costs.

5. Image Problems

Cause: Placeholder or logo images, promotional overlays like “Sale” or watermarks, resolution too small, image URLs blocked by robots.txt, or images that were unreachable at the time of the crawl.

Fix: Use product images without text, borders, and promotional graphics, with sufficiently large dimensions (at least 250 px, significantly more recommended) and stable, publicly accessible URLs. Provide additional views via `additional_image_link`, not as the main image with an overlay.

Control: Call the image URL directly in the browser; after the next crawl, the message will disappear. Note: Image rejections often require a new crawl and do not resolve with just the feed upload.

6. Missing Mandatory Attributes per Category

Cause: In areas like apparel, Google expects additional information – size, color, age group, gender – and a common `item_group_id` for variants. If these are missing, products are rejected or poorly categorized.

Fix: Map attributes from shop data instead of freely filling them in the feed. Group variants using a common `item_group_id` so that sizes and colors do not compete against each other as individual products.

Control: Filter by category in the product overview and check if the attribute columns are comprehensively filled.

7. Policy Rejection

Cause: Prohibited or restricted products, trademark issues, misleading information, or phrasing in the title that sounds like advertising – capitalization, exclamation marks, “Free,” price information in the title.

Fix: Construct titles factually: brand, product, most important characteristics. Remove promotional additions and special characters. For restricted categories, check in advance whether delivery is even permissible and in which target markets – and only then request a review.

Control: After correction, initiate a new review and await the status, instead of sending multiple small changes consecutively.

8. Website and Account Requirements

Cause: Missing or incomplete information on returns and withdrawals, no accessible contact details, no valid certificate, a checkout that is not accessible without login, or an unverified domain.

Fix: Keep return, shipping, contact, and impressum information complete and publicly accessible, verify and claim the domain, make checkout testable without registration.

Control: These errors affect the entire account – after the fix, the number of deliverable products usually normalizes within a few days.

Error Message, Cause, Fix – The Overview

This table helps with quick assignment when you have a message and are unsure where to start.

In What Order You Fix Things

Error lists are long, working hours are limited. Therefore, the order determines the effect – not the number of messages processed.

1. 1Account issues first. Website and policy problems can affect the entire product range. A single fix here outweighs a hundred individual corrections.
2. 2Rejections by revenue share. Sort affected items by revenue or margin from recent weeks and start from the top. Ten strong products beat a thousand long-tail items.
3. 3Systematic causes before individual cases. If three thousand items show the same message, it's due to mapping, not the product. Correct the rule instead of individual items.
4. 4Warnings with quality impact. Missing attributes and weak titles don't stop delivery, but they impact categorization and click-through rate.
5. 5Long-tail last. Everything that together accounts for less than one percent of revenue is dealt with collectively in one pass.

Checklist for Monthly Feed Hygiene

Anyone who goes through these points once a month will have resolved most rejections before they cost revenue.

• Review rejections and warnings by quantity and by revenue share, not just by quantity.
• Price and availability sample of five to ten important items per target market.
• Check shipping and delivery times for each target country against the actual checkout.
• Check mandatory attributes per category for completeness, especially for new assortments.
• Inspect new product images for overlays, placeholders, and accessibility.
• Review titles and descriptions of bestsellers for factual phrasing.
• Control feed update and last successful fetch – otherwise a silent breakdown might go unnoticed for weeks.
• Cross-check target markets: Are all countries you sell to also activated?

Typical Errors When Fixing

Not every fix is progress. These four patterns ensure that problems recur or new ones arise.

• Blanket feed rules. Setting `identifier_exists = false` for the entire feed solves the message but simultaneously damages the product matching for all branded items.
• Only correct in the supplemental feed. A Supplemental Feed is ideal for additions, but if price or availability remains incorrect in the shop, the rejection will return.
• Not waiting for re-indexing. Multiple consecutive corrections before the last status has been checked make the cause untraceable.
• Diagnostics as the only source. The overview shows what Google objects to – not what revenue is tied to it. Only linking it with your revenue data provides a priority.

Keeping Product Health Permanently in View

Feed hygiene is not a project, but a state. That's why monitoring belongs where your product data is already submitted for auction: at the CSS level.

At csspartner.io, you see product health across all target markets in the portal – rejected items, warnings, and their development over time. Typical gaps are supplemented or corrected via the Fix Center, without you having to rebuild the feed for every single case.

The advantage for the CPC is an added bonus: via a Google CSS, you enter the auction with up to 20 % more bidding power for the identical budget – at a fixed price of £17 per month, with no setup fee and no minimum contract term. A clean feed and cheaper clicks work in the same direction: more deliverable products that cost less per click.

Frequently Asked Questions about Merchant Center Errors