United Kingdom · CAP Code · landing pages

Hypoallergenic claims on UK landing pages — CAP literacy

“Hypoallergenic”, “allergy-friendly formula”, and family-range allergy badges appear above the fold on skincare and baby-care landing pages. Shoppers often treat those lines as proof the entire range is safe for every allergy profile — not a bounded panel study on one formula. This guide helps UK marketers inventory hypoallergenic claims against published CAP substantiation literacy. Not ASA clearance and not legal advice.

Not ASA clearance. Not legal advice. CiteBefore inventories advertising claims and evidence columns. The ASA decides complaints.

Free scan  ·  £29 Register  ·  £79/mo Watch

Why hypoallergenic needs its own register row

Hypoallergenic is not interchangeable with dermatologically tested, suitable for sensitive skin, or fragrance-free. Each phrase triggers different shopper expectations about formulas, populations studied, and allergy risk.

Inventory exact wording on hero modules, comparison tables, and retailer feed titles before scaling paid social.

Cross-read allergen-free claims, dermatologically tested claims, and dermatologist recommended claims.

Common landing-page patterns

Visible wordingTypical shopper readEvidence column habit
Hypoallergenic formulaSafe for all allergy sufferersProtocol, population, SKU scope
Hypoallergenic fragranceNo reaction riskSeparate row from base formula
Developed for allergy-prone skinClinical outcome impliedDo not merge with tested-only lines
Hypoallergenic* (*see INCI)Asterisk scope unclear on mobileLog footnote prominence
Family hypoallergenic rangeEvery product in carouselWeakest SKU sets collection claim

CAP 3.7 literacy — objective cosmetic claims

Objective efficacy and suitability claims generally need substantiation your team holds offline. CiteBefore inventories what shoppers see on the live page at scan time.

Qualifications buried only in T&Cs may not match material information expectations — compare hero vs footer prominence.

See advertising claim substantiation, results may vary disclaimers, and health claims on PDPs.

INCI, fragrance and free-from stacks

Retailers pull short claims into marketplace titles while PDPs carry longer INCI lists. When essential oils or botanical extracts appear in INCI, hypoallergenic headlines need consistency checks against allergen-free tiles.

Log feed strings separately from Shopify hero copy.

Read puffery vs objective claims and organic ingredients claims when natural positioning sits beside allergy language.

Collections and bundle modules

Gift sets may mix hypoallergenic hero copy with non-claimed minis. Treat each component tile as its own register row.

Before/after imagery beside allergy headlines still counts as ad copy — capture adjacent captions.

See bundle pricing claims and before-and-after URL capture.

Worked example

Hero: “Hypoallergenic body wash for the whole family.” Accordion: “Patch tested on 40 volunteers without known allergies; formula contains limonene.” Register capture:

Common misreadings

Pre-publish checklist

CaptureWhy it matters
Exact hypoallergenic string per URLFeeds may differ from hero
Population / protocol qualifiersShoppers infer universal safety
Free-from lines on same carouselCross-read allergen-free guide
Endorsement badges on same pageSeparate substantiation tracks
Post-deploy scanFree scan on live URL

Agency and retailer feeds

Marketplace titles often truncate qualifications. Inventory feed-specific strings separately from owned-site hero copy.

Hand off using the claim register template so media buyers know which allergy lines are cleared for paid search.

See claim register template and agency substantiation handoff.

What CiteBefore does not do

We do not design patch tests, review CRO certificates, or provide ASA Copy Advice. We inventory visible advertising strings on URLs you submit.

Seasonal campaigns and limited editions

Limited-edition scents and gift-wrapped minis often reuse core hypoallergenic claims from the parent range. When the INCI differs — even slightly — the limited SKU needs its own register row before Black Friday traffic lands.

Influencer seeding kits sometimes print allergy claims on outer cartons that never appear on the main PDP. Capture packaging photography in your scan notes.

Subscription renewal emails that repeat hypoallergenic language count as advertising when they link back to the product page — log email hero strings if they mirror site copy.

See limited time offer claims, free gift with purchase claims, and subscription auto-renewal claims.

Archive scan PDFs when you reformulate so historic hypoallergenic strings are traceable if a complaint references an older cache date.

Questions

Must hypoallergenic apply to every SKU on the landing page?

Shoppers often read a collection hero as covering all variants. Log whether the claim applies to one formula, a panel-tested batch, or the full range.

Is hypoallergenic the same as allergen-free on a PDP?

No. Allergen-free lines describe named substances absent; hypoallergenic describes reduced reaction risk. Inventory separate register rows.

Does CiteBefore review patch-test protocols?

No. CiteBefore inventories visible claim strings and evidence columns on URLs you submit. It does not audit lab files.

Can a footnote limit hypoallergenic to patch-tested volunteers?

Footnotes can qualify claims when material information is clear and prominent. Capture location relative to the hero module.

Should marketplace titles inherit hypoallergenic hero copy?

Feed titles are part of the ad — log Amazon, TikTok Shop and owned-site strings separately on the same SKU.

Try free scanPricing

All guides: /guides/.