A WordPress Maintenance Checklist We Actually Follow
Staging, a click path, and a note you can read. Auto-updates without a human are how Tuesday morning outages start.Staging, a click path, and a note you can read. Auto-updates without a human are how Tuesday morning outages start. We run WordPress maintenance as a retainer with a checklist, not as “we will keep an eye on it.”
This is the list we actually follow. Steal it. If a host’s one-click updates are your whole plan, you do not have a plan.
Before anything touches production
A staging environment that is not a plugin toggle nobody uses. Copy of production data, or a sanitized copy if you cannot. PHP and plugin versions written down. A click path: home, a key landing page, login, a form, and if it is Woo — a product, cart, and checkout. That path is the acceptance test.
Backups you have restored once. A backup that has never been restored is a story. We prefer host-level plus an offsite copy. File and database together.
Updates in a boring order
Minor core, then plugins, then the theme, then major core. Not all at once on Friday. After each group, the click path. Woo and membership sites get a paid test order or a membership login, not just a visual glance.
We read changelogs for payment, cache, builder, and security plugins. If a plugin is abandoned, the maintenance ticket is “replace or remove,” not “hope.” Custom code belongs in a small plugin or a child theme we control — see custom plugin vs another extension.
Security and users
Logins: 2FA for administrators, no generic admin, XML-RPC off unless something real needs it. File editing in admin off. A firewall or host WAF is not an excuse to keep unused plugins around. Each plugin is an attack surface and a future PHP conflict.
Users: remove the freelancer who finished last year. Application passwords and unused REST applications too.
What we report
A short note: what changed, what we clicked, what we did not do, what is waiting (PHP bump, theme rewrite, speed). If you want a content program, hire a writer; we will keep the site able to publish. Speed work is a separate scope — WordPress speed optimization or a speed audit.
Need this run on a calendar instead of in a panic? Book a consultation. For stores, pair it with WooCommerce maintenance.