Name the owners of the site, email and data
The website owner knows which services, prices and terms are current. The developer keeps templates and integrations working within the contract. The CRM or email owner can verify that an enquiry reached the right queue. Give each check a named owner or role and a backup.
List the systems that store your site or enquiry records. Check who can access the domain, hosting, dashboard and inboxes that receive enquiries. A system link and the owner's role are enough for the maintenance log. Keep passwords out of the table.
Put the checks on the calendar
Start with events that could break something. Add regular checks to catch changes outside the plan. The team might test the form after every edit and review the terms on key pages once a month.
Agree frequency with the owner based on how often the site changes and what a failure would cost the business.
| Task and when to check | Owner | What to save | When to escalate |
|---|---|---|---|
| Open key pages and the form after a release | Developer or person on duty | URL, time and results on a phone | A page is down or the form is unreachable |
| Confirm receipt of a test enquiry after changing the form or recipient | Form owner and CRM owner | Approved test and a matching reference in the queue | The site confirmed receipt but the intended queue has no record |
| Check services, prices and contacts after a change in terms | Content owner | List of affected pages and sign-off from the owner | Prices or terms on the site differ from current terms |
| Check the backup and recovery plan before a risky change | Hosting owner | Backup date and result of an approved restore test | The backup is incomplete or the restore failed |
| Check the domain and certificate before renewal | Domain or infrastructure owner | Expiry date and renewal confirmation | Expiry is approaching and renewal isn't confirmed |
Walk through one path as a customer
Open the relevant service page on a phone, find the terms, follow the link to the form and check what happens after submission. Agree on a test with the recipient before sending it. If the site takes orders, add a checkout check on a test site.
When the offer changes, check all the places it appears. A new price may be on the service page while the catalogue card still shows the old one. Terms should match where the customer makes the decision and where they place the order.
Choose technical checks for your platform
A WordPress site may need theme and plugin updates. A managed platform may handle some updates for you. Find out what the provider owns, what your team checks and which integrations you maintain.
Before changing a critical component, agree where to test it, who releases it and how to restore the working version. If you change how payments or emails are routed, test that route separately from the page design.
Record failures so someone else can reproduce them
Log the date, page URL, steps and result. Attach evidence without customer data and record who took the task. If the failure blocks enquiries, use the agreed urgent channel. Agree structural changes or a template rebuild as separate work.
Choose the audit that matches your question
Choose the free audit when you need to understand your own website first. Choose the competitive audit when your next decision depends on comparing your website with relevant alternatives. Both turn supported evidence into practical actions.