Merchant Center

Merchant Center for Peptides: Setup, Suspensions, and Recovery

How Merchant Center reviews peptide product data, the suspension reasons that actually occur, and a sequenced recovery process that does not restart the review clock.

Key takeaways

  • Merchant Center reviews your product data and the landing page behind every item. Fixing the feed alone rarely lifts a suspension.
  • Most peptide suspensions we see are misrepresentation or unapproved-substance related, not technical feed errors.
  • Requesting review before every issue is fixed is the single most costly mistake — each failed request burns time and goodwill.
  • Verification, claim, and business-information hygiene should be complete before the first feed upload.

How Merchant Center review actually works

Merchant Center evaluates three layers: your account (entity, verification, contact, policies), your product data (titles, descriptions, attributes, images, prices, availability), and your destination pages (what a shopper sees when they click). A peptide catalogue can be technically flawless in the feed and still be suspended because destination pages read as consumer therapeutics.

Automated checks catch structure. Human review catches meaning. Peptide accounts almost always get human review at some point, which is why consistency across the whole domain matters more than optimisation of any single field.

The pre-upload checklist

  • Website verification and claim complete, with a matching legal entity name.
  • Business information filled fully: address, customer service contact, and a working returns policy page.
  • Checkout live and testable — a reviewer will attempt to reach the cart. Broken or gated checkout without explanation is a fast disapproval.
  • Shipping and tax configured to real, non-placeholder values.
  • Research-use presentation consistent from product page through cart and checkout.
  • Documentation (COA, purity, batch) linked from product pages.

Sequence matters

Submit a small, clean subset of products first. A 900-SKU upload into an unverified account is how one policy problem becomes an account-level suspension.

Writing peptide product data that survives review

FieldAvoidPrefer
TitleOutcome or condition language, dosage protocols, superlativesCompound name, specification, quantity, purity reference, form
DescriptionUsage instructions, benefits, testimonialsComposition, storage, handling, documentation, intended research context
ImageLifestyle shots, syringes in use, body imageryClean product photography on white, label legible
AttributesBlank GTIN/brand/condition, guessed categoriesComplete identifiers, correct product category, accurate availability

Incomplete identifiers are also a silent performance tax: items with missing attributes compete poorly even when approved. See Peptide Google Shopping for the structure side.

The suspension reasons that actually occur

  1. Misrepresentation. Entity, contact, policy or claim gaps. Usually resolved with site changes, not feed changes.
  2. Unapproved substances / restricted products. Human-use framing anywhere on the destination path.
  3. Policy violation on a subset of items. Often one legacy collection or a handful of imported descriptions.
  4. Mismatched product data. Price, availability or variant mismatches between feed and page.
  5. Repeat violation after a failed review request. The most avoidable category.

A recovery process that does not waste review cycles

  1. Read the exact notice. The stated reason narrows the search dramatically; do not start a general clean-up before reading it.
  2. Audit the whole domain against that reason: product pages, collections, blog, FAQs, reviews, images, PDFs.
  3. Fix and document. Keep a written change log with URLs and dates — it is useful if you need escalation later.
  4. Verify propagation. Cached pages, CDN copies, and app-generated pages frequently still show old content.
  5. Re-crawl your own site to confirm no remaining page contradicts the fix.
  6. Then request review, once, with a clear summary of what changed.

Do not

Do not create a second Merchant Center account, move to a new domain, or lightly reword the same claims. All three are read as circumvention.

Founder Question

“Support keeps sending us the same policy link. How do we actually get a human answer?”

Our Perspective

You usually don’t — and building a strategy around getting one is a trap. The productive path is to treat the policy link as the specification and make your site and product data unambiguously satisfy it, then submit once with a documented change set. In our experience, accounts that recover are the ones that stopped negotiating and started removing ambiguity.

Practical Recommendation

  1. Fix the destination pages before you touch the feed. In the suspensions we review, the product data is usually a symptom and the landing page is the cause.
  2. Submit a small, clean subset of your catalogue first. A 900-SKU upload into an unverified account is how one policy problem becomes an account-level suspension.
  3. Document every change with dates before requesting review. Appeals are far easier to argue when you can show what changed and when.

What we learned

In our experience, the accounts that recover fastest are the ones that treat a suspension as a site-wide documentation project rather than a feed ticket. The ones that stay suspended are almost always the ones that requested review before every contradicting page was found and fixed.

Frequently asked

How long does a Merchant Center review take?

Review requests commonly take several business days, and complex or repeat cases take longer. Treat each request as a single, well-prepared attempt rather than an iteration loop.

Can I advertise on Search while Merchant Center is suspended?

Frequently yes, depending on the reason and whether the issue is account-level. A Merchant Center suspension and a Google Ads account suspension are separate events, though the same root cause often triggers both.

Do I need GTINs for peptides?

Where identifiers exist, supply them. Where they genuinely do not, use the correct identifier-exists handling and make brand and MPN complete and consistent instead of leaving fields empty.

Next step

If you want this applied to your account and your site rather than read in the abstract, book a 30-minute strategy session. We will look at the domain before the call.

Book a Strategy Call

Want this reviewed on your account?

Book a 30-minute strategy session. We look at your site and account before the call, so the time goes on decisions rather than discovery.

See a Sample Readiness Report →