Trust & Proof: Peridot – Signal Evidence & AI Readability

Peridot

(https://askperidot.com) πŸ“Έ Data Snapshot: June 21, 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.
7 Impact Weight: 20 / 100
35% Reputation

The site exhibits clear trust theatre patterns with a review_count of 21 but a proof_links_count of 0. While it claims to have insights and reviews, it fails to link to any third-party verification platforms like G2, Capterra, or TrustRadius. This lack of external proof paths forces the user to take the ’21 reviews’ claim on blind faith, which is a significant red flag in the SaaS space.

Proof density is low regarding social and experiential evidence, though high on technical specifications. The site lists exactly which tools it integrates with (Zoom, Google Meet, etc.), which serves as technical proof of functionality. However, the ratio of unsubstantiated claimsβ€”like the 21 unlinked reviews and the ‘thousands of insights’β€”to verifiable client success stories is poor, as there is not a single named customer referenced.

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