Trust & Proof: Lifesum – Signal Evidence & AI Readability

Lifesum

(https://lifesum.com) πŸ“Έ Data Snapshot: May 27, 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.
10 Impact Weight: 20 / 100
50% Reputation

Trust theatre is present in the ‘As seen in’ section featuring logos for Forbes, Wired, and TechCrunch, which lack direct outbound links to the source coverage. Additionally, while the site claims 920,957 reviews, the structured data (review_count) only reflects 31 on the homepage, creating a discrepancy between the marketing narrative and the technical proof. The absence of a trust_theatre_flag indicates these are not overt template-level badges, but the lack of proof paths for the ’60+ million users’ claim remains an issue.

The proof density is internally high but externally low. The site relies on massive internal numbersβ€”60 million users and nearly 1 million reviewsβ€”to create a sense of scale, but it provides almost no external proof paths like App Store links, third-party certification badges, or clinical trial references. The ratio of specific numbers (substance) to vague assertions is healthy, but the verifiability of those numbers is weak.

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
75Review mentions (all pages)
3External proof links (all pages)
PageReviewsProof links
/ (home) 31 1
/nutrition-explained/ 22 1
/work/ 0 0
/contact/ 22 1
πŸ”— Identity & Technical Layer β€” schema JSON-LD: declared ratings, reviews & identity proof
Homepage β€” no schema detected (entity gap)
/nutrition-explained/ β€” no schema detected (entity gap)
/work/ β€” no schema detected (entity gap)
/contact/ β€” no schema detected (entity gap)