Reading a Small Business Site Like a Stranger Would
Most small business owners know their website intimately, which is exactly why they struggle to see it. After months of editing, every page looks clear to the person who wrote it. A better test is to pretend you have never seen the site before, arrive from a search result on a phone, and try to do one specific thing: find out what the business does, confirm it serves your area, and reach a human. This article walks through a reading method you can run yourself in about thirty minutes, and it explains the questions to put to anyone who offers to change the site afterward.
Start with a single task, not a general look
Open the site in a private browser window so cached pages and saved logins do not distort what you see. Choose one realistic task a customer might have, such as "find the hours and phone number" or "see whether they handle my type of job." Time yourself and write down each click it takes. If you cannot complete the task within a minute or two without hunting, that is a useful finding, even if the rest of the site looks polished.
Repeat the exercise with two or three different tasks. Patterns matter more than any single result. If every task requires starting from the homepage and navigating through a menu of vague labels, the structure is the problem, not one page's wording.
Test the phone experience separately
Most local customers arrive on a phone, often while walking, driving, or comparing options quickly. Check the site on a phone-sized screen, either with your own device or your browser's responsive view. Look for text that is too small to read without zooming, buttons that sit too close together to tap reliably, and images that push the important information far down the page.
Pay attention to the contact details. Is the phone number visible without scrolling on the first screen? Is it a link that dials when tapped? Is the address spelled consistently wherever it appears? Small inconsistencies, such as two different phone numbers in the footer and on the contact page, make a visitor wonder which one is current.
Check the trust basics a visitor looks for
A visitor deciding whether to contact you is usually asking simple questions: Who runs this? What exactly do they do? Where are they located? How do I reach them? Walk through the site and note whether each question has a clear answer on the pages a customer would naturally visit. A services page that lists offerings without explaining who each one is for leaves the visitor guessing.
Look at how the site describes its process. A short explanation of what happens after someone gets in touch, such as whether they receive a quote, a callback, or a scheduled appointment, reduces hesitation. Be honest with yourself about whether every claim on the page is one you can back up with specifics, and remove any wording that sounds impressive but says nothing concrete.
A comparison worth making before you hire help
When you decide to have someone improve the site, a useful exercise is to write two short lists before the first conversation. The first list describes the problems you observed in the reading test: slow-loading pages, a confusing menu, a contact form that is hard to find, missing location details. The second list describes the outcome you want, stated in terms a customer would notice, such as "a visitor can see our hours and call us within thirty seconds on a phone."
Compare that to what a provider proposes. A vague promise to "refresh the design" is hard to evaluate. A specific description of which pages will change, what will stay the same, and how the result will be checked is much easier to judge. Ask the provider to explain how they would confirm the problems you listed are fixed, and whether the work covers all the pages a customer might visit or only the homepage.
Questions to ask before anyone changes your site
Before agreeing to any changes, ask the provider to answer these in writing: What exactly is included, and what is excluded? Which pages and devices will be tested after the work? Who will own the content and account logins when the project ends? How will you be informed of changes, and how do you request a revision? What happens if the result does not match the scope you agreed to? Where a provider offers a fixed-price fix for a small, well-defined problem, confirm the exact boundaries so the price reflects the actual work.
A good provider will welcome these questions because they show you have thought about the project. Keep your notes from the reading test, since they become the baseline for judging whether the changes helped. The goal is not a perfect website but one that a stranger can understand, trust, and act on within a minute.