1. Start with crawlability and indexability.
Before polishing titles or chasing speed scores, confirm that important pages can actually be reached and interpreted. Check HTTP status, robots rules, canonical tags, sitemap presence, redirect behaviour and whether the intended pages are indexable.
2. Review titles, headings and page purpose.
Each important page should have a clear purpose. The title, H1 and main copy should agree on the topic rather than competing with each other. Look for missing or duplicated titles, weak descriptions, heading misuse and pages that do not answer the intent behind their target query.
- Unique, descriptive title and H1.
- Enough useful content to answer the page's job.
- Internal links from relevant parent or supporting pages.
- No obvious duplication or near-empty pages.
3. Check performance without treating one score as the diagnosis.
Page speed matters because slow loading and unstable layouts create friction. Use field or lab data where available, but inspect the underlying causes: oversized images, render-blocking resources, layout shifts, excessive JavaScript and slow server response.
4. Verify tracking and conversion signals.
Check whether GA4, GTM and advertising tags are present where expected. Code presence is not the same as runtime accuracy, so a full implementation review may still need browser or account access. The audit should say what was verified and what remains unverified.
5. Review security and trust basics.
Confirm HTTPS, sensible security headers where measurable, mixed-content issues, and obvious domain/email security signals. Security is broader than a public crawler can prove, so label passive observations honestly.
6. Review UX and conversion friction.
Technical health does not guarantee that a visitor can understand the offer. Check mobile readability, navigation, calls to action, form friction, clarity of next steps and whether important service pages answer the questions that stop users from converting.
7. Finish with priorities, not a dump of warnings.
A good audit should separate critical blockers from useful improvements. Group findings into Now, Next and Later, show affected URLs and explain why each fix matters. That turns a scan into an implementation plan.
Frequently asked questions
What is a website audit?
A website audit is a structured review of technical, SEO, content, performance, tracking, security and user-experience signals to identify what should be fixed and in what order.
How often should a website be audited?
A full audit is especially useful before or after a redesign, migration, major content change or unexplained performance decline. Smaller health checks can be run more frequently.
Is an automated audit enough?
Automation is useful for repeatable evidence and broad coverage, but results still need prioritisation and context. Not every warning deserves the same urgency.
Should a website audit include affected URLs?
Yes. A useful finding should show where the problem occurs so the team can reproduce, fix and verify it.
Turn the checklist into a free multi-page audit.
Run the Professional Website Audit across up to 12 pages to surface technical SEO, content, tracking, security and performance findings with affected URLs and priorities.
Run Free Professional Audit →