Blog / How the internet works /

Website audits: what I check first

A website audit can turn into a 200-line spreadsheet that nobody reads. The trick is the order. Check the things that can make the whole site disappear first, and leave the polish for later.

Here’s the order I’d follow, based on years of working with WordPress, Shopify and other sites for different organisations. It’s a method, not a template to copy blindly. Every site has its own quirks.

1. Can people and search engines reach it at all?

Before anything clever, check the basics:

  • Does the site load on both www and non-www, and does one redirect to the other?
  • Does HTTP redirect to HTTPS, in one step?
  • Is the certificate valid and the domain not about to expire?
  • Does DNS point where you expect?
  • Is the server responding quickly and without errors?

If any of these are wrong, nothing else matters yet. DNS, SSL and Cloudflare: what site owners should know covers the background.

2. Is Google being told to stay away by accident?

This is the most expensive mistake and one of the most common, usually left over from a redesign or staging site.

  • Open /robots.txt and read it. Is anything important blocked?
  • Check for noindex tags on key pages (view source, or use Search Console’s URL Inspection).
  • Look at canonical tags: do they point to the right version of the page?

The difference between these tools is explained in robots.txt and noindex: when to use which.

3. What does Search Console say?

If the site has Search Console, spend ten minutes there before using any other tool. It’s Google’s own view.

If Search Console isn’t set up, setting it up is task one.

4. Crawl the site

Run a crawler and look at the big groups first:

  • Pages returning 404 or 5xx errors.
  • Redirect chains and loops.
  • Duplicate titles and descriptions across many pages.
  • Pages with no internal links pointing to them (orphans).
  • Thin or empty pages.

Don’t try to fix everything it lists. Sort by how many pages are affected and how important they are. A method for that is in a practical system for triaging audit findings.

5. Look at the money pages

Every site has a handful of pages that matter most: the homepage, top products or services, contact page, checkout, and the posts that bring in traffic. Open each one on a phone and ask:

  • Does the page say clearly what it is?
  • Is the title sensible and not truncated?
  • Does the main call to action work?
  • Are images loading and compressed?

For shops, a product page audit based on shopper decisions goes deeper.

6. Speed and stability on mobile

Test the key pages, not just the homepage. Look at loading, layout shifts and responsiveness using a mix of lab tools and real-user data. Don’t chase a perfect score; look for the one or two things holding pages back. Speed testing tools compared explains how to do that sensibly.

7. Security and maintenance

  • Are the CMS, theme and plugins up to date?
  • Are there abandoned plugins or apps?
  • Are there working backups, and has anyone tested a restore?
  • Who has admin access, and should they?
  • Is there uptime monitoring?

A WordPress maintenance checklist for site owners is a fuller version.

8. Content and structure

Only now do I look at what’s on the pages:

  • Which pages get traffic and which get none?
  • Are there several pages competing for the same search?
  • Is there outdated content that should be updated, merged or removed?
  • Do important pages link to each other sensibly?

A content audit is where the long-term wins are, but it’s pointless on a site that’s blocked, broken or slow.

9. Tracking

Check that analytics is recording, key events (purchases, form submissions) fire, and there’s no duplicate tagging. Broken tracking leads to wrong decisions that look right in a report.

How to write it up

A good audit report has three parts:

  1. What’s broken and costing you, with evidence.
  2. What to fix, in order, with who should do it.
  3. What can wait.

Plain words, screenshots and a short summary at the top. I wrote about what makes a report people actually read in writing an SEO audit report people actually read.

Things that don’t belong at the top

  • Meta description length warnings on low-traffic pages.
  • Perfect scores in a speed tool.
  • A long list of “minor” issues with no impact attached.
  • Backlink counts without context.

They’re fine to fix when you have time. They shouldn’t hide the problem that’s actually costing you visitors.

Key takeaways

  • Work from “can it be reached” to “is it indexable” to “does it perform” to “is the content good”.
  • Search Console is the first tool, not the last.
  • Prioritise by number of pages affected and business importance.
  • Write findings with evidence and an order of work.

A quick audit pass

Today, spend 30 minutes: load your site on both versions of the URL, read your robots.txt, open Search Console’s pages report, and test your most important page on mobile. What’s the first thing that looks wrong?