Trust & Proof: Lucky Strike – Signal Evidence & AI Readability

Lucky Strike

(https://lucky-strike.jp) 📸 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.
15 Impact Weight: 20 / 100
75% Reputation

The site currently shows a review_count of 0 and no trust_theatre_flags, which prevents it from being a high-level offender. However, the proof_links_count of 1 refers only to social media presence rather than third-party validation or press coverage. The site offers no external proof paths that verify its status as an entertainer beyond the existence of its own social accounts.

The proof density is nearly zero as the site contains no verifiable evidence of past events, attendance, or artistic output within the HTML. The only evidence provided is ‘Presence Proof’ (links to social platforms) rather than ‘Performance Proof’ (results or reviews). It lacks all of the industry’s required elements, including venue details, ticket pricing, and accessibility information.

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