Workflow7 min read
Website maintenance checklist: weekly, monthly and yearly tasks for client sites
By the RenewalRemind team
Website maintenance has three rhythms. Continuously: uptime, SSL and DNS monitoring. Weekly to monthly: core, theme and plugin updates, backups with a test restore, security and form checks. Yearly: renewals for domains, hosting, SSL, email and licences, plus a review of access, costs and what the site still needs. Write it down once and run the same list for every site.
Key takeaways
- Automate what can be automated: monitoring, backups and reminders.
- Monthly: updates, a test restore, forms and checkout, broken links and speed.
- Yearly: every renewal date, every account's access and every cost.
- Agree in writing what your maintenance plan covers — especially renewals and who pays for them.
Websites don't break all at once. They drift: a plugin falls behind, a backup quietly stops, a certificate renewal fails, a domain card expires. A maintenance checklist turns that drift into a routine. Use the one below as a starting point and run the same list for every site you look after.
Continuously (automate these)
- Uptime — is the site answering with a real page? Every 5–15 minutes for important sites.
- Response time — is it getting slower week by week?
- SSL certificate — valid, and warned about well before expiry.
- DNS — does the domain still resolve?
- Backups — running on schedule, stored away from the server.
None of these should depend on someone remembering. See the uptime monitoring guide for intervals and alerting.
Weekly
- Review any downtime, slow-response or SSL alerts from the past week and note causes.
- Apply security updates for the CMS, plugins and themes (on busy sites, test on staging first).
- Check that the latest backup completed and its size looks normal.
- Skim for spam comments, odd new users or unexpected admin accounts.
Monthly
- Apply all remaining core, plugin and theme updates; remove plugins nobody uses.
- Submit every contact form and, for shops, place a test order end to end.
- Check page speed on the homepage and the most important landing page.
- Look for broken links and 404s in your analytics or search console.
- Check search console for new indexing, security or manual-action issues.
- Review upcoming renewals for the next 60 days and invoice or confirm them.
- Send the client a short report: uptime, updates done, issues fixed, anything they need to decide.
Quarterly
- Restore a backup to a staging site and check that it works. A backup you've never restored is a guess.
- Review user accounts: remove people who left, reduce admin access to those who need it.
- Change shared passwords and rotate API keys that were shared outside the team.
- Check the PHP (or runtime) version is still supported and plan upgrades.
Yearly
- Every renewal date — domain, hosting, SSL, email, premium plugins and themes, maintenance contracts. Confirm each has an owner, a payer and a reminder. Here's a system for that.
- Check domain registrant details and the registrar account email — renewal notices go there.
- Review costs: are you paying for hosting, plugins or seats nobody uses?
- Review the site with the client: what's out of date, what's missing, what should change next year.
- Update the privacy policy and cookie notice if tools or data collection changed.
What to put in a maintenance plan
If you sell maintenance to clients, write down:
- What's included — updates, backups, monitoring, a set number of small changes, the monthly report.
- Response times — how fast you react to downtime, and during which hours.
- Renewals — which ones you track and pay for, which ones you remind the client about, and what happens if they don't pay.
- Ownership — the client owns the domain, hosting and content; you have access.
- What's not included — redesigns, new features, and fixing problems caused by changes the client made themselves.
Frequently asked questions
How often should a website be maintained?
Monitoring should run continuously, updates and backups weekly or monthly depending on how often the site changes, and a full review of renewals, access and costs once a year.
What should a website maintenance plan include?
Typically updates, backups, security checks, uptime and SSL monitoring, small content changes and a monthly report. Say clearly whether hosting, domain and licence renewals are included and who pays for them.
How do I make sure backups actually work?
Restore one to a staging site at least once a quarter. A backup that has never been restored is a hope, not a backup.