Most attacks on small business websites are automated. They do not target you personally. They scan for weak passwords, outdated software and forgotten accounts. That is good news, because a short list of basic measures stops the great majority of them. This checklist is written for site owners, not security specialists, and uses WordPress examples where a platform is named.
How to use this checklist
Go through it once in full, then repeat the review section every quarter. Mark each item done, not applicable or needs action.
1. Accounts and passwords
- Every person has their own account. No shared logins.
- Each password is long, random and used nowhere else, stored in a password manager.
- No account uses an obvious username such as admin.
- Two-factor authentication is switched on for all administrators, and for the hosting, domain and email accounts too.
- Each user has the lowest role that lets them do their work.
- Accounts of former staff and former suppliers are removed.
- The email address for the administrator account is current and itself protected with two-factor authentication.
2. Software and updates
- The CMS, themes and plugins are up to date.
- Automatic updates are enabled for at least minor and security releases.
- Unused plugins and themes are deleted, not merely deactivated.
- Every plugin and theme comes from the official directory or a reputable vendor. No pirated or so-called nulled software, which very often contains malware.
- The server runs a supported PHP version.
- Before adding a plugin, it is checked for recent updates and active maintenance. See How to Evaluate a WordPress Plugin Before Installing It.
3. Backups
- Automatic backups run on a schedule that matches how often the site changes.
- A copy is stored away from the web server.
- Several older versions are kept.
- A restore has been tested. See How to Create a Basic Website Backup and Test a Restore.
4. Connection and hosting
- The whole site loads over HTTPS with a valid, automatically renewing certificate.
- File transfers use SFTP, not plain FTP.
- The hosting control panel has a strong unique password and two-factor authentication.
- Each website has its own database user.
- The host provides or allows a firewall and malware scanning.
5. Login and form protection
- Repeated failed login attempts are limited or blocked.
- Forms are protected against spam and automated submissions.
- If comments are not used, they are switched off.
- XML-RPC is disabled if nothing needs it.
- User registration is switched off unless the site requires it.
6. Configuration
- File editing from the dashboard is disabled.
- Directory listing is off, so visitors cannot browse folders.
- Error messages are not displayed to visitors.
- Backup files, database exports and old copies of the site are not stored in publicly reachable folders.
- Installation and test files are removed.
7. Domain and email
- The domain is registered in the name of the business, in an account the business controls.
- Auto-renewal is on, and the payment method is valid.
- Domain transfer lock is enabled.
- SPF, DKIM and DMARC records are set, which makes it harder for others to send email pretending to be you.
8. Data and privacy
- The site collects only the personal data it needs.
- Form submissions containing personal data are not kept longer than necessary.
- Payment card details are handled entirely by a certified payment provider and never stored on your server.
- Third-party services that receive visitor data are listed in the privacy policy.
9. Monitoring
- Uptime monitoring alerts you if the site goes down.
- Google Search Console is set up. Its Security issues report warns of detected hacking or malware.
- A security plugin or the host’s scanner checks for changed files and known malware.
- Someone reviews the list of administrator accounts regularly for unknown entries.
10. People
- Everyone with access knows not to enter the site password on a page reached from an email link.
- Unexpected messages about invoices, domain expiry or account suspension are verified by logging in directly, not by clicking the link.
- Access is given through individual accounts, never by sharing your own password.
Quarterly review
- Review all user accounts and remove those no longer needed.
- Confirm updates are current.
- Confirm the latest backup exists and test a restore at least twice a year.
- Check the domain and certificate renewal dates.
- Remove plugins you no longer use.
If you suspect the site has been hacked
- Do not delete anything yet. Note what you observed and when.
- Contact your host. Many offer cleanup assistance and can check server logs.
- Change all passwords: CMS, hosting, database, SFTP and the associated email.
- Put the site into maintenance mode if it is distributing malware or spam.
- Restore from a clean backup taken before the incident, then update everything.
- Find out how the attacker got in. Restoring without closing the gap invites a repeat.
- Check Search Console for security warnings and request a review once the site is clean.
- If personal data may have been exposed, you may have legal notification duties. Seek advice promptly.
The five measures that matter most
- Unique strong passwords with two-factor authentication.
- Prompt updates.
- Tested off-site backups.
- Few plugins, from trustworthy sources.
- Minimal, individual user access.
Next step
Build these checks into your routine with the Monthly Website Maintenance Checklist, and review HTTPS and SSL Certificates Explained if any part of the secure connection is unclear.
