A website is not finished when it launches. Software ages, certificates expire, plugins are abandoned, contact forms stop sending emails and pages quietly break. Most failures are boring and preventable, yet customers often discover them before the owner does. A maintenance schedule turns "someone should check that" into routine tasks with a clear owner. This checklist groups the work by frequency so you can see what takes ten minutes and what needs a developer. It complements our website maintenance guide and the argument in why maintenance is not optional.
Weekly: Ten-Minute Checks
Open the site on a phone and a computer and make sure the homepage and main pages load properly. Submit your own contact form and confirm the message arrives, including a look in the spam folder, because a silent form is one of the costliest hidden faults. Check any alerts from your uptime monitoring, confirm that the latest backup completed (see backup automation) and delete spam comments or suspicious new user accounts. Search for your own business name once a week and look for odd pages or spam results, which can be an early sign of a hack. If your site takes orders or bookings, place a test order. These checks are simple, and a short written list means anyone on the team can do them.
Monthly: Updates and Health Checks
Monthly work is where most security protection happens. Apply updates to the CMS, plugins and themes, ideally after testing them on a staging copy. Run a vulnerability scan, as explained in frequent security scans, and look for broken links and 404 errors. Review your analytics for unexpected drops in traffic, enquiries or speed using the measures in key website metrics and the tools in performance monitoring tools. Finally, check the user list and remove staff or agencies who no longer need access.
Quarterly: A Deeper Review
Every three months, test a real restore from backup, not just the existence of one; the method is in our guide to backup and disaster recovery. Work through a security audit checklist, review page speed and Core Web Vitals, and check the site on real devices, since emulators are not enough. Read your own pages for outdated prices, staff names, opening hours and offers, and refresh content that has slipped, as in refreshing old content. Do a spot check of accessibility and review any third-party scripts or integrations that may have changed.
Yearly: Renewals and the Bigger Picture
Once a year, confirm that your domain, SSL certificate and hosting are renewed, that auto-renewal cards are still valid and that the contact emails on those accounts are actually monitored. An expired certificate can do real damage, as described in expired SSL certificates, and our domain and DNS guide explains what to keep on file. Check that your hosting plan and PHP version are still supported. Update the copyright year, privacy policy and legal pages, then ask whether the design and features still serve your goals, using the FAQ on when to redesign and maintain. Plan next year's improvements with continuous improvement.
If You Only Have an Hour a Month
Not every business can do everything on this list. If time is short, protect the essentials first: confirm backups are running and recent, apply security updates, test your contact form and checkout, put every renewal date in a shared calendar and run a security scan. Everything else can wait for a while, though not forever, because small neglected jobs compound into expensive problems. Our article on why websites fail after year one shows how that usually happens.
Who Should Do What
Give every task an owner, a date and a place to record the result. Simple weekly checks suit an internal staff member, while updates, scans, restores and server work are better handled by a developer, a trade-off discussed in outsourcing versus in-house maintenance. Keep a log of what changed and when, so problems can be traced quickly. It is also worth reading about life after launch when you plan your budget.
If you would rather not run this checklist yourself, ANGLIA can take it on. We answer common questions in ongoing support after launch, and with 20+ years and 5,000+ projects behind us we know where websites tend to fail. Use our contact page to ask about a maintenance plan.






