Small business websites are hacked every day, not because attackers chose them, but because automated tools scan the internet for known weaknesses: an outdated plugin, a weak admin password, an abandoned test site. A hacked site can show spam to your customers, steal enquiry data, be flagged by Google with a warning, or simply disappear.
Most of these attacks are preventable. This checklist covers the protections every business website should have, in plain language, so you can check yours or ask the right questions of whoever looks after it.
1. Accounts and passwords
- Use unique, long passwords for the website admin, hosting, domain registrar and email. A password manager makes this practical.
- Turn on two-factor authentication wherever it is offered, especially for the domain registrar, hosting and website admin. If attackers get into the domain account, they can take everything.
- Give each person their own login. Shared "admin" accounts make it impossible to know who did what, or to remove someone who leaves.
- Remove old accounts for former staff, agencies and freelancers.
- Keep owner access in the business's name. Our ownership checklist explains why.
2. Software updates
- Update the content system, theme and plugins regularly. Most WordPress hacks exploit known holes that already have a fix.
- Remove plugins and themes you no longer use; deactivated code can still be attacked.
- Choose plugins that are actively maintained, with recent updates.
- On hosted platforms such as Shopify, the platform handles core updates, but apps and third-party scripts still need reviewing.
Updates can occasionally break features, which is why they belong in a regular maintenance routine with testing, not a once-a-year panic.
3. HTTPS everywhere
Every page should load over HTTPS with a valid certificate. Browsers mark plain HTTP pages as "Not secure", and any form on them sends data unprotected. Most hosts provide free certificates; make sure they renew automatically and that every HTTP address redirects to HTTPS.
4. Backups you have tested
- Back up files and the database automatically, at least daily for sites that change often.
- Keep copies off the server, so a hacked or failed server does not take the backups with it.
- Keep several days or weeks of history, so you can restore a version from before a problem started.
- Test a restore at least twice a year. A backup that has never been restored is a hope, not a plan.
5. Forms and spam
- Protect contact and enquiry forms with spam protection, such as a lightweight challenge or hidden fields, so attackers cannot flood your inbox or use the form to send spam.
- Collect only the information you need. Every extra field is more personal data to protect under the PDPA.
- Make sure form submissions are sent and stored securely, and that you know where they go.
6. Hosting and the server
- Use reputable hosting with security updates handled for you, and malware scanning if available.
- Keep each website in its own account or container, so one compromised site cannot infect others.
- A web application firewall, offered by many hosts and CDN providers, blocks common automated attacks before they reach the site.
- Make sure hosting, domain and email accounts are not all protected by the same password.
7. Watch for warning signs
- Search Console's Security issues report shows if Google has detected hacked content or malware. Check it monthly; our Search Console guide explains where to find it.
- Search Google for
site:yourdomain.comand look for pages you did not create, often in another language or about pharmaceuticals or gambling. - Watch for sudden changes: new admin users, unexpected redirects on mobile, emails bouncing, or a hosting account using far more resources than usual.
8. Know what to do if it happens
Write down a short plan now, while things are calm:
- Who to call: your developer, hosting provider and domain registrar.
- How to put the site into maintenance mode or take it offline.
- Where the clean backups are and how to restore them.
- How to change every password and remove unknown accounts.
- Whether personal data may have been exposed, and what notification obligations apply. Malaysia's amended PDPA introduced data breach notification requirements; check the current rules and our PDPA guide.
- After cleaning, how to request a review in Search Console if Google flagged the site.
A monthly security routine
- Apply updates and test the main pages and forms
- Confirm backups ran and are stored off the server
- Check Search Console's Security issues report
- Review user accounts and remove anyone who no longer needs access
- Check that HTTPS works and the certificate is valid
Security is built into how we set up and maintain websites. If you are not sure who last updated your site, or whether backups exist, ask us for a check-up. Read our technical SEO checklist for the other health checks.
