Company WordPress Sites: A Monthly Security Checklist

By · 8 November 2026 · 4 min read

Illustration of a monthly calendar and a WordPress security checklist with items ticked off

Many company websites are built on WordPress. After launch they are often left alone: nobody logs in for months, update notices pile up and the accounts of staff who have left are still active. Everything looks normal, until one day the home page changes or Google shows a warning.

The good news is that WordPress security upkeep doesn't have to be complicated. With one person responsible and a clear schedule, most of the work fits into a single session each month. This article gives you a checklist you can use yourself, or ask your website provider to follow.

Why check every month?

WordPress already does part of the work itself. Since version 3.7, minor core updates, including security releases, install automatically by default. Since version 5.5, plugins and themes can also be set to update automatically.

But automatic doesn't mean done. Automatic updates can fail, can be switched off by the host or by another plugin, and they don't deal with things like user accounts or backups. WordPress's own documentation points out that plugins have deep access to your site, which is why keeping them updated matters. A monthly check makes sure the automatic parts are really working, and that the rest gets done.

1. WordPress, plugin and theme updates

  • Open Dashboard > Updates. Make sure WordPress, plugins, themes and translations are all on the latest version.
  • On the Plugins screen, check the automatic updates column. Turn it on for plugins you trust, and note which ones you deliberately update by hand.
  • Check the notification emails from WordPress. By default, WordPress emails you when automatic plugin or theme updates succeed or fail. A "failed" email needs following up.
  • Make sure there is a recent backup before any major update. The WordPress documentation recommends backing up before updating, so you can roll back if something breaks.

2. Clear out unused plugins and themes

WordPress's security guide is clear on this: if you are not using a plugin, delete it from the system. A deactivated plugin is still on the server, and still needs looking after.

  • Delete plugins that are deactivated and won't be used again.
  • Delete inactive themes. If in doubt, keep one default WordPress theme as a fallback.
  • Check whether your active plugins are still being developed. A plugin its author hasn't updated in a long time is worth replacing.
  • Make sure every plugin and theme comes from an official source. The WordPress guide says not to get plugins or themes from untrusted sources. We go into this in our article on pirated plugins and themes.

3. Review users and access rights

Open the Users screen and read the list one by one. The question is simple: does everyone on this list still work with you, and does their role match their job?

  • Deactivate or delete the accounts of former employees and former vendors.
  • Limit the Administrator role. According to the WordPress documentation, an Administrator has access to every admin feature. Someone who writes articles only needs the Author or Editor role.
  • Make sure everyone has their own account, not one admin account shared between several people.
  • Make sure two-step verification is on for every admin account. WordPress's security guide recommends enabling it. We explain how in our article on two-step verification for website admins.
  • Under Settings > General, check whether "anyone can register" really needs to be on. For a company profile website, it usually doesn't.

4. Check Site Health and the logs

WordPress has a built-in diagnostic tool under Tools > Site Health. It flags critical issues that can become security weaknesses, for example:

  • the server's PHP version is outdated and needs updating;
  • debug mode is showing error messages to visitors, even though they can contain sensitive information;
  • background updates are not running;
  • there are plugins waiting to be updated.

Fix everything in the critical category. If it needs server access, ask your host or website provider for help. Then look at the security or login logs if you have them. The WordPress guide calls logs your best friend for understanding what is happening on your site, because prevention alone is sometimes not enough.

One setting only needs to be applied once but is worth rechecking: switch off the file editor in the dashboard with the DISALLOW_FILE_EDIT setting. The WordPress guide says this editor is often the first tool an attacker uses after managing to log in.

5. Make sure backups run and can be restored

WordPress's security guide recommends backing up your data regularly, including the database. Each month, check three things: the latest backup really exists and is recent, a copy is stored away from the website's server, and every so often you try restoring it to a test environment. The full guide is in our article on the 3-2-1 backup rule.

Monthly checklist summary

  1. WordPress, plugins, themes and translations are on the latest version.
  2. Failed update emails have been followed up.
  3. Unused plugins and themes have been deleted.
  4. Every plugin and theme comes from an official source and is still maintained.
  5. The user list has been reviewed and old accounts deactivated.
  6. Every admin uses two-step verification.
  7. Site Health shows no critical issues.
  8. A recent backup exists, is stored off the server and has been tested.

WordPress security isn't about one magic plugin. What matters is that someone checks, every month, with the same list.

No time or team to do this every month? Every one of our website packages includes hosting and maintenance, so updates and server security are our responsibility once the site is live.