United Kingdom · CAP Code · landing pages
Repairability score claims on UK landing pages — CAP literacy
Electronics and appliance landing pages show repair index numbers, spare-part promises and modular design heroes beside sustainability tiles. Shoppers often read scores as guaranteed longevity without opening methodology footnotes. This guide helps UK marketers inventory repairability strings on live URLs. Not ASA clearance and not legal advice.
Free scan · £29 Register · £79/mo Watch
Repairability score heroes on electronics pages
Phones, laptops and small appliances landing pages increasingly show repairability scores, spare-part availability icons and right-to-repair headlines beside sustainability photography. Shoppers often treat the index number as a durability promise without opening methodology footnotes.
Under CAP Code 3.7, objective score claims need substantiation — marketers inventory exact rating strings before product launches.
Cross-read recycled content percentage claims, recyclable packaging claims, and eco certification badge claims.
Common repairability score patterns
| String | Shopper read | Register note |
|---|---|---|
| Repairability score 8.2/10 | Independent index | Capture methodology version |
| Designed for easy repair | Modular parts implied | Separate from numeric score row |
| Spare parts available 7 years | Parts longevity | Match sold SKU and region |
| Tool-free battery replacement | Feature claim | Evidence for specific model |
| Top repair rating in category | Comparative superlative | Log baseline and date |
Qualifiers and index updates
Repair indices update scoring rules between product generations. CAP literacy expects material qualifications when old and new methodology badges appear on the same site.
Bundle pages may show a headline score without stating which variant was tested — log configuration tables separately.
See bundle pricing claims and superlatives and best claims.
Worked example
Hero: “Repairability score 7.8 — spare parts stocked for ten years.” Spec tab names index version 2024 on model XR-200. Literacy notes:
- Score: 7.8 objective — evidence folder should match sold SKU.
- Parts promise: Ten years — archive supplier letter in register.
- Index version: Named on-page — log report filename.
- Marketplace title: Omits score — reconcile feed copy.
Common misreadings
- Generic wrench icon assumed to prove high score. Log explicit number or index name.
- Warranty length merged with repair score row. Warranty and index are separate claims.
- Refurb SKU excluded from hero scope. Variant tables should list outlet models.
- Installer repair copy treated as product score. Whole-system claims need separate evidence.
Desk checklist
| Check | Pass hint |
|---|---|
| Hero matches spec table score | Same figure and index |
| Methodology footnote current | No legacy index without context |
| Comparative ranks scoped | Category and date named |
| Marketplace feed logged | Separate register row |
| Agency handoff register | Agency handoff guide |
Right-to-repair crossover
Vegan and plant-based claims on accessory pages do not substantiate repair scores — inventory each claim class separately on sustainability URLs.
Net-zero headlines beside repair badges stack green themes — split register rows per CAP section.
See vegan plant-based claims and net-zero headline claims.
Promotional modules
Launch campaigns may shorten repairability score to easy fix for headline space — log promotional strings separately from evergreen PDP copy.
Limited stock modules must not imply permanent high scores when only promotional SKUs were tested.
See limited stock availability claims and was/now pricing claims.
Register hygiene reminder
Date-stamp each CiteBefore scan when suppliers change modular designs — score mismatches are a frequent complaint theme after silent hardware revisions.
Keep index PDF filenames in the evidence column even when methodology text is truncated on mobile layouts.
See claim substantiation and claim register template.
B2B catalogue overlap
Trade catalogues sometimes show indicative repair scores without naming the tested configuration — log B2B and consumer URLs separately when the same model appears on both.
Subscription bundles attaching care plans may imply repair outcomes — inventory each device score independently before publishing package narratives.
See puffery vs objective claims when save-the-planet language sits beside numeric repair heroes.
Outlet and refurbished SKU rescans
Outlet subdomains may retain full-strength repair heroes on end-of-line models with different internal layouts — schedule rescans after SKU merges.
Refurbished listings sometimes drop spare-part footnotes present on new-model pages — capture refurb URLs as their own register rows.
See clearance sale claims and refill pouch claims when promotional modules sit beside repair badges on the same URL.
Repair score comparisons in email
Email campaigns may restate landing-page repair scores with different rounding — capture email HTML exports alongside PDP scans in the same register batch.
Loyalty app tiles sometimes show legacy scores after a product refresh — schedule rescans when app release notes mention hardware changes.
See star rating review count claims and trust badge award claims when social proof modules neighbour repair heroes.
Questions
Are repairability scores objective claims on a landing page?
Numeric scores and index ratings are usually measurable — CAP literacy expects substantiation for stated repair scores and methodology footnotes.
Must repairability heroes match the physical product label?
Shoppers expect consistency between hero badges, spec tables and in-box scoring labels. Log each surface separately in the register.
Does CiteBefore verify independent repair index tests?
No. CiteBefore inventories visible copy on submitted URLs. Test reports remain your compliance folder.
Can green icons substitute for named repair scores?
Leaf badges without numbers may still imply easy repair — inventory explicit score strings when icons sit beside sustainability copy.
Do marketplace feeds inherit outdated repair scores?
Feeds often lag relabelled SKUs. Log retailer strings separately from on-site hero copy.
All guides: /guides/.