Product Disapproval vs. Account Suspension in Merchant Center: What Peptide Stores Should Fix First

What is the difference between a product disapproval and an account suspension?

A product disapproval is an item-level decision: one product fails the product data specification or a Shopping policy, stops showing on Google, and the rest of your catalogue is unaffected. An account suspension is an account-level decision: Google has concluded that your website, business information or product data as a whole breaks its policies, and every product in the account stops showing for that country. The first is a data problem you fix item by item; the second is a trust problem you fix across the whole domain before asking for one review.

Google’s own help centre draws the line plainly. Product-level issues “only affect individual products, not your entire account.” Account-level issues “impact all of your products in Merchant Center.” Both come in two strengths — a warning, which lets items keep showing with possibly limited performance, and the hard version, a disapproval or a suspension.

For peptide stores the distinction matters more than usual, because the same underlying problem — a page that reads like a drug claim — can surface either way. One product with a benefit claim in its title may be disapproved on its own. The same language repeated across the site, blog and FAQ is more likely to be read as an account-level problem. For the triggers that most often lead to account-level action, see why Merchant Center suspends peptide stores.

How do you tell which one you have?

Look at where the issue appears and how many products it covers. The table below is built from Google’s Merchant Center documentation, read on 23 September 2026.

	Product-level issue	Account-level issue
Where it appears	“Needs attention” tab under Products, and on each product’s detail page	A banner at the top of the account; also via “View setup and policy issues” on the Needs attention tab
Scope	The affected item only (and only in the affected country)	Every product in the account for that country
Warning version	Item keeps showing; performance may be limited; can become a disapproval	Warning email with examples and a 7- or 28-day warning period; products keep showing
Hard version	Disapproved item stops showing	Suspension: all products disabled from appearing across Google
Typical cause	Data mismatches, missing attributes, landing page problems, a single policy-violating product	Website-wide policy issues such as misrepresentation, business transparency, or repeated or egregious violations
How to resolve	Fix the data at source, then “Request website check” or “I disagree with the issue”	Fix the site and account, complete identity verification if asked, then “I fixed the issue” or “I disagree with the issue”
Review time	Up to 7 business days; fresh crawls after a fix usually finish within 24–48 hours	Up to 7 business days; the review covers all issues for the country

What causes product-level disapprovals on peptide stores?

Google lists the common website causes of product disapprovals: placeholder content, broken links, missing or inconsistent information, inaccurate descriptions, categories that differ between the site and the data, robots.txt blocking Googlebot or Googlebot-Image, unavailable or slow landing pages, and landing pages that redirect to a generic page instead of the product.

On peptide catalogues, four patterns come up repeatedly. We describe them as recurring patterns, not measured frequencies:

• Data drift. Prices, sale prices or stock status change on the site but not in the feed. This is the classic route to preemptive item disapproval. Google’s automatic updates for price, availability and condition can correct small gaps if your product pages carry structured data, but Google says they are not a replacement for regular feed updates.
• Titles and descriptions carrying claims. App syncs often push the full product body into the description attribute, so any benefit, dosing or “studied for” language on the page goes straight into the feed. Google then reviews the item against its healthcare and unapproved-substance rules.
• Identifier and category gaps. Many peptide products have no GTIN. That is allowed when it is true, but the data must say so honestly rather than inventing identifiers.
• Landing page problems. Age gates, pop-ups or bot protection that stop Google reaching the product page, and variant URLs that land on a collection instead of the item.

If the feed itself is the recurring source of trouble, read manual feeds for peptide catalogues.

When does a product problem become an account problem?

Google describes three routes from item trouble to account trouble:

1. A warning that is not resolved. If you do not request a review during the warning period, Google re-reviews at the end of it. If any issues remain, “your account will be suspended and your products will be disabled from appearing across Google.”
2. Repeated or severe violations. Google’s guidance for Shopify merchants states that offers can be disapproved when they break policy and that “repeated or severe rule violations may lead to an account suspension.”
3. Egregious issues. “In some cases when an egregious account-level issue is detected, no warning is given and the account is suspended immediately.” For Misrepresentation, suspension on detection without warning is Google’s stated approach.

There is also a fourth route that operators miss: the initial review. When products are uploaded to an account for the first time, Google reviews products and website together, typically within 3–5 business days for Shopping ads. If that review finds non-compliance, Google says the account is suspended immediately. A brand-new peptide store therefore skips the item-level stage entirely.

What should you fix first?

Use the status you are actually in, not the one you fear. This is the sequence we use:

Status	First move	Then
Account suspended	Stop all feed and account changes; record the exact policy named and the country	Complete identity verification if requested, remediate the whole domain, fix product data, then one review request
Account warning (7 or 28 days)	Read the examples in the warning email; they point to the pattern	Fix or remove violating products and pages; use the one courtesy review only when everything is done
Preemptive item disapproval	Fix price and availability at source; add product structured data; turn on automatic updates	Request a review once the site and data agree
Product disapprovals only	Download the affected-items CSV and group by issue	Fix each group at the source (site or feed), then request website checks in batches

Two rules make the order non-negotiable. First, an account-level review “will apply to all issues for the country,” so a half-fixed catalogue drags down the whole request. Second, Merchant Center limits attempts: if issues are not resolved by the second review attempt, a one-week cool-down may begin, it may lengthen with each unsuccessful review, and Google says support cannot shorten it.

During a warning period, Google also notes that if the violating products are removed from the account, you do not need to request a review; the account is re-reviewed automatically at the end of the period. That is a legitimate option when a product line cannot be made compliant — provided the product also comes off the website.

Should you delete disapproved products, exclude them, or fix them?

Option	What it does	When it is right
Fix the data	Corrects the item so it can be re-approved	Data mismatches, missing attributes, titles or descriptions with claims that can be rewritten
Fix the landing page	Corrects what Google crawls	Unavailable pages, blocked crawlers, page copy that contradicts compliant positioning
Exclude from a destination	excluded_destination keeps the item in the account but out of Shopping ads or free listings	Items you sell but choose not to advertise; not a fix for a policy violation
Remove from feed and site	Takes the product out of Google’s view entirely	Products that cannot be sold compliantly under the policy cited
Disagree	Asks Google to reverse the finding	Only when you can evidence that the decision was wrong; Google notes you may get one chance

For advice on wording a disagreement or a fix summary, see how to write an appeal that gets read.

How long does each path take?

These are the timings Google publishes. Anything beyond them — including “our client was back in three days” stories — is anecdote, not a clock you can plan around.

Stage	Published timing
Initial review of a new account	Up to 3–5 business days for Shopping ads; may be longer for other programmes
Account warning period	7 or 28 days, with one courtesy review available at any time during it
Review after a request	Up to 7 business days, at account and item level
Fresh crawl after a fix	Usually within 24–48 hours
Cool-down	May begin if issues are not resolved by the second attempt; one week initially; may increase; cannot be shortened by support
After approval	Approved products eligible to show within 24 hours

If you are not sure which state your account is in, or whether your site would survive an account-level review, run the Google Ads Readiness Score or book a strategy call. We cannot promise reinstatement or approval; we can help you avoid spending review attempts on a site that is not ready.

Sources

• Google Merchant Center Help — Issues in Merchant Center (product-level vs account-level issues, PID, initial review)
• Google Merchant Center Help — Request a review of your issues (review timing, warning periods, cool-down)
• Google Merchant Center Help — Fixing Merchant Center warnings and account suspensions for policy violations (Shopify merchants)
• Google Merchant Center Help — Automations and product data optimizations
• Google Merchant Center Help — Product data specification

Checked 23 September 2026. Google changes its help content without notice; the text in your account notice governs.

Frequently asked