Google Merchant Center Errors Irish Shops Must Fix

A single wrong price can remove a product from Shopping results just as a sale begins. For Irish retailers, Google Merchant Center errors often come from small gaps between the product feed, product page, structured data and checkout.

The fix is rarely to edit one field and hope for the best. Every version of the offer must agree before Google can trust it. Identify where Google found the conflict, correct the source of truth, then allow the feed and website to catch up.

Key Takeaways

• Triage Google Merchant Center errors by checking account-level issues, feed processing errors and item-level problems in that order.
• Keep price, currency, availability and condition consistent across the product feed, landing page, structured data and checkout.
• For Irish shops, verify EUR pricing, VAT treatment, delivery coverage and shipping costs for the regions you serve.
• Use accurate GTINs, MPNs, brands and variant data, and never replace manufacturer identifiers with guessed values or internal SKUs.
• Fix recurring problems at their original source, then recheck Diagnostics after the next feed refresh and Google crawl.

How to triage Google Merchant Center errors

Open the Diagnostics page first. It separates problems into account-level issues, item issues and feed processing errors. Statuses such as unavailable desktop URL and checkout incomplete show where to investigate.

A red error can cause a product disapproval and stop a product appearing in free listings or Shopping ads. Warnings may not block a listing today, but they can support a preemptive item disapproval before visibility is lost. An unresolved policy violation can contribute to account suspension, although not every warning causes suspension.

Use this order:

1. Check account-level issues first, including the shop’s business information, as these can affect every product.
2. Review feed processing errors next, because a failed product feed import can leave the whole catalogue stale.
3. Group item issues by cause, such as a price mismatch, misrepresentation error, missing GTIN or broken product URL.
4. Fix the data at its original source, rather than editing individual products in Merchant Center.
5. Return to the Diagnostics page after the next sync and Google crawl.

Google’s Merchant Center issue guidance explains how product, feed and account issues appear in Diagnostics.

A product-level correction cannot clear an account policy problem, and an account review will not repair a broken import.

Know the difference between feed, item and account issues

Each issue type calls for a different response. Treating them as one list wastes time and can make an account problem harder to diagnose.

Feed issues usually start before Google sees the product

A product feed issue means Google couldn’t read or process data as expected. These import failures are feed processing errors. Common causes include invalid spreadsheet headers, duplicate item IDs, malformed XML, an invalid image link attribute, inaccessible image URLs, or a scheduled fetch that no longer works.

For a Shopify or WooCommerce shop, also check whether a plugin update disconnected the Merchant Center account, changed permissions, or stopped sending variant data. If an import failed at 07:00, don’t assume the 07:30 product update reached Google.

Check the source’s last successful refresh, item count and processing messages. Compare those figures with the number of active products in your shop. A sudden drop from 800 items to 42 is a feed problem, not 758 separate disapprovals.

Item issues affect offers, not necessarily your whole shop

These issues appear against individual offers. They include missing identifiers, image problems, price discrepancies and policy restrictions on particular products. An unavailable desktop URL can stop Google reaching the landing page for that offer.

Fix these in batches where possible. If 120 products share the same “missing value [gtin]” issue, repair the product-information workflow rather than opening 120 records in Merchant Center.

Fix price and availability mismatches first

Price and availability mismatches are among the most damaging Google Merchant Center errors because they affect buyer trust. Google compares the submitted offer in your product feed with the live landing page, structured data and checkout.

An Irish retailer selling a jacket for EUR 79.99 should show EUR 79.99 in the feed, product page and checkout. If the shop displays VAT-inclusive prices, the submitted amount must match the same VAT-inclusive EUR amount shoppers see. Check the shop’s tax settings if net and gross amounts conflict.

Find the source of the mismatch

Check the exact URL in the affected item, ideally in an incognito browser. Choose the same variant that Google is reviewing, then add it to the basket. If the basket can’t complete the same offer, record the outcome as checkout incomplete.

Look for these common faults:

• The feed still contains yesterday’s regular price after a sale started.
• The page defaults to a EUR 39.99 variant, while Google receives a EUR 44.99 parent product price.
• A discount appears only after a shopper selects a size or colour.
• Inventory software marks an item out of stock, but the feed refresh runs overnight.
• A promotion code changes the basket total, although the product page shows the undiscounted price.

The product data specification sets out Google’s attribute requirements, including accurate price and availability data.

Use automations as a safety net, not a repair strategy

Merchant Center can automatically update price, availability, condition and some image details from your website. Enable relevant settings under Products and Automations.

Automated item updates can reduce temporary mismatches, but they’re a safety net rather than a substitute for fixing the source. They won’t fix a theme that publishes the wrong structured data or a checkout that adds unexplained charges.

For a timed sale, check the regular price, sale price and dates across the ecommerce platform, feed app and on-page schema. An expired promotion left in a feed is an easy route to a disapproval.

Check variants, GTINs and product identifiers

Google needs enough information to understand which product you’re selling and verify its unique product identifiers. For branded products, provide a manufacturer-assigned GTIN where one exists. If no GTIN applies, Google’s normal requirement is an MPN combined with a brand.

Never invent a GTIN, reuse one from a similar item, or use an internal SKU in place of the manufacturer value in the GTIN attribute. That creates conflicting product data and can hurt matching across Google’s catalogue.

Match each variant to the right offer

Colour, size and material variants need careful handling, and their unique product identifiers must stay consistent across the catalogue. A black, size-medium trainers listing should point to the selected black, size-medium version of the page, with its own price, availability and image where these differ.

Generic parent URLs often cause trouble. Google may crawl the default variation, then find a price or stock level that conflicts with the feed item.

In Shopify, inspect whether the Google sales channel maps every variant correctly. In WooCommerce, check that your feed plugin exports variation IDs, variant-level stock and the right image rather than only the parent product’s details.

Improve data before adding more attributes

More attributes won’t fix inaccurate data, so start with a clean product title, brand, GTIN or MPN and correct condition. Check each variant’s image link attribute and product URL, then review the image for a promotional overlay against Google’s requirements.

For handmade, custom or genuinely unbranded goods, follow Google’s identifier rules and data quality requirements when no recognised GTIN exists. Document why the identifier is absent in your catalogue process, so staff don’t later add guessed values to clear a warning.

Sort out shipping settings for Ireland

Shipping settings often fail when a retailer treats Ireland as one simple destination. Delivery costs can differ across the Republic, Northern Ireland, islands, bulky products and courier services.

Your Merchant Center shipping setup must match the shipping costs a buyer can actually select at checkout. If your store offers EUR 5.95 standard delivery in the Republic of Ireland and free delivery above EUR 75, configure and test that logic accurately.

Test realistic Irish delivery scenarios

Run orders to a Dublin address, a rural County Mayo address and any other region you serve differently. Then compare the configured shipping costs, delivery timing and destination eligibility with Merchant Center and the checkout results. Record the test as checkout incomplete if a shopper can’t finish the order because the configured destination, rate or eligibility rule is inconsistent.

If you don’t deliver to Northern Ireland, make that clear in your website policy and target settings. Northern Ireland is not part of the Republic of Ireland for delivery or currency rules, even when your shop’s shipping plugin groups it under “Ireland”.

Likewise, if a product needs a freight quote, don’t submit a flat EUR 9.99 shipping rate unless customers can genuinely complete checkout at that cost.

Google’s checkout requirements stress that availability must remain consistent through the landing page and checkout process.

Make returns, refunds and business details easy to find

Merchant Center expects customers to find clear information about delivery, returns and refunds. Your return and refund policy should state the return period, exclusions, return method, refund timing, who pays return postage and a contact route for questions.

Put this policy in the site navigation or footer, and link to it from product pages where practical. A vague footer link or policy hidden behind an account login can create friction for customers and policy reviewers.

Irish consumer rules also matter. The CCPC guidance for selling products explains that the Consumer Rights Act 2022 applies to consumer products sold in Ireland from 29 November 2022. Your published policy should reflect your actual legal and operational position.

Avoid the signals behind a misrepresentation error

A misrepresentation error is an account-level trust concern, not an isolated product problem. These account-level issues can arise when Google can’t establish that the shop is transparent, trustworthy and able to complete a purchase as advertised.

Audit these areas before asking for a review:

• Your business information, including legal business name, registered address and contact details, is consistent across the website, Merchant Center and payment pages.
• The website uses HTTPS and has no broken purchase path, checkout incomplete message, placeholder page or misleading claim.
• Product pricing, shipping costs and availability are clear before payment.
• Your return and refund policy, privacy and terms pages work on mobile and desktop.
• Your Merchant Center website is verified and claimed by the correct business.

Google’s account review guidance advises merchants to check that shipping and return policies are clear and functional before they request a review.

Repair website and structured-data mismatches

Structured data is the machine-readable product information in your page code. It often drives automatic updates, yet it can become stale after a theme edit or app conflict.

For product offers, Google compares submitted product feed data with landing page content and its markup. Price, currency, availability and condition should agree across all three. A page that shows EUR 29.00 while its markup says EUR 35.00 creates an obvious conflict.

Check the live page rather than your theme settings

Don’t rely on the CMS editor. Open the published product URL and inspect its rendered source, including scripts from review, subscription or feed apps. Check for an unavailable desktop URL or checkout incomplete status, as technically valid product pages fail when buyers can’t check out.

Common faults include:

• A theme outputs the first variant’s price for every variation.
• Schema uses “InStock” after stock has reached zero.
• A cache plugin serves yesterday’s product markup.
• The visible price includes VAT but JSON-LD uses a net price.
• Two apps publish competing Product schema blocks.

Test a representative sample after every theme release. Prioritise best sellers, sale items and products with many variants because they create the most exposure when data goes wrong.

Shopify and WooCommerce problems that keep returning

Both platforms can send accurate product data, but their connectors only reflect the rules you give them. Most recurring errors come from timing, variant setup or custom theme work. The 90-day AEO plan for Shopify, WooCommerce and BigCommerce covers these platform-specific feed and schema checks in more depth.

Shopify checks that prevent stale feed data

Review the Google and YouTube channel’s product status after changing prices or stock. Confirm that products are published to the sales channel, each variant has an appropriate SKU, and the shop’s market and currency settings match Ireland targeting.

A common problem occurs when a Shopify theme shows a dynamic variant price, but structured data stays fixed on the first option. Another occurs when “compare-at price” is used for a sale, but the connector sends an incorrect regular or active price.

Recheck the product page after an automatic collection rule, inventory app or bulk-edit tool changes data. Those tools can alter products faster than a feed connector refreshes.

WooCommerce checks for plugin and cache conflicts

WooCommerce sites commonly depend on a connector, product feed plugin, caching layer and stock-management extensions. Any one of them can publish outdated values.

Clear relevant caches after changing sale pricing, stock logic or schema settings. Then check the feed’s generated XML or CSV, not only the WooCommerce product editor. If variations are missing, review whether the feed plugin exports child products and whether variable-product stock is managed at parent or variation level.

Keep a record of plugin updates that affect feeds, checkout or structured data. It makes the next mismatch quicker to trace.

Move integrations to Merchant API

As of 18 August 2026, Google’s Content API for Shopping has been shut down. Stores and agencies with custom integrations should now use Merchant API, Google’s separate route for programmatic product feed and account management.

Google’s Merchant API announcement confirms the Content API sunset date. An old custom connection may still appear to work in parts of a platform, but it should be treated as a migration risk until the provider confirms Merchant API support.

Monitor errors programmatically at scale

For larger catalogues, use Merchant API to retrieve product and account issues regularly. A daily export of item-level issues and feed processing errors can reveal patterns before a marketing campaign sends traffic to unavailable products.

Group reports by issue type, severity, product brand, category, data source and date first detected. That turns a list of 500 errors into a prioritised work queue.

Track product data quality and campaign readiness as well as volume. Ten wrong prices on best-selling items can matter more than 200 missing optional attributes on discontinued products.

A concise Merchant Center troubleshooting checklist

Use this checklist when product listings suddenly lose approval or visibility in Shopping ads after a product disapproval:

• Confirm the account has no unresolved account-level issues, website claim problem or policy review request.
• Check whether the latest product feed completed successfully, contains the expected product count and has no feed processing errors.
• Open affected product URLs on desktop and mobile, then test the selected variant and checkout. Record any checkout incomplete result.
• Compare price, currency, availability and condition across the feed, page and basket.
• Verify EUR pricing for Ireland matches the shopper-facing price, including VAT where your storefront displays it.
• Review GTIN, brand and MPN fields against manufacturer data, including the image link attribute.
• Test delivery rules and shipping costs for the Irish regions you serve, then compare them with Merchant Center shipping settings.
• Check that return, refund, delivery, contact and business information pages are visible and current.
• Enable applicable Merchant Center automations, then investigate the cause of every repeated correction.
• Recheck the Diagnostics page after a feed refresh and crawl, recording what changed and when.

Prevent errors before a campaign goes live

Build product-data checks into normal trading activity. Price changes, sale launches, new shipping rules and catalogue imports all need a product feed check before paid traffic increases. A pre-launch review enables preemptive item disapproval, catching problems before affected products lose visibility.

Set a weekly routine for active retailers and a daily one during major promotions. Compare a small sample of high-value products against the live site, including prices, stock, images, delivery and variant selection.

Keep ownership clear. Ecommerce staff should own product information and its data quality requirements. Developers should own feeds and schema, while customer service or operations should verify delivery and returns information. Merchant Center works best when those three sources tell buyers the same story.

Frequently Asked Questions

What should I check first when a product is disapproved?

Start with the Diagnostics page and check for account-level issues, feed processing errors and item-level problems. Then open the affected product URL, select the relevant variant and test the complete checkout journey.

Why does Google report a price or availability mismatch?

Google compares the product feed with the live page, structured data and checkout. A stale feed, incorrect variant mapping, cached markup, VAT difference or delayed stock update can make these sources disagree.

Do Irish shops need separate shipping settings for different areas?

Shipping settings should reflect the delivery costs and eligibility customers can actually select at checkout. Test addresses in Dublin, rural counties and any other areas with different rates, and make Northern Ireland coverage clear if it is handled separately.

Can Merchant Center automations fix product errors?

Automated item updates can reduce temporary price, availability and image mismatches. They are only a safety net, however, and will not repair incorrect source data, structured markup or checkout charges.

When should a shop request an account review?

Request a review only after resolving the underlying account-level concern and checking that business details, website claims, policies, shipping, pricing and checkout are clear and functional. Correcting an individual product will not resolve a wider misrepresentation or trust issue.

Final thoughts

The fastest way to resolve Google Merchant Center errors is to trace each problem back to its source. Correct the feed, product page, markup and checkout together, then let Merchant Center reprocess the product.

For Irish shops, accurate EUR pricing, clear delivery coverage and accessible consumer policies matter as much as a well-built product feed. When every customer-facing detail agrees, Shopping listings have a much stronger foundation.