Trust & Proof: YWallet – Signal Evidence & AI Readability

YWallet

(https://ywallet.app) 📸 Data Snapshot: May 24, 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.
18 Impact Weight: 20 / 100
90% Reputation

The site avoids trust theatre entirely; the review_count and trust_theatre_flag are 0 and false respectively across all slots. It does not use fake testimonials or unverified partner logos to create a false sense of scale. While proof_links_count is 0 in the metadata, the body text provides direct outbound links to the Google Play Store, App Store, and GitHub for source code verification.

Proof density is high relative to the site’s size, with a focus on functional proof rather than social proof. Every claim regarding platform availability is backed by a specific link to an external repository or application store. The Security page provides concrete examples of PIN authentication and database encryption rather than vague assertions of being secure.

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