Consumer health brands have some of the best product content on the web — ingredients, dosage, warnings, condition guides, hundreds of FAQ answers. And very often none of it is machine-readable. When I audit OTC and supplement sites, the most common finding is the simplest one: zero structured data, with everything locked in HTML, tabs and JavaScript widgets.
For AI assistants that matters more than for classic search. When someone asks “what can I take for heartburn during pregnancy?” or “which vitamin tablets have the most B12?”, the model looks for sources it can read with confidence. Here's how I map schema.org types for OTC, supplement and medical-device brands — and the mistakes that are easy to make.
Why structured data matters more in health
- Higher bar for trust. Health is a YMYL area. Search engines and AI models are more cautious and prefer sources that are explicit, consistent and clearly authored.
- Retailers often say it better than you. If a pharmacy chain or marketplace lists your ingredients and pack sizes in structured form and your own site doesn't, the retailer becomes the source AI quotes — including its mistakes.
- Complex portfolios confuse models. One umbrella brand can cover OTC medicines, supplements, medical devices and self-tests. Without explicit markup, AI can't tell which product is which.
Which schema type for which product
Schema.org type map · consumer health
| Page or product | Type | Key properties |
|---|---|---|
| OTC medicine | Drug | activeIngredient, dosageForm, administrationRoute, doseSchedule, warning, legalStatus |
| Food supplement, vitamins | DietarySupplement | activeIngredient, recommendedIntake, safetyConsideration, targetPopulation |
| Medical device (gels, tests) | MedicalDevice | purpose, contraindication, adverseOutcome |
| Condition guide | MedicalWebPage + MedicalCondition | about, signOrSymptom, possibleTreatment, lastReviewed, reviewedBy |
| Product Q&A | FAQPage | Question / Answer — identical to the visible text |
| Range page | ItemList, ProductGroup | itemListElement, hasVariant, variesBy |
| Brand and sub-brands | Organization, Brand | parentOrganization, sameAs, logo |
On top of the health-specific type, every product still needs commerce data: gtin13 per pack size, brand, and offers where you sell or link to retailers.
Drug or medical device is a regulatory decision
Choosing between Drug, DietarySupplement and MedicalDevice isn't a stylistic SEO choice. It must follow the product's legal classification — the one printed on the pack and in the legal text of the page.
In one audit a single brand family included an antifungal medicine, a menopause supplement, a lubricating gel registered as a medical device and a self-test kit — all under the same name. Marking the gel as a Drug would contradict its own label. The rule I use: the regulatory status decides the type, the marketing team doesn't.
A minimal example
JSON-LD · generic antacid tablet (simplified)
{
"@context": "https://schema.org",
"@type": "Drug",
"name": "Example Antacid Chewable Tablets",
"brand": { "@type": "Brand", "name": "Example" },
"activeIngredient": "Calcium carbonate, magnesium carbonate",
"dosageForm": "Chewable tablet",
"administrationRoute": "Oral",
"isAvailableGenerically": false,
"legalStatus": "Over-the-counter",
"warning": "Do not exceed the stated dose. Read the leaflet.",
"gtin13": "0000000000000"
}Every value must be copied from the approved label or leaflet — never rewritten for SEO.
Mistakes I see most often
OTC & supplement schema · do and don't
Do
- Build it once at template level for all brands on the platform
- Mark up FAQ answers that already exist on the page
- Declare sub-brands as
Brandlinked to the parent company - Add GTIN per pack size
- Check your data against retailer listings
Don't
- Use
Drugfor devices or supplements - Put claims in schema that aren't on the approved label
- Leave “where to buy” only in a JavaScript widget
- Mark up reviews or ratings you don't show
- Let schema and visible text drift apart
Check the retailers too
Structured data on your site is only half of the picture. AI assistants also read pharmacy chains, supermarkets and marketplaces. In audits I regularly find retailer listings with outdated ingredients, wrong dietary claims or a different pack size. Your own site, properly marked up, should be the canonical source — and discrepancies should be fixed at the retailer, not just noted.
Structured data for health brands is part of my technical SEO and GEO / AI visibility work. More on the sector: SEO for pharma and consumer health.
Based on structured-data audits I have run for consumer health brands (OTC medicines, supplements and medical devices); product names in examples are generic. Types and properties follow schema.org.
FAQ
Frequently asked questions
Drug, from schema.org's health and life sciences vocabulary, with properties such as activeIngredient, dosageForm, administrationRoute, warning and legalStatus — plus product data like brand and gtin13.
No. Food supplements should use DietarySupplement. Using Drug for a supplement contradicts its legal status and can mislead both search engines and AI assistants.
Follow the product's legal classification as stated on the pack and in the page's legal text. It is a regulatory decision, not an SEO one.
Yes, as long as it matches questions and answers visible on the page. Rich results for FAQ are limited, but the markup still makes the answers easier for machines to read.
No. Every value should come from the approved label, leaflet or packaging text. Structured data describes the product; it doesn't add new claims.
It helps AI systems read product facts with confidence and makes your site a stronger canonical source than retailer listings. It works best together with clear visible text.
