Most WordPress security advice is written for developers, or for selling a plugin. This checklist is for business owners who want to know what actually matters, in what order, and what they can hand to someone else. It’s based on what we see when we clean up compromised sites: the same few gaps come up again and again.
How do I secure a WordPress site?
Keep WordPress, plugins and themes updated; use strong, unique passwords with two-factor authentication; remove anything you don’t use; keep tested off-site backups; and put a firewall in front of the site. Those five steps close the doors that most attacks on business websites walk through.
The rest of this checklist expands each step and adds the next layer for sites that handle payments or personal information.
Why do WordPress sites get hacked in the first place?
Most attacks on small-business websites are automated, not personal. Bots scan huge numbers of sites for known weaknesses (an outdated plugin with a published vulnerability, a guessable admin password) and exploit whatever they find.
That’s good news, because it means the fixes are mostly about basic hygiene rather than expensive technology. It also means “we’re too small to be a target” isn’t true: the bots don’t check your turnover.
What are the most important WordPress security steps?
Updates, access control, removing unused software, backups and a firewall. If you only do these five, you’ll have closed most of the gaps we find during clean-ups.
1. Keep WordPress, plugins and themes updated
Security fixes are delivered through updates. When a vulnerability in a popular plugin is announced, automated attacks often start soon after. Check for updates at least weekly, and apply security releases quickly. Before updating a business-critical site, take a backup and check your key pages and forms afterwards.
2. Lock down logins
- Give every person their own account. Never share one admin login.
- Use long, unique passwords stored in a password manager.
- Turn on two-factor authentication for every administrator.
- Limit repeated login attempts, through your security plugin or firewall.
- Remove accounts for staff, contractors and agencies who no longer need access.
3. Give people the lowest role they need
Someone who writes blog posts needs the Author or Editor role, not Administrator. Fewer administrators means fewer accounts that can install plugins or change code if a password leaks.
4. Remove plugins and themes you don’t use
Deactivated plugins can still be exploited if their files remain on the server. Delete anything you’re not using, including old themes (keep one default theme as a fallback). Replace plugins that haven’t been updated by their developer in a long time.
5. Keep tested backups off the server
Backups stored on the same hosting account can be deleted or infected along with the site. Keep copies off-site, keep several days or weeks of history, and occasionally test that a restore actually works. A backup you’ve never restored is a hope, not a plan.
6. Put a firewall in front of the site
A web application firewall filters malicious traffic before it reaches WordPress. The better ones apply “virtual patches” that block known plugin vulnerabilities even before you’ve updated. This can be a plugin-based firewall or a service at the DNS level.
What else should I do if my site takes payments or stores personal data?
Add monitoring, tighter hosting and a plan for incidents. WooCommerce stores and sites that collect personal information carry more risk and more responsibility.
Monitor for changes
File-change and uptime monitoring tell you quickly when something is modified or goes offline, rather than weeks later when a customer complains.
Choose hosting that isolates your site
On cheap shared hosting, a compromise of one site on the account can spread to others. Keep business-critical sites on hosting with proper isolation, current PHP versions and server-level security.
Know what you’ll do if it happens
Write down who to call, where the backups are, and who has access to the hosting and domain. If personal information could be exposed, understand your obligations under Australia’s Notifiable Data Breaches scheme before you need them.
Are security plugins enough on their own?
No. A security plugin helps with scanning, login protection and firewall rules, but it can’t stop you running outdated software, sharing passwords or keeping untested backups. Some malware even disables security plugins once it’s inside.
Think of a plugin as one layer. The checklist above is the rest.
How often should I review WordPress security?
Check updates weekly, review users and plugins quarterly, and do a fuller review once a year or whenever staff, agencies or hosting change. Security isn’t a one-off job. Plugins get abandoned, people leave and new vulnerabilities are published every week.
If that’s more than you want to manage, our WordPress security and hardening service does a one-off review, and our care plans handle the ongoing work, including a hack-cleanup guarantee on Business and Commerce plans.
Frequently asked questions
Yes, when it’s maintained. WordPress core is actively supported and receives regular security releases. Most compromises come from outdated plugins, weak passwords and unmaintained sites, not from WordPress itself.
Several reputable plugins do the job well. What matters more is that it’s configured properly, kept updated, and combined with updates, strong logins and off-site backups.
For administrators, yes. Two-factor authentication stops most attacks that rely on stolen or guessed passwords, and it takes a few minutes to set up.
Check that updates are current, backups restore successfully, only the right people have admin access, and monitoring alerts actually reach someone. A periodic external review can confirm nothing has been missed.
Want a second set of eyes on your site’s security? Ask Dr Web for a security review, or run the free Hack Checker first.
