Trust & Proof: Skymark Airlines (SKYMARK) – Signal Evidence & AI Readability

Skymark Airlines (SKYMARK)

(https://skymark.co.jp) 📸 Data Snapshot: June 19, 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

Trust theatre is minimal because the site relies on regulatory and logistical proof rather than social proof widgets. While it lacks independent review aggregators (review_count: 0), it provides high-substance evidence through official PDF forms, medical protocol lists, and partnership credits for intellectual property like the Pikachu Jet (Pokemon/Nintendo). The site does not make bold performance claims (e.g., ‘Best Airline in Japan’) that would require verified links, staying within the realm of objective service offers.

Proof density is high due to the volume of verifiable logistical data. Across the 4 pages, there are dozens of specific data points including flight dates, age restrictions for infants (28 days), and specific fare names. Vague assertions are discarded in favor of ‘Notes’ and ‘List of Cautions,’ which provide the negative constraints required for high-substance technical content.

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 0
/ja/campaign/ 0 1
/ja/timetabeleandfares/ 0 0
/ja/support/customer.html 0 0
🔗 Identity & Technical Layer — schema JSON-LD: declared ratings, reviews & identity proof
Homepage — no schema detected (entity gap)
/ja/campaign/ — no schema detected (entity gap)
/ja/timetabeleandfares/ — no schema detected (entity gap)
/ja/support/customer.html — no schema detected (entity gap)