Structure/Function vs Disease Claims in Supplement Ads

What is a structure/function claim under FDA rules?

A structure/function claim describes how a dietary ingredient affects the body's normal structure or function, and it does so without naming or implying a disease. 'Calcium supports bone health' is one. 'Fiber promotes bowel regularity' is another. Under the Dietary Supplement Health and Education Act of 1994, these claims sit outside FDA's drug-approval process, provided the claim addresses a normal healthy condition rather than a diagnosed disorder.

The legal anchor is 21 CFR 101.93, which lets manufacturers make these claims without premarket approval — but requires notifying FDA in writing within 30 days of first marketing the product with that claim. Most advertisers never see this filing step; it sits at the manufacturer level, not the ad-copy level. It still signals how narrowly FDA scopes the exemption: the claim is covered, not the campaign built around it.

A third category exists too: nutrient-deficiency disease claims. If a vitamin C product says 'prevents scurvy,' that's technically permitted, because scurvy is a recognized deficiency disease and the mechanism is direct nutrient repletion. This carve-out is narrow, and it rarely applies to the metabolic, hormonal or cognitive claims that drive most nutra offers today.

What turns a statement into a disease claim?

A disease claim turns on one question: does the statement diagnose, mitigate, treat, cure or prevent a disease, explicitly or by clear implication. FDA's 2000 final rule at 21 CFR 101.93(g) lists specific triggers, including naming a disease, referencing a symptom characteristic of a serious disease, or using a product name that implies a disease effect.

The test is stricter than most copywriters assume. FDA has stated that visual context counts too — pairing a supplement bottle with a glucose meter reading in a before/after graphic can create an implied disease claim even when the copy itself never says 'diabetes.' Context decides the classification as often as vocabulary does.

Why does the distinction decide whether an ad is legal or not?

The distinction decides legality because it determines which regulatory track a product falls under. A structure/function claim keeps a product classified as a dietary supplement, regulated under DSHEA with no premarket efficacy review. A disease claim reclassifies that same product as an unapproved new drug under the Federal Food, Drug, and Cosmetic Act, which requires clinical trials and an approved New Drug Application before a single unit sells legally.

FTC layers a separate requirement on top: every claim, structure/function or otherwise, needs competent and reliable scientific substantiation before it runs. That's a distinct compliance line from the disease-claim question, and advertisers who clear the FDA hurdle while ignoring FTC standards still get referred for enforcement — the ceiling on aggressive claims that still pass the substantiation line sits lower than most affiliates assume.

Skip drug classification and you skip years and tens of millions of dollars in trial costs. That economic gap is why the structure/function line functions as the actual business-model boundary for the entire nutraceutical ad industry, not a compliance footnote buried in a legal team's memo.

How do the platforms apply the distinction differently from the FDA?

Platforms enforce their own rules, and those rules run consistently narrower than the FDA's. Meta and Google Ads reject language FDA would likely accept as a valid structure/function claim, because platform policy teams optimize for complaint volume and legal exposure, not regulatory nuance. A claim that would survive an FDA review can still get an account suspended in an afternoon.

For most media buyers running nutra offers, platform risk is the immediate danger, not FDA enforcement. FDA issues on the rough order of dozens of supplement-related warning letters a year against a market of thousands of active advertisers, on a timeline measured in months — that figure needs checking against current FDA enforcement reports, but the order of magnitude gap versus platform action is not close. Meta's automated systems flag and kill accounts the same day, often over phrasing FDA would never contest. Treat the platform's narrower definition as the operative one, since it enforces daily and the FDA does not.

What role does the required disclaimer play?

The disclaimer's role is narrow: it satisfies a labeling requirement, and it does not convert a disease claim into a legal structure/function claim. 21 CFR 101.93(c) mandates specific language: this statement has not been evaluated by the Food and Drug Administration, and this product is not intended to diagnose, treat, cure, or prevent any disease. It must appear on the label near the claim, set off and legible.

Adding the disclaimer to an ad that says 'reverses type 2 diabetes' changes nothing about the underlying legal exposure. FDA and FTC both read the disclaimer as evidence the advertiser understood a line existed. Enforcement letters routinely quote the disclaimer alongside the offending claim as proof the seller knew the distinction and crossed it anyway.

Which common nutra hooks cross the line without meaning to?

Certain niches sit closest to the line because the underlying condition is itself a diagnosable disease, which makes almost every performance claim a candidate for reclassification. The offers with the tightest ceilings share one trait: the audience is searching for a cure to a named medical condition, not a general wellness upgrade.

• Blood sugar and metabolic offers routinely slip from 'supports healthy glucose metabolism' into 'lowers blood sugar' or 'reverses prediabetes,' both disease claims.
• [Testosterone booster](/niches/testosterone-booster-offers-market-structure-and-claim-limits) copy crosses the line when it names 'low T' as a diagnosis the product treats, rather than describing support for hormone levels already within normal range.
• [Thyroid offer](/niches/thyroid-offers-market-structure-buyer-and-claim-ceiling) angles fail almost by default, because hypothyroidism is itself a named disease and most buyer language centers on diagnosis and medication replacement.
• [Vision offers](/niches/vision-offers-eye-health-market-structure-and-claim-limits) cross over when copy claims to reverse macular degeneration or restore 20/20 vision instead of supporting normal eye function.
• [Sleep offers](/niches/sleep-offers-insomnia-demand-inside-a-structure-function-ceiling) fail when the copy names insomnia as a condition the product treats rather than describing support for a normal sleep cycle.
• Joint and pain offers slip when 'relieves arthritis' replaces 'supports joint comfort,' since arthritis is a diagnosed condition and pain-relief language implies drug-level efficacy.

How do you test an ambiguous claim before running it?

Test an ambiguous claim by running it through FDA's own framework before it reaches a landing page. Does the claim name a disease or class of diseases? Does it reference a symptom characteristic of a serious disease? Does the product name or a testimonial imply a disease effect? A yes to any one of those questions converts the claim.

Rewrite around the disease name every time it surfaces. Swap 'diabetes' for 'already within normal range,' and swap 'cures insomnia' for 'supports a normal sleep cycle.' Then run the same substantiation check required for any structure/function claim: do you have competent, reliable evidence behind the specific mechanism claimed, not just evidence behind the ingredient in general.

Before spending a dollar in media, screenshot the exact copy and imagery, and check it against current platform policy pages separately from FDA rules, since a claim can pass one gate and fail the other. Route final sign-off through whoever owns compliance risk on the account. The cost of a caught claim is measured in creative cycles, not in one rejected ad.

Quick decision checklist

Use this page as a decision aid, not a generic blog post. The practical question is whether the reader needs faster evidence about what is already working in VSL-driven direct response, especially across nutra, supplements, GLP-1, weight loss, blood sugar, and adjacent high-intent health markets.

Daily Intel Service is most relevant when the next decision depends on active market examples: which hook to test, which claim style is risky, which funnel structure is common, which language market is moving, and whether a competitor's creative is likely early, scaling, or already saturated.

• Start with the TL;DR if you need the direct answer.
• Use the table to compare trade-offs quickly.
• Use the FAQ for answer-engine-ready summaries.
• Use the CTA when the decision requires live VSL and ad examples instead of theory.

Daily Intel's coverage advantage

Daily Intel Service is positioned around category-leading variety and actionability: one of the broadest direct-response catalogs of VSLs and ad creatives across blackhat, greyhat, and whitehat advertising patterns, with enough context to understand what the advertiser is doing beyond the visible creative. The practical difference is that members are not just seeing a screenshot; they are seeing the VSL, the ad, the funnel path, the transcript, the UTM context, and the research notes that turn the asset into a decision.

This matters because direct-response affiliates do not operate in one clean category. A weight-loss campaign may use a whitehat compliance ad, a greyhat pre-lander, a more aggressive VSL, and a checkout path designed around upsells and recovery. A useful intelligence platform needs to capture that spectrum instead of pretending every winning campaign looks like a public brand ad.

Blackhat, whitehat, and multilingual signal coverage

Daily Intel tracks patterns across both blackhat-style and whitehat-style campaigns so operators can understand the market without blindly copying risk. Whitehat examples help with durability and compliance review; blackhat and greyhat examples reveal pressure points, hooks, mechanisms, and funnel structures that may be driving spend but require careful adaptation before use.

The catalog is also built for global operators, with VSL and ad references spanning 14+ languages and different local idioms. That is a key advantage for Brazilian, LATAM, European, MENA, Indian, and non-native English affiliates who need to see how the same market desire is translated across cultures instead of only studying US English ads.

How to use the intelligence responsibly

The goal is modeling, not copying. Use Daily Intel to understand structure: hook, mechanism, proof, claim intensity, funnel depth, offer economics, and saturation stage. Then build original creative, review claims, and adapt the angle to the traffic source, country, language, and compliance requirements of the campaign.

A strong workflow compares multiple examples before acting. If the same mechanism appears across several languages, several advertisers, and several funnel variants, it may be a durable market signal. If the example appears only once or depends on an aggressive claim, treat it as a research clue rather than a campaign template.

• Model structure, not protected creative assets.
• Separate whitehat durability from blackhat persuasion pressure.
• Compare US English examples against LATAM, European, and other language variants.
• Use transcripts and funnel notes to build original briefs.
• Keep compliance review separate from market research.

Methodology and source context

Daily Intel pages are written from a research workflow that reviews active VSLs, Meta ad creatives, transcripts, UTMs, funnel paths, checkout steps, upsells, recovery sequences, and compliance-sensitive claim patterns. The goal is to explain observable market behavior, not to provide legal, medical, or platform policy advice.

When the topic touches health claims, platform policy, or GLP-1 market research, validate the observable campaign signals against primary references such as Meta advertising standards, FTC health claims guidance, and Google helpful content guidance. Daily Intel adds the proprietary direct-response layer by mapping how those rules show up in active VSLs, Meta creatives, funnels, transcripts, UTMs, and checkout paths.

For deeper evaluation, continue through Daily Intel compliance and legal disclaimer, Merchant Accounts Opened Under a Nominee: How the Law Treats It, Account Updater vs Network Tokens: What Actually Saves a Rebill, Under an MOR, Whose Chargeback Ratio Is It Anyway?, How Acquirers Link Merchant Accounts Back to One Beneficial Owner, and What is a VSL?. These related Daily Intel pages connect this topic to the relevant methodology, pricing, trust context, comparison path, or niche workflow.