A practical look at what a modern website audit should review, from AI search visibility and performance to accessibility, privacy and security.

A modern website audit should do more than list broken links or score a homepage. A useful audit now needs to show whether your website can be found, understood, trusted, used and maintained across the ways people interact with the web.

That means looking at search visibility, AI-shaped discovery, real user performance, accessibility, privacy, security and the commercial journey together. A weak page is rarely weak in only one place. Poor structure can affect search, confusing content can affect conversion, and slow scripts can affect both performance and privacy compliance.

AI search visibility has become part of the audit

Search is no longer only about whether a page ranks in a familiar list of blue links. Website owners now need to understand whether their pages are eligible, understandable and useful in newer search experiences where answers, summaries and discovery surfaces can reduce the obvious click path.

A strong audit should review page intent, service clarity, content depth, headings, internal linking, structured data, crawlability and whether important commercial pages answer the questions real customers are asking. This is where SEO foundations still matter. The basics have not disappeared, but the standard for clear, useful and well-structured content has become higher.

How to fix it

Start by mapping each key service page to a real customer question, then check whether the page gives a direct answer, useful supporting detail and a clear next step. Thin pages, duplicated service copy and vague claims should be rewritten before chasing more technical search changes.

Performance needs real user evidence

A website can feel fine in the office and still perform badly for customers on mobile data, older phones or slower connections. That is why a modern audit should look beyond a single speed score and review loading performance, layout stability and interaction responsiveness.

Core Web Vitals are still a useful starting point because they focus on what users actually experience. Largest Contentful Paint, Cumulative Layout Shift and Interaction to Next Paint can expose problems that are easy to miss during a visual review. Heavy scripts, unoptimised images, complex layouts and slow third-party tools can all make a polished website feel unreliable.

A good website audit should separate quick wins from deeper technical work. Compressing images may help, but a slow theme, bloated plugin stack or poor hosting setup may need a more structural fix.

Accessibility, privacy and consent need to be checked together

Accessibility should not sit in a separate document that nobody reads. It affects navigation, forms, buttons, colour contrast, focus states, error messages and how confidently people can complete important actions. WCAG 2.2 gives teams a stronger baseline for checking whether a website can be used by more people in more situations.

Privacy checks now need the same practical treatment. Cookie banners, analytics tags, tracking scripts and consent settings should be reviewed as part of the same audit because they affect trust, measurement and compliance. If a website is collecting data before consent is handled properly, or if key events are not being measured at all, the business may be making decisions from incomplete or risky data.

How to fix it

Test the important journeys manually. Use a keyboard, submit forms, trigger errors, reject non-essential cookies and check whether analytics still records meaningful business actions in a compliant way. Automated scans help, but they cannot replace walking through the experience like a real visitor.

Security checks should reach beyond the padlock

Seeing a padlock in the browser is not enough. A modern audit should check whether the website uses sensible security headers, whether old software is still being exposed, whether forms are protected, whether plugins or dependencies are maintained, and whether backups and recovery steps are clear.

This matters most on websites that have been left alone for a while. Small technical issues can build quietly until they become performance problems, security risks or content management headaches. If that sounds familiar, our article on what happens when your website is left alone explains why maintenance gaps often show up slowly before they become urgent.

Ongoing website support should also be part of the recommendation when an audit finds recurring issues rather than one-off fixes. There is little value in repairing the same problem every few months without improving the system around it.

Good audits end with priorities, owners and next steps

The best audit output is not a long spreadsheet of warnings. It is a practical plan that explains what matters, why it matters, who should handle it and what should happen first.

Some issues will protect trust, such as fixing broken forms or improving consent handling. Some will protect visibility, such as rewriting weak service pages or improving crawlability. Others will protect performance and long-term ownership, such as reducing plugin bloat, updating templates or moving to stronger hosting.

A modern website audit should help you decide whether the site needs a few focused fixes, a structured support plan or a deeper rebuild. When the findings are prioritised properly, the audit becomes a decision-making tool rather than another document that gets filed away.