United Kingdom · CAP Code · landing pages
Wireless range and signal strength claims on UK landing pages — CAP literacy
Mesh Wi‑Fi, IoT gateways and outdoor radio pages use coverage maps, metre range and throughput heroes beside antenna specs. Buyers often read range badges as guaranteed in their home without obstacle footnotes. This guide helps UK marketers inventory wireless range strings on live URLs. Not ASA clearance and not legal advice.
Free scan · £29 Register · £79/mo Watch
Wireless range and signal strength heroes on tech pages
Mesh Wi‑Fi, smart security and industrial gateway pages stack whole-home coverage, metre range and throughput claims beside antenna diagrams.
Shoppers often treat headline range as guaranteed in their property without reading obstacle footnotes or setup guides.
Start with noise level claims, battery life claims, and energy efficiency claims when radio heroes sit beside power themes.
Separate range claims from speed puffery
Theoretical peak throughput on packaging differs from real-world range claims — inventory whether the hero cites Mbps or metres.
Industry-leading coverage lines without a test method read as puffery — log whether the hero cites a floor plan or only tone.
See superlative claims and puffery vs objective claims.
Common wireless wording patterns
| Hero phrase | Evidence column | Register note |
|---|---|---|
| Whole-home Wi‑Fi coverage | Floor plan test memo | Log home size |
| 300 m outdoor range | Line-of-sight protocol | Note obstacles disclaimer |
| Mesh node count for 4 bed | Named kit list | Match SKU bundle |
| Bluetooth 100 m range | BLE test conditions | Separate from Wi‑Fi row |
| Up to 1.2 Gbps wireless | Throughput test setup | Distinguish theoretical peak |
Worked example — mesh Wi‑Fi bundle page
A hero states: “Whole-home coverage up to 350 m² on a two-storey layout with three nodes — tested on concrete and timber floors.” Register rows:
Log 350 m² and storey count in the evidence column — different layouts change outcomes.
Record three-node kit as tested bundle — single-node buyers may not achieve the same coverage.
Capture floor material note in substantiation — obstacle disclaimers must stay visible near the hero.
Match the SKU photograph to the node count cited in the claim.
- Area and layout: Floor plan evidence row.
- Node count: Bundle scope row.
- Floor types: Test conditions row.
- SKU photo: Variant alignment row.
Common misreadings on wireless copy
Mbps hero assumed to prove range in metres — throughput and coverage are separate register rows.
Bluetooth range on accessory page assumed to cover the hub sold separately — log device pairs explicitly.
Comparison vs competitor claims assumed substantiated — read comparative claims guide when named rivals appear.
App screenshot assumed to substantiate hero — log app store URL separately from landing hero.
Wireless claim inventory checklist
| Check | On page? | If missing |
|---|---|---|
| Named environment or floor plan | Sometimes | Flag vague hero |
| Obstacles disclaimer near hero | Often footer-only | Visibility gap |
| Hardware bundle match | Sometimes | Feed audit |
| Separate Bluetooth vs Wi‑Fi rows | Usually | Two register rows |
| Theoretical vs measured throughput | Often | Clarify in register |
Subscriptions and pricing rows beside radio heroes
Subscription auto-renewal claims on checkout do not substantiate range heroes — inventory billing rows separately.
Installment buy now pay later claims describe finance — unrelated to radio performance unless footnotes link them.
See subscription auto-renewal claims and installment BNPL claims.
What CiteBefore will and will not do
CiteBefore inventories wireless range and signal strength strings you submit on live URLs and maps them to evidence columns.
We do not run chamber tests, certify throughput, or file ASA responses — inventory support only.
When claim density rises, pair with advertising claim substantiation and testimonials vs substantiation.
Star rating review count claims describe social proof — separate row from radio test evidence unless reviews cite lab data.
Free delivery claims describe logistics — unrelated to range unless bundled footnotes merge themes.
Firmware, mesh handoff and setup guide alignment
Mesh kits often publish range figures based on three-node reference layouts while the default SKU sells a two-node box — inventory whether the hero matches the carton count.
Firmware release notes sometimes change transmit power or band steering behaviour — log hero date stamps when legal teams refresh substantiation folders.
Setup PDFs buried off-site may cite shorter range than the ecommerce hero — register PDF URL separately from the product detail page.
Professional installer claims on trade pages must not contradict consumer heroes unless variant tabs explain commercial test layouts.
Comparator and marketplace feed hygiene
Comparison tables that pit range against a named rival need substantiation for both columns — read comparative vs competitor claims when brands appear.
Marketplace bullets often inherit longest-range copy from the manufacturer while your D2C page shows conservative figures — treat feeds as separate URLs.
Affiliate landing pages may shorten obstacle disclaimers — capture full disclaimer text near the hero on each monetised URL.
See comparative vs competitor claims and star rating review count claims.
Questions
Are wireless range and signal strength claims objective?
Metre range, dBm readings and throughput figures are measurable when scoped to named environment and hardware. CAP literacy expects substantiation — inventory exact radio strings.
Must hero range claims match the router and client sold?
Buyers expect consistency between headline coverage maps, antenna specs and setup footnotes. Log each bundle row separately.
Does CiteBefore run anechoic chamber tests?
No. CiteBefore inventories visible advertising copy on submitted URLs. Radio lab reports remain your product folder.
Can IP rating claims substitute for wireless range wording?
Ingress and radio performance use different tests — cross-read IP rating guide when both appear on the same hero.
Do retailer feeds inherit outdated range figures after firmware changes?
Feeds often lag updated radio profiles. Log merchant and on-site hero strings separately.
More guides
All CiteBefore guides: /guides/. Free scan: claim inventory scan.
Inventory wireless range heroes before media spend
The free scan captures coverage and throughput strings on your URL so evidence columns stay aligned with heroes.