Skip to content

Test your website now

Free, no card. We read only public pages.

Run free audit →

UX quality · Info severity

No Trust Signals on Website: Publish Truthful Relevant Evidence

Review missing trust-signal detection. Publish real relevant evidence, respect permissions and scope, and separate a matching link from verified credibility.

Published · Updated

What the check tests

Check
ux.trust-signals - Trust signals present
Passes when
Commercial sites should surface at least one of: customer logos, testimonials, case studies, security or compliance badges.
Scope
graded once per site
Severity
Info
Fix effort
medium - a working day
Impact when fixed
low

In one paragraph

No trust signals on website means this check did not find links matching its evidence-related wording patterns. It does not establish that the site lacks all credibility information, and a matching support or preview link can create a false pass. Present genuine relevant evidence where useful, without fabricating customers, reviews, statistics, certifications, or claims. Judge what visitors can actually verify rather than the detector alone.

Why it matters

People evaluating a service may look for clear operator identity, understandable product behaviour, relevant examples, and evidence supporting important promises. Testimonials and case studies can contribute when genuine, but they are not the only useful signals.

A new product can be transparent about its stage and demonstrate real functionality without pretending to have an established customer base. A reproducible demo or clearly labelled example is different from a claimed customer result.

Evidence has scope. A supplier's certification is not automatically yours, a logo does not prove a partnership, and one review does not guarantee outcomes for everyone. Explain relationships and limitations accurately rather than treating badges as decorative persuasion.

How WebAuditOS evaluates this finding

The supplied site-wide rule searches observed link text and addresses for fragments such as case-stud, testimonial, customer, reference, success-stor, and review. External links can count, with documented render fallback.

A match passes; no match on readable pages warns informationally; incomplete rendered coverage can be ungraded. Inline quotes or logos without links can be missed, while customer login, API reference, or preview can pass accidentally. It does not verify the truth, relevance, authorship, permission, or quality of any evidence.

How to fix it

  1. Identify the claims visitors need confidence in: what the service does, who operates it, its limits, relevant experience, and the outcome of actual use. Do not assume every business needs the same testimonial layout.
  2. Inventory truthful material already available. Product demonstrations, transparent methodology, named operators, supported capabilities, and documented practices can be useful even without customer quotes.
  3. Where a genuine case study exists, link it clearly. For example:
<a href="/case-studies/example-project">Read the project case study</a>

Use a real appropriate project and avoid making a fictional example appear to be a customer engagement.

  1. Obtain suitable permission and review context before publishing names, quotes, logos, or sensitive results. Keep the evidence current and faithful to what the person or organisation actually endorsed.
  2. Substantiate figures and distinctions. Identify the measurement, period, scope, and relevant limitations rather than displaying an impressive number without explanation.
  3. Clearly label demos, illustrative data, sponsored material, or internal tests so users do not mistake them for independent customer evidence. Do not buy or invent feedback to fill a page section.
  4. Review the public resource's accessibility and working links. A genuine document behind an unexplained access wall may not serve an evaluator, while confidential evidence may appropriately need a controlled request route.
  5. Rescan and document false positives or negatives. A matching customer-support link should not be treated as verified proof, and a truthful inline demonstration should not be dismissed merely because this rule reads anchors.

What the fix can break

Publishing stale or overstated proof can damage credibility. Assign ownership and review claims when products, relationships, or certifications change.

A dedicated evidence page can expose details not intended for public release. Decide what can be shared and preserve confidentiality where needed.

Do not create irrelevant links containing review or customer just to pass. The objective is truthful useful information, not a recognisable substring.

Questions

No. The detector's vocabulary is much narrower than real credibility or evidence.

Must a new product invent testimonials?

No. Be transparent and show truthful demonstrations or verifiable information instead.

Does a customer logo prove an endorsement?

Not by itself. Explain the actual relationship and use material appropriately.

Review pricing information, operator contact, and security information.

In the report

Test this on your own site

Every scan runs ux.trust-signals on every page it crawls, on every plan. The finding carries this id, so a line in a report can be matched to the explanation above - and the free scan needs no account.