Most small business owners only think about website security after something goes wrong: a contact form flooded with spam, a browser warning on the homepage, or a site that suddenly redirects to something it shouldn't. By then you are fixing a problem instead of preventing one. The good news is that the basics are not technical, and most of them come down to who controls what.
The short answer
A secure small business website needs HTTPS on every page, strong unique logins with two-step verification, regular backups you can actually restore, as little third-party code as possible, and logins that belong to you, not to your developer. Get those five right and you have dealt with the large majority of everyday risk. Nothing here makes a site unhackable, and anyone who promises that is selling something.
1. Check that every page loads over HTTPS
HTTPS is the padlock in the browser bar. It encrypts what visitors send to your site, including contact form details. Browsers warn visitors when a page is not secure, and that warning costs you trust before anyone reads a word.
Type your address into a browser with and without the "www", and with "http://" at the start. Every version should land on the same secure address. Then click through your key pages. A single page that loads insecure content, often an old image or script, can trigger a warning. Also ask where your certificate renews and who is responsible. An expired certificate takes a site from fine to alarming overnight.
2. Lock down your logins
Weak or reused passwords are a far more common way in than clever attacks. For your website, hosting, domain registrar and email, use a different long password for each, kept in a password manager, and turn on two-step verification wherever it is offered.
Pay attention to your domain registrar in particular. If someone takes control of your domain, they can redirect your website and intercept your email. Many owners have not logged in to the registrar in years and no longer know which email address it is tied to. Find out today.
Then look at who has access. Former staff, past agencies and freelancers often keep logins long after the work ends. Remove anyone who no longer needs access.
3. Know what is running on your site
Every plugin, add-on and embedded script is code written by someone else, and each one needs to be kept up to date. A site built on a large number of plugins has more to maintain, and an out-of-date plugin is a common weak point. This is not a reason to avoid tools you need. It is a reason to ask what is installed and why.
A simple test: ask whoever looks after your site for a plain list of what is running, what each piece does and when it was last updated. If nobody can answer, that is the finding. A site with fewer moving parts has fewer things to go wrong, which is one reason we build custom sites without piles of add-ons.
4. Keep backups, and test that they work
A backup you have never restored is a hope, not a plan. Ask three questions. How often is the site backed up? Where are the copies stored? How long would it take to bring the site back, and who does it?
Take a manual backup before any major change, and label it with what you are about to do. If something breaks, you can go back to a known good version in minutes rather than rebuilding from memory.
5. Own your logins and your domain
This is the one most owners miss. If your domain is registered in your developer's account, or your hosting sits under their login, you are one falling-out or one closed business away from losing your own website. You should hold the owner login for your domain, your hosting and your website itself. A good developer hands these over on launch day without being asked, and does not charge you to get your own property back.
6. Deal with form spam properly
Spam through contact forms is mostly an annoyance, but it can bury real enquiries. Use a spam check on every form, and do not rely on the notification email alone. Send a test enquiry once a month and confirm it arrives. A form that quietly stops delivering is a security-adjacent problem that costs real money.
Frequently asked questions
Is a small business website really a target?
Yes. Most attacks are automated and look for common weaknesses on any site, not a particular business. Being small does not make you invisible, which is why the basics matter more than the size of your company.
Do I need a security plugin or a paid security service?
Not necessarily. Fixing the basics comes first: HTTPS, strong logins with two-step verification, backups, and keeping what runs on your site to a minimum. Whether you need anything extra depends on how your site is built and what it does, so ask your developer to explain the reasoning in plain English.
How often should I check my website's security?
A short check once a month is a sensible rhythm: confirm the padlock shows on key pages, test your forms, review who has access, and confirm a recent backup exists. Check your domain and certificate renewal dates at the same time.
What should I do if my website has been hacked?
Change your passwords for the website, hosting and domain registrar straight away, restore from a clean backup if you have one, and contact whoever manages your site. If customer details may have been exposed, get advice on your obligations under Australian privacy law. We are not lawyers, so check with a professional on that part.
Who should own my domain and hosting accounts?
You should. Your business name should be on the registrar account, your email on the login, and you should hold the owner access. A developer can be added as a user to do the work, but the accounts are yours.