Google Merchant Center Checkout Experience Requirements: Why a Bad Checkout Gets You Suspended

Google sends buyers from Shopping ads and free listings directly to your website. When that experience is poor or misleading, Google's reputation suffers along with yours. That is why Google actively audits checkout flows, not just product data. A checkout that passes visual inspection can still trigger a suspension if it violates the specific requirements Google enforces for pricing accuracy, required disclosures, and mobile functionality.

Why Google audits checkout flows

Most merchants focus their compliance efforts on feed data: product titles, prices, GTINs, and image quality. That is correct, but it is not enough. Google's automated systems and human reviewers also check the actual purchase journey a buyer takes after clicking a Shopping ad. They look at whether the price on the ad matches the price at checkout, whether required information is shown before the buyer commits, and whether the checkout works on mobile.

A suspension triggered by a checkout issue is often harder to identify because the feed itself looks clean. If your products are disapproved or your account is suspended for misrepresentation and you cannot find an obvious data error, a checkout audit is the right next step.

The checkout requirements

1. Price must match at every stage

The price displayed in your Shopping ad must match the price on your product page, in the cart, at checkout, and on the final order confirmation. This applies to the total the buyer pays. Adding fees at checkout that were not disclosed at the product page level is a violation, even if the individual fee seems minor. Common examples that trigger suspensions:

The rule is simple: the number the buyer sees when they click your Shopping ad should be the number they pay, or any additions must be clearly disclosed and visible before they begin checkout.

2. Required information before order confirmation

Before a buyer confirms their order, your checkout must display and allow modification of:

Showing these at some point during checkout is not enough. They must be present at the order review stage, before the buyer clicks the final purchase button. If your checkout compresses all of this into a confirmation email after purchase, that is too late for Google's requirements.

3. No fake urgency or dark patterns

Google specifically audits for dark patterns in the checkout flow. Violations in this category include:

These patterns are treated as misrepresentation because they create false urgency or obscure the real terms of the transaction.

4. SSL required across the entire checkout

Your full checkout flow must run on HTTPS. An HTTP checkout page is an immediate suspension risk. This includes every step: cart, checkout, payment, and confirmation. If your product pages are HTTPS but your checkout redirects to an HTTP page (common with older third-party payment integrations), that violates the requirement.

5. Mobile checkout must work

Google's crawler tests mobile checkout separately from desktop. If your checkout breaks on mobile, displays incorrectly on narrow screens, or requires desktop-only interactions to complete a purchase, that is a policy violation. Test your entire checkout flow on an actual mobile device, not just a browser's responsive design preview.

6. Payment methods disclosed before checkout begins

Accepted payment methods must be visible to buyers before they start the checkout process. If a buyer goes through the full checkout only to discover at the payment step that their preferred method is not accepted, that creates a poor experience Google will flag. Show accepted payment methods on your product pages or at the cart stage.

The most common violation: the surprise fee pattern

The single most common cause of checkout-related suspensions is what you could call the surprise fee: the price in the ad is €X, but by the time the buyer reaches the final payment screen, the total is €X plus additional charges that were not disclosed anywhere earlier in the journey. These extra charges are typically labeled as processing fees, service fees, or handling fees.

Merchants often add these fees because third-party payment processors charge per-transaction fees that eat into margins. The instinct is to pass that cost to the buyer at checkout. The result is a price mismatch between the ad and the final charge, which Google treats as misrepresentation.

The fix is either to include these fees in your listed price or to disclose them clearly on the product page before the buyer clicks your Shopping ad. A note like "€2.50 processing fee applies at checkout" on the product page is sufficient disclosure. Hiding the fee until checkout is not.

How to audit your own checkout

Before submitting a reinstatement request, audit your checkout personally. This is the process:

  1. Start from a Google Shopping ad, not directly from your website. Click your own ad and follow the exact path a buyer would take.
  2. Screenshot every page: the product page, the cart, every checkout step, and the order confirmation.
  3. At each step, check: does the price match what was shown in the ad? Is the shipping cost visible? Is the delivery estimate shown? Is the returns policy linked?
  4. Repeat the entire flow on a mobile device, not a desktop browser in mobile simulation mode. Use an actual phone.
  5. Have someone else run through the same flow independently. A second pair of eyes catches things you have become blind to.

Document everything with screenshots. When you submit the reinstatement request, you will need to describe the changes you made with specific evidence of what was wrong and what was fixed.

After fixing checkout issues

Once you have corrected the issues, submit a reinstatement request through Merchant Center. In the request, describe each specific change you made. "I fixed my checkout" is not sufficient. "I removed the €2.50 handling fee from the checkout and included that cost in the listed product price. Screenshots of the product page and checkout confirmation are attached showing consistent pricing across all steps" is the kind of specific documentation that moves a reinstatement forward.

Google's reviewers see hundreds of reinstatement requests. The ones that succeed are specific, documented, and show that the merchant understood the exact violation rather than making general changes and hoping for approval.

If your reinstatement request is denied, the denial typically identifies the remaining issue. Use that feedback to run another checkout audit, fix the specific problem identified, and resubmit with updated documentation.