Most business websites do not fail because of one dramatic decision. They become unreliable through small omissions: an update that keeps getting postponed, a form nobody tests, a domain renewal owned by a former employee, or a backup that has never been restored.
A useful maintenance checklist should prevent those gaps without turning a marketing manager into a system administrator. The aim is clear ownership and evidence that the important work happened.
Every week: watch the customer-facing essentials
- Confirm the home page and important landing pages load normally.
- Submit each lead or enquiry form and confirm the message reaches the intended person.
- Check important transactions, logins or booking steps where applicable.
- Review uptime or incident alerts and assign any follow-up.
- Look for unexpected pages, redirects, pop-ups or browser warnings.
This is a short operational check, not a security audit. It catches visible problems before customers have to report them.
Every month: maintain the working website
Review software and dependencies
Identify updates for the CMS, extensions, themes, framework packages and connected services. Do not treat every update as a blind “update all” exercise. Check compatibility, confirm a current backup and define the important journeys to test afterwards.
WordPress advises site owners to keep plugins and themes current and recommends a current backup before updating. Its automatic-update feature is opt-in for individual plugins and themes, so enabling it is a decision—not proof that every part of the website is covered.
Verify backups and recovery readiness
Confirm that backups completed, are stored somewhere appropriate and cover the files and data needed to restore the website. Periodically test the restore process. A green “backup completed” message is not the same as a proven recovery route.
Check forms, integrations and notifications
Test contact forms, email delivery, CRM connections, payment notifications and any other route that moves a customer enquiry into the business. Check both the user confirmation and the internal notification.
Review access
Remove former staff and vendor accounts that are no longer needed. Confirm that administrators use individual accounts rather than one shared login. Record who owns the domain, hosting, analytics and third-party services.
Review website health
Look for broken links, missing images, certificate issues, crawl errors, unusual traffic changes and obvious performance regressions. The goal is to identify a change that deserves investigation, not to chase a perfect score in every tool.
Every quarter: improve, do not merely preserve
- Review whether priority pages still match current services and customer questions.
- Check mobile journeys on a real phone.
- Review search performance and queries that are beginning to gain impressions.
- Identify outdated claims, people, prices, dates and downloadable files.
- Choose one or two improvements to speed, usability or conversion.
- Revisit the support backlog and remove work that is no longer valuable.
Maintenance becomes more useful when it creates momentum. A website that is technically current but commercially stale is only partly maintained.
Every year: confirm ownership and lifecycle
Review the domain registrant, DNS, hosting, licences, repositories, source files, analytics ownership and emergency contacts. Confirm renewal dates and payment methods are controlled by the organisation.
Then review the technology lifecycle. Is the CMS or framework version still supported? Are important plugins or packages abandoned? Is the hosting runtime compatible with the next supported version? Major upgrades are easier to plan a year early than a week late.
Give every check three things
For each maintenance item, record:
- Owner: the person or provider accountable for doing it.
- Evidence: the report, log, test result or ticket showing it happened.
- Escalation: what triggers investigation or approval.
That simple structure turns a checklist into an operating rhythm.
When to bring in a website care team
External support is worth considering when checks are repeatedly skipped, knowledge sits with one person, updates feel risky, or ordinary changes take too long to arrange. Start with a review of the current site and its ownership gaps. The right maintenance scope should follow the real website—not a generic package list.