A WordPress maintenance checklist for site owners
A WordPress site doesn’t usually fail in one dramatic moment. It drifts.
A plugin stops getting updates. A backup job quietly fails and nobody notices for months. An editor uploads a 6 MB photo. Someone leaves the team and still has an admin account. The contact form stops sending emails. None of it is urgent on the day it happens, which is exactly why it builds up.
I learned most of what’s on this list from looking after a busy WordPress site with lots of people publishing to it. The pattern was always the same: the problems that hurt were the ones nobody had been asked to check. So here’s the list, split by how often each job needs doing. Most of it takes minutes.
Key takeaways
- Backups you’ve never restored are a hope, not a backup.
- Update often, in small steps, and test after.
- Remove what you don’t use: plugins, themes, users.
- Keep an eye on Search Console so you hear about problems before your visitors do.
- Write down what you checked. A checklist only works if someone owns it.
Weekly (15 minutes)
Check the site works
Open the homepage, a key page and a recent post on your phone. Click the menu. Submit the contact form and make sure the email arrives. If you run a shop, add something to the basket.
It sounds too simple to bother with. It’s also how you find out the form has been broken for a fortnight.
Apply updates
WordPress core, plugins and themes all need updating. Minor core releases (security and bug fixes) usually install automatically. Plugins and themes need your attention, unless you’ve switched on auto-updates for ones you trust.
A sensible routine:
- Check a backup exists from today.
- Update plugins one or a few at a time, not all forty at once.
- Check the site after each batch.
- If something breaks, you know which update did it.
For bigger releases (a major WordPress version, a page builder, WooCommerce), wait a few days, read the changelog, and test on a staging copy if your host offers one.
Look at Search Console
A quick look at the Overview page: any new errors under indexing, any sudden change in clicks, any security or manual action messages? You don’t need to analyse anything weekly. You just need to notice. If something does look wrong, there’s a calm routine in after a traffic drop.
Monthly (an hour)
Test a backup restore
Backups fail silently. The plugin says “completed”, the file is empty, or it’s stored on the same server that just went down.
Once a month, check that:
- backups are running on schedule (daily for busy sites, weekly for quiet ones)
- they include both the files and the database
- at least one copy is stored off the server: cloud storage, not just your host
- you can actually restore one. Restore to a staging site or a local copy. Do it once and you’ll know how long it takes when it matters.
Review plugins
Go through the plugin list:
- Anything deactivated? Delete it. Deactivated plugins can still be a security risk.
- Anything not updated in a year or more? Check whether it’s abandoned, and look for an alternative.
- Anything doing the same job as another plugin? Pick one.
I wrote a fuller version of this in auditing your WordPress plugins.
Check speed
Run the homepage and one typical post through PageSpeed Insights and compare with last month. A sudden drop usually means a new plugin, a big image, or a new embed. Core Web Vitals (LCP, FID and CLS) also have their own report in Search Console, which shows trends across the whole site.
Fix broken links
Run a crawl or a link checker and fix the broken internal links you find. Outbound links to sites that have gone are worth fixing too. There’s a process in how to find and fix broken links.
Check comments and forms for spam
Spam comments sitting in the moderation queue, or worse, approved, make a site look abandoned and can add junk links. Check your anti-spam plugin is working.
Quarterly (half a day)
Users and access
Go to Users and check every account:
- Does everyone listed still need access?
- Does anyone have a higher role than they need? Most editors don’t need to be administrators.
- Is two-factor authentication switched on for admins?
When people leave, accounts tend to stay. This is one of the simplest security wins there is. (More in WordPress security basics.)
Themes
Delete themes you’re not using, except one default theme as a fallback. Make sure your active theme is still maintained, and that any changes you’ve made live in a child theme, so an update doesn’t wipe them.
PHP version and hosting
Check Tools → Site Health. It will tell you if your PHP version is out of date, if background updates are failing, or if something else needs attention. Old PHP versions are slower and stop getting security fixes. Your host can usually switch versions from the control panel; test the site afterwards.
While you’re there, check your SSL certificate renews automatically and your domain isn’t about to expire.
Content
- Are there old posts with outdated facts, or pages for things you no longer offer?
- Are there thin pages that should be improved, merged or removed? (Content pruning covers how to decide.)
- Does the XML sitemap still only include the pages you want indexed?
Database
Over time, the database fills with post revisions, spam comments and leftover data from removed plugins. A clean-up (with a backup first) can make the admin a bit snappier. Don’t go mad with it: you don’t need to do this weekly.
Write it down
Keep a simple log: date, what was checked, what was changed, anything that needs follow-up. A shared document is fine.
This matters most when more than one person looks after the site. Without it, everyone assumes someone else did the backup check. With it, you can see at a glance that the last restore test was in June, and do something about it.
A printable version
| How often | Job |
|---|---|
| Weekly | Site works on mobile, forms send, updates applied, Search Console glance |
| Monthly | Backup restore test, plugin review, speed check, broken links, spam check |
| Quarterly | Users and roles, unused themes, PHP and Site Health, SSL and domain, content review, database clean-up |
Related reading
- Auditing your WordPress plugins before they slow you down
- WordPress security basics every site owner should know
When did you last restore a backup, not just make one? If you can’t remember, that’s this month’s first job.