How to prevent a hack: a security checklist for small business websites
Fixing a hacked site takes hours, and cleaning up the consequences takes weeks. Prevention is much less work; it just has to be done regularly. This list sums up what to watch in 12 points, and for each one I note what you can do yourself and what is worth handing over to someone.
Ferenc KulcsárUpdated: 30 October 2026Reading time: about 5 min
The three most important
If you only have time for three things, make it these. I tell every client the same:
- Update regularly Most hacks are automated and look for known but unpatched flaws.
- Two-factor login everywhere Admin, hosting, and every connected account, such as Tag Manager.
- Licensed plugins, external backups Never a cracked theme. Backups stored away from your hosting.
The full list
1. Regular updates
Updating the WordPress core, the theme and the plugins is the most important protection. The vast majority of hacks are not targeted human attacks but the work of automated programs looking for known vulnerabilities in outdated plugins and themes. You can do this yourself, but have a fresh backup before a major update, because sometimes something breaks.
2. Backups stored independently of your hosting
If your hosting account is hacked, or the host suspends it, the backups stored on it may be out of reach too. This is how I back up my clients’ sites: the database daily (hourly for online shops) and all files weekly, to encrypted external cloud storage. I keep daily backups for 30 days and weekly full backups for 2–3 months, because an infection sometimes stays hidden for weeks. Worth leaving to an expert, at least the setup and a test restore.
3. Two-factor authentication
Turn it on for WordPress administrator accounts, your hosting, your domain manager and every connected service (for example Google Tag Manager, Shopify staff accounts). A leaked password alone is then not enough to log in. You can do this yourself.
4. Unique, strong passwords
Every service needs a different password, stored in a password manager. If your password leaks from another site, attackers automatically try it elsewhere. You can do this yourself.
5. Regular review of access
Every quarter, check who has access to the site, the hosting and the connected accounts. Revoke the access of departing employees, former developers and subcontractors immediately. In one of my cases, attackers got into an online store through the still-active account of an external marketer who had left a year earlier. You can do this yourself.
6. Licensed plugins and themes only
Never use a cracked (“nulled”) premium theme or plugin downloaded for free: they almost always contain a hidden back door. If you do not know where your theme comes from, ask whoever built the site, or have it checked. Leave the check to an expert.
7. Delete unnecessary plugins and themes
A deactivated plugin still stays on the server, and if it is vulnerable, it can still be attacked. Delete what you do not need. You can do this yourself, but back up first.
8. Firewall and hardening
A web application firewall (WAF) filters out known attack patterns, while correct file permissions and a few WordPress settings (for example disabling the file editor in the admin) make the attacker’s job harder. Worth leaving to an expert.
9. An up-to-date PHP version
The PHP version running on your hosting also has a support period. An outdated version no longer gets security fixes. Before switching, it is worth testing that every feature of the site still works. Worth leaving to an expert.
10. One site, one hosting account
If several sites run on one hosting account, one hacked site can infect the others. Important sites are worth keeping in a separate account. Discuss it with your host or developer.
11. Google Search Console
Register your site and check that notifications go to your email address. This is where Google tells you if it finds a security problem or strange pages. You can do this yourself. I wrote about the signs worth watching for in this article.
12. Uptime monitoring
An uptime monitoring service checks your site every minute and tells you when it goes down. That way you do not hear it from a customer. You can set it up yourself.
A 15-minute monthly routine
Once the above is set up, this is enough once a month:
- Check for pending updates.
- Check that the latest backup was completed.
- Go through the user list.
- Type site:yourdomain.com into Google and look for foreign results.
- Look at the Search Console notifications.
If you do not have time for this
Most of the hacked sites I repair are not damaged by bad intent but by a skipped routine: a plugin not updated for two years, backups kept on the hosting, a former developer’s access still active. My maintenance service takes care of these regularly, and I send you a short monthly summary of what happened.
If the damage is already done, start with what to do in the first 24 hours.
Frequently asked questions
Should I turn on WordPress automatic updates?
For minor security updates, yes. For major version changes and more complex sites (for example online shops), it is better if someone updates in a controlled way and then checks that everything still works.
Isn’t my host’s backup enough?
It is a good start, but if the hosting account is hacked or suspended, the backup may be out of reach too. Hosts also often keep only a few days, while an infection can stay hidden for weeks. That is why you need an independent backup kept for longer as well.
How much does prevention cost?
A fraction of what restoring a hacked site and the downtime cost. Maintenance is billed monthly; the exact fee depends on the size of the site and how often it needs to be backed up.
I run a small site. Why would anyone attack me?
Nobody is attacking you; they are attacking the vulnerable plugin. Automated programs scan everyone and hack every site where they find an open gap, regardless of size.
