United Kingdom · CAP Code · landing pages
U-value thermal insulation claims on UK landing pages — CAP literacy
Insulation and HVAC accessory pages use W/m²K figures, lambda values and Part L compliance heroes beside installation photography. Specifiers often read thermal numbers as guaranteed as-built outcomes without opening thickness tables. This guide helps UK marketers inventory U-value strings on live URLs. Not ASA clearance and not legal advice.
Free scan · £29 Register · £79/mo Watch
U-value and thermal performance heroes on building product pages
Insulation board, cavity closer and duct-lagging landing pages stack W/m²K figures, lambda values and building-regulation compliance badges beside installation photography. Specifiers often treat the headline U-value as a guaranteed as-built outcome without opening thickness tables.
Under CAP Code 3.7, objective thermal performance claims need substantiation — marketers inventory exact numeric strings before seasonal trade campaigns.
Cross-read energy efficiency rating claims, recycled content percentage claims, and eco certification badge claims.
Common U-value wording patterns
| String | Specifier read | Register note |
|---|---|---|
| U-value 0.18 W/m²K | Wall build-up target | Confirm tested thickness on-page |
| Thermal conductivity λ 0.022 | Material property | Separate from system U-value row |
| Part L compliant solution | Regulatory fit | Log approved build-up reference if stated |
| Up to 30% heat loss reduction | Comparative saving | Baseline build-up named if claimed |
| HVAC duct wrap reduces losses | Plant-room scope | Split HVAC from envelope claims |
Thickness variants and system boundaries
Multi-thickness configurators may show a U-value for 100 mm while the hero cites 150 mm stock — log variant tables separately.
Composite system claims must scope which layers were tested — adhesives, fixings and air gaps change outcomes.
Thickness tables beside multi-buy kits need per-SKU U-values — read bundle pricing claims and comparative vs competitor claims when savings charts stack.
Worked example
Hero: “External wall board — U-value 0.19 W/m²K at 120 mm in standard masonry build-up.” Download tab cites BS EN 12667 on product IW-120. Literacy notes:
- System U-value: Objective — evidence should match named build-up.
- Thickness: 120 mm — confirm sold SKU thickness matches.
- Test standard: EN 12667 or ISO 8301 cited on-page — store the lab report name in the register row.
- Merchant snippet: Shows generic 0.18 — reconcile feed copy.
Common misreadings
- Lambda value assumed to equal installed U-value. System calculation differs from material property.
- Green leaf icon treated as Part L proof. Log explicit compliance language.
- Installer case study merged with product U-value row. Project-specific outcomes need separate substantiation.
- End-of-line boards on outlet URLs. Capture clearance thicknesses separately from the main range hero.
Desk checklist
| Check | Pass hint |
|---|---|
| Hero matches datasheet U-value | Same thickness and build-up |
| HVAC vs envelope claims split | Separate register owners |
| Comparative savings scoped | Baseline named if claimed |
| B2B feed logged | Separate row from consumer URL |
| Agency handoff register | Agency handoff guide |
Recycled content and packaging crossover
Recycled content heroes on insulation facings sit beside thermal numeric claims — inventory each claim class separately on sustainability URLs.
Recyclable packaging claims concern end-of-life — not in-service U-value — split rows when both appear.
See recyclable packaging claims and carbon neutral offset claims.
Promotional and trade catalogue modules
Trade counter QR landing pages may shorten Part L compliant to green solution for headline space — log promotional strings separately from evergreen PDP copy.
Was/now pricing modules must not imply permanent thermal upgrades when only promotional stock applies.
Seasonal price cuts must not imply a better U-value — see was/now pricing claims and limited time offer claims on trade landing pages.
Register hygiene reminder
Date-stamp each CiteBefore scan when suppliers reformulate boards after fire-performance retests — U-value mismatches are a frequent complaint theme after range refreshes.
Keep hot-box or guarded-hot-plate report PDF filenames in the evidence column even when methodology text is collapsed in accordions.
Archive lambda certificates in the same register row as the hero figure — see claim substantiation and claim register template.
BIM objects and merchant data
BIM object portals sometimes show indicative U-values without naming the tested build-up — log object URLs separately from marketing heroes.
Comparison sites paraphrase lambda figures — capture third-party strings beside on-site copy.
See puffery vs objective claims and made in UK origin claims when local manufacture tiles sit beside thermal numbers.
Compostable packaging claims on delivery materials do not substantiate in-wall thermal performance — keep logistics copy out of the U-value evidence folder.
Net-zero headline claims on corporate pages must not imply every SKU meets the hero U-value unless substantiation covers the range.
See compostable packaging claims and net-zero headline claims.
Questions
Are published U-value figures objective claims on a building materials landing page?
Declared W/m²K values for insulation boards and HVAC duct lagging are measurable. CAP literacy expects substantiation for stated thermal performance — inventory exact numbers and test standards.
Must hero U-values match the datasheet for the sold thickness?
Trade buyers expect consistency between headline lambda/U figures, thickness tables and CE marking copy. Log each variant row separately in the register.
Does CiteBefore run hot-box laboratory tests?
No. CiteBefore inventories visible advertising copy on submitted URLs. Test certificates remain your technical compliance folder.
Can R-value headlines substitute for U-value claims?
Markets use different metrics — converting without qualification may mislead. Cross-read comparative claims when both appear.
Do merchant feeds inherit outdated U-values after product reformulation?
B2B feeds often lag relabelled SKUs. Log merchant and on-site hero strings separately.
All guides: /guides/.