The Peptide Site Remediation Checklist: What to Fix Before You Appeal
A 40-point, domain-wide remediation checklist for peptide websites before a Merchant Center or Google Ads appeal: identity, policies, product claims, catalogue scope, content, checkout and feed.
Key takeaways
- Remediate the whole domain, not the flagged product. Google’s review reads your products, website, accounts and third-party sources, and a review request applies to every open issue for that country.
- The fastest fixes are the most skipped: one consistent legal name, address, phone and email everywhere, plus visible shipping, refund and privacy policies. Google’s own troubleshooting guidance lists these explicitly.
- Claims are removed, not softened. “Studied for” and “investigated for” phrasing still describes effects on the body; the FDA quoted exactly that language as drug claims in its August 2026 warning letters.
- Catalogue scope is part of remediation. Reconstitution supplies, dosing calculators and prescription-drug-named products change how the entire store is read.
- Keep a dated change log with before-and-after evidence. It is the backbone of an appeal and the only way to know what actually changed.
What should a peptide website fix before appealing a Google suspension?
Before appealing, a peptide website should fix five areas across the entire domain: business identity and contact consistency, visible shipping, refund and privacy policies, product-page claims that describe effects on the body, catalogue items that signal human use (such as reconstitution supplies and dosing tools), and feed data that does not match the site. Appealing before all five are done usually spends a scarce review on a site that still fails.
The checklist below is the one we work through before any review request. It is grouped by area rather than by policy because a single page can breach several policies at once, and because remediation is done page by page. Work top to bottom: identity problems are cheap to fix and block everything else.
Remediation is not repackaging
This checklist brings an honest business into line with what Google and regulators require. It is not a way to disguise a store that sells for human use as a research supplier. If the underlying business model is the problem, copy edits will not change the outcome — and showing reviewers something different from what customers experience is cloaking, which Google treats as its own violation.
How should you run the audit?
- Crawl the full domain. Export every indexable URL — products, categories, blog, FAQ, policy pages, landing pages and any old campaign pages still live. Merchant Center reviewers are not limited to the URLs in your feed.
- Snapshot the current state. Screenshot or archive each page before editing. Your appeal will describe what changed; you need the “before.”
- Open a change log. One row per change: URL, what was changed, why (which policy), date, who. A spreadsheet is fine.
- Work the sections below in order. Mark each item pass, fixed or not applicable. “Mostly” is a fail.
- Re-crawl after edits. Caches, CDN copies and page builders regularly serve old content for days. Verify the live page, not the editor.
Which identity and policy items does Google check first?
These map directly to Google’s published guidance for Misrepresentation and “Website needs improvement” issues.
| # | Check | Pass standard |
|---|---|---|
| 1 | Legal business name | Identical on the site footer, About page, Merchant Center business info, Google Ads billing and payment descriptor |
| 2 | Physical address | A real business address, consistent everywhere; not a bare PO box |
| 3 | Phone and email | Working, monitored, on the domain’s contact page and matching Merchant Center |
| 4 | About page | Explains what the company does and who it serves in plain language |
| 5 | Shipping policy | Costs, carriers, timelines, regions served and regions excluded |
| 6 | Return and refund policy | Conditions, timelines and process; if you do not accept returns, say so clearly |
| 7 | Privacy policy and terms | Present, current, linked from every page footer |
| 8 | Footer links | Shipping, refund, privacy, terms and contact all reachable in one click |
| 9 | Identity verification | Completed in Merchant Center with documents that match the account data |
| 10 | Domain and brand | No imagery, seals or wording implying government, university or pharmaceutical-company affiliation you do not have |
What needs to change on peptide product pages?
Product pages are where most unapproved-substance findings live. Google’s healthcare policy disallows non-approved products marketed in a way that implies they are safe or effective for preventing, curing or treating a disease. The FDA’s August 2026 letters quoted research-hedged copy as evidence of intended human use. Both point the same way.
| # | Check | Pass standard |
|---|---|---|
| 11 | Effect language | No description of what the compound does to a human body — including “studied for,” “investigated for,” “may support” |
| 12 | Disease and condition terms | No conditions, symptoms or body outcomes (weight, healing, libido, sleep, ageing) in titles, bullets or descriptions |
| 13 | Dosing, routes, protocols | No dosages for people, injection instructions, cycle lengths or stacking advice |
| 14 | Product naming | No prescription drug names or confusingly similar codes and abbreviations |
| 15 | Factual specification | Identity, sequence or CAS where applicable, quantity, form, storage, lot number |
| 16 | Testing documentation | Certificates of analysis that are real, lot-matched and from an identifiable lab; no unsupported “99%+ pure” badges |
| 17 | Images | Product photography only; no syringes, before-and-after, physiques or clinical-looking injection shots |
| 18 | Reviews and UGC | On-page reviews moderated — a customer describing their results is a claim on your page |
| 19 | Structured data | Schema and meta descriptions updated too; old claims often survive in page metadata |
| 20 | Legacy URLs | Old product URLs with claims redirected or removed, not just unlinked |
The disclaimer test
Read the page with the “research use only” line covered up. If what remains reads like a supplement or drug listing, the disclaimer is doing no work. The FDA letters make this explicit: disclaimers were noted and then outweighed by the rest of the website.
Which catalogue items put the whole store at risk?
Some products change how every other product on the site is read. These are scope decisions, not copy edits.
| # | Item | Why it matters |
|---|---|---|
| 21 | Bacteriostatic water and reconstitution kits | Cited by the FDA as providing the means to prepare an injectable drug when sold alongside peptides |
| 22 | Syringes, needles, pens | Same inference, stronger |
| 23 | Dosing or “peptide calculators” | Cited in the same letters as evidence of human-use intent |
| 24 | Prescription-drug-named products | Triggers prescription drug rules that a research supplier cannot be certified under |
| 25 | Branded “blends” with outcome names | Names like “Recovery” or “Lean” are claims |
| 26 | Products on Google’s prohibited list | Not appealable; remove from feed and consider removing from site |
You may decide to keep some of these on the site and exclude them from the feed. Understand the trade-off: Merchant Center reviews the website, not only the feed, so excluding an item from Shopping does not remove it from review.
What about blog content, checkout and the feed?
| # | Check | Pass standard |
|---|---|---|
| 27 | Blog and guides | No dosing guides, protocol posts or benefit round-ups; delete or rewrite, do not just unlink |
| 28 | FAQ pages | No “how much should I take” answers |
| 29 | Pop-ups and email capture | No outcome promises in offers or lead magnets |
| 30 | Social embeds and influencer content | Embedded posts are page content |
| 31 | Checkout | HTTPS, working, total cost shown before payment, no hidden subscription terms |
| 32 | Buyer attestations | If used, a genuine step rather than a pre-ticked box |
| 33 | Payment descriptor | Matches the business name customers see |
| 34 | Feed titles | Match the rewritten product pages exactly |
| 35 | Price and availability | Match the landing page, including variants and sale prices |
| 36 | Out-of-stock items | Marked correctly or removed; unavailable offers fall under Misrepresentation |
| 37 | Placeholder text and broken links | None anywhere on the domain |
| 38 | Crawler access | Product and policy pages reachable by Google’s crawlers without a login, challenge page or block |
| 39 | Linked accounts | No suspended Google Ads account linked to the Merchant Center |
| 40 | Data source | At least one product present; Google notes an empty data source can block the review button |
How do you document the fix for an appeal?
The appeal is only as good as the evidence behind it. From the change log, prepare:
- A one-paragraph summary naming the policy cited and stating what category of change was made across the domain.
- A grouped list of changes — identity, policies, product pages, catalogue scope, content, feed — with counts (“rewrote 46 product descriptions,” “removed 3 product lines”).
- Before-and-after examples for the pages most likely to have triggered the finding.
- Documents requested in the flow, such as business registration or identity documents, matching the account data exactly.
Keep it factual. Arguing that competitors are doing the same thing, or that the product is legal, is not a remediation. Google’s Misrepresentation page asks appellants to be “thorough, accurate, and honest.”
How do you know the site is ready to submit?
- Every row in the checklist is pass, fixed or genuinely not applicable.
- The live site has been re-crawled after all edits, with no cached old versions.
- The feed has been re-fetched and item statuses reflect the new pages.
- Someone who did not do the edits has read ten random product pages with the disclaimer covered and found no claims.
- The change log and evidence pack exist before the button is pressed.
Then request the review once. See the six suspension triggers for how the review and cool-down periods work. The Google Ads Readiness Score is a quick self-check against the same categories, and if you want the checklist run by someone who has seen it fail in every way, book a strategy call. Remediation improves your odds; it does not guarantee a decision Google has not made yet.
Sources
- Google Merchant Center Help — Fixing Merchant Center warnings and account suspensions (website audit guidance)
- Google Merchant Center Help — Request a review of your issues
- Google Merchant Center Help — Misrepresentation and Healthcare and medicines
- U.S. FDA — Warning letter 735127, 24 August 2026, and other peptide-seller letters published the same day in the FDA warning letter database
Checked 23 September 2026.
Founder Question
“Can we just add stronger disclaimers and resubmit?”
Our Perspective
A disclaimer states your terms; it does not change what the rest of the page says. Both Google’s policy and the FDA’s 2026 warning letters look at the page as a whole, and the letters explicitly noted research-use disclaimers before concluding the products were marketed for human use anyway. The work is removing what contradicts the disclaimer, not making the disclaimer louder.
Practical Recommendation
- Crawl and snapshot the full domain before editing, then keep a dated change log. It is both your quality control and the backbone of the appeal.
- Fix identity and policy consistency first — it is the cheapest work on the list and blocks everything else if it is wrong.
- Have someone who did not do the edits read ten random product pages with the disclaimer covered. If anything still reads as a benefit claim, the site is not ready.
What we learned
Nearly every stalled recovery we look at has the same shape: the product pages were cleaned, but a guide, an FAQ answer, a customer review or a bac water bundle still told the reviewer what the products were for. The checklist exists because nobody remembers all forty items under pressure, and the one that gets missed is usually the one Google finds.
Frequently asked
How long does remediation usually take?
It depends on catalogue size and how much content carries claims. A small store with clean identity data can be remediated in days; a large catalogue with years of blog content can take weeks. Rushing to appeal before the work is finished is the most common way to lose time.
Do I have to remove bacteriostatic water from my store?
Not necessarily from the business, but understand the risk. The FDA cited bacteriostatic water sold alongside peptides as evidence of injectable human use, and Merchant Center reviews the whole site, not just the feed. It is a scope decision to make deliberately.
Is a research-use-only disclaimer still worth having?
Yes, as an accurate statement of your terms, but it is not a remediation on its own. The rest of the page must be consistent with it.
Should I delete old blog posts or rewrite them?
Either, as long as the claims are gone from the live domain. If a post has search value, rewrite it without dosing or benefit content and keep the URL; if not, remove it and redirect.
Can I fix only the products named in the notice?
You can, but the review applies to the account and site as a whole. Fixing only named items is the most common reason a second review fails.
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 CallRelated articles
Why Merchant Center Suspends Peptide Stores: The 6 Triggers to Check First
The six Merchant Center policy triggers behind peptide store suspensions, how to tell which one you actually hit from the notice, and why the fix diff…
The Google Ads Compliance Checklist for Peptide Companies
A practical, page-by-page compliance checklist for peptide websites and Google Ads accounts, in the order we run it during an audit.…
The Google Misrepresentation Policy, Explained for Peptide Advertisers
Misrepresentation is the most common peptide suspension reason, and the least explained. What reviewers look for, and how to make a site verifiably tr…