The WordPress Maintenance Checklist For A Small Business
Most small-business WordPress sites are maintained the same way: nobody touches anything until something breaks. The site went live, the person who built it moved on, and two years later there are 23 plugin updates waiting, the host is about to retire the PHP version, and the only backup anyone can find is the one the developer took on launch day.
That isn’t neglect so much as fear. An update broke the site once, and now nobody dares press the button.
A WordPress maintenance checklist fixes that by turning a vague worry into a short list of jobs with a day of the week beside each one. Some take five minutes. Some a good host does for you overnight. None of them need a developer.
This post is the list we use on client sites: what belongs on it, how often each job runs, how to update without breaking anything, and what a monthly maintenance hour actually looks like. It applies on any host, including the one you’re on now. Where a managed platform changes the answer, we say so, and we say where it doesn’t.
Key Takeaways
- Maintenance is six jobs: backups, updates, security, performance, content housekeeping and monitoring.
- Weekly is updates, the scan report and spam. Monthly is accounts, unused plugins and a speed check. Quarterly is PHP, forms and a restore test.
- Never update the live site first. Clone to staging, update there, click through, then push.
- A backup you have never restored is a hope, not a plan.
- A managed host takes the nightly jobs off the list. The judgement calls stay with you.
What Belongs On A WordPress Maintenance Checklist?
Six jobs. Every item on the forty-point lists you’ll find elsewhere is a sub-item of one of these.
- Backups. A nightly copy of the files and the database, kept at least 30 days, that you can restore yourself without a ticket.
- Updates. WordPress, the plugins and the theme, on a schedule, on a copy of the site first.
- Security. A malware scan that runs without you, no shared admin accounts, no plugins installed “just to try”.
- Performance. A page cache that is actually on, images sized before upload, and a check that the site isn’t slower than last month.
- Content housekeeping. Spam, broken links, old drafts, and the 2024 price list still on the Services page.
- Monitoring. Something that tells you the site is down before a customer does.
The first three are where sites get hurt. The last three are where they quietly get worse. If the whole list feels like too much, start with the first three.
That settles what is on it. The part most owners get wrong is how often.
How Often Should Each Job Run?
Weekly for the things that go wrong quickly, monthly for the things that drift, quarterly for the things that only matter when they matter.
| Job | Weekly | Monthly | Quarterly |
|---|---|---|---|
| Confirm last night’s backup is in the list | Yes | ||
| Apply plugin and theme updates, on staging first | Yes | ||
| Read the malware scan report | Yes | ||
| Clear spam comments and form entries | Yes | ||
| Review user accounts and remove anyone who has left | Yes | ||
| Delete inactive plugins and themes | Yes | ||
| Check page speed and fix stale content | Yes | ||
| Review the PHP version | Yes | ||
| Submit every form and complete one purchase | Yes | ||
| Restore a backup and click through the result | Yes | ||
| Check the domain and SSL renewal dates | Yes |
Two things are missing from the table on purpose. The backup itself and the malware scan should run every night without you, and if you’re doing either by hand, that’s the first thing to fix, not something to schedule. On a shared cPanel host a nightly backup is often a paid add-on and the scan is a plugin you install. On Oxyforge both run every night, and the scan reports what it finds rather than deleting anything; see how malware scans work.
The weekly column is where the time goes, and it’s almost all one job.
How Do You Update WordPress Without Breaking The Site?

Update a copy of the site, not the site.
Clone To Staging First
A staging site is a private copy of your live site at its own address. You update the copy, click through the pages that earn money, and only then push the result live. If the update breaks something, you’ve lost ten minutes and nobody saw it.
WP Engine, Kinsta and SiteGround all include staging on their managed plans. On a cPanel host, Softaculous can usually make a copy, and the WP Staging plugin works almost anywhere. On Oxyforge it’s on every plan: clone, update, push, with a backup of production taken automatically before the push. The steps are in staging sites.
The order on any host: WordPress first, then the theme, then the plugins a few at a time, reloading the form or checkout page after each batch, then push. If something broke, throw the staging copy away and go again without the plugin that broke it.
What About Automatic Updates?
WordPress applies its own minor security releases automatically by default, and you can switch on auto-updates for each plugin from the Plugins screen. The WordPress.org guide to updating covers both.
The question is which plugins to trust with it. In our experience, the boring ones. SEO plugins, form plugins and anything that has never once broken a site can update itself. Page builders, WooCommerce and anything that touches payment get updated by hand, on staging, because a page builder update at 3am that breaks the layout is still broken at 9am when the first customer arrives.
On Oxyforge, automatic updates for WordPress and plugins are off until you turn them on, and take a backup before each run, so a bad update is a restore rather than a rebuild.
Clear The Cache After
After any update, clear the page cache. A theme update served with last week’s cached CSS looks exactly like a broken site, and you’ll spend twenty minutes diagnosing a problem one button fixes. On a managed host it’s usually one click; clear the cache shows where that button is on ours.
The short version: staging for the risky updates, auto-updates for the safe ones, and the cache cleared after both.
What Does A Monthly Maintenance Hour Look Like?
Say you run a physiotherapy clinic. The site has a booking plugin, a contact form, a page builder and about a dozen plugins in total. First Monday of the month, 9am, coffee in hand.
- Backups, two minutes. Open the host’s backup list and confirm last night’s entry is there. You’re checking the job ran, not restoring anything.
- Clone to staging, five minutes. Read the scan report while it runs. Clean this month.
- Update on staging, fifteen minutes. WordPress, then the theme, then the plugins three or four at a time. After each batch, reload the booking page.
- Click through, ten minutes. Make a test booking. Submit the contact form. Open the site on your phone.
- Push to live, five minutes. Push, clear the cache, open the booking page in a private window and check it again.
- Accounts, five minutes. Three admin users. One belongs to the receptionist who left in July. Delete it and reassign her posts to yourself.
- Plugins, five minutes. Two inactive plugins somebody tried once. Delete them. An inactive plugin is still code on your server that nobody is updating.
- The stale page, ten minutes. The Services page still says “from $80”. It’s been $95 since March. Fix it.
About an hour, most of it waiting. Do this twelve times a year and the 23-updates-waiting situation never happens again.
Which Jobs Should Your Host Be Doing For You?
The nightly ones, and anything that needs a server rather than a person. If you’re paying for managed hosting and still doing these by hand, you’re paying for the wrong thing.
- The backup, every night, kept long enough to catch a problem you notice late, with a restore you run yourself.
- The malware scan, every night, with a report you can read.
- The page cache, on by default and cleared when you publish.
- PHP, kept on a supported version, with a switch you control.
- The SSL certificate, renewed without you noticing.
What no host can do is the judgement calls. Nobody else knows which plugin matters most, whose account should go, or that the Services page is out of date. Those stay on your list whoever hosts the site.
Two honest limits on our side. Oxyforge puts Cloudflare in front of every site on Cloudflare’s free plan, which absorbs attacks and caches pages at the edge but does not include a web application firewall; WP Engine and Kinsta both include one, and if your site has been attacked before, that’s a fair reason to pick them. And we don’t move sites for people. Migration is self-service, with SFTP, WP-CLI and a database manager on every plan to do it with.
If you’d rather work from a terminal, WP-CLI shortens the monthly hour: wp plugin list --update=available shows what’s waiting and wp core verify-checksums tells you whether WordPress’s own files have been tampered with.
What To Do Next
- Write the six jobs on one page, with a day of the month beside each. Backups, updates, security, performance, content, monitoring. That’s the whole checklist.
- Ask your host three questions. Is there a nightly backup, how long is it kept, and can I restore it myself? How backups work shows what the answers look like when they’re good.
- Do the first monthly hour this week, on a staging copy. If you don’t have one, that’s step four.
- If step 2 came back as a shrug, compare the plans on the pricing page. Nightly backups kept 30 days, staging, scans and a restore you run yourself are on every one of them, and a free account gets a 24-hour temporary site to try it on, no card needed.
Frequently Asked Questions
How often should a WordPress site be maintained?
Weekly for updates, the scan report and spam, monthly for user accounts, unused plugins and a speed check, and quarterly for PHP, forms and a restore test. The nightly jobs, backups and malware scans, should be running on their own. If you are doing them by hand, that is the first thing to change.
Should I turn on automatic updates for WordPress plugins?
For some plugins, yes. Turn them on for the ones that have never broken anything, such as SEO and form plugins, and leave them off for page builders, WooCommerce and anything that touches payment. Those get updated by hand on a staging copy, where a problem costs you ten minutes instead of a morning of lost orders.
Do I still need a maintenance checklist on managed hosting?
Yes, a shorter one. A managed host takes the nightly jobs off the list: backups, malware scans, the page cache, PHP and SSL. What it cannot do is the judgement calls, such as which plugin to update first, whose account to delete, or whether the price list on the Services page is still right. Those stay with you.
What happens if I never update WordPress?
Nothing, for a while, which is why so many sites go unmaintained. Then a plugin with a known hole gets used to get in, or the host retires an old PHP version and the theme stops working. By that point there are dozens of updates waiting and applying them all at once is far more likely to break something than applying three a week would have been.