Trust & Proof: Loomly – Signal Evidence & AI Readability

Loomly

(https://loomly.com) 📸 Data Snapshot: May 31, 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.
8 Impact Weight: 20 / 100
40% Reputation

The site exhibits moderate trust theatre by claiming ’50k+ Customers’ while providing a review_count of only 10 on the About page and 1 on the Homepage, with a proof_links_count of 0 for external verification. There are no named client case studies with before-and-after metrics in the provided text, only a ‘Case Study Template’ for users to download. The claim ’10x your followers’ is a bold performance assertion that lacks any linked source or data-backed proof path.

Proof points are concentrated in product specs (10+ channels, 25% yearly discount, 50% non-profit discount) rather than client outcomes. The site offers ‘Downloadable’ resources like a ‘Post Ideas Guide’ as proxy substance, which provides utility but does not function as proof of efficacy. The ratio of unsubstantiated growth claims to verified client success stories is approximately 5:1.

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
26Review mentions (all pages)
4External proof links (all pages)
PageReviewsProof links
/ (home) 1 1
/pricing/ 1 1
/about/ 10 1
/careers/ 14 1
🔗 Identity & Technical Layer — schema JSON-LD: declared ratings, reviews & identity proof
Homepage — no schema detected (entity gap)
/pricing/ — no schema detected (entity gap)
/about/ — no schema detected (entity gap)
/careers/ — no schema detected (entity gap)