← All insights

Buying a service

What should you actually receive from a website audit?

A useful audit helps you make decisions. A long list of general tips is not enough.

By Kie at WIDELINE · 16 September 2026

A clear boundary

Before paying, establish which pages, devices and journeys are included. Check whether the review covers public content only or also analytics, search data and internal systems. Access to a report is different from proof that someone has analysed it.

Evidence beside each finding

Look for a page reference or screenshot, the observation, its effect on the customer and a practical recommendation. A measured result should include its source and period. Where the evidence is incomplete, the audit should explain what needs checking.

An order you can act on

Priorities should consider the likely value, urgency, effort, confidence and dependencies. Fix a broken enquiry route before polishing a decorative section. Distinguish changes you can make now from decisions that need more data or a separate project.

A roadmap you can keep

The deliverable should be useful whether you ask the auditor to implement it, use another supplier or work through it yourself. Confirm the file format, review conversation, delivery window and whether implementation is included in the price.