Lizzard Solutions

WordPress Security Checklist: 15 Steps for Small Business

· Lizzard Solutions
WordPressWebsite SecurityCybersecuritySmall BusinessChecklist

By Nemanja Vukmirović, Lizzard Solutions. Last updated 16 November 2026.

Most hacked small business websites are not targeted by anyone in particular. Automated bots scan the internet for old plugins, weak passwords and forgotten admin accounts, and a WordPress site with any of those gets found sooner or later.

This WordPress security checklist gives you 15 concrete steps, grouped by priority, that an owner or office manager can follow without being a developer. You also get a plugin audit table to copy, a monthly routine and a short plan for what to do if the site is already compromised.

TL;DR

  • Most WordPress break-ins start with outdated plugins or themes, weak or reused passwords, and too many administrator accounts.
  • Fix those three first: update everything, turn on multi-factor login, and cut admins down to the people who really need it.
  • Keep off-site backups you have actually restored once, and review plugins every month.

What is WordPress security?

WordPress security is the set of settings, habits and tools that keep a WordPress website, its admin area and its data safe from unauthorised access, malware and data loss. In practice it means keeping WordPress core, plugins and themes updated, protecting logins, limiting user permissions, hosting the site securely and keeping tested backups.

WordPress core is maintained by a large team and patched quickly. The weak spots are usually what gets added around it: extensions, accounts and hosting. The official WordPress hardening guide says the same thing in more technical detail.

Action for today: open your dashboard and note how many plugins, themes and administrator users you have.


Why are small business WordPress sites attacked?

Attackers rarely care what your business sells. They want your server for spam, your visitors for redirects to scam pages, or your customer data. Small sites are attractive because they often have no one watching them.

  • Outdated plugins and themes with publicly known vulnerabilities.
  • Weak or reused passwords, tried automatically against the login page.
  • Too many admin accounts, including those of former staff and old agencies.
  • Nulled (pirated) premium plugins, which often contain hidden malware.
  • Cheap hosting with old PHP versions and no isolation between sites.

These map closely to the broken access control and vulnerable components risks in the OWASP Top 10, the standard list of web application risks.


The WordPress security checklist: 15 steps by priority

Work from top to bottom. The first five steps close most of the common entry points. You can copy this table into a document and tick off each row.

#StepPriorityHow often
1Update WordPress core, all plugins and themesCriticalWeekly or automatic
2Delete unused plugins and themes (not just deactivate)CriticalMonthly
3Turn on multi-factor authentication for every adminCriticalOnce, then for each new user
4Use unique, long passwords stored in a password managerCriticalOnce, then on staff changes
5Keep off-site, automatic backups and test a restoreCriticalDaily backup, quarterly test
6Reduce administrators; give others Editor or Author rolesHighQuarterly review
7Remove accounts of former staff and agenciesHighOn every departure
8Install plugins only from wordpress.org or the real vendorHighEvery new plugin
9Enforce HTTPS and set security headersHighOnce, check yearly
10Use a supported PHP version on your hostingHighCheck every 6 months
11Limit login attempts or add a web application firewallMediumOnce
12Disable file editing in the dashboardMediumOnce
13Use SFTP and separate database credentialsMediumOnce
14Monitor uptime and file changesMediumContinuous
15Write down who to call and what to do if hackedMediumOnce, review yearly

Key takeaway

If you only have one hour, do steps 1 to 4. They cost nothing and remove the reasons most small sites get compromised.


Steps 1 to 5: updates, logins and backups

1. Keep everything updated

Since WordPress 5.5 you can switch on automatic updates for each plugin and theme from the Plugins screen, as described in the WordPress auto-updates documentation. Turn it on for well-maintained plugins. For a shop or booking plugin, update on a fixed day and test the checkout or booking form afterwards.

2. Delete what you do not use

A deactivated plugin is still on the server and can still be exploited. Delete plugins and themes you do not use, and keep one default theme as a fallback. Fewer extensions also mean a faster site.

3 and 4. Protect every login

Multi-factor authentication stops most password attacks even when a password leaks. Our multi-factor authentication guide explains which method to choose. Pair it with a team password manager so nobody reuses the same password for the site, email and banking.

5. Backups you have restored at least once

Store backups outside your hosting account, so a hacked or cancelled server does not take them with it. A backup you have never restored is a guess. Follow the 3-2-1 backup approach and restore to a test copy every quarter.


Steps 6 to 10: users, plugins and hosting

WordPress has built-in roles: Administrator, Editor, Author, Contributor and Subscriber, explained in the WordPress roles and capabilities guide. Most staff who write news or update pages need Editor, not Administrator.

  • Give Administrator only to the owner and the person or agency that maintains the site.
  • Delete or downgrade accounts the same day someone leaves. Our user access review template makes this a quarterly habit.
  • Never install nulled premium plugins. Buy from the real vendor or pick a free alternative.
  • Before installing a plugin, check when it was last updated and whether it supports your WordPress version.
  • Ask your host which PHP version the site runs on and whether it is still supported. Our guide to web hosting for small business lists what to ask.

HTTPS and security headers protect visitors in the browser. The website security headers checklist shows which six headers to set and how to test them.


Steps 11 to 15: hardening and monitoring

These steps need a developer or a capable host, but each one is done once.

  • Limit login attempts or put the site behind a web application firewall, so bots cannot guess passwords endlessly.
  • Disable the built-in file editor by adding define( 'DISALLOW_FILE_EDIT', true ); to wp-config.php. An attacker who gets into the dashboard then cannot edit theme code from the browser.
  • Use SFTP, not plain FTP, and give the database user only the permissions WordPress needs.
  • Monitor the site for downtime and unexpected file changes. Our website uptime monitoring guide covers free tools.
  • Write a one-page incident plan: who has hosting access, where backups are, and who informs customers.

Watch out

Security plugins help, but they are not a substitute for updates, MFA and backups. Two overlapping security plugins can also slow the site or block each other.


Worked example: a plugin audit table

This is example data for a fictional dental clinic website, not a real client. Copy the columns and fill them in for your own site once a month.

PluginStill needed?Last vendor updateAuto-updateDecision
Contact form pluginYes, main lead source2 weeks agoOnKeep, test form after updates
Old slider pluginNo, homepage redesigned3 years agoOffDelete
Booking plugin (premium)Yes1 month agoOffKeep, update manually on Tuesdays
Second SEO pluginNo, duplicates the first6 months agoOnDelete
Backup pluginYes3 weeks agoOnKeep, test a restore this quarter

In this example, two of five plugins go, which removes two possible entry points in ten minutes. The same review belongs in your website maintenance checklist.


What to do if your WordPress site is hacked

  1. Take a copy of the current site and logs before changing anything, so you can see what happened.
  2. Change all passwords: WordPress admins, hosting panel, SFTP, database and the email tied to the admin account.
  3. Restore a clean backup from before the infection, then update everything immediately.
  4. Scan for leftover admin users, unknown plugins and modified files.
  5. If customer personal data may have been exposed, check your legal notification duties with a lawyer. Our incident response plan template helps you organise the steps.

If you are not sure the site is clean, a professional review is cheaper than a second infection. For the wider picture beyond the website, read our cybersecurity guide for small business.


Frequently asked questions

Is WordPress secure enough for a business website?

Yes, when it is maintained. WordPress core is actively patched, and most problems come from outdated plugins, weak passwords and poor hosting. If nobody will update and monitor the site, a simpler platform may be safer. Our comparison of WordPress vs Webflow vs custom builds helps you decide.

Do I need a security plugin?

A good security plugin or a firewall from your host adds login protection, malware scanning and alerts. It helps, but it does not replace updates, multi-factor login and tested backups. Use one well-maintained security tool, not several that overlap.

How often should I update WordPress plugins?

Check for updates at least weekly, and turn on automatic updates for well-maintained plugins. Critical security releases should be applied as soon as possible. For plugins that run payments or bookings, update on a set day and test those features right after.

Does changing the login URL make WordPress secure?

Hiding the login page reduces automated noise, but it is not real protection. Attackers can still find other ways in through outdated plugins. Treat it as a minor extra after multi-factor authentication, strong passwords and limited login attempts.

Want to know how secure your website is?

Run our free website security check to see HTTPS, headers and common weak spots, or ask us to audit and harden your WordPress site.

Check my website security