Website security checklist for small businesses
A non-technical website security checklist for small businesses: what to set up once, what to check monthly, and what to plan before anything goes wrong.
Published · updated
// short answer
Set up two-factor authentication, automatic updates, tested off-site backups, HTTPS with HSTS, security headers, and SPF plus DMARC once. Then each month update software, run a passive check and confirm a backup restores.
You don't need a security team to look after a small business website. You need a short list of sensible habits, done regularly, and someone to ask when something looks odd.
This checklist is that list. It's split into things to do once, things to do every month, and things to know before you need them. Work through it over a few weeks rather than all at once. Every item you tick off makes your site a less attractive target.
Do once: the foundations
Know who has the keys
Make a short, private list of every account that controls your website:
- your domain registrar (where you bought the domain);
- your DNS provider (often the same as the registrar, sometimes your host or a CDN);
- your hosting account;
- your website admin (WordPress, Shopify, Wix or similar);
- your business email.
For each one, note who has access. If a former developer or agency still has a login, remove it or change the password. If the domain is registered in someone else's name, get it moved into the business's name. Losing control of your domain is far more disruptive than most website problems.
Turn on two-factor authentication
Two-factor authentication means a password alone isn't enough to log in. Turn it on for every account on the list above, starting with your domain registrar, hosting and email. An authenticator app is better than text messages where you have the choice.
Use a password manager
Every account should have a long, unique password. Nobody can remember dozens of those, which is why password managers exist. Share access through the manager rather than by email or chat.
Make sure HTTPS works everywhere
Your site should load with https:// and a padlock, and the http:// version should redirect there automatically. Your SSL certificate should renew automatically. Once that's solid, ask your developer to add HSTS so browsers always use the encrypted connection.
Protect your email domain
Set up SPF, DKIM and DMARC for your domain. Together they make it much harder for scammers to send email that looks like it's from you. Start DMARC at p=none to watch, then tighten it. Our guide what is DMARC, and does my small business need it? walks through the steps.
Add the basic security headers
These are free instructions your site sends to browsers. Six of them cover most of the value. See the six security headers every website should send.
Set up backups you can restore
Backups should be automatic, kept somewhere separate from your website, and kept for at least a few weeks so you can go back to before a problem started. Then, once, actually restore one to a test location. A backup you've never restored is a hope, not a plan.
// free, passive, 30 seconds
See how your site does on the basics
Do every month: the maintenance
Update everything
One of the most common ways into a small business site is software that wasn't updated: the CMS itself, plugins, themes or extensions. Check for updates at least monthly, and turn on automatic updates for minor releases where your platform supports it.
Remove what you don't use
Old plugins, themes you tried once, test pages, forgotten admin users. Each one is more to maintain and more to go wrong. If you're not using it, delete it.
Review your users
Look at who has admin access to your website. People change roles and leave. Admin rights should match the people who need them today.
Run a quick check
Run a free passive check on your site after any big change, and at least once a month. It takes about 30 seconds and catches settings that have quietly drifted, like a certificate that failed to renew or a header that disappeared after a hosting move.
Glance at your search results
Search Google for site:yourbusiness.co.za now and then. If you see pages you didn't create, especially in another language or selling things you don't sell, your site may have been tampered with. Our guide how to tell if your WordPress site has been hacked explains what to do next.
Know before you need it
What to do if something goes wrong
Write down, in one place, who you'd call: your developer, your host's support line, and anyone who helps with security. Note where your backups live and how to restore them. When something goes wrong, nobody wants to be searching for passwords.
Your data protection obligations
If your website collects personal information through contact forms, accounts, bookings or orders, data protection law applies. In South Africa that's POPIA, which requires reasonable security measures and notification when personal information is compromised. Our guide on what POPIA means for your website covers the basics in plain English.
How to tell real warnings from scams
You'll sometimes get emails saying your site is "at risk" or your domain is "expiring", with a link to pay. Many are phishing. Don't click the link. Log in to the real account directly, or ask someone you trust.
Where quick checks stop
A passive check reads what every visitor can already see. It can't see weak passwords, out-of-date plugins that don't announce their version, or bugs in your forms. A deeper vulnerability scan can, but it's an active test, so it must only run with proof of ownership and your written permission. Be wary of anyone who offers to scan your site without asking for both.
Your checklist at a glance
Once:
- List every account that controls your website, and who has access.
- Turn on two-factor authentication everywhere.
- Move to a password manager.
- Confirm HTTPS works and redirects properly.
- Set up SPF, DKIM and DMARC.
- Add the six basic security headers.
- Set up automatic, off-site backups, and test a restore.
Every month:
- Update the CMS, plugins and themes.
- Remove unused plugins, themes and users.
- Review who has admin access.
- Run a quick passive check.
- Glance at your search results.
Know in advance:
- Who to call, and where the backups are.
- Your data protection obligations.
- How to spot fake security warnings.
Want someone else to keep the list?
Some business owners enjoy this kind of thing. Most would rather not. That's what Odesstra is for.
Start with the free website security check. If you'd like ongoing help, website security monitoring means a person checks your site regularly and tells you when big news affects it, and website security fixes handles the work, quoted per job. See pricing for details, or book a short call.