Auditing a Small Business Site's Basics: Questions to Ask Before You Hire Anyone
Most small business owners only think about their website when something breaks, a page loads slowly, or a customer mentions they couldn't reach the contact form. Yet the core state of a site is often knowable with a few simple checks you can run yourself. This article focuses on a different angle than a generic health check: instead of listing every technical term, it walks through how to inventory what your site actually depends on, how to write down what you already know, and how to frame questions before you pay anyone for help. Nothing here is a recommendation about specific tools, vendors, or contract terms. It is a method for thinking clearly about a site you may not fully understand.
Start with an inventory, not a fix
Before you can judge whether your website is in good shape, you need to know what it consists of. Open a plain document and list the parts you can identify: the domain name and where it is registered, the company or person who hosts the files, the content management system or builder you use to edit pages, any forms, booking widgets, or embedded maps, and the email address that receives contact submissions. Many owners discover that these pieces live in four or five different accounts, each tied to a different login or a former employee's email.
This inventory is not busywork. It tells you who can change what, and it reveals gaps such as a domain that renews through a personal card no one remembers or a contact form that sends messages to an inbox nobody checks anymore. Write the owner of each item next to it, even if the answer is 'unknown.' Unknowns are the most useful lines on the page because they become your first questions.
Check the things a visitor experiences
Once you know the parts, test the experience from the outside. Open the site on a phone and on a desktop, ideally in a private browsing window so cached pages do not mislead you. Click every main navigation item, submit the contact form with a test message, and confirm that the message arrives. Look at the phone number and address in the footer and confirm they are current. Check that images load and that no page shows a broken link or an error message.
Keep a short record of what you find, including the date and the browser you used. A single observation is a snapshot; two or three records taken over several weeks show whether a problem is intermittent, which matters when you describe it to someone else. Notes like 'the quote form returned a blank page on Tuesday evening from a phone' are far more actionable than 'the site seems off.'
Compare what you see against what you intended
A useful audit asks whether the site still does its job. Write down the three or four actions you want a visitor to take, such as calling, requesting a quote, booking an appointment, or reading a specific service page. Then ask whether each action is easy to find within a few seconds and whether the path works end to end. Sites often drift: a promotion from two years ago still sits on the homepage, a discontinued service still appears in the menu, or a link points to a page that was renamed.
Also compare your site against your other public listings. If your hours, address, or services differ between the website and the directories where customers find you, note each mismatch. Inconsistent information rarely causes a dramatic failure, but it quietly erodes the confidence of someone deciding whether to contact you.
Questions to ask before you pay for help
When a problem outruns what you can check yourself, the next step is a conversation with a provider. The quality of that conversation depends on the questions you bring. Ask what exactly is included in the quoted work and what is excluded. Ask who will have access to your accounts and how access is granted and removed. Ask how changes are documented so you can understand what was done after the fact. Ask how the provider communicates progress and how you can reach them when something urgent comes up.
Compare answers across providers using a simple grid: scope clarity, access handling, documentation, communication channels, and how the work is priced. The rows matter more than any single answer. A provider who gives specific, plain answers to each row is easier to evaluate than one who responds with vague reassurance. Ask for the terms in writing before work starts, and read them against the scope you wrote down in your inventory.
A practical checklist to finish: know every account that touches your site, confirm who owns each one, test the core visitor paths on mobile and desktop, record findings with dates, compare the site to your intended actions and to your public listings, and prepare written questions before any conversation. An audit of this kind takes an afternoon and gives you a clear picture to bring to any decision about your website.