Before You Request Another Google Merchant Center Review: What to Check First

Open Merchant Center and read the current wording in Needs attentionor the relevant issue details. Record whether the problem is account-wide, affects particular products, names Misrepresentation, or identifies another prerequisite. Use the current message rather than an old screenshot or a summary from memory.

Google distinguishes product-level issues from account-level warnings and suspensions. A product may be disapproved because its data or destination does not meet a requirement; an account-level issue can stop many or all products from appearing. Those are different investigation scopes. If only certain products are affected, download or note the affected examples and look for a shared source rather than assuming the entire store needs rebuilding.

Also check whether Merchant Center asks for identity verification, a non-empty product data source, or another action before review is available. A missing or disabled review button does not by itself mean the suspension is permanent. The status shown in your own account is the reliable starting point.

A customer should be able to understand who operates the store, what the business sells and how to get help. Compare the business name, trading name, address and customer-service details shown on your website with the information in Merchant Center and any relevant payment or business profile. Do not add details you cannot support; correct genuine differences.

Check the homepage, contact page, about page, policy pages, footer and checkout. Look for an old company name, a different address, an abandoned support email, a template phone number or a contact form that does not work. If the store uses a trading name, explain the operator relationship plainly instead of leaving visitors to infer it.

Google's current Misrepresentation guidance says merchants should represent their business and products accurately and provide the information people need to make an informed decision. It may consider information from the website, accounts and other sources. That is why consistency matters, but it is not a reason to manufacture badges, reviews, office locations or partnerships. Verifiable facts are more useful than decorative trust signals.

If your issue specifically mentions Misrepresentation, see our focused guide to observable Merchant Center Misrepresentation concerns. It explains the evidence MerchantProof can examine without claiming access to Google's internal reasoning.

Policy pages need to help a real customer make a purchase decision. Confirm that shipping destinations, delivery costs, handling time and expected transit time are understandable before checkout. Then compare those statements with the shipping settings used in Merchant Center and with any delivery message shown on product or basket pages.

Review the returns and refund policy in the same way. It should say whether returns are accepted, the relevant window, important eligibility conditions, how a customer starts a return, who pays return postage and how refunds are handled. If returns are not accepted for a lawful reason, state that clearly. Do not leave a generic template that conflicts with your actual operation.

Google's guidance says return and refund information should be easy to find and consistent across the website. Test every footer link and read policy banners, product-page summaries and checkout copy together. A polished policy page does not resolve a contradiction elsewhere: “free returns” in a banner and customer-paid returns in the policy still tell two different stories.

For a representative set of affected and important products, compare the submitted product record with the exact destination a shopper reaches. Check the product ID, title, variant, URL, price, currency and availability. The destination should describe and sell the same item, and the submitted values should agree with what the customer can see.

Price and availability deserve three-way checks: the feed or other product data source, the visible page and the structured product data in the page HTML. Google's price guidance explains that its crawler compares submitted price with landing-page and structured values. Its availability guidance likewise requires submitted and landing-page availability to match. A theme, app or currency selector can create a mismatch even when the administrator believes the source value is correct.

Load pages in a clean browser session and select the submitted variant. Check whether JavaScript changes the price only after the initial HTML arrives, whether sale prices have expired, whether VAT or mandatory charges appear differently, and whether an “in stock” product can actually be bought and delivered to the target country. Check redirects too: the submitted URL should end on the specific purchasable product, not a category page, search page, different variant or homepage.

Fix the source that creates the wrong value and update product data on a sensible schedule. Do not repeatedly hand-edit exported rows if an app or catalogue rule will overwrite them. For issue-specific examples, read the MerchantProof pages on product disapprovals and account-level suspension diagnostics.

Start at the homepage, use the main navigation, open several product pages, add an item to the basket and continue far enough through checkout to verify that the journey is functional. Test on a phone as well as a desktop. Look for broken links, password gates, certificate warnings, blank sections, placeholder text, unsupported payment claims, pop-ups that hide important information and pages that fail without a particular browser state.

Confirm that customers can see the full price and important purchase conditions before committing. Make sure contact, terms, shipping and returns information remains accessible during the journey. If a product is promoted as available, verify that the selected variant can reach the basket and checkout for the country you target.

This is not a search for visual perfection. A plain, working and honest store is more useful than an elaborate site with dead ends or unclear conditions. Record each defect, its page and the evidence that the correction now works.

Many difficult cases are not caused by one absent page. They are caused by several individually plausible statements that disagree. Search the store for the business name, address, delivery promise, return window, support email, currency, availability language and key promotional claims. Compare the results side by side.

Include announcement bars, FAQs, product tabs, structured data, checkout notices and old policy URLs. Remove abandoned versions and make the current version reachable. Where information legitimately varies by product or destination, explain the difference instead of presenting one universal promise.

Keep a short change record: what was inconsistent, which source was authoritative, which pages were corrected and how you verified the result. That record helps you avoid random edits and gives you a clearer explanation if Merchant Center asks for more information.

Do not assume every Merchant Center suspension is caused by a linked Google Ads account. Check whether Merchant Center explicitly names a linked-account suspension. If it does, Google's current guidance says the Google Ads suspension must be resolved before the Merchant Center issue can be reviewed. Unlinking or removing the suspended Ads account does not resolve that Merchant Center issue.

Handle the Ads appeal through the route Google provides, then return to Merchant Center and check whether a review is available if the Merchant Center account remains suspended. MerchantProof does not resolve Google Ads suspensions or submit appeals, so a case that depends on that prerequisite is outside the paid diagnostic scope.

Once the underlying work is complete, return to the relevant issue in Merchant Center. The review option appears only where it is available. Google may require another action first, and some unsuccessful reviews can lead to a cooldown during which a new request is unavailable. Merchant Center should show the applicable status or timing; Google support cannot simply bypass a cooldown.

Do not use the button's presence as evidence that the store is ready. It is only an available process step. Before selecting “I fixed the issue,” recheck the affected pages, data source and account prerequisites. If you believe the issue is an error, use the disagreement route Google presents and give a thorough, accurate explanation.

Reviews can take time, and the status shown in Merchant Center is authoritative. A review that is not approved does not reveal every internal signal Google considered. Return to the observable evidence and the issue details instead of inventing a hidden cause.

An independent review is useful when you can see the Merchant Center issue but cannot turn a mixture of website, policy and product-data evidence into a reliable correction order. It should identify observable problems, distinguish confirmed evidence from possibilities, state what could not be checked and give you a practical way to verify each correction.

MerchantProof provides a one-time £99 diagnostic for supported UK online stores. It checks the public website, supplied product data and evidence, then adds human review and a prioritised action plan. It does not need your Google account login, does not submit a review or appeal and cannot guarantee approval or reinstatement. Google may consider account history and other information MerchantProof cannot access.