How to Prepare a Merchant Review Request

A Merchant Centre suspension can stop Shopping traffic while stock is still live, campaigns are funded and customers are ready to buy. To prepare a merchant review request properly, treat it as the final stage of a correction process, not a quick form to submit as soon as the warning appears. Google needs to see that the underlying issue has been resolved across your store, feed and account.

A strong request is concise, factual and supported by real changes. A rushed one can lead to another rejection, more lost trading time and less clarity about what to fix next.

Check the suspension before you request a review

Start with the exact issue shown in Merchant Centre. Do not rely on a generic description from a previous email or an assumption based on what another merchant has experienced. The account diagnostics, policy section and affected products can indicate whether the problem concerns misrepresentation, website needs improvement, shipping information, product data, restricted content, misleading claims or another policy area.

The scope matters. A disapproved product requires a different response from an account suspension. If the account is suspended for misrepresentation, for example, changing a handful of product titles is unlikely to be enough. Google may be assessing whether shoppers can understand who they are buying from, what they will pay, when goods will arrive and how they can obtain support or a refund.

Take a record of the notice, affected countries, products and any dates given. Then review your previous changes. Repeatedly requesting reviews without material corrections is not a recovery strategy. It can waste valuable time when your paid acquisition is already interrupted.

Identify the actual customer journey

Open your store as a new customer would. Check it on desktop and mobile, without assuming that your familiarity with the business makes the information obvious. Can someone find your contact details, trading identity, delivery times, return process and total costs before paying?

For Shopify retailers, common weak points include template policy pages left incomplete, contact forms with no business details, inconsistent dispatch times, collections linking to unavailable products and checkout charges that are not clearly reflected in the delivery policy. These are trust and transparency issues as much as technical ones.

How to prepare a merchant review request after fixes

Only request a review once your corrections are live, visible and tested. Your submission should accurately state what was changed and where Google can verify it. Do not claim that the account is fully compliant if you have not checked the relevant areas. Review teams can see the live store and feed, and vague assurances add little value.

Keep an internal correction record while you work. Note the page or feed field changed, the reason for the change and the date it was published. This helps you write a clean request and prevents important work being missed when several people have access to Shopify, Merchant Centre and the advertising account.

Your evidence will normally fall into three connected areas: website transparency, product-feed accuracy and account-level policy controls. The exact balance depends on the suspension reason, but all three deserve a check before submission.

Website trust signals

Your website should present a genuine, contactable retailer. Make sure the business name is used consistently across the site, policy pages and checkout. Provide an accessible contact route and enough information for a customer to understand who is responsible for an order.

Review delivery, returns, refund, privacy and terms pages for clarity rather than simply confirming that they exist. Delivery information should explain locations served, processing or dispatch timing, estimated delivery periods and charges. Return terms should state the return window, condition requirements, process and any relevant exclusions. If an item is made to order or subject to a longer lead time, say so prominently on the product page as well.

Check product claims with care. Unsupported health, performance, scarcity or pricing claims can create policy risk. So can misleading sale prices, automatic discounts that do not work as advertised, or product pages where the variant shown in the feed cannot actually be purchased.

Feed and landing-page consistency

A compliant-looking policy page will not resolve a feed that points shoppers to inaccurate offers. Review product titles, descriptions, prices, availability, images, identifiers, shipping settings and landing-page links. The item submitted to Google must match the item a shopper sees after clicking.

Pay particular attention to variant products. A feed may advertise the lowest variant price while the landing page defaults to a higher-priced option. An out-of-stock size may remain in the feed as available. Currency, promotional prices and delivery costs can also become inconsistent after theme, market or app changes.

Use the final landing page, not only the product data in Shopify, as your test point. Add representative products to basket and continue through checkout. Confirm that pricing, stock status, delivery options and policy links remain clear at each stage. If you sell internationally, test the country and currency covered by the affected Merchant Centre programme. A UK store setup does not automatically prove that the same customer experience works for another market.

Account and access checks

Confirm that the Merchant Centre account details, website domain and claimed ownership are correct. Check that authorised users are known to the business and remove old agency or staff access where appropriate. Review linked Google Ads accounts, feed rules and third-party apps that may overwrite product data.

This is also the point to stop making overlapping changes. If a feed-management app, Shopify market setting and manual Merchant Centre rule all alter prices or availability, you need to establish which source is controlling the final data. Otherwise, a correction can appear live briefly and then be overwritten before review.

What to write in the review request

The best review request is short enough to be read quickly and detailed enough to direct the reviewer to completed work. Avoid emotional language, blame or promises about future improvements. You are explaining what is now in place.

Use the suspension reason as your structure. State that you reviewed the account and website, name the relevant corrections, and confirm that the live store and feed were checked. If you discovered a specific error, acknowledge it plainly. Honest precision is stronger than broad statements such as “everything has been fixed”.

A suitable format is:

> We reviewed the suspension notice and completed a full check of our website, product data and checkout journey. We updated our delivery, returns and contact information so customers can clearly see our business details, costs, timings and support process. We also corrected affected product data to match the live landing pages, including price, availability and variant information. The changes are live and have been tested. Please review our Merchant Centre account again.

This is a framework, not wording to copy blindly. Replace each general statement with the changes you genuinely made. If the issue was a feed policy breach, focus more heavily on the corrected attributes and affected products. If it was website trust or misrepresentation, explain the store-level improvements without turning the request into a long defence of your business.

Do not attach irrelevant material or try to overwhelm the reviewer with screenshots unless the review process specifically asks for them. The live website and feed are the primary evidence. Your job is to make them easy to verify.

Submit once, then keep the store stable

Submit through the review route provided in Merchant Centre after final testing. Review times vary, and Google retains final approval authority. No consultant or merchant can guarantee reinstatement, particularly where the platform identifies unresolved or repeated policy concerns.

Once submitted, avoid major changes to policy pages, theme behaviour, prices, shipping settings or feed sources unless a genuine business need requires them. A stable, consistent store gives the reviewer a clearer picture of the corrections you have made. Continue monitoring diagnostics, but do not submit duplicate requests unless Merchant Centre indicates that another action is needed.

If the request is declined

A declined review does not always mean the original fix was wrong. It may mean the correction was incomplete, another policy issue remains, the live pages did not match the feed at review time, or the account needs a wider trust and technical audit.

Return to the suspension wording and inspect the full customer journey again. Check more than your best-selling products, especially products with variants, promotional pricing, international shipping or supplier-led fulfilment. Look for contradictions between product pages, policies, checkout and feed data.

When internal changes have already failed, a manual audit is usually more useful than another generic appeal. Pulserig GMC Compliance & Ads Rescue reviews the practical points that automated checklists often miss, then prepares the account for a properly evidenced submission.

The most useful next step is not to send a longer message. It is to make the store easier for a real customer to trust and for a reviewer to verify - then request review with confidence.