Skip to content
Blog Security

The WordPress Maintenance Checklist We Use for Every Client Site

The first WordPress site you look after is easy. You remember to update it, you know where the backups are, and you notice when something looks off. By the tenth site, that memory stops working. By the thirtieth, you find out a contact form has been broken for three weeks because a client mentions, a little too calmly, that “it’s been quiet lately.” This is the WordPress maintenance checklist we ended up with after making most of those mistakes ourselves. It is split by how often each job needs doing — weekly, monthly and quarterly — and for each one we say whether it should be automated or still needs a human. Copy it, change it, make it yours.

Why a checklist beats “I’ll keep an eye on it”

WordPress itself is rarely the problem. The plugins around it are. According to Patchstack’s State of WordPress Security in 2026, 11,334 new vulnerabilities were found in the WordPress ecosystem in 2025. 91% of them were in plugins, 9% in themes, and only a handful in WordPress core. For the most heavily targeted ones, the typical time from public disclosure to the first attack was about five hours. Five hours is shorter than most people’s working day. “I’ll update everything on Friday” is not a plan any more. A checklist turns maintenance from something you remember into something that simply happens — and makes it obvious which parts should run on their own.

Every day (let the machines do this)

Nobody should be checking these by hand. They need to run in the background and only get your attention when something is wrong.
  • Uptime checks. Every few minutes, from outside the site. You want an alert when the site goes down and when it comes back, so you know how long it was out.
  • Automatic backups. At least daily for sites that change often (shops, blogs with comments, membership sites). Keep several generations — for example 7 daily, 4 weekly and 3 monthly copies — so a problem you notice late can still be undone.
  • Security alerts. Failed login spikes, a new administrator account nobody created, changed core files, a plugin with a known vulnerability. These should reach you where you actually look: e-mail, Slack or Telegram.

Every week

1. Update plugins and themes — safely

This is the job that matters most and the one people put off because they are afraid of breaking something. That fear is fair: updates do break sites sometimes. The answer is not to update less, it is to update in a way you can undo.
  • Take a backup (or check that last night’s finished) before you start.
  • Update one plugin at a time, not twenty in one click, so you know which one caused a problem.
  • After each update, load the home page, a key inner page and the login page. Look for errors, not just a white screen.
  • If something breaks, roll back that one plugin and wait a few days for a fix.
Doing this by hand across many sites eats an afternoon a week. This is exactly the kind of job worth automating: updates that run at night, one by one, check the site after each one and roll back on their own when something goes wrong.

2. Look at the alerts you ignored

Every week, spend ten minutes on the warnings you swiped away: the PHP warning that keeps coming back, the SSL certificate that expires in 20 days, the broken image a page has been showing since a media library clean-up. Small things left alone tend to turn into the urgent call on a Monday morning.

3. Check that forms and e-mail still work

This is the quiet failure that costs clients the most. A contact form can look perfect and still send nothing, because an SMTP password changed or the hosting company started blocking mail. Send a test entry through the main form, or better, get alerted when a form that usually receives messages suddenly goes silent for a few days.

Every month

4. Test a restore, not just a backup

A backup you have never restored is a hope, not a plan. Once a month, pick one site and restore its latest backup to a staging copy, or at least download it and check that the database and the files are really there and the size makes sense. If your backups only live on the same server as the site, move a copy somewhere else — S3, Dropbox or an FTP server you control.

5. Check speed and Core Web Vitals

Run PageSpeed on the home page and your most visited page, on mobile. You are not chasing a perfect 100; you are looking for change. A score that drops from 85 to 60 in a month usually means a new plugin, an uncompressed hero image or a third-party script someone added.

6. Clean up users, plugins and the database

  • Remove user accounts that are no longer needed — especially old administrator accounts from freelancers or past staff.
  • Delete plugins and themes that are deactivated. Deactivated code can still be attacked.
  • Clear spam comments, old post revisions and expired transients. Most sites do not need hundreds of revisions per page.

7. Look for broken links and SEO accidents

Broken internal links and missing images slowly hurt both visitors and rankings. Worse is the SEO accident: the “Discourage search engines” box left ticked after a redesign, or a page that got a noindex tag by mistake. Both are easy to fix and painful to discover months later in Search Console.

8. Send the client a report

If you do maintenance well, clients don’t see it — which makes it easy for them to wonder what they are paying for. A short monthly report fixes that: updates made, backups taken, threats blocked, uptime and speed, and, if you have it, search and traffic numbers. Keep it to a page or two. Nobody reads a 30-page PDF.

Every quarter

  1. Check PHP and WordPress versions. Old PHP versions stop getting security fixes. Plan the upgrade with the host before it becomes urgent, and test the site on the new version first.
  2. Review who has access. Hosting panel, domain registrar, DNS, Cloudflare, Google accounts, the WordPress admin. People leave; their access often doesn’t.
  3. Check domain and SSL renewal dates. An expired domain takes the website and the e-mail down. Make sure auto-renew is on and the card on file still works.
  4. Run a privacy check. Is there a privacy policy link? Does the cookie banner actually block tracking until the visitor agrees? Do forms have a consent checkbox? Laws like the GDPR in Europe and KVKK in Turkey expect these basics.
  5. Review the plugin list. For each plugin, ask: do we still need it, is it still maintained, and has it had an update in the last year? Replacing one abandoned plugin is easier than cleaning up after it.

The checklist at a glance

How often Task Automate?
Every few minutes Uptime check Yes
Daily Backups, security alerts Yes
Weekly Plugin, theme and core updates Yes, with rollback
Weekly Review alerts, test forms and e-mail Alerts yes, review by hand
Monthly Test a restore By hand
Monthly Speed, broken links, SEO accidents Checks yes, decisions by hand
Monthly Users, plugins and database clean-up Partly
Monthly Client report Yes
Quarterly PHP version, access review, renewals, privacy, plugin review By hand

How we run this across many sites

You can do all of this with a spreadsheet, a calendar reminder and a lot of discipline. We did, for a while. What finally worked was putting every site in one dashboard so the checklist runs itself and only the exceptions reach us. That is why we built Guard Core WP. It checks uptime every 5 minutes, takes backups on a schedule and keeps several generations, updates plugins one by one at night and rolls back by itself when a site breaks, watches for hacks, PHP errors and broken links, and sends client reports with the sections you choose. The quarterly jobs still need a person — but they take an hour instead of a week. If you look after more than a handful of WordPress sites, try it free for 14 days. No card needed.

Frequently asked questions

How often should a WordPress site be maintained?

Uptime, backups and security monitoring should run all the time. Updates are best done weekly, and some security fixes should be applied the same day. Restores, speed and clean-up are monthly jobs; access, PHP versions and plugin reviews can be quarterly.

Is it safe to turn on automatic updates in WordPress?

It is safer than not updating, as long as you can undo a bad update. Have a recent backup, update one plugin at a time, check the site afterwards and roll back automatically if it breaks. That is what turns automatic updates from a gamble into a routine.

What is the most common reason WordPress sites get hacked?

Out-of-date plugins. Most WordPress vulnerabilities are found in plugins, not in WordPress itself, and the dangerous ones are attacked within hours of becoming public. Keeping plugins updated, removing unused ones and using strong, unique passwords with two-factor login prevent most attacks.

How long does WordPress maintenance take per site?

Done by hand, expect one to two hours per site per month, more for shops. With monitoring, backups, updates and reports automated, most months need only a few minutes per site — you spend your time on the sites that actually have a problem.