Signal 02 of 09 · Nebula Diagnostic Spec v1.0.0
Trust Signals
Does the page support its claims before asking for commitment?
Decision rule
At least one verifiable proof element must appear near the conversion ask: named results, sourced review counts, case studies, or identifiable company and author information. A run flags pages that make strong claims with no adjacent, checkable support.
What the engine inspects
- ·testimonial and logo blocks
- ·review widgets
- ·case study links
- ·author and company identity markup
How to check it yourself
- Locate the primary conversion ask on the page.
- Within one screen of it, look for checkable proof: named testimonials, sourced review counts, linked case studies, identifiable company details.
- Strong claims with no adjacent verifiable support fail the signal.
The engine automates this inspection and attaches measured evidence to every failing condition. A manual pass is not a substitute for the recorded evidence trail, but it should agree with it.
Pass / fail examples
Pass
A pricing claim sits next to a linked case study naming the customer and the measured result. Support is checkable. Clear.
Fail
"Trusted by hundreds" appears with no names, no sources, and no links. Flagged.