Certificates of Analysis on Peptide Sites: How to Publish Testing Evidence Without Creating Claims Risk

How should a peptide company publish certificates of analysis without creating compliance risk?

Publish each COA as a batch-level specification record. The batch number should match what ships, and the record should show the testing lab, methods, test date and a way to verify it. Keep every benefit, research and dosing statement off the COA page. A COA can support objective claims about identity, purity and content for the sample tested. It cannot support claims about safety, effects or regulatory status, and presenting it as if it does creates risk with Google, with payment underwriters and with regulators.

Almost every peptide store publishes COAs now. The ones that cause trouble tend to fail in one of three ways. The COA is used as a platform for efficacy copy. The site makes a blanket purity claim the COAs do not support. Or the COA cannot be tied to what the customer actually receives. All three can be fixed without removing testing evidence.

What does a certificate of analysis prove, and what does it not prove?

Test commonly on peptide COAs	What it can support	What it does not support
HPLC purity	The percentage of the main peak for the sample tested, by that method	Purity of other batches; absence of contaminants the method does not detect
Mass spectrometry (identity)	That the molecular mass observed is consistent with the stated compound	Quantity per vial; purity
Content / quantity assay	The measured amount in the vial tested versus the label	Consistency across the lot unless several samples were tested
Endotoxin (e.g. LAL)	The endotoxin result for the sample, against the stated limit	Sterility; suitability for any human use
Sterility / microbial	The microbial result for the sample, by the stated method	Manufacturing controls (that is GMP, not testing)

None of these tests says anything about what a compound does in a body, whether it is safe, or whether it is approved. That boundary matters for the copy you write around the COA.

Accreditation has limits as well. ISO/IEC 17025 is the international standard for the competence of testing and calibration laboratories. National accreditation bodies grant it for a defined scope of methods. A lab can be accredited for HPLC purity and still run other tests outside that scope. There is no such thing as an “ISO 17025 certified peptide”. If you mention accreditation, name the accreditation body and link to the lab’s public scope document.

What do Google, underwriters and regulators look at on a COA page?

• Google Ads and Merchant Center. The Misrepresentation policy prohibits “inaccurate claims” under Unreliable claims. It also prohibits making it seem you are supported by another organization when you are not. A COA page that implies a lab endorses your products, or that the product is approved, runs into both. The Healthcare and medicines policy is still assessed on the whole destination.
• Payment underwriters. Underwriters read the site for claims and for whether the business is what the application says it is. Consistent, dated, batch-matched testing records are one of the few trust signals a peptide site can show that do not involve claims. Our payment underwriting guide covers what else they review.
• FDA. In the warning letters we read for this guide, the COAs were not the issue. What FDA quoted was the surrounding copy. Letter 735063 to Peptide Partners (24 August 2026) listed statements from product pages, including “This laboratory study … suggests that semaglutide could have potential benefits for bone health” and that SS-31 “could be a potential treatment to protect the retina”. These were research summaries, and FDA treated them as evidence of intended use. Letter 721806 (31 March 2026) did the same with “studied for” copy despite “Research Use Only” labelling.
• FTC. The FTC’s policy statement on advertising substantiation says objective claims need a “reasonable basis” before they are disseminated. “Every batch third-party tested” and “99% purity” are objective claims.

Which testing and purity claims need changing?

Common wording	Why it creates risk	Safer version
“99%+ purity guaranteed” (site-wide)	Objective claim applied to every batch, including untested ones; a guarantee you cannot substantiate	“HPLC purity for batch [ID]: [result]% (tested [date] by [lab])” on each product
“Pharmaceutical grade”	Implies a regulatory or compendial standard the product may not meet	Describe the actual specification and the test used
“Tested in an FDA-registered lab”	Suggests FDA oversight or approval of the product	Name the lab and, if true, its accreditation body and scope
“Clinically tested” / “lab-proven safe”	Safety or clinical claim that analytical testing cannot support	Remove
“Every batch third-party tested”	Fine if literally true; misleading if some batches are tested in-house or not at all	Keep only if every live batch has a published COA; otherwise say which products are tested
Lab logo as a badge	Can imply endorsement by the lab	Plain-text lab name and a link to the report or verification page
COA with a “Benefits” or “Research” section beside it	The copy FDA quoted in 2026 letters	COA page with specifications only

What should a COA page contain?

Use this as a checklist. Each item gives a reviewer something they can check:

1. Batch or lot number that matches the label on the product currently shipping. If you have several batches in stock, publish each one.
2. Testing laboratory name, as the lab names itself, with location.
3. Methods for each result (for example HPLC for purity, mass spectrometry for identity) and the limit or specification each result is compared against.
4. Sample date and report date. A report older than the batch is a mismatch that reviewers notice.
5. Verification route. A QR code, report ID or link to the lab’s own verification page, where the lab offers one. An unverifiable PDF is weaker evidence.
6. An unedited document. Do not crop, restyle or overlay marketing on the lab’s report. If you add your own summary, label it as yours and make sure it matches the report exactly.
7. Accreditation, only with evidence. Name the accreditation body and link to the scope, or say nothing.
8. A retention rule. Keep superseded COAs on file with dates. If Google, a processor or a regulator asks what your page showed in a given month, you should be able to answer. Our appeal guide explains why dated records matter.

Keep the COA page separate from any page with usage, protocol or research content, and do not link from the COA to a dosing calculator. Our site remediation checklist covers the rest of the product page.

How do you check a testing lab before relying on its reports?

Your COA is only as credible as the lab behind it. Before relying on a lab, check:

• That the lab exists and operates. Look for a physical address and a service description on its own website, not only on vendor pages.
• Scope, not just the word “accredited”. Find the lab in the accreditation body’s directory and read which methods are on the scope.
• Independence. Is the lab third-party, or connected to your supplier? Say which on the page.
• Whether reports can be verified. Public verification databases or report IDs make fabricated or edited COAs easier to catch, and edited COAs are a documented problem in this market.

We maintain a Peptide Testing Facilities directory that records which facilities state their services, methods and accreditations on their own websites. Its methodology explains how each point is evidenced. Use it as a starting point for your own checks, not as a substitute for them.

Do COAs help with Merchant Center or Google Ads approval?

Not directly. Google does not publish a COA requirement for peptide products. A COA does not change how the Healthcare and medicines or Unapproved Substances policies apply to a product. What it can do is support the transparency side of a review. Clear business identity, specifications that match the feed, and claims you can back up all bear on Misrepresentation, which is where many peptide suspensions sit. See why Merchant Center suspends peptide stores.

Two practical points. First, make sure the product title, quantity and form in your feed match the COA and the product page. Mismatches between feed and landing page are a common product-level disapproval. Second, a COA does not justify naming a product in a way Google considers confusingly similar to an unapproved substance.

If you want a quick read on where your site stands, the Readiness Score takes about five minutes. For a page-level review before an appeal or launch, book a strategy call.

Sources

• U.S. FDA — Warning letter 735063, Peptide Partners LLC (24 August 2026) and Warning letter 721806, Gram Peptides (31 March 2026)
• U.S. FTC — Policy Statement Regarding Advertising Substantiation and Health Products Compliance Guidance (December 2022)
• Google Advertising Policies Help — Misrepresentation (Unacceptable business practices, Unreliable claims) and Healthcare and medicines
• ISO — ISO/IEC 17025 testing and calibration laboratories
• Microsoft Advertising — Healthcare and Pharmaceutical Ad Policy (updated 1 July 2026): ads and landing pages must not include “statements that misrepresent regulatory approval or review of a product”

Checked 2026-09-30. This is not legal advice; have counsel review product and testing claims.

Frequently asked