---
title: Cybersecurity tips for small business websites
canonical: https://wpsecurityninja.com/cybersecurity-tips-small-business-websites/
---
Bots scan small business sites all day because weak logins and old plugins are easy to find. If you run WordPress, most of the useful work is boring: keep software current, protect credentials, and know how to restore.

![Cybersecurity for small business sites](https://wpsecurityninja.com/media/2018/12/hackers-cybersecurity.webp)

For pen testing and a longer frame, see [cybersecurity for small business](https://wpsecurityninja.com/small-business-cybersecurity/). This page is the short checklist for owners who maintain the site themselves.

## 1. Treat updates as payroll, not a hobby

- WordPress core, every plugin, and your theme on a fixed day each week.
- PHP on a branch with active or security support per [php.net](https://www.php.net/supported-versions.php).
- Delete unused plugins. Disabled plugins still execute if someone uploads a matching slug.

Security Ninja free [security tests](https://wpsecurityninja.com/security-tests/) and [vulnerability scans](https://wpsecurityninja.com/vulnerabilities/) flag stale software. You still apply the patches.

## 2. Backups you have actually restored

Keep an offsite backup and a one-page restore note: where the files live, how long the last restore took, and who is allowed to run it.

Test a restore once in a while. A backup nobody has opened is a guess.

## 3. Passwords and 2FA on every privileged role

Shared `info@` passwords and one admin account for the whole agency are how small shops lose control.

- Unique long passwords for hosting, WordPress, email, and DNS.
- 2FA (email or authenticator app) on administrators, editors, shop managers, and anyone who can install plugins. WP Security Ninja and Wordfence both support 2FA across roles.

## 4. Fewer plugins, clearer ownership

Each plugin is code that runs on every request. Ask:

- Do we still use it?
- Who gets the security email when it has a CVE?
- Is it from a vendor that ships patches?

## 5. HTTPS and sane hosting

TLS on the whole site, HSTS when your host supports it, and a plan to patch the server stack, not only WordPress.

## 6. Firewall and login limits

Rate-limit failed logins. Block known bad IPs at the edge when you can. Security Ninja Pro adds [Cloud Firewall](https://wpsecurityninja.com/cloud-firewall/) and [login protection](https://wpsecurityninja.com/login-protection/) alongside 2FA.

## 7. WooCommerce and forms

Stores and lead forms need the same basics plus abuse controls:

- Rate limits on checkout, cart, and coupons ([WooCommerce security](https://wpsecurityninja.com/woocommerce-security-guide/)).
- No DIY card forms. Use a gateway that tokenizes card data.
- Watch for card testing spikes in orders and gateway dashboards.

## 8. Monitoring you will open

Pick one weekly slot, about 15 minutes:

- Pending updates
- Failed login spikes in Events
- Search Console security issues
- Uptime or form notifications that suddenly stop

## 9. Incident card on the wall

Write half a page:

1. Who takes the site offline?
2. Where is the latest clean backup?
3. Who resets hosting, WordPress, and email passwords?
4. When do we call the host, the gateway, or outside cleanup?

Start with [signs of a hack](https://wpsecurityninja.com/signs-wordpress-site-is-hacked/) and [first steps](https://wpsecurityninja.com/what-should-you-do-if-your-wordpress-site-is-hacked/).

## 10. Honest scope

A security plugin does not hand you a compliance certificate. For most small WordPress sites, the stack is maintained software, tight access, a tested restore path, and outside help when the site is already compromised.

Publisher: Larsik Corp. Security Ninja has protected 100,000+ sites since 2011. See [pricing](https://wpsecurityninja.com/pricing/) if you want Pro firewall and malware tools on top of the free tests.
