A website can look polished while its contact form is broken, its certificate is expiring or its backups have never been restored. Maintenance is a set of small checks performed consistently.
First: make sure customers can reach you
Submit a test enquiry through every public form. Check the inbox that should receive it, not just the browser success message. Test booking buttons, phone links and WhatsApp links from a mobile device. Confirm opening hours and business details are still correct.
Record who owns each lead channel and what happens when the primary mailbox fails. An undelivered enquiry is a commercial problem even when the website reports HTTP 200.
Verify backups and rollback
Check whether database and file backups completed. Compare their timestamps with your recovery policy. At least periodically, restore a backup into an isolated environment so you know the files and database can actually be used together.
Before updates, document a rollback point and the version being changed. Do not apply security patches to a live customer portal without understanding database migration requirements.
Review software and access
Update maintained plugins, server components and libraries through a tested workflow. Remove unused accounts, verify multifactor authentication for administrators and rotate credentials where appropriate. Check error logs for suspicious request patterns without exposing personal data.
Scan for accidentally public staging areas, backup archives and debug tools. An old ZIP in a web-accessible directory can expose more than the polished live site.
Check the mobile experience
On a real phone, load your homepage and most-used service page, open menus, complete a form and test an account sign-in with a safe test account. Watch for content below the viewport, tiny targets, keyboard overlap and horizontal scrolling.
Use both a narrow phone and a desktop browser. A successful desktop Lighthouse run cannot substitute for an actual mobile interaction.
Review search health and performance
Check Search Console for indexing changes, new server errors and important pages that have disappeared from impressions. Look at PageSpeed Insights or field Core Web Vitals for signs of degrading load or interaction experience. Don't panic over every non-indexed filter URL; prioritize pages that should rank.
Monthly evidence log
- Date and person performing the check
- Contact form result and test inbox
- Backup date and recent restore status
- Updates applied and rollback reference
- Top indexing or performance issue
For deeper release checks, use the technical audit checklist.
The 60-minute monthly review
Allocate the first 10 minutes to backups and uptime: confirm a recent backup exists and that somebody has successfully tested a restore, rather than trusting a green backup badge. Check monitoring alerts for repeated outages. Use the next 10 minutes for security updates, account access and any unexpected new administrators.
Spend 15 minutes acting like a customer. Open the site on a phone, use the menu, submit a test enquiry, verify the confirmation reaches the right inbox and open the most important product pages. Finish with 15 minutes in Search Console or your analytics tools, followed by 10 minutes noting actions, owners and deadlines.
| Time | Check | Evidence to save |
|---|---|---|
| 10 minutes | Backups, restore test and uptime | Backup timestamp and restore result |
| 10 minutes | Updates and permissions | Changed versions and access review |
| 15 minutes | Mobile purchase or contact path | Test submission and screenshot |
| 15 minutes | Search visibility and broken pages | Priority URLs and action list |
| 10 minutes | Assign fixes | Owner, priority and due date |
Escalate exceptions rather than waiting for next month
If a contact form fails, the website returns errors, an unknown administrator appears or a backup cannot restore, treat it as an incident now. A maintenance calendar is a reminder, not a reason to delay urgent fixes. A page losing a few impressions, by contrast, needs comparison over time before you declare an outage.
For a broader handover, use our technical audit checklist or the Versys Site Health Toolkit.
Reference notes
- Google Search Console Help
- OWASP Top 10
This is a practical editorial guide, not a claim that any setup guarantees a specific outcome. Verify platform features, regulations and prices before making business decisions.
