Small Business Website Security: The Short Checklist That Covers Most of the Risk
A plain-language website security checklist for small businesses: how small business sites actually get attacked, the ten controls that prevent most of it, a 20-minute self-check you can run today, and what to do if your site has already been hacked.
Small business website security is mostly about closing a short list of known doors: logins without multi-factor authentication, software that has not been patched, a domain account nobody remembers the password to, and backups that do not exist. Small business sites are rarely attacked by someone who chose them. They are found by automated tools that scan the internet for those exact weaknesses, and the fix for nearly all of it is routine rather than technical.
I am a security engineer, and this is the checklist I would want every small business owner to run once, whoever built their site.
How do small business websites actually get hacked?
Owners often assume they are too small to be a target. That is true in the sense that nobody is looking for you specifically. It is irrelevant in practice, because automated attacks do not choose. They try everything.
The common paths in are few:
- Known vulnerabilities in outdated software. A plugin, theme, or content management system with a published security hole. Scanners find it within days of the vulnerability being announced.
- Stolen or guessed logins. Admin accounts with reused passwords, shared passwords, or no second factor. Credential lists from other breaches are tried automatically against login pages.
- Compromised accounts around the site. The domain registrar, the hosting account, or the email account that can reset both. Whoever controls these controls the website, whatever the site’s own security looks like.
- Abandoned access. A former employee or a previous web designer whose account was never removed.
What attackers do once in is usually unglamorous: inject spam links or pages to borrow your search ranking, redirect visitors to scams, send spam from your server, or skim data from your forms. The damage to a small business is a site flagged by browsers and search engines, lost inquiries, and a cleanup bill.
The checklist
Accounts
1. Turn on multi-factor authentication everywhere that controls the site. That means the site’s admin login, the hosting account, the domain registrar, and the email account those accounts send password resets to. If you do one thing from this list, do this. An authenticator app is stronger than text-message codes, and either is far better than nothing.
2. Give every person their own login, and remove the ones that should be gone. Shared logins make it impossible to remove one person’s access without changing it for everyone, so in practice nobody changes it. List every admin account on the site and the hosting account, and remove anyone who no longer works with you, including previous designers and agencies.
3. Use a password manager. Unique, long passwords for each account, stored somewhere other than a sticky note or a shared spreadsheet. Most password managers have business plans that let you share specific logins with specific people.
The domain
4. Make sure your business owns the domain, and lock it down. The domain should be registered in your business’s name, in an account you control, with auto-renew on and a payment card that will not expire unnoticed. Turn on the registrar lock (often called transfer lock), which prevents the domain from being moved to another registrar without an extra step. Losing control of a domain means losing the website and the email at once. I covered ownership in more detail in how to choose a web designer.
5. Set up email authentication on the domain. SPF, DKIM, and DMARC are DNS records that tell receiving mail servers which senders are allowed to use your domain. They make it harder for someone to send convincing email that appears to come from you, and they help your own mail reach inboxes. Since 2024, Google and Yahoo have required senders to authenticate their mail, with stricter rules, including DMARC, for bulk senders. Your email provider has setup instructions for all three.
The software
6. Keep everything updated, and remove what you do not use. The content management system, every plugin, every theme. Turn on automatic updates for security releases where the platform supports it. Then delete plugins and themes that are deactivated, because inactive code can still be vulnerable and nobody is updating it. Fewer components means fewer holes. This is the core of the website maintenance routine.
7. Serve the whole site over HTTPS. Every page, not just the contact form. Certificates are free from most hosts through Let’s Encrypt, and browsers warn visitors about pages that are not secure. Check that the certificate renews automatically.
Recovery and forms
8. Keep backups somewhere other than the server, and test one. A backup on the same server as the site can be lost or encrypted along with it. Keep at least one copy elsewhere, keep several days or weeks of history so you can go back to before a compromise, and restore one at least twice a year to prove it works.
9. Collect only what you need through forms. Every field on a form is data you are now responsible for. A contact form needs a name, a way to reply, and a message. Do not collect Social Security numbers, card numbers, or health details through a general website form. Use a payment processor or a purpose-built secure intake tool for those. Add spam protection to forms so they do not become a channel for junk or abuse.
Ownership
10. Name the person responsible. Someone has to apply updates, receive the renewal notices, see the security alerts from the host, and remove access when people leave. When that responsibility belongs to nobody, every other item on this list slowly stops being true.
A 20-minute self-check you can run today
- Log in to your domain registrar. Confirm the domain is in your business’s name, auto-renew is on, the transfer lock is on, and MFA is enabled. If you cannot log in, that is the finding.
- Log in to your hosting account and your site’s admin. Turn on MFA on both. List the admin users and remove anyone who should not be there.
- Check for pending updates in the site’s admin. If there are many, or some are years old, the site needs attention before anything else on this list.
- Visit your site with
http://instead ofhttps://. It should redirect to the secure version automatically. - Search Google for
site:yourdomain.comand scroll through the results. Pages you do not recognize, especially about pharmaceuticals, gambling, or in a language you do not use, are a common sign of a spam injection. - Ask whoever manages the site where the last backup is, and when one was last restored.
If everything passes, you are ahead of most small business sites. If something fails, you now know where to start.
What if my website has already been hacked?
Signs include browser or Google warnings on your site, unfamiliar pages in search results, redirects to other sites, admin users you did not create, or a hosting provider suspending your account.
Work in this order. Change the passwords and turn on MFA for the registrar, hosting, site admin, and email first, from a device you trust, because cleaning a site while the attacker still has a login is wasted effort. Contact your host, since many have a security team or a cleanup process. Restore from a clean backup taken before the compromise if you have one, then apply every update before putting the site back online, or the same hole will be used again. If you have Google Search Console set up, check the Security Issues report, and request a review once the site is clean. If your forms collected personal information, get advice on whether you have notification obligations, because those depend on your state and the type of data.
Does the type of website matter?
Yes. A site built on a content management system with a database and plugins has a large surface to keep patched, and most of the checklist’s software items exist because of it. A static site, built as plain files and served from a content delivery network, has very little server-side software to attack, so the patching burden shrinks considerably. That is one of the reasons I build static sites for most small businesses.
The account and domain items do not shrink with architecture. A static site with a registrar account protected by a reused password is still one phishing email away from losing its domain. Items 1 through 5 and 10 apply to every site.
Frequently asked questions
Is my small business website really a target?
Not specifically, but it does not need to be. Most attacks on small business websites are automated scans that look for known vulnerabilities and weak logins across huge numbers of sites. Any site with outdated software or an unprotected admin login will eventually be found.
What is the most important website security step for a small business?
Turning on multi-factor authentication for the site’s admin, the hosting account, the domain registrar, and the email account that receives password resets. Together those accounts control the website, and MFA blocks most attacks that rely on stolen or guessed passwords.
Do I need a security plugin?
A security plugin can help on a content management system like WordPress, mainly with login protection and malware scanning. It is not a substitute for updates, MFA, backups, and removing unused accounts. A plugin is also more software to keep updated.
How often should I check my website’s security?
Apply updates as they are released or at least monthly, review admin accounts whenever someone leaves, and run the full checklist once a year. The 20-minute self-check is a good quarterly habit.
What are SPF, DKIM, and DMARC?
They are DNS records for your domain that authenticate your email. SPF lists the servers allowed to send mail for your domain, DKIM adds a cryptographic signature to outgoing messages, and DMARC tells receiving servers what to do with mail that fails those checks. Together they make it harder to impersonate your domain by email.
The one-sentence version
Put multi-factor authentication on every account that controls your site and domain, keep the software patched and minimal, keep a tested backup somewhere else, and make one named person responsible for all of it.
If you would rather have a site where most of this is handled by design, with hosting, updates, monitoring, and backups covered by a care plan, everything is on the websites page.
Jose Lugo is a CISSP-certified security engineer with 12 years of U.S. Army intelligence experience. He builds secure AI work environments and fast, maintainable websites for businesses at josecustom.ai. See his portfolio of 13 live client systems at portfolio.josecustom.ai.