Backups & maintenance · Explainer
WordPress Maintenance Checklist: Weekly, Monthly, Yearly

Short answer
Every week, confirm the backup ran, install pending updates, and test the contact form, checkout, and login. Every month, review Site Health, clean the database, and delete unused plugins, and every quarter, test a full restore and review admin users. Once a year, renew the domain and hosting and confirm the SSL certificate renews.
Key takeaways
- Weekly work is a backup check, pending updates, and a test of the contact form, checkout, and login.
- Minor core releases install automatically by default, and per-plugin auto-updates arrived in WordPress 5.5.
- Site Health sits under Tools and sorts results into critical issues, recommended improvements, and passed tests.
- WordPress.org recommends PHP 8.3 or greater and MySQL 8.0 or greater, or MariaDB 10.11 or greater.
- WordPress core does not include two-factor login, so add it with a plugin for every administrator.
- Test a full restore on staging every quarter, because a backup you never restored is a guess.
What does WordPress maintenance cover?
WordPress maintenance is the routine work that keeps a site secure, recoverable, and working: updates, backups, security checks, monitoring, and clean-up.
Most of it is small work done on time. A plugin update takes minutes when nothing is broken. The same update takes hours when it lands on a site with no recent backup and three years of unreviewed user accounts.
A checklist turns that work into a habit instead of a rescue.
Five jobs make up almost all of it. Keep WordPress core, themes, and plugins updated. Keep backups that you can restore.
Watch for security problems. Check that the site still works. Remove what you no longer use.
Everything in this guide fits under one of those five jobs.
What should you do every week?
Every week, confirm the latest backup ran, install pending updates, and test the pages that earn money: the contact form, the checkout, and the login.
Start with the backup, not the update. Open your backup plugin or your host panel and check the date of the latest backup and that a copy reached off-site storage. WordPress.org suggests weekly backups for smaller sites and daily backups for high-activity sites, as its backup guide states (checked November 2026).
A backup that only exists on the same server is lost with the server.
Store at least one copy away from the server. CISA recommends three copies on two kinds of storage with one copy off-site, as its backup guidance explains (checked November 2026).
Then open Dashboard, then Updates, and install what is waiting. Back up first if the backup check showed a gap. After updates, open the site and test the pages that matter.
Site Health cannot see a form that quietly stopped working, so click through it yourself. Also read the update emails WordPress sends after automatic updates, since they report failed updates you would otherwise miss.
| When | Task | Why it matters |
|---|---|---|
| Weekly | Confirm the backup ran and reached off-site storage | A failed backup looks safe until you need it |
| Weekly | Install pending core, plugin, and theme updates | Fixes close holes attackers already know about |
| Weekly | Test the contact form, checkout, and login | Forms break quietly after updates |
| Monthly | Review Site Health and delete unused plugins | Unused code still needs patching |
| Monthly | Check speed and broken links | Slow pages and dead links lose visitors |
| Quarterly | Test a full restore on staging | A backup you never restored is a guess |
| Quarterly | Review admin users and passwords | Old accounts are an open door |
| Yearly | Renew the domain and hosting, confirm SSL renews | An expired domain takes the whole site down |
What should you do every month?
Every month, review Site Health, clean the database, delete unused plugins and themes, and check speed and broken links.
Open Tools, then Site Health. The Status tab sorts results into critical issues, recommended improvements, and passed tests. Critical issues can include background updates not working, plugins waiting for updates, or an outdated PHP version.
Fix critical items first and note what you changed.
Delete plugins and themes you do not use. Deactivating is not enough, because the files stay on the server and still need patching. WordPress.org's hardening guidance says to keep plugins updated and delete the ones you do not use.
Keep one default theme as a fallback, and remove the rest.
Clean up the database too. Old post revisions, spam comments, and expired transients build up over time. The guide to optimizing the WordPress database explains what to remove and what to leave alone.
Then check your speed on a slow connection and scan for broken links and 404 errors. Fix the links that visitors actually hit.
What should you do every quarter?
Every quarter, test a full restore on staging, check your PHP version, and review every administrator account.
The restore test is the most important quarterly job. Pick a recent backup, restore it to a staging site, and click through the home page, a post, the contact form, and the checkout. WordPress.org says it is highly recommended to check automated backups with a manual backup once in a while, as its backup guide states (checked November 2026).
A restore test is that check, done properly.
A paid backup service can cover the schedule for you. Jetpack VaultPress Backup runs a full backup at least once a day and adds real-time backups after each change, as its backup documentation explains (checked November 2026).
Check the PHP version next. WordPress.org now recommends PHP 8.3 or greater and MySQL 8.0 or greater, or MariaDB 10.11 or greater, plus HTTPS support. Older PHP versions have reached end of life and no longer receive security fixes, so an old version is a risk even when the site looks fine.
Your host panel or the Site Health Info tab shows the current version.
Then review users. Remove accounts for people who no longer work on the site, and demote anyone who does not need administrator rights. Turn on two-factor authentication for every administrator, since WordPress core does not include two-factor login and it must be added with a plugin, according to the WordPress brute-force guidance (checked November 2026).
What should you do once a year?
Once a year, renew the domain and hosting, confirm the SSL certificate renews, and update your privacy and legal pages.
A domain that expires takes the whole site offline, and recovery can take days. Check the renewal date at your registrar and turn on auto-renewal with a payment method that will still work next year. Do the same for hosting, and confirm the SSL certificate renews automatically.
A certificate that lapses shows visitors a security warning before they see your site.
Use the same visit to refresh your busiest pages. Prices, screenshots, and version numbers drift out of date, and a page that says the wrong price costs trust. Update the privacy page and any legal pages at the same time, since the tools and services you use change over a year.
For the bigger picture, the guide to writing a WordPress maintenance plan helps you turn this checklist into a written plan.
How do updates and automatic updates work?
Minor core releases install automatically by default, and since WordPress 5.5 you can turn on automatic updates for each plugin and theme.
Automatic background updates for core have existed since WordPress 3.7, and by default they cover minor releases, which are usually security and maintenance fixes. Sites installed from version 5.6 onward also get major releases automatically unless that setting is changed. You can check the setting on the Dashboard, then Updates screen.
For plugins, open Plugins, then Installed Plugins, and use the Enable auto-updates link in the Automatic Updates column, or use bulk actions for several at once. Themes work the same way, one theme at a time, from Appearance, then Themes. Turn on auto-updates for plugins from developers you trust, and review the rest by hand each week.
Auto-updates are safest with backups running, so you can roll back if an update breaks something. The guide to enabling automatic updates for plugins covers the settings in detail.
How do you check site health and security?
Open Tools, then Site Health, fix critical issues first, and keep logins locked down with strong passwords, two-factor login, and HTTPS.
Site Health is WordPress's built-in check. Its Status tab groups results into critical issues, recommended improvements, and passed tests. Its Info tab shows technical details you can copy to your clipboard, which is useful when you ask your host or a developer for help.
The guide to using Site Health in WordPress explains each screen.
Security is mostly the other jobs done on time. WordPress.org's hardening guidance puts it plainly: once a security fix is released, the details needed to exploit the old version are almost certainly in the public domain, so an out-of-date site is an easy target. Use long, unique passwords from a password manager, avoid the username admin, and require HTTPS for the admin area.
The hardening guidance also recommends directory permissions of 755 and file permissions of 644. To force admin sessions over SSL, add define( 'FORCE_SSL_ADMIN', true ); to wp-config.php, as the WordPress HTTPS guide explains (checked November 2026).
What should you record in a maintenance log?
Record the date, what you did, the versions before and after, and anything odd you noticed, even in a plain spreadsheet.
A log turns maintenance into evidence. When a site breaks, the first question is always what changed, and a log answers it in seconds. Note each backup date and where the copy went, each update with the version numbers, each restore test with the result, and each user change.
The log also shows patterns. If the same plugin breaks after every update, the log proves it and tells you to replace it. If backups fail on the same day each week, the log points at a server job that runs at that hour.
Keep the log where the whole team can see it, and review it at the quarterly check.
How do you keep the routine from slipping?
Put the weekly and monthly jobs on a calendar, automate what can run alone, and keep the list short enough to finish in one sitting.
Backups and updates can run on a schedule. Testing a form, reading a security alert, and reviewing users cannot, so those need a calendar slot. Do the weekly round at the same time each week, and treat it as fixed work, not spare work.
If you manage several sites, use the same checklist for all of them and the same log format. The routine gets faster with practice, and the sites get steadier. A site that gets an hour of care each week rarely needs a weekend of rescue work.
To set the right backup rhythm for each site, see the guide on how often to back up WordPress.
Frequently asked questions
How much time does WordPress maintenance take each week?
About an hour a week for a small site, plus a longer session each quarter for the restore test. The weekly round is a backup check, updates, and a quick test of the main pages. The quarterly restore test takes longer, but it is the job that proves your backups work.
Should I turn on automatic updates for every plugin?
Turn them on for plugins from developers you trust, and review the rest by hand each week. Auto-updates are safest with backups running, so you can roll back if an update breaks something. Check the Dashboard, then Updates screen to see your core update setting.
Does every site need the same schedule?
No. The checklist is a rhythm, not a rule. A store that takes orders daily should back up daily and test its checkout weekly. A small blog with few posts can follow the weekly and monthly pace in this guide. Adjust upward when the site changes often or earns money.
What do I do first when Site Health shows a critical issue?
Open Tools, then Site Health, and fix the critical issues first. Common ones are background updates not working, plugins waiting for updates, and an outdated PHP version. The Status tab explains each issue and how to fix it.
Should I delete unused plugins or just deactivate them?
Delete them. Deactivating leaves the files on the server, where they still need patching and can still be attacked. Keep one default theme as a fallback and remove the rest. If you might need a plugin later, you can install it again from WordPress.org.
Sources
- Backups: Advanced Administration Handbook WordPress Developer Resources
- Brute Force Attacks: Advanced Administration Handbook WordPress Developer Resources
- HTTPS: Advanced Administration Handbook WordPress Developer Resources
- Backing Up Your WordPress Site Learn WordPress
- Back Up Government Data CISA
- Back up your site with Jetpack VaultPress Backup Jetpack
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.


