A website audit should end with decisions. If the result is a long export of warnings with no indication of what matters, you still have the difficult part to do.
Choose a business question
Start with a question such as “why do people abandon this enquiry form?” or “can customers understand our services without calling us?” You can still review the whole website, but the question gives you a way to prioritise the findings.
List the pages that support the main customer journey: the entry page, a service or product page, supporting proof, and the form or checkout. Include a mobile visit and a returning visit. A homepage-only audit misses much of the experience.
Walk through the site as a customer
Try to complete the main task without using what you already know about the business. Can you tell who the offer is for? Is the next step clear? Are important costs or conditions explained before you reach the form?
Submit a test enquiry using an agreed test address. Check the confirmation on screen, the admin notification and the customer acknowledgement. Mark the record as a test so it does not become an unexpected sales lead. This one exercise checks several systems together.
Review search access and page meaning
Inspect important URLs in Search Console. Check response codes, indexing directives, canonical URLs and whether the sitemap contains the pages you want discovered. A sitemap helps discovery; it does not guarantee indexing. Google explains its role in the sitemap documentation.
Read titles and headings as a set. Do several pages promise the same thing? Is an article still talking about a year or product that is no longer relevant? Keep useful existing URLs when refreshing content, and plan redirects before moving pages.
Check speed, accessibility and maintenance
Test representative templates rather than every page in isolation. Look for slow loading, unexpected layout movement, unclear keyboard focus, unreadable text and images without useful alternatives. Ask who handles updates, backups and broken integrations.
Use automated tools to find clues, then verify them. A tool can flag an image without alternative text; a person still needs to decide whether the image conveys information or is purely decorative.
Write findings that someone can act on
A useful finding includes the page, the observed problem, the likely customer impact, the recommended change, an owner and a way to check the result. For example: “On mobile, the error message sits above the visible area. Move it next to the field and confirm that focus reaches it.”
Fix broken journeys and access problems first. Follow with improvements that make the offer clearer, then polish. Agree a small first batch rather than starting twenty changes at once. Recheck the same tasks after release so the audit becomes a record of improvements, not a document left in a folder.
Have a project in mind?
Let’s talk it through