United Kingdom · CAP Code · landing pages
pH-balanced claims on UK landing pages — CAP literacy
“pH-balanced”, numeric pH ranges, and skin-kind badges appear on intimate wash and cleanser landing pages. Shoppers often treat those lines as lab-backed proof of safety — not marketing shorthand for mild surfactants. This guide helps UK marketers inventory pH-balanced claims against published CAP substantiation literacy. Not ASA clearance and not legal advice.
Free scan · £29 Register · £79/mo Watch
Why pH-balanced needs its own register row
pH-balanced headlines sit beside sensitive-skin, gynaecologist-tested and microbiome badges on intimate wash and facial cleanser landing pages. Shoppers read pH-balanced as both a measurable acidity claim and a safety promise about irritation.
Log the verbatim pH-balanced string from each live URL — hero, comparison module, retailer feed title, and app deep link — before you approve paid media.
Cross-read dermatologically tested claims, hypoallergenic claims, and sulfate-free claims.
Common landing-page patterns
| Visible wording | Typical shopper read | Evidence column habit |
|---|---|---|
| pH-balanced formula | Skin-friendly acidity on every use | Log tested pH range and product type |
| pH 5.5 balanced | Specific numeric claim | Batch scope and measurement method |
| Balanced for sensitive skin | Suitability plus pH implied | Split suitability from pH evidence |
| pH-balanced intimate care | Category-specific scope | Do not generalise to face wash SKUs |
| Family pH-balanced range | Every product in carousel | Weakest SKU sets collection claim |
CAP 3.7 literacy — measurable claims
Where pH-balanced implies a tested property, substantiation files should match the numeric or qualitative wording shoppers see. CiteBefore inventories visible strings; your team holds lab notebooks offline.
Comparative charts that show competitor pH bars need the same register discipline as hero headlines.
See advertising claim substantiation, clinically proven green claims checklist, and results may vary disclaimers.
Rinse-off vs leave-on context
Shampoo heroes may claim pH-balanced while body wash PDPs on the same brand omit testing footnotes. Give each product type its own register row.
Intimate wash copy must not imply medical treatment — keep wording literacy separate from health claims on PDPs.
Read health claims on PDPs and fragrance-free claims when allergy language stacks beside pH rows.
Collections and bundle modules
Subscription bundles may show pH-balanced on the kit hero while individual sachets lack the claim. Capture each SKU URL separately.
TikTok Shop overlays sometimes shorten pH-balanced to balanced only — log shortened strings as distinct register rows.
Bundle modules: refill pouch claims. Influencer modules: influencer endorsement claims.
Worked example
Hero: “pH-balanced intimate wash for daily use.” Footnote: “Maintains pH between 4.5 and 5.5 in stability testing on current formula.” Register capture:
- Hero: pH-balanced plus daily use — split measurable claim from frequency puffery.
- Footnote: Numeric range — evidence column should cite test method.
- Category: Intimate wash — do not reuse row for facial foam without new capture.
Common misreadings
- pH-balanced merged with natural/organic badges. Origin claims ≠ pH testing.
- Dermatologist quote treated as pH substantiation. Endorsement ≠ lab data.
- One batch COA pasted as proof for entire range. Tie evidence to SKU and batch code.
- Review stars treated as pH evidence. Inventory review claims separately.
Pre-publish checklist
| Capture | Why it matters |
|---|---|
| Exact pH-balanced string per URL | Feeds may differ from hero |
| Numeric pH if stated | Shoppers treat numbers as guarantees |
| Product type (rinse-off / leave-on) | Scope limits collection claims |
| Health or suitability lines on same page | Separate substantiation tracks |
| Post-deploy scan | Free scan on live URL |
Agency and retailer feeds
Paid social often tests pH-balanced against skin-kind language while the PDP footnote stays below the fold on mobile — capture mobile and desktop screenshots separately.
Boots and Superdrug feeds may truncate pH-balanced — log feed title strings independently from owned-site heroes.
Handoff: claim register template, trust badge claims.
What CiteBefore does not do
CiteBefore is not a formulation lab and not ASA Copy Advice. It records claim strings and where they appear on URLs you submit at scan time.
Promo and subscription copy
Welcome emails repeating pH-balanced subject lines are advertising when they deep-link to product pages — log subject and preheader alongside on-site heroes.
Auto-replenish flows must not imply pH stays balanced across reformulations without a fresh scan.
See subscription auto-renewal claims and free trial vs money-back offers.
Retail pharmacy and clinic listings
Pharmacy aggregator pages sometimes show pH-balanced snippets pulled from brand hubs while clinic-only SKUs omit footnotes — capture each listing URL on the register.
Clinic treatment menus that borrow retail pH-balanced icons need separate capture rows because professional services copy is still advertising when it sells product.
See dermatologist recommended claims and made in UK origin claims.
Questions
Must pH-balanced apply to every SKU on the landing page?
Shoppers read pH-balanced heroes as covering entire ranges. Log whether testing applies to one formula, rinse-off only, or all variants.
Is pH-balanced the same as dermatologically tested?
No. pH-balanced describes acidity/alkalinity positioning; dermatologically tested describes human patch protocols. Inventory separate register rows.
Does CiteBefore verify lab pH readings against heroes?
No. CiteBefore captures visible claim text on URLs you submit. Lab certificates remain your formulation team's task.
Can a footnote limit pH-balanced to intimate wash only?
Footnotes can qualify claims when material information is clear and prominent. Capture location relative to the hero module.
Should marketplace titles inherit pH-balanced PDP copy?
Feed titles are part of the ad — log retailer and owned-site strings separately on the same SKU.
All guides: /guides/.