Web trust: observable signals worth reviewing

What the scanner observes

Compare the page title and opening promise with what the organisation actually offers. Check that a visitor can identify the publisher, find a suitable contact route and understand the next step without guessing.

The implemented trust check flags a missing or very short title. Identity, contact details and the truth of claims still require a human review.

AuditLume reads the final public response and initial HTML only; the finding remains a prompt for verification rather than a conclusion about the whole organisation.

A responsible manual review

Automated output is an invitation to investigate, not a verdict. Check representative pages, complete the real user task and include people with different devices or needs. Treat unusual results as context to understand rather than a score to optimise blindly.

• Write a specific title for each important page.
• State who publishes the site and how to contact them.
• Explain scope, exclusions and realistic response expectations.
• Ask someone outside the project to describe the offer after one minute.

How to prioritise

Review the evidence on the exact public page, record the current state, make one controlled change and check again. Keep screenshots or response details when they help colleagues understand the decision.

1. Write a specific title for each important page.
2. State who publishes the site and how to contact them.
3. Explain scope, exclusions and realistic response expectations.
4. Ask someone outside the project to describe the offer after one minute.

Limits to remember

A positive signal does not certify accessibility, privacy, security, legal compliance or search performance. A missing signal does not by itself prove harm. AuditLume reads public responses and initial HTML; specialist, legal and manual reviews remain separate activities.