Before you start: two rules
1. Never experiment on your live site. Try uncertain updates or settings on a staging copy (many hosts offer one-click staging, or a developer can create one).
2. Have a backup you have actually restored. Untested, it is a hope, not a plan. A restore needs both database and files (WordPress backup documentation).
Why maintenance matters
WordPress, plugins and themes get regular bug and security fixes, and older WordPress versions are not maintained with security updates (hardening guide). Months of skipped updates make each update riskier, as more changes land at once; careless updates can break a form, layout or integration. This routine balances both.
Weekly (15 to 30 minutes)
- Site loads on phone and computer: home, a service page, contact.
- Mobile data too: many visitors in Nigeria arrive on it, not office Wi-Fi.
- Contact form works: a test message reaches the right inbox.
- Last night's backup completed, stored off the website's own server.
- Updates reviewed in the dashboard, security releases noted.
- No obvious problems: unexpected pages, spam comments, dashboard warnings.
Monthly (1 to 2 hours)
- Update staging first: core, plugins, themes; then check key pages and forms.
- Back up live, then apply the same updates there.
- Re-test the contact form and key pages after updating.
- Check Site Health (Tools → Site Health, Status tab).
- Delete unused plugins and themes; deactivated code can still be exploited.
- TLS certificate (padlock) expiry, if your host does not auto-renew.
- Log changes: date, versions before and after, breakages and fixes.
More detail: what Site Health flags
Site Health flags common configuration problems, such as an outdated PHP version or inactive plugins and themes that should be removed (Site Health documentation). Delete unused plugins rather than leaving them installed and deactivated.
Quarterly (half a day)
- Test a restore to staging or a temporary location; record date and result.
- Review users: remove leavers, minimise administrators, one login per person.
- Strong authentication (such as two-factor) for administrators, where supported.
- Review plugins: what each does, who relies on it, still maintained?
- Hosting account: PHP version, disk space, control panel access, billing contacts.
- Content accuracy: services, staff, prices, hours and locations.
Once a year
- Ownership: domain, hosting, WordPress admin and analytics in the organisation's name.
- Access: at least two people can reach each account.
- Renewal dates: domain, hosting and premium plugin licences.
- Dollar renewals: card or account limit and balance cover them at today's rate.
- Recovery plan written down: who restores, from which backup, how long.
Things not to do on a live site
Unknown plugins
Never install one "to try it".
Theme edits in WordPress
Lost on the next theme update, and a typo can take the site down.
Bulk clean-ups
No database clean-up or "optimisation" plugins without a restorable backup.
Shared admin logins
One login per person, never shared.
Security plugin myths
A security plugin does not replace updates and backups.
What this checklist does not cover
This routine reduces risk but cannot make a site perfectly secure. It is not a security audit, penetration test or compliance review, nor a substitute for specialist advice if you suspect a compromise. If your site is hacked:
- Take it offlineOr put up a maintenance page.
- Protect backupsKeep them safe.
- Get specialist helpBefore restoring anything.
Copy this checklist
Copy this checklist freely for internal use. Rather have someone else run it? See website care.
Sources and further reading
Product capabilities and guidance change. These are the primary sources this article relies on, checked on the review date above.
- Hardening WordPress, WordPress Developer Resources
- Backups, WordPress Developer Resources
- Upgrading WordPress, WordPress Developer Resources
- Site Health screen, WordPress.org Documentation
This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.