A research-use-only disclaimer alone won't pass Google Ads review. Here's the specific copy pattern — with before/after examples — that actually works.
A research-use-only disclaimer on its own doesn't get a peptide brand's landing page through Google Ads review. As covered in our breakdown of the Unapproved Substances policy, Google's reviewers — automated and human — look at the entire user journey, and a disclaimer that contradicts the rest of the page copy won't hold up. What actually works is a specific pattern of language, structure, and framing across the whole page, not a single line of boilerplate legal text.
This is what that pattern looks like in practice, with real before/after examples.
The single highest-leverage shift in research-use-only copy is moving from outcome language to specification language. Outcome language tells the reader what will happen to them. Specification language tells the reader what the product is.
Before (outcome-framed, high risk): "BPC-157 helps repair damaged tendons and speeds up recovery from injury."
After (specification-framed, compliant): "BPC-157 is a synthetic peptide studied in preclinical research for its interaction with tissue repair pathways. Sold strictly for laboratory and research use."
The second version describes the compound's research context without telling the reader what it will do for them personally. That distinction — third-person research description versus second-person outcome promise — is the line Google's reviewers are trained to look for.
The hero section carries the most weight because it's often what gets scanned first by both human reviewers and automated systems cross-referencing against ad copy. Avoid:
Use instead:
Product-level copy is where most brands unintentionally reintroduce risk after getting the hero section right. A common pattern: a compliant hero section sits above a product description that lists "recommended dosage," "how to use," or a comparison table implying use cases. Any dosing or usage-instruction content anywhere on the page — even below the fold, even in a collapsed FAQ accordion — reframes the entire product as intended for consumption rather than research, and Google's review process reads the full page, not just the visible-on-load section.
What belongs in a compliant product description: molecular formula, molecular weight, CAS number where applicable, purity specification, storage and handling requirements framed for laboratory conditions, and third-party testing or Certificate of Analysis availability. What doesn't belong: dosage ranges, administration frequency, "how to use" content of any kind, or any language implying the product is intended to be consumed or administered to a person or animal outside a research setting.
This is the most commonly missed compliance surface. Brand-written copy is easy to control; customer-submitted reviews are not, and Google's review process reads visible on-page reviews the same way it reads brand copy. A landing page with perfectly compliant hero and product copy sitting above a reviews widget full of "this fixed my shoulder in two weeks" comments creates exactly the ad-copy-versus-destination-content mismatch that fails appeals.
Practical options: moderate reviews before publishing to filter out outcome-claim language, disable public reviews entirely on higher-scrutiny SKUs, or replace an open review widget with curated, pre-approved testimonial copy that's been written to stay within the same specification-forward framing as the rest of the page.
FAQ content is a common place brands accidentally undo compliant copy elsewhere on the page, because FAQ answers tend to get written more casually — answering the question a real customer would actually ask ("how much should I take?") rather than staying within research-use framing. Any FAQ entry addressing dosage, administration, or expected personal outcomes should either be removed or rewritten to redirect toward research-context information instead of direct answers to consumption questions.
Pages that pass review consistently tend to follow the same shape: hero section with research-context headline and clear "for laboratory/research use only" statement near the top (not just in a footer disclaimer), specification-forward product description, sourcing and testing information, a compliant FAQ, and either no reviews section or a moderated one. This mirrors the broader landing page compliance checklist we cover in our full audit guide, applied specifically to the copy layer rather than the technical/structural layer.
No — even a brief, qualified mention of a use case ("some researchers have studied this for...") reads as an implied benefit claim to Google's review systems. Keep all use-case-adjacent language in third-person research-literature framing, citing published research rather than implying an outcome for the reader.
Yes, generally — any content a visitor can reach from the landing page, including linked PDFs, is fair game for review. Make sure CoAs and any linked documents follow the same specification-only framing as the main page.
No — the disclaimer needs to be visible on the actual landing page the ad sends traffic to, not buried later in the purchase flow. Google's review evaluates the destination the ad promises, not the full site.
At minimum whenever ad copy changes, a new product launches, or Google's policy pages are updated — and as a standing quarterly check even without a specific trigger, since customer reviews and other user-generated content can drift out of compliance over time even when the brand's own copy hasn't changed.
See the exact landing page framework used in a compliance-first account rebuild.
Get a free 30-minute audit of your Google Ads or Meta Ads account. We’ll review compliance, structure, and growth opportunities — no strings attached.
Book a Free Audit