Fast. Simple. No meetings. No delays.
Home / Blog / WordPress / WordPress Security Hardening Checklist for Business Sites

WordPress Security Hardening Checklist for Business Sites

Practical hardening steps: updates, accounts, plugins, backups, file permissions and monitoring — in priority order.

Cover graphic for the article: WordPress Security Hardening Checklist for Business Sites

A practical WordPress security checklist, in priority order: keep core, themes and plugins updated, remove what you do not use, protect every account with strong passwords and two-factor authentication, take tested off-site backups, lock down files and configuration, and monitor for changes. These steps cover the most common ways sites get compromised.

WordPress security checklist: why sites get compromised

WordPress is widely used, so attackers automate against it. They rarely target your business specifically; they scan for known weaknesses and try them on every site they find. The usual entry points are boring and preventable:

  • An outdated plugin or theme with a published vulnerability.
  • Abandoned plugins that no longer receive fixes.
  • Weak or reused passwords, especially on admin accounts.
  • Pirated or "nulled" themes and plugins carrying hidden backdoors.
  • Shared hosting accounts where one compromised site infects its neighbours.
  • Old staging copies and forgotten test installs left online.

That list is your priority guide. Core WordPress is maintained actively; most incidents involve what you added to it or how it is run.

Updates and plugin hygiene

Work through this list first, because it delivers the most protection for the least effort.

  1. Inventory everything. List every plugin and theme, what it does and who owns the decision to keep it.
  2. Delete what is inactive. A deactivated plugin still sits on disk and can still be exploited. Remove unused themes too, keeping one default as a fallback.
  3. Replace abandoned plugins. If a plugin has not been updated for a long time or has been closed by its author, plan its replacement.
  4. Source only from trusted places. Use the official directory or the vendor directly. Never install nulled premium plugins.
  5. Update on a schedule. Security fixes should be applied promptly; routine updates can be batched weekly. Test on a staging copy for sites with ecommerce or complex plugins.
  6. Keep PHP supported. Hosts retire old PHP versions; running an unsupported one means no security patches at the language level.

Fewer plugins mean a smaller attack surface. If a plugin does something a few lines of theme code could do, consider whether it earns its place.

Accounts, passwords and 2FA

  • Enable two-factor authentication for every user who can publish or administer. Authenticator apps are better than SMS.
  • Use a password manager and unique passwords, including for hosting, domain registrar, email and database accounts, not only WordPress.
  • Do not use an admin account for daily writing; give editors the Editor role and keep administrators to a minimum.
  • Remove accounts for people who have left, and review the user list quarterly.
  • Avoid an obvious username like admin, and limit login attempts or add a challenge on the login form.
  • Where possible, restrict access to the admin area by IP address or put it behind your hosting provider's protection layer.

Backups you can restore

A backup you have never restored is a hope, not a backup. Aim for these properties:

  • Both files and database, since content lives in the database and uploads live on disk.
  • Stored off the server. A backup on the same account is lost with the same incident.
  • Several generations, because malware may sit unnoticed for weeks.
  • Frequency matched to change. A brochure site can back up weekly; a store taking orders needs far more frequent database backups.
  • A restore test on a staging site at least a couple of times a year, with written steps for who does what.

File permissions and configuration

These changes are small but meaningful, and are best made by someone comfortable with hosting.

  • Use the least permissive file permissions your host allows; files and folders should not be writable by everyone.
  • Disable the built-in theme and plugin file editor in the dashboard, so a stolen login cannot edit code directly.
  • Protect wp-config.php: keep it out of public reach, use unique secret keys and salts, and use a non-default database table prefix if you set up a new site.
  • Block PHP execution in the uploads folder where your server allows it.
  • Force HTTPS across the whole site and set sensible security headers.
  • Turn off directory listing and remove leftover installers, readme files and old backups from the web root.
  • Use a unique database user with only the permissions the site needs.

Check your hosting plan too. Isolated accounts, malware scanning at server level and automatic patching of server software all reduce risk. For wider web-application practices, see our web application security checklist for business owners.

Monitoring and alerts

Hardening reduces risk but does not remove it, so you also want to notice problems quickly.

  • Uptime monitoring that alerts a real person.
  • File integrity monitoring or scheduled malware scans, through a security plugin or your host.
  • Alerts for new administrator accounts, plugin installs and failed-login spikes.
  • Search Console and email notices for security warnings or spam pages.
  • Regular log review, or at least access to logs when something looks odd.

Security plugins help with scanning, login protection and firewalls, but they are one layer. They cannot fix an abandoned plugin or a reused password. Assign ownership too: someone should be responsible for the monthly checks. A website maintenance plan is one way to make that routine.

If you are already hacked

  1. Stay calm and preserve evidence. Take a copy of the files and logs before cleaning.
  2. Contain it. Put the site in maintenance mode or take it offline if it is serving malware or spam.
  3. Change all credentials: WordPress users, hosting, database, FTP/SFTP, email and API keys, from a clean device.
  4. Find the entry point. Check for outdated plugins, unknown admin users, modified files and unfamiliar scheduled tasks.
  5. Clean or restore. Restore from a backup taken before the compromise if you have one, then update everything. Otherwise, replace core, plugin and theme files with fresh copies and inspect the uploads folder and database.
  6. Close the hole that let them in, or they will return.
  7. Request review if search engines or browsers flagged the site, and consider whether you hold personal data that may trigger notification duties. Requirements vary by country and change over time, so confirm with the official regulator or a qualified adviser.

Next step

Pick the first three items you can finish this week: remove unused plugins, switch on two-factor authentication, and prove one backup restores. If you want help auditing a site or planning ongoing care, see our packages or the overview on software development for Australian businesses.

Frequently asked questions

Are security plugins enough?

No. A security plugin adds useful scanning, login protection and a firewall, but it cannot fix an abandoned plugin, a reused password or a weak hosting setup. Treat it as one layer alongside updates, strong accounts, tested backups, sensible file permissions and monitoring, rather than as a complete solution.

How often should I update?

Apply security updates promptly, within days where possible, and batch routine updates weekly. Sites with ecommerce or complex plugins should test on a staging copy first. Also review the plugin list regularly, because an unmaintained plugin is a risk even if you keep updating everything else.

What should I do after a hack?

Preserve a copy of the files and logs, take the site offline if it is spreading malware, change every credential, and find the entry point. Restore from a clean backup or replace files with fresh copies, close the hole, and check whether any legal notification duties apply with a qualified adviser.

Related articles

🚀 Start Now