United Kingdom · CAP Code · landing pages
Cruelty-free and not tested on animals claims on UK landing pages — CAP literacy
“Cruelty-free”, “never tested on animals”, and certification bunny marks appear in hero modules, PDP bullets and ethics rows. Shoppers often read those lines as applying to every ingredient and every market you sell into — including legacy formulations and gift-set components. This guide helps UK marketers inventory cruelty-free claims against published CAP/ASA substantiation literacy. Not ASA clearance and not legal advice.
Free scan · £29 Register · £79/mo Watch
Why cruelty-free claims need their own register row
Cruelty-free and not tested on animals are not the same claim as vegan, organic, or dermatologically tested. A brand can be vegan yet still need precise wording about testing history, third-country sales, or parent-company policies.
Inventory the exact string on each URL variant before paid traffic scales — hero, PDP accordion, footer sustainability row, and influencer UGC tiles may differ.
Cross-read vegan and plant-based claims, organic ingredients claims, and health claims on PDPs.
Common landing-page patterns
| Visible wording | Typical shopper read | Evidence column habit |
|---|---|---|
| 100% cruelty-free | Never tested at any stage | Scope: finished product vs ingredients |
| Not tested on animals | No animal testing ever | Date range; third-party sales channels |
| Leaping Bunny / certification mark | Independently verified | Mark scope; expiry on register |
| We do not test on animals* | Absolute promise | Read asterisk — supplier/raw material lines |
| Cruelty-free since [year] | Historical cut-off | Log year in visible string column |
CAP 3.7 literacy — scope and material information
Published CAP materials treat many environmental and ethical claims as objective unless clearly qualified. If the hero says cruelty-free but the FAQ mentions markets where testing is legally required, inventory both strings and their prominence.
See advertising claim substantiation and puffery vs objective claims for qualification habit — not ASA clearance.
Read advertising claim substantiation and puffery vs objective claims.
Collections and variant SKUs
Shopify Clean Beauty collections imply every variant meets the same cruelty-free standard — one legacy SKU without updated supplier letters breaks the collection promise.
Same discipline as bundle pricing claims and limited stock counters: log PDP-level strings, not only collection blurbs.
See bundle pricing claims and limited stock claims.
Badges and certification rows
Third-party marks beside not tested on animals tiles are part of the ad — log mark name, scope, and adjacent copy.
When a certification badge appears, cross-read eco certification badge claims — separate register row from the headline cruelty-free string.
See eco certification badge claims and dermatologist recommended claims when professional endorsement lines sit on the same page.
Agency handoff
Client-supplied ethics one-pagers often merge cruelty-free with recyclable packaging language — split rows in the claim register template before go-live.
Run a free scan on the live URL after deploy; marketing decks may not match rendered HTML.
Use the claim register template and agency handoff guide.
Worked example — hero vs FAQ mismatch
A cosmetics landing page shows: “Cruelty-free — not tested on animals.” The PDP accordion says: “Where required by law, selected products may be registered through local testing pathways.” Register rows might record:
- Hero string: Absolute cruelty-free — shopper may read zero exceptions.
- Qualification location: Accordion only — check material information habit.
- Separate row: Any vegan icon — see vegan claims guide.
- Evidence column: Supplier attestation dates — held offline, not scanned by CiteBefore unless you upload internally.
Common misreadings
- Parent company policy pasted as SKU-level claim. Log entity scope in the register.
- Not tested on animals read as vegan. Separate rows for composition vs testing.
- Pre-2009 testing history omitted from internal files but implied by copy. Capture dates in evidence column.
- Influencer #ad tiles not inventoried. See influencer endorsement claims when creators restate cruelty-free lines.
Pre-publish inventory checklist
| Capture | Why it matters |
|---|---|
| Exact cruelty-free string per URL variant | Locale and UTM pages may differ |
| Certification mark name and scope | Marks are objective claims |
| FAQ exceptions and asterisks | Contradiction risk with hero |
| Collection vs PDP scope | Weakest SKU sets collection claim |
| Icon + adjacent tile text | Icons are part of the ad |
Why ethical claims attract scrutiny
Shoppers and NGOs treat cruelty-free headlines as factual ethics statements. When challenged, your team needs URL-dated strings and supplier scope already in the register — not a post-hoc search through email.
Reformulations and new markets can outpace legacy hero copy. Scan live URLs after any supplier change.
What CiteBefore does not do
We do not audit laboratories, verify certification body databases, or replace ASA Copy Advice. We inventory visible strings and flag evidence gaps on a live URL.
Questions
Must cruelty-free claims apply to every ingredient in the formula?
Shoppers often read a headline as covering the entire SKU including suppliers' sub-components. Inventory whether the claim applies to finished product, brand line, or parent company policy only.
Is not tested on animals the same as vegan on a landing page?
No. Vegan addresses animal-derived ingredients; cruelty-free addresses testing practices. Log separate register rows — see the vegan claims guide.
Does CiteBefore verify supplier audit letters for cruelty-free claims?
No. CiteBefore inventories visible claim text and evidence columns. It does not audit supply chains.
Can a rabbit icon beside not tested on animals stand alone?
Icons are part of the ad — log with adjacent copy and check whether certification is named.
Should collection page blurbs inherit SKU-level cruelty-free claims?
Only if every linked SKU meets the same substantiated standard. Log collection copy separately from PDP strings.
All guides: /guides/.