Trust & Proof: Jellyfish – Signal Evidence & AI Readability

Jellyfish

(https://www.jellyfish.com) 📸 Data Snapshot: May 16, 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

While the site does not trigger the trust_theatre_flag by displaying unverified reviews, it suffers from a total proof path absence. With a proof_links_count of 0 and a review_count of 0, the site provides no external validation for its claims of being ‘faster’ or ‘smarter.’ The bold assertions in the meta title lack any linked source, named client, or verified third-party rating, making the entire digital presence a claim-only environment.

The ratio of verifiable evidence to assertions is 0:4, based on the four unsubstantiated claims in the meta title and zero proof points in the body. Not a single named client or specific percentage of growth is mentioned in the data. The site relies entirely on vague assertions without providing a single external proof path or verifiable technical specification.

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
🔗 Identity & Technical Layer — schema JSON-LD: declared ratings, reviews & identity proof
Homepage — no schema detected (entity gap)