Open the website you already have and choose one important customer task, such as finding a service and starting an inquiry. These seven checks will help you describe what is working and what needs attention.
For each check, record the page address, what you tried, the result, and one status: working, problem found, or not yet checked. Keep observations separate from guesses about the cause. This is a first inspection, not a full technical, SEO, or accessibility audit.
1. Explain the page’s job
Start with the homepage and one important service page. Write one sentence describing what a visitor should understand or be able to do there.
If you cannot identify that purpose, note what is missing or competing for attention. Do not decide that a new layout is the answer yet. A clearer service explanation may be the first thing to investigate.
2. Read the offer without filling in the gaps
Check whether the page identifies the service, who it is for, and any important limits. Ask someone unfamiliar with the business to describe the offer after reading it.
Record the question or misunderstanding, not just “confusing copy.” For example: “The reader could not tell whether we repair existing installations or only supply new ones.” The service-page content guide can help organize the missing answer.
3. Follow the main button to its destination
Open the primary call to action. Does the destination match the label? Is the expected next step available? A button labeled “Book” should not leave someone wondering why no appointment can be selected.
If the route includes a form, use an agreed, clearly labeled test and confirm where it arrives. Follow our contact-form testing checklist for the full delivery check rather than submitting real customer details.
4. Find the service from the homepage
Try to reach the chosen service using the site’s ordinary navigation. Record misleading labels, missing links, and destinations that do not answer the promised question.
Focus on where the task becomes unclear rather than counting clicks against an arbitrary limit. A useful observation is “I opened Services but could not find the repair service listed on the homepage.”
5. Repeat the task on another screen and with a keyboard
Check the same route on a phone and a larger screen. Look for overlapping content, missing information, and controls you cannot comfortably use. On a computer, try reaching the links and controls with the keyboard and note whether you can see which one has focus.
The W3C’s initial accessibility checks offer a starting point. Passing these few checks does not establish complete accessibility.
6. Check the page’s basic search presentation
Read the browser title and main heading. Do they accurately identify the page? Note repeated generic titles or a heading that no longer matches the content.
If search visibility is a concern, ask the site owner to inspect the URL in Search Console. Appearance alone cannot establish indexing status. Our small business SEO basics explain how this fits with content and internal links.
7. Give the important findings an owner
Keep a short list of confirmed issues. Include the affected task, page, evidence, business impact, person responsible, and next action. Keep an unresolved question marked as unknown instead of quietly treating it as a pass.
Prioritize a broken essential route before an optional visual preference. Website support can begin with those concrete observations. If the findings suggest a wider change, use our repair-or-redesign guide to discuss the scope.
After a correction, repeat the check that found the issue and record the result. “Changed” and “checked” should be separate entries.
