A practical starting point
Check the customer journey, record issues and distinguish small content changes from larger technical work.
1. Follow the route a customer takes
Open your main pages on a phone and a desktop. Start at the homepage, find a service and try to reach the contact or booking option. Check that navigation works, text is readable and important buttons are not hidden by banners or overlapping elements.
Use the keyboard as well as a mouse where possible. Notice whether you can reach links and form controls and see which control has focus. These checks can uncover usability issues, but they are only a first review; they do not establish that the whole site meets accessibility standards.
Checklist
- Main navigation and service links
- Visible contact or booking options
- Readable phone layout and keyboard focus
2. Test forms and important links carefully
If you own the site and have permission, send a brief, non-sensitive test enquiry and confirm it arrives at the intended destination. Seeing a success message is not the same as verifying delivery. Check any spam folder or connected system that is part of your normal process.
Test phone, email, booking and other important links. A third-party destination can change even when your website has not. Do not use real customer information for test messages, and avoid placing orders, making payments or submitting repeated tests without an agreed testing process.
3. Review information that can go out of date
Check hours, contact details, service descriptions and any displayed prices or offers. Read your most important pages as a new visitor. Remove expired promotions and correct wording that describes a service you no longer provide.
Keep a simple change list with the page address, the incorrect text and the approved replacement. Group related edits so they can be reviewed together. A small factual correction is different from a new page, a rewritten service description or a major redesign.
Checklist
- Current hours, contacts and offers
- Accurate service descriptions
- Page addresses and approved replacement text
4. Know who handles technical changes
Check that the site loads over HTTPS without browser security warnings, and note any pages that fail or behave unusually. If your platform uses software or plugins that need updates, confirm who is responsible and what testing is required before changing them.
Ask your hosting or platform provider about backups, restoration and account recovery rather than assuming they are included in a care agreement. Before a significant change, confirm a recovery route. Do not share passwords or recovery codes in an issue list. Report suspicious activity through the appropriate provider or support channel.
5. Record issues and choose the right kind of help
Log what you checked, what failed, which device was involved and what should happen instead. Prioritize problems that prevent enquiries or leave business information wrong. After a fix, repeat the affected customer journey rather than assuming the change solved everything.
One Touch's Website Care Plan includes basic site, contact-form and link checks plus one small content change each month. It does not include new pages, major redesigns, large copy rewrites or new features. Ongoing local SEO is a separate service; use its scope when you need continued search-content work.
A resource to keep
Monthly Website Check Log
Copy an entry for each check in your own document. Record real observations, and mark anything you did not test as not checked. This log is not a security audit, accessibility certification or proof of enquiry delivery.
Important: keep sensitive information out
Do not include passwords, API keys, recovery codes, payment information, Social Security numbers or real customer data in this log. Use non-sensitive test details. Share account access securely through provider invitations or delegated permissions, not this document.
MONTHLY WEBSITE CHECK LOG Copy this entry for each check in your own document. Replace the bracketed prompts with observations; mark untested items as not checked. IMPORTANT: Do not include passwords, API keys, recovery codes, payment information, Social Security numbers or real customer data in this log. Use non-sensitive test details. Share account access securely through provider invitations or delegated permissions, not this document. 1. Review date / reviewer role [Record the date and the role responsible for this review.] 2. Page / customer journey checked [Record the page address and the steps you followed, such as service page to contact option.] 3. Device / browser [Note phone or desktop and browser. Include keyboard checks where relevant.] 4. Expected result [Describe what should happen, such as a working link or confirmed test enquiry delivery.] 5. Observed result / issue [Record pass, fail or not checked, then explain what you observed. A form success message alone does not confirm delivery.] 6. Priority / next action [Prioritize blocked enquiries and incorrect business information. Describe the correction or who should investigate.] 7. Responsible role / target date [Record who will follow up and a requested date. Do not assume the task is covered by a care plan.] 8. Recheck date / outcome [Repeat the affected journey after a fix. Record the result or mark it not yet rechecked.] 9. Outstanding questions [List unresolved issues or decisions. Keep separate checks for separate issues.]
When you want a hand
Related support
Check the plan's full scope before deciding whether routine care fits the work your site needs.
Further reading
Continue exploring
More small-business guides
- Planning your websiteWhat to prepare before building your small business website
- Understanding search visibilityLocal SEO basics: what to check before starting ongoing work