A WordPress maintenance checklist your team can finish
A maintenance checklist should tell the next person what to do, not remind them that websites need attention. “Check security” is too vague. “Review new vulnerability notices, identify affected installations and assign an owner” is a task someone can finish.
Use this checklist as a starting point, then remove items that do not belong to your service. Add the client-specific checks that do. A restaurant booking site and a membership site should not have identical acceptance criteria.
At the start of the working day
- Review open incidents and confirm who owns each response.
- Check for failed or overdue backups. Investigate the cause before starting repeated retries.
- Review new security notices against the versions actually installed.
- Look for changes in error patterns, not just the total number of log lines.
- Read client messages for upcoming launches, payment changes or access problems that affect planned work.
Keep this session short. Its output is an assigned queue, not a promise that every issue will be fixed immediately. If an urgent incident interrupts planned maintenance, say which work has moved and give it a new owner or date.
During the agreed maintenance window
- Confirm the scope and check that nobody else is deploying to the same site.
- Verify a usable recovery point and the access needed to restore it.
- Read relevant release notes, especially for major versions and integrations.
- Test higher-risk changes on an isolated staging copy.
- Apply the approved set of changes and record old and new versions.
- Run the site’s acceptance checks, including the destination of a form or transaction.
- Record failures and deferred items separately from completed work.
The WordPress update instructions recommend backing up before an update. For an agency, that recommendation becomes more useful when the checklist names the recovery point and the person who could restore it. “Backup enabled” does not answer either question.
Once a month, inspect the things that drift
Review administrator access, license renewals and the inventory of plugins and themes. Ask whether inactive software still has a reason to be present. Do not delete something solely because it is inactive; first check dependencies, rollback needs and ownership.
Check storage growth against the retention policy. Schedule a restore exercise if the last one is stale or the site has changed significantly. Look at recurring alerts and decide which need a permanent fix. Review the client’s critical journey after changes to external services, even if WordPress itself has not changed.
Finish with a client-facing summary. Explain completed work, unresolved risks and decisions you need from them. Avoid a long export of successful background checks with the important blocked item buried near the bottom.
Use a small completion record
For each maintenance session, capture: site, operator, date, approved scope, recovery point, changes, tests, exceptions and next action. That is enough structure to support a handover without turning every plugin update into a report-writing exercise.
Keep the record beside the work, not in a private notebook. If the operator is away tomorrow, another teammate should be able to see whether a failed checkout was already present before the update.
Start with one site and time the routine. If it is too long to sustain, cut duplicate reporting before you cut recovery or functional checks. Leave a checkbox open when a check was not done. A named exception is useful; a guessed pass is not. For the weekly schedule around this checklist, see managing multiple WordPress sites; for the backup check itself, use a dedicated restore exercise rather than a dashboard screenshot.
Have a correction or a workflow we should cover? Tell the IrmaWP team.