> ## Documentation Index
> Fetch the complete documentation index at: https://patterns.heurilens.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Trust Signals
> A measurable UX pattern where users hesitate or abandon actions because credibility cues are missing, unclear, or mistimed.
## Trust signals as measurable UX
Trust is not a feeling users articulate.\
It is a **decision accelerator**.
When trust signals are present, users act faster.\
When they are missing or weak, users hesitate — even if the offer is strong.
## What breaks when trust signals fail
Trust breakdowns rarely look dramatic.\
They show up as *small delays* at critical moments.
Common failure modes:
* credibility cues appear **after** the decision moment
* signals exist but lack clarity or relevance
* multiple weak signals compete instead of one strong cue
* design looks “polished” but unverified
## Observable user behavior
> “Users don’t say ‘I don’t trust this.’\
> They simply don’t continue.”
Behavioral traces include:
* pauses before primary CTAs
* repeated scrolling around pricing or forms
* hovering over buttons without clicking
* exits from high-intent pages (pricing, signup, checkout)
## How trust breaks across surfaces
Typical issues:
* pricing shown without social proof
* guarantees hidden below the fold
* unclear refund or cancellation terms
What users do:
* compare plans repeatedly
* leave to “think about it”
* seek reassurance elsewhere
Typical issues:
* asking for sensitive data without explanation
* missing security or privacy cues
* no indication of what happens next
What users do:
* stop mid-form
* abandon at the final step
* hesitate before submit
Typical issues:
* bold claims without evidence
* testimonials that feel generic
* logos without context
What users do:
* skim quickly
* doubt claims
* postpone decisions
## Product-level signals Heurilens looks for
Heurilens evaluates trust at the **moment of decision**, not globally.
Key checks:
* presence of credibility cues near CTAs
* relevance of proof to the user’s intent
* clarity of guarantees, policies, and next steps
* consistency of trust cues across pages
* visual priority of the strongest signal
## How Heurilens detects trust issues
Detects where users are expected to commit (signup, pricing, submit).
Checks whether trust cues appear before or after hesitation begins.
Assesses clarity, relevance, and dominance of trust indicators.
## Example output from Heurilens
Primary actions lack immediate credibility reinforcement.
Users hesitate at high-intent moments due to missing or delayed trust cues, reducing conversion confidence.
## Example fix direction generated by Heurilens
Rather than adding “more badges,” Heurilens recommends **better timing and focus**:
* place the strongest trust cue **next to** the decision
* replace generic proof with context-specific evidence
* explain *why* information is requested before asking
* clarify what happens immediately after action
* reduce competing trust messages to one dominant signal
Trust is built fastest when users don’t have to look for reassurance.
## Why this pattern matters
Trust failures do not reduce interest.\
They reduce **commitment**.
Users want to proceed —\
they just need confirmation that it’s safe and worth it.
***
## Related patterns
Early clarity sets the baseline for trust.
Predictable rules strengthen credibility.
Forms amplify trust weaknesses.
Trust cues must visually dominate at the right moment.
Run an analysis and see where users hesitate due to missing trust signals.