A peptide product page is read by three audiences at once: the buyer deciding whether to trust you, Google’s systems checking it against your product feed, and anyone assessing what your store intends its products to be used for. This guide is for owners and marketers of research-use-only (RUO) peptide stores. It sets out what the page should contain and in what order, from the title and certificate of analysis to reviews, Product schema and mobile layout. It is general information, not legal or regulatory advice.
- Describe the material, not a use. Identity, purity, form, quantity and storage belong on the page. Effects, dosing and human-use language do not.
- Put the batch evidence next to the buy button. A lot number, a stated purity and a link to that lot’s certificate of analysis (COA) do more for trust than any badge.
- The page and the feed must agree. Google checks the landing page for title, description, image, price, currency, availability and a buy button, and compares them with your product data.
- Policies are part of the product page. Shipping costs, returns and contact details have to be easy to find before purchase. Google treats leaving them out as misrepresentation.
- Reviews are your content once you publish them. Moderate for human-use statements with a written rule applied to positive and negative reviews alike, and never write or buy reviews.
- A good page is necessary, not sufficient. Google restricts unapproved pharmaceuticals in Shopping. No template guarantees approval.
- What the page has to do
- The page order, with an annotated wireframe
- Title and description
- COAs, batch data and third-party testing
- Images that meet Google’s image rules
- Pricing, quantity breaks, shipping and returns
- The RUO acknowledgement and reviews
- Product schema, page speed and mobile layout
- Merchant Center approval, conversion and a pre-launch checklist
- FAQ
- Sources
1. What the page has to do
Most product page advice assumes one reader. An RUO peptide page has three, and each reads for something different.
- The buyer wants to confirm what the material is, how pure this lot is, what it costs delivered and whether the supplier is real.
- Google wants the page to match the product data you submitted. Its landing page requirements list the key elements it expects: title, description, image, price, currency, availability and a buy button. The same page says all the information in the data source will be verified.
- Regulators and payment underwriters read the page as evidence of intended use. Under 21 CFR 201.128, intended use can be shown by labelling claims, advertising matter, or oral or written statements, and by the circumstances surrounding distribution.
The third reader is not hypothetical. FDA warning letters to peptide sellers, including TXP Innovations (24 August 2026), Prime Sciences (31 March 2026) and Summit Research Peptides (10 December 2024), each say that website evidence established intended human drug use despite research-use labelling. The evidence they quote is mostly the sellers’ own product-page text. The TXP and Prime Sciences letters also point to bacteriostatic water sold alongside the products, and in one case a kit with a syringe. Our RUO website compliance checklist covers what those letters flag across the whole site.
A template cannot make a product eligible. Google’s Shopping ads and listings policies place unapproved pharmaceuticals and supplements under restricted healthcare content and say some content may not be listed anywhere. Google’s healthcare and medicines policy for ads does not allow certain products regardless of any claims of legality. Neither page mentions research use only as an exception. Build the page to be accurate. Do not build it to look like something it is not.
2. The page order, with an annotated wireframe
Order matters because most buyers decide from the first screen, and because Google’s crawler reads the same page. The principle is simple: identity and evidence first, policies before the purchase, long-form detail below.
| # | Element | Where | Why it sits there |
|---|---|---|---|
| 1 | Product title | Top of the buy box | Must describe the same product as the feed title |
| 2 | Main image and gallery | Top left, or first on mobile | Google expects an image on the landing page. The buyer checks it against the label |
| 3 | Identity line | Under the title | Form, quantity per vial, CAS number where one exists, catalogue number |
| 4 | Purity and batch strip | Under the identity line | Stated purity, current lot number, link to that lot’s COA |
| 5 | Price, variants, quantity breaks | Buy box | Price and currency must be clearly shown and match the feed |
| 6 | Availability | Next to price | Google checks that availability is clearly shown |
| 7 | RUO statement and add to cart | Buy box | The statement is read at the moment of purchase |
| 8 | Shipping and returns summary | Directly under the button | Costs and conditions disclosed before purchase |
| 9 | Description and specification table | Below the first screen | Full identity data for buyers who read on |
| 10 | COA panel and testing method | Below the description | The document itself, with the lab’s name |
| 11 | Storage and handling | Below the COA | Laboratory storage conditions for the material |
| 12 | Reviews | Near the bottom | Service and quality feedback, moderated |
| 13 | Business details | Footer | Legal name, address, contact route, policy links |
Infographic: annotated product page wireframe
RUO peptide product page wireframe
Numbers match the table above. On a phone the blocks stack top to bottom, image first.
3. Title and description
The on-page title and the feed title do not have to be identical. Google’s title attribute page says they should refer to the same product. In practice we keep them the same, because it removes one source of mismatch.
Title
Google allows 1 to 150 characters for a feed title and says not to include promotional text or capital letters for emphasis. Price, sale and delivery information do not belong in a title either. A workable pattern for an RUO page is:
[Compound name] [quantity per vial] [form], for research use only
Put the most identifying words first, because Google says it will truncate titles that do not fit.
Description
Google’s description attribute page allows up to 5,000 characters, asks you to describe only the product itself, and says not to include promotional text, links to your store or other sites, or comparisons with other products. That suits an RUO page well. Write the description around four things:
- Identity. Chemical name and synonyms, sequence, molecular formula, molecular weight, CAS number where one is assigned.
- Purity. The figure for the current lot and the method used to measure it.
- Form. Physical form, appearance, quantity per vial, container type.
- Storage. Recommended storage conditions for the material as supplied.
| Page element | Write this | Not this |
|---|---|---|
| Title | Compound, quantity, form, RUO | Outcome words, prescription brand names, “best”, “sale” |
| Opening line | What the material is and its stated purity | What it “does”, who it is “for”, or what studies “suggest” it may treat |
| Quantity | Mass per vial | “Doses per vial”, “weeks of supply” |
| Handling | Storage temperature, protection from light and moisture | Reconstitution-for-injection steps, calculators, injection supplies |
| Related products | Other catalogue items by category | “Stacks”, kits with syringes, “frequently used with” |
| Image alt text | “[Compound] 10 mg vial, lot label” | Body-part or outcome descriptions |
The “not this” column is drawn from the kind of text the FDA letters quote. The Prime Sciences letter cites a product title that paired a prescription brand name with “Weight Loss Supplement” and an “Application” line about disease treatment. A research-use footer did not outweigh either. For a wider treatment of site wording, our Google Ads for peptides page covers how page text and ad text are reviewed together. For feed titles specifically, see our guide to peptide product feed optimization, and for choosing the words themselves, peptide keyword research.
4. COAs, batch data and third-party testing
A certificate of analysis is the strongest trust signal an RUO page can carry, and it is also plain product information. How it is presented decides whether a buyer believes it.
Make it lot-specific
- Show the current lot number near the buy button, and link it to the COA for that lot. A single undated PDF reused across every batch tells the buyer nothing about the vial they will receive.
- Match the label. The lot number on the page, the COA and the vial should be the same string.
- Keep an archive. List previous lots with their COAs on the page or in a COA library, so a customer holding an older vial can find its document.
- Update on changeover. When stock moves to a new lot, change the page figure and the linked document together.
What a buyer looks for on the document
- Product name, lot number and quantity tested
- Test date and the date of the report
- Methods, for example HPLC for purity and mass spectrometry for identity
- Results as numbers, with the chromatogram or spectrum where the lab supplies one
- The name of the laboratory that ran the tests, and a report or sample reference
Third-party testing
If you say “third-party tested”, the page should name the laboratory and say which tests it ran on which lot. If testing was done in-house or by the manufacturer, say that. The accurate statement is the safe one: Google’s misrepresentation policy does not allow inaccurate claims, and a purity figure the document does not support is an inaccurate claim.
A COA reports what was measured on a sample of a lot. Present it as that. Do not describe the material as “pharmaceutical grade”, “sterile”, “safe” or “clinically tested” unless a document you hold says exactly that, and be aware that such words also describe a use. Purity is a quality statement about a research material. It is not a suitability statement.
5. Images that meet Google’s image rules
Google’s image link attribute page sets the rules for the main feed image, and the same image normally leads the product page.
- Show the exact item. The primary image must clearly display the item being sold. No placeholders, generic images or graphics that do not show the product.
- No overlays. No promotional elements, watermarks or graphic stamps on the main image. That rules out purity badges and “lab tested” seals placed over the photo. Put those facts in text beside the image.
- No borders.
- Size. At least 500 x 500 pixels, with around 1500 x 1500 or above recommended. Google’s page says enforcement of the 500 x 500 minimum for all product images begins on 31 January 2027.
Beyond Google’s rules, the picture is also a statement about use. A photograph of the sealed vial with a legible label, including the research-use statement and lot number, supports the page. Syringes, needles, alcohol swabs, body imagery, gym or clinic settings and before-and-after pictures contradict it. Keep them out of the gallery, the lifestyle banners and the category thumbnails. Use secondary images for the label close-up, the packaging and a thumbnail of the COA.
Image handling in the feed is covered in more depth on our Google Shopping for peptides page, and creative for ads in our Performance Max for peptides guide.
6. Pricing, quantity breaks, shipping and returns
One clear price
Google’s landing page requirements say to clearly show the price, in the currency of the product data, and to not change displayed product information after initial loading. Its mismatched price page says the prices in the page HTML need to match exactly the prices uploaded to Merchant Center, and that Googlebot reads structured data to verify pricing.
For an RUO store this has three practical consequences.
- The default price is the feed price. Whatever variant loads first should show the price submitted for that variant’s feed item.
- Quantity breaks go in a table. Show the single-unit price as the main price and list the breaks beneath it, for example by number of vials and price per vial. Do not display the lowest tier as the headline figure if a buyer of one unit pays more.
- No surprises at checkout. Google’s checkout requirements say the price must not increase at checkout and that mandatory fees must be clearly shown. Card surcharges and handling fees added at the last step fall foul of that.
Shipping
Google lists not disclosing all applicable shipping costs as a misrepresentation issue. State the cost or the rule for calculating it, the free-shipping threshold if you have one, the dispatch time and the regions you ship to, in two lines under the buy button with a link to the full policy. Shipping rates in Merchant Center may be overestimated, as long as they are not higher on your store at checkout.
Only promise dispatch times you can meet. The FTC’s Mail, Internet, or Telephone Order Merchandise Rule guide says a seller must have a reasonable basis for any shipping time it states or implies, and for shipping within 30 days where no time is stated, and sets out delay notices and refunds when that is missed.
Returns
Google’s return policy page asks for clear and conspicuous refund and return information on the website, reachable without logging in and consistent with what you enter in Merchant Center. It should state the time frame, the method and any fees, and address ordinary change-of-mind cases as well as defective items. Many RUO stores do not accept opened material back. That can be a legitimate position, but it has to be written down, disclosed before purchase and applied as written. Google lists denying a refund that your own policy allows as an unacceptable practice.
Clear terms also reduce disputes. See peptide payment processing for how processors read the same pages, and our guide to chargebacks and processor redundancy.
7. The RUO acknowledgement and reviews
The acknowledgement
State the research-use condition in three places: in the title or first line, beside the add-to-cart button, and as a tick-box the buyer must accept at checkout that links to your terms. Keep the wording short and literal, for example that the product is sold for laboratory research use only and is not for human or veterinary use.
Two cautions apply.
- The statement does not carry the page. Each of the FDA letters cited above reached its conclusion despite a research-use statement, because the rest of the site said otherwise. The acknowledgement is consistent with a compliant page. It does not create one.
- Do not hide the product behind it. A full-page gate that keeps the title, price, availability or buy button from loading until a visitor clicks through works against Google’s requirement that the landing page show those elements and not change them after loading. Place the acknowledgement at add-to-cart or checkout. Show Google’s crawler exactly what a visitor sees. Serving it something different is cloaking, and we do not do that.
Reviews
None of the three FDA letters we read cites customer reviews. The evidence quoted is the sellers’ own copy, product names, bundled items and, in one letter, social media posts. Even so, a review you choose to display is text published on your product page, and 21 CFR 201.128 looks at written statements and the circumstances of distribution. Our working rule is that reviews describing personal use, dosing or outcomes should not appear on an RUO product page.
That has to be done without distorting the reviews themselves.
- Publish a moderation rule. Say that reviews mentioning human or animal use, dosing or health outcomes are not published, whatever the star rating.
- Apply it to content, never to sentiment. A one-star review about slow delivery stays up. A five-star review describing personal results does not.
- Ask about what you can stand behind. Prompt reviewers on packaging, delivery, documentation and support.
- Never write, buy or seed reviews. The FTC’s Consumer Reviews and Testimonials Rule, in effect since 21 October 2024, covers fake reviews, incentives conditioned on a particular sentiment and undisclosed insider reviews, and allows civil penalties for knowing violations. It also has provisions on review suppression. Read the FTC’s questions and answers, and take advice, before you finalise moderation rules.
- Edit nothing. Publish a review as written or do not publish it. Rewriting a customer’s words to remove a claim makes it your statement.
8. Product schema, page speed and mobile layout
Product structured data
Google’s merchant listing documentation is the reference for pages where a shopper can buy. In summary it asks for a Product with a name, an image and an Offer, and for the Offer to carry a price above zero and a currency. Availability, identifiers, shipping details and a return policy are recommended additions. Check the current property tables before you build, because they change.
Three rules from Google’s general structured data guidelines matter most here.
- Mark up only what is visible. Structured data must be a true representation of the page content. The price, availability and rating in the markup have to be the ones on screen.
- No fake or misleading content. That includes reviews. Google’s review snippet guidelines also say not to include fake or undisclosed incentivised reviews in the page or the markup.
- No guarantee. Google does not promise that valid markup will produce a rich result.
Keep the schema description as clean as the visible one. Markup is marketing text too.
Page speed
Google recommends achieving good Core Web Vitals. The thresholds published on web.dev are a Largest Contentful Paint within 2.5 seconds, an Interaction to Next Paint of 200 milliseconds or less and a Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads on mobile and desktop. On a product page the usual causes of a poor score are an oversized main image, review and chat widgets that load before the content, and price or stock blocks that appear late and push the layout down. That last one is also a Merchant Center risk, because displayed product information should not change after loading.
Mobile layout
Google says it uses the mobile version of a site’s content for indexing and ranking, and asks that mobile and desktop carry the same content and structured data. So the phone layout is the page of record.
- Stack in the wireframe’s order: image, title, identity, purity and lot, price, availability, RUO statement, button, shipping summary.
- Keep the COA link and lot number above the fold or one short scroll below it. Do not bury them in a collapsed tab that a buyer never opens.
- Let specification tables scroll sideways inside their own box, so the page itself never scrolls horizontally.
- Do not remove the specification table, storage section or policy links on small screens to save space.
9. Merchant Center approval, conversion and a pre-launch checklist
Merchant Center reviews a product by reading its landing page. Most of the avoidable problems are mismatches: a feed price that differs from the page, availability that is not stated, a link that lands on a category, a main image with a badge on it, or policies a visitor cannot find. Google’s checkout page says plainly that omission of relevant information is considered a misrepresentation, and its misrepresentation policy says some practices can lead to suspension without prior warning. If you are already there, see Merchant Center recovery, and if the Google Ads account is affected, our suspension appeal and recovery playbook.
On conversion, we do not publish benchmark figures for this category, because we have none we could source and stand behind. What we can say is what the page changes for a buyer: whether they can confirm identity and purity for the lot in stock, see the delivered cost before checkout, and find a real business behind the store. Those are the same things Google’s policies ask for. Measure the effect in your own analytics, one change at a time. The buyers the page does win are worth keeping in touch with on the same terms. See peptide email marketing.
- Title names the compound, quantity and form, includes the research-use statement, and describes the same product as the feed title.
- Description covers identity, purity, form and storage only. No effects, conditions, dosing or audiences.
- Lot number on the page matches the linked COA and the vial label.
- COA is lot-specific, dated, names the laboratory and the methods, and opens on a phone.
- Testing claims say who tested what. “Third-party” is used only where it is true.
- Main image shows the actual product at 500 x 500 pixels or more, with no overlay, watermark or border.
- Gallery contains no syringes, needles, body imagery or before-and-after pictures.
- Price and currency on first load match the feed and the structured data. Quantity breaks are in a table beneath.
- Availability is stated in text and matches the feed.
- Checkout is on HTTPS, adds no undisclosed fees, and the price does not increase.
- Shipping cost, dispatch time and returns are summarised under the button and linked in full, readable without logging in.
- RUO acknowledgement appears beside the button and as a checkout tick-box. It does not block the page from loading.
- Related products include no injection supplies, kits or “stacks”.
- Reviews follow a published moderation rule applied regardless of rating. None are written, bought or edited by the business.
- Product schema validates and matches what is visible, including price, availability and any rating.
- Mobile page shows the same content as desktop, in order, with no horizontal scroll.
- Core Web Vitals have been checked on the live template, and price and stock do not shift after load.
- Footer shows the legal business name, address and a working contact route.
10. FAQ
What should a peptide product page include?
A title naming the compound, quantity and form, a description limited to identity, purity, form and storage, the current lot number with its certificate of analysis, an image of the actual product, a clear price and availability, shipping and returns information, a research-use statement, and business contact details.
Does a research-use-only disclaimer make a product page compliant?
No. FDA warning letters to peptide sellers in 2024 and 2026 concluded that website evidence established intended human use despite research-use labelling. The statement has to be consistent with everything else on the page, including titles, descriptions, images and related products.
Will a well-built product page get my peptides approved in Google Merchant Center?
Not on its own. Google restricts unapproved pharmaceuticals and supplements in Shopping and says some content may not be listed anywhere. An accurate page that matches the feed removes avoidable disapprovals such as price or availability mismatches. It does not change whether a product is eligible.
Where should the certificate of analysis go on the page?
Put the stated purity, the current lot number and a link to that lot’s COA close to the buy button, then show the document and test methods in a panel below the description. Keep an archive of earlier lots so customers can find the document for a vial they already hold.
Can I put a purity badge or “lab tested” seal on the product image?
Not on the main image used in your product feed. Google’s image rules do not allow promotional elements, watermarks, graphic stamps or borders on it. State the purity and testing details in text next to the image.
How should an RUO store handle customer reviews?
Publish a written moderation rule and apply it to content, not to star rating. Reviews about service, packaging and documentation are fine. Reviews describing personal use, dosing or outcomes should not be displayed. Never write, buy or edit reviews. The FTC’s Consumer Reviews and Testimonials Rule has applied since 21 October 2024.
Should the page be hidden behind an age gate or RUO pop-up?
We advise against a gate that stops the title, price, availability or buy button from loading. Google expects those elements on the landing page and says displayed product information should not change after loading. Place the acknowledgement at add-to-cart or checkout, and show crawlers the same page visitors see.
What structured data does a peptide product page need?
Product markup with a name, an image and an Offer carrying the price and currency, following Google’s merchant listing documentation. Add availability and other recommended properties where you can. The markup must match what is visible on the page, and valid markup does not guarantee a rich result.
Have your product page template reviewed
Peptide Marketing works only with research-use-only peptide brands. We will go through one of your product pages against your feed, your structured data and the checklist above, and tell you what to change first. We do not help disguise products or work around platform policies.
Prefer email? Write to hello@peptidemarketing.info.
Sources
- Google Merchant Center Help: Landing page requirements, Title, Description, Image link, Product data specification, Mismatched product price, Checkout requirements and best practices, Return policies, Misrepresentation and Shopping ads and listings policies
- Google Ads policy: Healthcare and medicines
- Google Search Central and web.dev: Merchant listing structured data, General structured data guidelines, Review snippet, Core Web Vitals and Search, Mobile-first indexing and Web Vitals
- FDA: warning letters to TXP Innovations LLC dba Tex Peptides, 24 August 2026, Prime Sciences, 31 March 2026 and Summit Research Peptides, 10 December 2024, and 21 CFR 201.128
- FTC: Consumer Reviews and Testimonials Rule questions and answers and Mail, Internet, or Telephone Order Merchandise Rule business guide
This guide is general information for businesses selling research-use-only products. It is not legal or regulatory advice. Sources were read on 16 November 2026. Google’s policies and enforcement change. Check the linked pages and take professional advice before you act.
Leave a Reply