Google Merchant Center Account Suspended? Repair Before Review

Identify the enforcement layer, reconcile your catalog, storefront and checkout, and prepare an evidence-based review request without account workarounds.

A Merchant Center suspension interrupts the connection between a retailer's catalog and the customers it is trying to reach. The immediate temptation is to submit another review, change campaign settings or replace the feed. None of those actions establishes that the underlying store and product information are consistent.

If your Google Merchant Center account is suspended, identify the exact account issue, preserve the notice and review history, then reconcile the affected products, storefront, checkout and business information before requesting review. Use the correction or disagreement route appropriate to the evidence. Do not create replacement accounts or disguise unresolved problems to obtain approval. Google's policy-issue guidance directs merchants to examine both their store and account before review.

This guide is for legitimate e-commerce operators and their paid-media teams deciding what to repair, who should own it and when a review request is defensible. The evidence register and acceptance gates below are our editorial recommendations. They cannot diagnose a private account or promise reinstatement.

First distinguish the enforcement layer

“Google suspended us” is too broad to commission useful work. Record the product, account, destination and country named in the notice. A product disapproval, Merchant Center account suspension, missing merchant verification and Google Ads advertiser-verification failure can require different evidence and different actions.

Google's review documentation distinguishes product issues from setup and policy issues. It also notes that verification requirements can need completion before review becomes available. A campaign report showing lost impressions does not identify which of those boundaries failed.

Open a separate incident line for each affected system. If Merchant Center names an account policy issue, investigate that issue there. If Google Ads also displays a separate verification or suspension notice, preserve it separately. Our Google Ads advertiser-verification guide addresses that neighboring problem; completing one workflow should not be recorded as proof that another account is clear.

For a broader commerce investigation, the e-commerce paid-media audit covers measurement, economics and channel dependencies. During an enforcement incident, however, establish eligibility before treating delivery loss as a bidding problem.

Preserve evidence before changing the store

Create a dated incident record with the exact issue wording, account identifier, affected countries, destinations, product examples and current review status. Retain emails and support case references. Record which people and integrations can change the catalog or storefront. Keep credentials, customer details and business documents in appropriate private systems; an agency discussion rarely needs unrestricted copies.

Next preserve representative before-state evidence. Useful examples include the submitted product identifier and variant, destination URL, displayed offer, checkout conditions and the relevant store policy. A screenshot without its URL, selected variant, market and time may be difficult to interpret later. Prefer a compact reproducible record over a folder of unexplained images.

The purpose is operational traceability. You need to distinguish a defect that existed when the notice arrived from a different defect introduced during remediation. This is particularly useful when a feed app, theme release, localization service and promotion engine all publish parts of the same customer journey.

Do not infer that every inconsistency you find caused the suspension. Mark each finding as confirmed noncompliance, a plausible contributor requiring investigation, or an unrelated improvement. A useful repair plan separates evidence from suspicion while still addressing all known applicable requirements.

Build a policy-to-asset register

Use one row per issue and repeat rows when different markets or product templates behave differently. This is a working diagnostic model, not Google's review checklist.

Boundary What to compare Owner to identify Acceptance evidence --- --- --- --- Business identity Account details, visible store identity and contact information Business owner Accurate, consistent records and reachable contact routes Product offer Submitted item, linked variant and visible availability Catalog owner The advertised variant resolves to the corresponding purchasable offer Transaction Product price, currency, shipping conditions and checkout Commerce operations The submitted offer is consistent with the applicable purchase path Customer policies Returns, refunds and delivery information Operations and policy owner Visible terms reflect the actual operating process Publication system Source catalog, feed integration and storefront templates Technical owner Corrected values survive the next ordinary update Review state Named issue, prerequisites and available action Account administrator A documented correction or evidence-based disagreement

The last two rows are easy to omit. Editing a visible price does little if a scheduled integration republishes the wrong value. Likewise, a technically repaired store may still have an unresolved prerequisite in the account. Assign acceptance to someone who can inspect the relevant system, rather than making the media buyer accountable for every dependency.

What a misrepresentation notice does and does not establish

A misrepresentation notice warrants careful investigation of what the business tells customers. Google's misrepresentation policy addresses misleading business or product information, unavailable offers, dishonest transaction conditions and unreliable claims. Some categories are treated as egregious and can lead to immediate suspension without prior warning. Google says its assessment can draw on the listing, website, accounts and third-party information.

That policy does not supply a universal diagnosis for an individual retailer. Adding an About page or changing a footer is not evidence that a particular suspension has been resolved. Start with the actual notice, relevant requirements and the business's real operations.

Check whether the site accurately identifies the seller, describes what the customer receives and explains material purchase conditions. Examine claims about authorization, affiliations, stock, fulfillment and product outcomes. Where substantiation is missing, remove or correct the claim. Do not manufacture a document, review, address or partnership to make the business appear more credible.

A consultant can help organize and test evidence. It cannot make a false commercial claim true by rephrasing it. If the business cannot substantiate a material assertion or determine whether an offer is lawful, that is an owner or qualified-adviser decision before further advertising. This article provides no jurisdiction-specific legal conclusion.

Reconstruct the advertised transaction

Choose affected product examples based on how the store works. Include relevant variants, currencies, promotion rules, shipping conditions and mobile templates. Start from the submitted link and trace the offer a customer can actually purchase. Record the outcome without submitting real orders merely to build an audit packet.

Google's landing-page requirements require the linked page to represent the corresponding product or variant and align key details with submitted product data. They also address consistent information across page loading and user contexts. Audit legitimate customer experiences and the systems generating them; never show a special compliant version only to reviewers or crawlers.

The price specification requires the submitted amount and currency to match the landing page and checkout, subject to its detailed pricing rules. Conditional promotions, membership prices and additional charges need their applicable treatment. Do not collapse every pricing situation into a generic instruction to copy the lowest visible number into the feed.

Separately check whether return and refund information is easy to find and reflects actual operations. Google's account guidelines call for clear return and refund policies, including explicit information when returns or refunds are not offered. A policy copied from another retailer is a poor acceptance record if your team cannot deliver what it says.

Correct the publishing cause before requesting review

Organize repairs by dependency. First establish the truthful business and offer information. Then fix the system responsible for publishing incorrect values. Finally verify the account settings, submitted data and customer journey together. This order is an editorial recommendation intended to reduce contradictory changes.

For example, if a promotion engine changes the storefront while the integration exports a different price, identify which system owns the offer and how updates propagate. A manual feed edit might temporarily remove the mismatch while leaving the next synchronization free to recreate it. Ask the technical owner to show the corrected ordinary update path.

Keep the scope explicit. A shared template defect may affect many products; a variant mapping defect may affect only a subset. Test enough examples to support the claimed repair boundary, and label untested areas. “We checked three products” should never become “the entire catalog is compliant” without evidence covering that conclusion.

Do not hide unresolved products to stage a cleaner review and restore them afterward. Google's bypassed-account-review guidance specifically describes catalog manipulation around review as abuse. Genuine correction of a noncompliant offer and manipulation to evade inspection are different actions. Follow the notice and applicable policy rather than using catalog size as an approval tactic.

An illustrative promotion and variant incident

Consider a fictional retailer selling a small and a large insulated bottle. The catalog submits the large variant at a temporary promotional price. The linked page opens with the small variant selected, while checkout applies the promotion only after an additional condition is met. A feed update later restores the old promotional amount after a person manually edits it.

This example is not a Sharply Labs client case or a claim about Google's hidden enforcement triggers. It illustrates why “the website looks fine” is an inadequate acceptance test.

The catalog owner first confirms which variant and offer the submitted identifier represents. Commerce operations confirms the actual promotion conditions and the price available to the relevant customer. The technical owner repairs the mapping and export rule. The team then compares the submitted item, linked variant and applicable checkout path after the next normal update.

Record what the test proves: the selected examples now agree and the ordinary publishing process preserved the correction. Record what remains unknown: whether other templates share the defect, whether the named account issue has additional causes and whether Google will accept the review. Those limitations should travel with the packet rather than disappear when the status meeting ends.

Prepare a review packet someone else can follow

A review request should make the relevant facts easy to verify. We recommend a short issue summary, the affected scope, a dated change log and representative evidence linked to each correction. Use the platform's requested fields and document requirements; a large attachment bundle is not automatically more persuasive.

Describe the original inconsistency, the responsible system, the change made and the verification performed. Where the issue is disputed, explain the factual disagreement and supply evidence for it. Avoid generic statements that every policy has been followed when your investigation only supports a narrower conclusion.

Separate implementation acceptance from the platform decision. A developer can confirm a template repair. An account owner can confirm the current review action and prerequisites. Only Google's returned decision establishes the outcome of that review. An agency's internal “ready” label must not be presented as approval.

Agree who submits and who monitors the response. Multiple parties making overlapping edits and contacting support without a common incident record can make the chronology harder to reconstruct. Keep subsequent correspondence attached to the same issue history and reassess any new information before proposing another action.

Why is the review button unavailable?

The answer depends on the issue and current account state. Google's review process describes prerequisites, correction and disagreement routes, and cooldown periods. Support cannot bypass or shorten a cooldown. Follow the dates and requirements shown for your account rather than treating a general help-page estimate as an appointment for reinstatement.

Issue-specific instructions can differ. The bypassed-review policy, for instance, has its own process. Do not apply the most convenient timeline from an unrelated issue to your suspension. If the interface and the relevant documentation leave the next action unclear, contact support with the preserved issue details and ask what prerequisite remains.

A missing button is not authorization to open a substitute account, alter ownership, misstate identity or repeatedly resubmit the same unresolved case. During a required wait, continue legitimate investigation and repair. Avoid promising a review date, approval probability or recovery amount to finance.

Relaunch only within the scope actually cleared

After a successful review, verify the returned account and product statuses, applicable markets and advertising destinations. Then inspect connected campaigns and their actual eligibility. Approval of an account issue should not be interpreted as evidence that every product, campaign or commercial claim has been accepted.

Preserve the repaired publishing rules and assign monitoring ownership. Recheck representative offers after promotions, catalog updates, theme releases and changes to shipping or refund operations. A useful operating record includes what changed, which examples were checked and who can respond if the discrepancy returns.

Reassess economics before restoring discretionary exposure. A period without Shopping delivery may coincide with inventory, demand or margin changes. Existing Shopping-versus-Performance-Max guidance can support the later campaign-architecture decision. Changing campaign type is not a substitute for resolving Merchant Center eligibility.

Do not promise to recover missed sales or restore previous ROAS. A reinstatement decision and a profitable acquisition program are separate outcomes, with different evidence. Budget authority should remain with the retailer under the agreed operating arrangement.

What to ask a paid-acquisition partner

Ask for a scoped evidence register, named repair owners, acceptance criteria and an honest list of unresolved questions. Request an explanation of which tasks belong to catalog operations, technical implementation, business verification and media management. Reject guaranteed reinstatement or requests to disguise the seller, replace accounts or hide unresolved offers.

For legitimate e-commerce and DTC teams seeking paid-acquisition support, bring a redacted notice, affected market and product examples, current review state and repair history to an initial conversation. We can examine the handoffs that need investigation and define responsible owners and a validation scope. Any detailed audit or implementation would be agreed separately. The conversation does not promise platform approval, reinstatement, recovered spend or advertising performance.