WordPress maintenance is often treated as a monthly plugin update. That is the smallest part of the job. A site that stays healthy needs someone watching updates, backups, access, certificates, forms, performance and renewals, with a record that proves each check happened.
This checklist is designed for the owner or operations manager who is responsible for the website but does not write code. Each item names an owner and the evidence to keep. Adjust the frequency to the site's risk: an online store needs more attention than a brochure site.
How to use the checklist
Create a recurring maintenance log with a row per check, the date, the person, the result and a link to the evidence. A check without evidence is a habit, not a control. Review the log monthly with the person who owns the website budget. If hosting is bought through a local reseller, confirm in writing who owns the domain, the hosting account and the backup destination.
Daily checks
- Uptime and errors. Confirm the site is reachable and check the error log for new fatal errors or repeated warnings. Owner: support. Evidence: uptime report and error log excerpt.
- Backup completion. Confirm the last backup job completed and the archive is readable. Owner: support. Evidence: backup dashboard or job log.
- Security alerts. Review alerts from the firewall, malware scanner and hosting provider. Triage rather than ignore. Owner: security. Evidence: alert register with disposition.
- Order or enquiry flow. If the site takes orders or leads, place a test order or check the queue. Owner: operations. Evidence: test transaction ID or inbox screenshot.
Weekly checks
- Plugin, theme and core updates. Apply updates on staging first, then production. Record the versions. Owner: developer. Evidence: update log with before and after versions.
- Failed login and lockout review. Check for brute-force patterns and locked accounts. Owner: security. Evidence: login report.
- Form and email delivery. Submit each important form and confirm the notification arrives. Owner: marketing. Evidence: test submission and inbox copy.
- Broken links and redirects. Scan the main navigation, campaign pages and checkout path. Owner: content. Evidence: broken-link report.
- Storage and database growth. Check disk usage, log size and backup size trends. Owner: support. Evidence: capacity chart.
Monthly checks
- Restore a sample. Restore a random file and a database table to a staging environment. Owner: support. Evidence: restore log with duration and result.
- User access review. Remove leavers, confirm administrator accounts, enforce multi-factor authentication. Owner: website owner. Evidence: access list with review date.
- Security scan. Run a malware and vulnerability scan, then investigate findings rather than only recording a score. Owner: security. Evidence: scan report and remediation notes.
- Performance check. Test the home page, a product page and checkout on a mobile connection. Compare against the previous month. Owner: developer. Evidence: timings and screenshots.
- SSL and domain renewals. Confirm certificate expiry, domain expiry and DNS renewal dates are in the calendar. Owner: support. Evidence: renewal register.
- Plugin inventory. Identify abandoned plugins, duplicate functionality and plugins with no clear owner. Owner: developer. Evidence: plugin list with status.
- Change log review. Confirm every production change has a ticket, a tester and a rollback note. Owner: developer. Evidence: change log with approvals.
Quarterly checks
- Full restore test. Rebuild the site from backup in an isolated environment, open it, place a test order and check the admin login. Owner: support. Evidence: timed restore record.
- PHP and database version review. Confirm the hosting stack is supported and plan an upgrade before end of support. Owner: developer. Evidence: version matrix and upgrade plan.
- Disaster recovery review. Revisit the recovery point and recovery time targets with the business. Owner: website owner. Evidence: signed review note.
- Vendor and hosting review. Check who owns the domain, hosting account, DNS and backup destination. Owner: operations. Evidence: ownership register.
- Content and SEO hygiene. Review thin pages, duplicate titles, redirect chains, sitemap errors and noindex settings. Owner: marketing. Evidence: crawl report.
Annual checks
- Access and role model. Re-test every role and remove permissions that are no longer needed. Owner: website owner. Evidence: access review record.
- Incident runbook. Update contacts, escalation paths and the offline copy of recovery steps. Owner: operations. Evidence: runbook with review date.
- Contract and renewal terms. Review hosting, plugin licences, support agreements and notice periods. Owner: finance. Evidence: renewal calendar.
- Security training. Brief the team on phishing, password managers and safe content uploads. Owner: operations. Evidence: attendance record.
- Retirement plan. Decide which plugins, themes or custom code should be removed rather than maintained forever. Owner: technical lead. Evidence: signed retirement list.
Verification
Once a quarter, pick three checks at random and ask for the evidence. If the log says a restore was tested, ask to see the timestamp and the restored site. If the log says access was reviewed, ask for the list and the reviewer's name. This is how you distinguish a maintained site from a maintained spreadsheet.
Common mistakes
- Updating everything on production at once, with no staging test and no rollback.
- Keeping the only backup on the same hosting account as the site.
- Letting a former employee retain an administrator login.
- Ignoring abandoned plugins because the site still loads.
- Letting the domain or hosting renewal sit in one person's personal email.
- Measuring success by the number of updates applied rather than by uptime, recovery and security outcomes.
Metrics
- Uptime and number of unplanned outages.
- Percentage of updates applied within the agreed window.
- Backup success rate and age of the oldest verified restore point.
- Measured restore time against the recovery time objective.
- Number of administrator accounts and overdue access reviews.
- Time to patch a critical security release.
If you want the routine run by a named team with a documented log, start with Managed Technology & Cybersecurity; the pricing page explains how maintenance plans are scoped. If the site has already been compromised, read the malware cleanup and prevention checklist.
Sources
- WordPress Developer Resources, Hardening WordPress, accessed 17 November 2026.
- NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning, accessed 17 November 2026.
- CISA, Cyber Essentials Toolkit, accessed 17 November 2026.
- WordPress, Release archive, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.