A website audit checklist for local business sites

Ask ten web designers what a website audit checklist should cover and you will get ten different answers, most of them borrowed from an SEO agency's blog and half of them irrelevant to a plumber in Frome with four pages and a contact form. A useful audit for a local business site is shorter than people expect, and it should be built around one question: does this site help the business win customers, or does it quietly cost them work.

Start with the phone in your hand

Open the site on your phone before you touch a laptop, because that is how most of their customers will meet it. Note how long it takes to appear, whether the text is readable without pinching to zoom, and whether buttons are large enough to tap without hitting the wrong one. A site that looks fine on a wide monitor can still be genuinely awkward on a mid-range phone over 4G, and that gap is the first thing worth writing down.

While you are there, glance at how the site behaves on a slower connection if you can simulate one. A page that takes eight or nine seconds to become usable will lose people before they ever see the phone number, and most visitors will not tell you why they left.

Check whether it is trusted before it is read

Look at the address bar. A missing padlock or a browser warning is an instant, visible problem that no amount of good copy fixes, and it is worth screenshotting on the spot. Then look for signs of age: a copyright year in the footer that has not moved in years, stock photography that looks a decade old, or a design pattern that gives away the platform it was built on. A theme that has clearly not been touched since it launched tells you something about how much attention the business has left for its own website.

If you can tell what the site runs on, note it. A dated WordPress install with an unmaintained theme is a different conversation to a Wix or Squarespace site that is simply under-used, and a business running purely on an Instagram or Facebook page is a different conversation again. They have already shown they want to be found online; they just have not bought the proper version of it yet.

Follow every path a customer would actually take

This is the part people skip because it takes longest, and it is the part that finds the most useful evidence. Click every link that promises to do something: book a table, request a quote, download a price list, join a mailing list. Fill in the contact form yourself with a throwaway address and see whether anything arrives. Dial the phone number if one is listed and check it is not still ringing through to a mobile someone left the business two years ago. A dead booking link or a form that silently fails is worth more to your pitch than a paragraph about design trends, because it is something the business can verify themselves in ten seconds.

Look for proof, not just presence

A local business lives or dies on trust signals a website either carries or does not. Are their Google reviews visible anywhere on the site, or do you have to go looking for them separately? Is there any evidence of past work: photos, case studies, before-and-afters, anything specific to what they actually do? A generic stock image of a smiling tradesperson tells a visitor nothing they could not get from a competitor's identical stock image.

Write it up like a report, not a checklist

The checklist is for you. What the business owner sees should be three short sections: what is working, what is likely costing them enquiries, and one specific thing worth fixing first. Keep it in plain English, name the actual pages and links you tested, and resist the urge to list every possible improvement. A report with twelve recommendations reads like a sales pitch. A report with one clear, well-evidenced problem reads like something a professional noticed and thought was worth mentioning, which is exactly the impression you want to leave.

This is also where an audit becomes a way in rather than a favour. If you have already read how to find web design clients in your own town, you will recognise the pattern: the audit is not preparation for the pitch, it is the pitch. A specific, checkable observation about someone's own website gets read in a way a generic introduction never does.

Doing it by hand versus doing it at scale

All of the above is worth doing by hand at least a few times, because it teaches you what a genuine problem looks like versus a cosmetic preference. Once you know what you are looking for, the repetitive part, checking speed, mobile rendering, SSL status, forms and site age across a list of fifteen or twenty businesses, is the part that eats an afternoon for very little extra insight. That is the part Patchscout runs automatically: it audits every site a search returns and flags the ones with no real website at all, so the manual checklist above becomes something you spend your time on for the two or three prospects worth pursuing, not all twenty.