Your homepage can load while your quote form sends inquiries to an inbox nobody checks. That’s why a website maintenance checklist should start with the thing a customer came to do: request an estimate, book a trip, or pay for an order. A useful plan tells you who checks that it works, who gets called when it doesn’t, and how to recover if a change breaks it.
Start with one customer task
Pick the action your business would miss first. On a home-services site, open the quote page on your phone, submit a clearly marked test inquiry using an email address you control, then check the inbox that is supposed to receive it. Don’t stop at the thank-you message. If the form says someone will call back, check that the person taking calls actually sees the inquiry.
For a booking site, check that customers can find availability and understand whether they’re requesting a slot or confirming one. Test the full booking or payment in a staging environment or your provider’s sandbox if available. A live link check is useful, but it doesn’t tell you whether the confirmation email or calendar update works. Don’t use real customer records or card details for test transactions. Stripe’s testing guide shows how its sandbox simulates payments without moving money.
Separate content changes from software updates
Keep a short list of things that change in real life: hours, service areas, prices and offers. Review the list monthly if it rarely changes, and check sooner when you’re running a promotion or changing seasonal hours. Make the task specific: “Check Saturday hours and the quote form” is easier to finish than “Check the website.”
For software, first find out which updates your host handles and which are yours. On a self-managed WordPress site, check compatibility and take a backup before making a substantial update. If you have a staging copy, test there first. After the update, repeat the customer task you picked above. Put routine updates on a calendar, but handle urgent security fixes promptly rather than waiting for the next monthly check. WordPress’s update instructions cover backups and compatibility.
Prove you can restore a backup
A downloaded backup proves you can access a file. It doesn’t prove you can bring the site back. Ask what the backup contains: the site files, any database, and the configuration you’d need to reconnect services. Check separately whether your booking platform or CRM keeps its own history. Plan how often to back up by asking how much recent work or customer activity you could afford to lose.
Have your host or developer restore a backup in a protected test environment with live email, booking and payment actions disabled. Then open key pages and compare recent content against what you expected. Note how long the restore took. If you can’t do that yet, write down what you’ve actually verified and schedule a real test. Keep a protected copy outside the live hosting account where your setup allows it. CISA’s backup guidance recommends keeping critical backups offline and encrypted and testing that they’re usable.
A website maintenance checklist to start with
- Weekly: Open the site on a phone, check the main inquiry or booking link, and confirm a test inquiry reaches the right inbox.
- Monthly: Check hours, offers and service details. Review routine updates and verify the last scheduled backup completed. Don’t put urgent fixes off until this check.
- Quarterly: Run a test restore, review who has access, and check whether outage alerts reach someone who will act on them.
- After a significant change: Repeat the customer test and check the pages you changed on a phone and a desktop. Record who can roll the change back.
Adjust the timing to the site. A brochure site that changes twice a year and a booking site with daily reservations don’t need the same plan.
Put a name next to each job
Write down who checks the site, who can restore it, and who steps in when either person is away. Make sure the business can access and recover its own domain, hosting and email accounts without relying on a former contractor. Give people named accounts with the access they need instead of sharing an admin password. Then put the first check on the calendar. If you only have time for one today, send a test inquiry and see who gets it.