Technical website audit checklist for small businesses

A small-business audit should find problems that stop customers from discovering, trusting, or contacting the company. It does not need to begin with a hundred-page export.

Choose five representative URLs: the homepage, a main service, an information or article page, the contact page, and one conversion page. Test them on mobile and desktop.

Availability and URL consistency

• HTTP redirects once to HTTPS.
• One preferred hostname is used consistently.
• Important pages return successful responses rather than soft error pages.
• Old addresses redirect directly to a relevant replacement.
• The certificate is valid for the public hostname.

Record redirect chains and intermittent failures with timestamps. They are hard to fix from memory.

Search access

Check the robots file, page-level robots directives, canonical links, and XML sitemap together. Confirm that pages intended for customers are not blocked and that private, duplicate, or filtered URLs are not promoted as canonical content.

Search titles should distinguish services and locations naturally. Avoid using the same generic title everywhere.

Mobile and keyboard use

At a narrow width, complete the main customer task. Can you open navigation, read the offer, call or write, accept or reject cookies, and submit a form without zooming sideways?

Then repeat with the keyboard. Focus must remain visible, controls must have understandable labels, and overlays must not trap or hide the active element.

Performance

Inspect the largest image and the heaviest scripts on each template. Common gains include:

• resizing and compressing hero photographs;
• loading nonessential media later;
• removing duplicate analytics or chat tools;
• caching fonts and static assets;
• reserving image and embed space to reduce layout movement.

Measure after clearing caches as well as during repeat visits.

Security and forms

Ensure HTTPS covers forms and embedded resources. Keep the framework, plugins, themes, and server runtime supported. Protect public forms against automated abuse without making them unusable for keyboard or assistive-technology users.

Submit a test enquiry. Confirm that validation explains what went wrong, the message arrives, and the confirmation does not reveal private data.

Trust and local information

Compare the website's name, address, phone, opening hours, service area, and legal identity with the information customers see elsewhere. Correct outdated details at the source rather than adding another conflicting version.

Show evidence appropriate to the service: qualifications, process, pricing basis, warranties, responsible author, or real contact details. Do not use invented testimonials or unsupported badges.

Conversion paths

Each core service page should offer a relevant next action. A contact button is not enough if it leads to a broken form or asks for information the company does not need.

Track successful submissions and outbound calls where privacy and consent allow. Also monitor failure: form errors, abandoned steps, 404 pages, and unavailable phone links.

Audit output

Use a short prioritized table rather than a pile of screenshots.

Assign an owner and verification step to every item. Recheck the public deployment, not only a preview environment.

For a broader model of the measured dimensions, continue with How to improve your website quality score.