Fix Merchant Center errors: causes & fixes

Google Shopping strategies for more revenue, in your inbox

Every other week: what is changing in Google Shopping, what we see in our customers' accounts, and what to do about it.

Once price changes, empty stock levels or new required fields come into play, hardly any Merchant Center account stays error-free for long. Unnoticed rejections stop your listings appearing in Google Shopping and cost you clicks and revenue.

Tackle errors systematically: understand the error class, fix the cause in the shop or feed, and check the result after the next crawl.

This guide works through the most common errors one by one. With a Google CSS Partner, you can see your product health in the portal and close feed gaps in the Fix Center.

Understand the error classes before you change anything

Merchant Center splits problems into three severity levels, each with different consequences for delivery.

Rejection: the product stays invisible in Shopping results, with no impressions. Treat this case as the highest priority.
Warning: the product keeps running, but with restricted placements or weaker matching. This case has medium priority, but fixing it often has a big impact.
Restriction: the product is only approved for certain target markets, programmes or formats. This mainly affects cross-border sales.

Just as important is the level at which a problem occurs:

Account level: problems with website requirements, policies or return information can block your entire range. Check this level first.
Feed and product level: missing attributes, invalid values or wrong prices affect individual items or product groups.

Check the account level first, then rejections ranked by revenue impact, and warnings last. Working on warnings for low-value items brings little benefit early on.

Why Merchant Center Problems Are So Costly

Disapproved products cause a direct loss of revenue: no auctions, no impressions. The damage depends on the revenue share of the items affected. Three disapproved bestsellers often hurt more than 800 niche products.

Disapproval: the product gets pulled from Shopping. Check the affected revenue drivers first.
Account warning: this puts your entire range at risk and takes priority over individual cases.
Product-level warning: the product stays active but loses reach through weaker placements and fewer formats.
Restriction: the product is only approved for certain markets or programmes. This usually shows up in cross-border selling.

These eight errors show up most often

The following eight cases cover most reports. Each point explains the cause, the fix and the check that follows.

1. Missing or invalid GTIN, MPN or brand

Cause: Google requires valid GTINs for branded products. EANs often end up in the wrong field, contain spaces, use incorrect check digits, or come from the outer carton.

Fix: submit the GTIN as a plain string of digits with 8, 12, 13 or 14 characters. For items without a barcode, use the brand and mpn fields and set identifier_exists to false where appropriate.

Check: after the next feed fetch, the error count drops and the GTIN shows as valid in the product view.

2. Price doesn't match the landing page

Cause: price mismatches arise from outdated feeds, discounts only applied at checkout, differences between net and gross prices, or the wrong currency.

Fix: always submit gross prices in the target market's currency and update the feed regularly. Store promotional prices with a date range in the sale_price field.

Check: compare the feed value with the visible price on the product URL in an incognito window, matching the target country and language.

3. Availability doesn't match

Cause: mismatches between in_stock in the feed and the product page arise from infrequent syncing, sold-out variants, or outdated structured data.

Fix: update stock levels at least daily. Align structured data with the feed and mark out-of-stock variants with out_of_stock.

Check: for five in-demand items, check that the feed status, on-page display and structured data all match.

4. Shipping costs and delivery times missing per target market

Cause: incomplete shipping information for international markets costs visibility. If the shipping cost at checkout differs from the feed data, Google rejects the item.

Fix: provide shipping cost, handling time and delivery time for every target country. For items that differ, use the shipping attribute at product level.

Check: run a test item through checkout for every target market and compare the displayed shipping cost.

5. Image problems

Cause: placeholder images, logos, promotional graphics, low image resolution, robots.txt blocks, or unreachable image URLs.

Fix: use clean product images at least 250px on the shortest side, with stable URLs. Provide extra views via additional_image_link.

Check: open the image URL in a browser. Image rejections only clear after Google re-crawls.

6. Missing required attributes per category

Cause: for apparel, Google requires details on size, colour, age group and gender, plus a shared item_group_id for variants.

Fix: map attributes directly from your shop data. Group variants under a shared item_group_id to prevent internal bidding competition.

Check: filter the product overview by category and check the attribute columns for completeness.

7. Rejection due to policy

Cause: policy violations, trademark issues, misleading claims, or promotional elements in the title such as capitalisation, exclamation marks, "free" or prices.

Fix: build titles factually from brand, product and key attributes. For restricted categories, check eligibility in the target market beforehand.

Check: after correcting, trigger a new review and wait for the result.

8. Website and account requirements

Cause: incomplete returns and contact details, a missing certificate, guest checkout disabled, or an unverified domain.

Fix: publish complete details on returns, shipping, contact and company information. Verify the domain and enable guest checkout.

Check: account-level errors affect every item. The status usually returns to normal within a few days of the fix.

How to quickly make sense of an unfamiliar error message

This table helps you quickly interpret unfamiliar messages.

Message	Likely cause	Fix	Where to check
Price doesn't match	outdated feed, net instead of gross, discount only applied at checkout	final price including tax, update more often	product page in incognito mode
Availability doesn't match	stock sync too infrequent, outdated structured data	sync daily, align status on page and feed	feed status vs. product page
Missing GTIN	EAN in the wrong field or invalid	plain digit string; own-brand items use brand + mpn	product detail in Merchant Center
Image cannot be crawled	URL blocked, image temporarily offline	stable, public image URLs; check robots.txt	image URL directly in the browser
Promotional text in image	overlay, watermark, sale badge	neutral product image without graphics	shop's image library
Missing shipping information	target market not configured	add shipping cost and delivery time per country	shipping settings in the account
Missing size/colour attribute	category-required fields not mapped	map attributes from shop data, set item_group_id	product overview by category
Policy violation	promotional title, restricted category	keep title factual, check eligibility, request a review	account level / policies

Fixing errors in this order has the biggest impact

When time is tight, prioritising your error list carefully gets you the most out of it.

1Account issues first: website and policy problems affect your entire range. One central fix replaces hundreds of individual corrections.
2Rejections by revenue share: sort affected items by revenue or margin over recent weeks. Work on high-revenue products first.
3Systematic causes before individual cases: if messages appear across many items, fix the underlying feed mapping.
4Warnings with quality impact: missing attributes and weak titles worsen matching and lower click-through rate.
5Long tail last: handle items with less than one percent revenue share together in one batch.

Changes only take effect after Google re-reads the feed. Feed updates take hours; image and website issues can take a few days.

This monthly checklist prevents new rejections

A monthly review of these points catches revenue-damaging rejections early.

Rejections and warnings: assess messages by absolute count and by revenue share.
Price and availability spot check: check five to ten key items per target market as a sample.
Shipping and delivery times: match the settings for every target country directly against checkout.
Check required attributes per category for completeness, especially with new ranges.
Review images of new products for overlays, placeholders and reachability.
Check titles and descriptions of bestsellers for factual wording.
Check the feed's update status and last fetch time to catch silent failures early.
Check your target markets: are all active selling countries approved?

These four patterns create new problems while fixing old ones

Some fixes create new problems. These four patterns come up repeatedly.

Blanket feed rules: setting identifier_exists = false for the whole feed damages the matching of all branded items.
Correcting only in the supplemental feed: if the price or stock level in the shop is wrong, the item gets rejected again.
Not waiting for the next crawl: stacking several corrections without checking in between makes debugging harder.
Diagnostics as the only source: combine Google's messages with revenue data to set clear priorities.

A Google CSS Partner shows you product health right in the portal

Feed hygiene is an ongoing job. The easiest way to monitor product data is directly at CSS level.

In the csspartner.io portal, you see product health, rejections and warnings across all target markets. The Fix Center suggests corrections for typical gaps, which you approve.

With a certified CSS, you also save 20% CPC at the same position, or gain 25% more bidding power at the same budget, for £17 a month with no setup fee.

Fix rejections on your top products first, then systematic errors, and handle the rest in your monthly review.

What Technical Support from a CSS Really Means

Many providers promise support. When it really matters, four concrete factors decide whether it works.

Someone Who Can Actually Read a Feed

Merchant Center alerts often only show symptoms, such as missing GTINs or price mismatches caused by faulty exports. Work systematically backwards through the chain from shop, to export, to feed, to Merchant Center.

Access to the Right Level

As a CSS, we analyse the account, feeds and products together. This lets us spot problems in individual items, categories, or website requirements such as return policies, contact details and payment methods, which often go unnoticed in Merchant Center alone.

An Escalation Path That Doesn't End at the Help Centre

For policy violations such as misrepresentation, clear evidence helps with Google's review. As a Google CSS partner, we use direct Google channels and provide the requested evidence on your legal notice, policies and pricing.

Monitoring, So Errors Don't Sit for Weeks

Unnoticed errors cost the most revenue. Keep an ongoing check on product health, disapproval rates and feed fetches, so losses don't turn up late in your quarterly report.

How a Support Case Works

Report with context: send the account ID, the original error message and the product URL so there's no need for follow-up questions.
Triage: we check whether the account, feed or products are affected and how much revenue is at stake.
Root-cause search: we compare shop data, export, feed and Merchant Center to pinpoint the error.
Implement the fix: permanent solutions belong in the shop. We handle quick adjustments directly in the feed.
Check after the crawl: we verify whether the disapproval is resolved or further errors remain.
Prevent recurrence: we clear up the root cause and make the process more robust for the future.

What Support Can't Replace

Good data quality depends on three ongoing shop tasks, whatever support you have.

Maintain mandatory attributes: without a correct GTIN, brand, condition, category, shipping and tax, every fix will fail.
Keep stock and prices current: a daily sync prevents most disapprovals.
Complete shop pages: Google requires pages covering returns, shipping, payment, legal notice and contact.

Support speeds up fixes and helps avoid errors. How much you need depends on how well you maintain your data.

Frequently asked questions about Merchant Center errors

How long does it take for a fixed error to disappear?

Price and stock errors usually clear within hours of the next fetch. Image and policy reviews take a few days.

Why is a product still rejected despite the fix?

Often the re-crawl hasn't happened yet, or a second cause remains. Check the feed values against the live product page.

Do I always need a GTIN?

Branded products need barcodes if the manufacturer assigns them. For own-brand and custom items, submit brand and manufacturer number instead.

What do I do with own-brand products without a barcode?

Submit brand and manufacturer number and set identifier_exists to false only for these items. Use a fixed number per variant.

Does switching CSS cost visibility or cause new errors?

No. Switching only changes the submission layer. Merchant Center account, feeds, IDs and campaigns stay unchanged.

How often should I check the feed?

Sync stock and prices daily, and work through the checklist once a month. During seasonal peaks, check top products weekly.