Trust & Proof: Raritan (Legrand) – Signal Evidence & AI Readability

Raritan (Legrand)

(https://raritan.com) 📸 Data Snapshot: June 19, 2026
Trust & Proof — The Lens

Count trust words (review, testimonial, rating, verified) against real outbound proof links (Google, Trustpilot, Clutch, G2, Yelp). Lots of trust language with zero verification links is trust theatre. Unlinked logo galleries count against it.

Trust & Proof Verifiable evidence vs. Trust Theatre.
16 Impact Weight: 20 / 100
80% Reputation

The site avoids most trust theatre traps; however, it lacks external verification links for its major claims. While it cites ‘1.5 Billion Hours of Runtime’ and ‘Trusted by the Top 10 Fortune 500’, these are stated as internal facts without third-party audit links or named public case studies (likely due to data center NDAs). The review count is low (2-4 per page) and appears to be an internal metric rather than a verified third-party feed.

The proof density is high for a product-led site, with 8+ distinct technical proof points found on the PX4 page alone. The site prioritizes technical specifications (±0.5% accuracy, waveform capture forensics) over vague assertions. However, external proof paths are limited to internal case study links, providing fewer ‘exit-ramps’ to third-party verification than expected for an ‘industry leader’.

Trust & Proof is read by weighing trust language against real verification. Below is the page-by-page tally of review mentions and external proof links, then the schema markup that may (or may not) declare verifiable ratings and identity proof.

🛡️ Trust Signals — reviews, proof links, trust-theatre check
10Review mentions (all pages)
4External proof links (all pages)
PageReviewsProof links
/ (home) 2 1
/products/power/power-distribution/intelligent-rack-pdus/ 4 1
/partners/ 2 1
/contact/ 2 1
🔗 Identity & Technical Layer — schema JSON-LD: declared ratings, reviews & identity proof
Homepage — no schema detected (entity gap)
/products/power/power-distribution/intelligent-rack-pdus/ — no schema detected (entity gap)
/partners/ — no schema detected (entity gap)
/contact/ — no schema detected (entity gap)