Google Merchant Center rejected: what should you do?

1. First determine: product disapproval or account issue?

Not every Merchant Center disapproval has the same impact. A single product may be disapproved because required data is missing, a price does not match or an attribute is incorrect. An account issue or suspension is broader and can limit the visibility of many or all products.

Do not start by making random changes. Write down the exact issue name and whether Google reports it at product or account level. That determines where your investigation should begin.

• Product level: inspect the affected item, its product data and landing page.
• Account level: also inspect the store as a whole, business information, policies, transparency and technical functionality.
• Several issues at once: handle each issue separately and then check that your fixes do not contradict each other.

2. Read the Merchant Center message carefully

Open the Merchant Center area that lists issues and products needing attention. Look beyond the short issue label: review the explanation, affected products, countries and programmes. Some issues point to a specific product-data error, while policy issues may be described more broadly.

Before changing anything, make a short record: issue name, level, affected products or account, date, and the pages or data connected to it. This prevents you from losing track of what you are actually repairing.

3. Audit the foundations of your webshop

Google expects a functioning online store that gives customers enough clear information to make a purchase decision. Do not only check whether policies exist somewhere; make sure shoppers can find them and that details remain consistent across pages.

Pay particular attention to:

• Business name, contact details and customer-service availability.
• Return and refund policy, including time limits and possible costs.
• Shipping costs, destinations and realistic delivery times.
• Payment methods and a functioning checkout without unexpected steps.
• Terms and privacy information.
• Working navigation with no broken links, empty pages, placeholder copy or unfinished areas.
• HTTPS and technically accessible product, cart and checkout pages.

A common problem is that individual pieces of information look correct but contradict each other. For example, a delivery promise on a product page that differs from the shipping policy, or a business name in checkout that does not match the name customers see on the store.

4. Compare product data with what shoppers see

Merchant Center uses product data to determine what appears on Google. That information needs to match the final landing page. Check a sample as well as every affected product for price, availability, currency, variant and product identity.

Pay extra attention to dynamic prices, promotions, variants and stock. If the feed says an item is available while the landing page says otherwise, or a sale price is not clearly visible on the page, disapprovals can follow.

• Price and currency in product data versus landing page.
• Availability: in stock, out of stock or preorder.
• Correct variant: colour, size, material or another selected option.
• Shipping information and additional costs.
• Product title, image and identity of the advertised item.
• Structured data on the product page when your webshop uses it.

5. For “misrepresentation”, audit transparency more strictly

The misrepresentation policy is broader than a simple feed error. Google describes it in terms of misleading, unclear or insufficiently transparent information about a business, product or offer. There is therefore rarely one universal field you can change and be done.

Review the full customer journey: from product listing to product page, cart, checkout, payment, shipping, returns and customer service. Claims, discounts, price information and business details should be clear and verifiable.

• Do not use offers, trust marks or claims you cannot substantiate.
• Do not hide important costs or conditions until late in checkout.
• Make sure business and contact details do not differ across the site.
• Make returns, delivery and payment information concrete rather than vague.
• Remove unfinished or generic template elements.

Read also: How to fix Merchant Center misrepresentation →

6. Request a review only when the repair is complete

Google advises merchants with account issues to review the policy, make the necessary changes and then request another review. A review is not a diagnostic button. Use it when you can reasonably explain what you checked and what you changed.

After the fixes, test the store again as a new customer. Check desktop and mobile, open policy links, add products to the cart and continue to the payment step. Then review your product data in Merchant Center once more.

• Keep a list of all corrections made.
• Make sure old cache is not serving previous versions of pages.
• Allow feed or product data to be processed again where necessary.
• Request the review from the relevant Merchant Center issue.
• Avoid unnecessary changes while the review is in progress.

7. What if the review fails again?

Do not automatically submit the same request again without new investigation. Compare the current issue with your earlier notes and look for inconsistencies the first audit may have missed. Also inspect areas that were not shown next to the issue, such as checkout identity, returns information, customer contact or stale product data.

For broad policy problems, you may need to assess the entire webshop again as one customer journey. The objective is not to “change something so Google tries again”, but to create a consistently transparent shopping experience.

What Merqivio can and cannot do

Merqivio checks visible and technically measurable webshop signals, including business information, returns, shipping, price and product consistency, HTTPS, structured data and trust/transparency.

Merqivio is independent and has no access to Google’s internal review systems. A scan or report therefore cannot guarantee approval. The aim is to identify as many known and controllable risks as possible before another review.

Frequently asked questions