Home/Guides/Security basics
Care guide

Website security basics
for a small business.

Most small business sites aren't hacked by someone who chose them. They're found by automated tools looking for an old plugin or a weak password. The fixes are mostly simple: keep software updated, lock down logins, keep off-site backups, and protect the accounts that control your domain. Here's what to do on WordPress, on a website builder and on a custom-coded site, and what to do if it happens anyway.

Updated November 2026 · 12 min read

A small padlock resting on a laptop keyboard
Photo: Markus Winkler / Pexels

The short answer

Most small business websites get hacked in one of a few boring ways: software that wasn't updated, a weak or shared password, or an account nobody remembered to protect. Almost all of it is automated. Bots scan huge numbers of sites for known holes and break into whichever ones still have them. You weren't picked. You were found.

That's good news, because it means the basics stop most of it:

  1. Keep software updated, or use a setup with no software to update.
  2. Turn on two-factor sign-in everywhere it's offered, starting with your email and domain registrar.
  3. Give everyone their own login with the least access they need, and remove people who leave.
  4. Keep backups somewhere other than the website, and test that they restore.
  5. Protect your forms from spam bots and don't collect sensitive information you don't need.

The rest of this guide covers each platform in turn, the accounts that matter more than the website itself, and what to do if the worst happens.

How small sites actually get hacked

These are the routes in we see most on small business sites:

  • Outdated plugins. On WordPress, a plugin with a known hole is the classic way in. Once a fix is released, the hole is public, and bots start looking for sites that haven't updated.
  • Weak or shared admin logins. One "admin" password shared by the office, the old web designer and a nephew who helped once. Bots try common passwords against login pages around the clock.
  • Abandoned themes and plugins. Software whose developer stopped updating it. When a hole turns up, no fix ever comes.
  • Unsecured forms. Forms with no spam protection get used to send junk, and badly built upload forms can let someone put a file on the server.
  • Stolen email passwords. Get into the email and you can reset the password on almost everything else.
  • Forgotten accounts. A registrar account under a former employee's email, or a hosting login from an agency you left years ago.

What do they want with a plumber's website? Usually not you. They want your site's good name with Google and with email filters. A hacked site gets used to host spam pages, redirect visitors to scams, send junk email, or hide malware. You often find out from a Google warning, a host suspending the account, or a customer asking why your site sent them somewhere strange.

Security on WordPress

WordPress can be run securely. Plenty of large organizations do it. The difference is that on WordPress, security is ongoing work, because the site is software made of many parts from many developers. This is the list:

WordPress security checklist

  • Update core, theme and plugins promptly, security releases within days. Update a staging copy first if you have one, after a backup either way.
  • Delete plugins and themes you don't use. Deactivated still means installed, and an installed plugin can still be attacked.
  • Replace anything abandoned. If a plugin or theme hasn't been updated by its developer in a long time, plan to swap it out.
  • Never install pirated ("nulled") premium plugins or themes. They're a common way malware gets onto a site.
  • Turn on two-factor sign-in for every admin account.
  • One login per person, with the lowest role that does the job. Someone who writes blog posts needs Author or Editor, not Administrator. No shared "admin" login.
  • Remove logins for people who've left, including old web designers and agencies.
  • Limit login attempts so bots can't guess passwords all day.
  • Keep backups off the server, on a schedule, and test a restore.
  • Put a web application firewall in front of the site. It filters known attacks before they reach WordPress. Many hosts and security services offer one.
  • Run malware scans, and read the alerts.
  • Keep the PHP version current with your host.

The two that matter most are updates and logins. A site with current plugins and two-factor admin logins has closed off the most common ways in. A firewall and malware scanning add a layer, but they don't replace updates.

If that list looks like more than you'll keep up with, that's worth knowing now. Either pay someone to do it every month, or move to a setup that doesn't need it. Our guide to what a care plan covers explains what that monthly work looks like, and custom-coded vs WordPress compares the two honestly.

Security on Wix, Squarespace and other builders

On a hosted builder, the platform runs the software, patches it and handles HTTPS. You can't install a vulnerable plugin onto their servers, so most of the WordPress list doesn't apply. What's left is the account.

Builder security checklist

  • Turn on two-factor sign-in for the builder account. On a builder, that account is the website.
  • Use contributor roles for staff and freelancers instead of sharing the owner login.
  • Review installed apps and add-ons and remove what you don't use.
  • Protect the email the account is registered to, since password resets go there.
  • If the domain is registered elsewhere, protect that registrar account too.

The risk on a builder is concentrated in one place: if someone gets into your builder account, they have the whole site. Two-factor sign-in on that account, and on the email behind it, covers most of it.

Security on a custom-coded static site

A static site is a set of finished files served to visitors. There's no database to break into, no admin login on the site to guess, and no plugins to patch. That makes the attack surface much smaller: most of the routes in described above simply don't exist. Our sites are static files on Cloudflare's edge with automatic HTTPS, and our speed and security page explains how that works.

Smaller isn't zero. With no website login to attack, the target moves to the accounts that control the site:

Static site security checklist

  • Two-factor sign-in on the domain registrar. This is the real crown jewel.
  • Two-factor sign-in on the DNS and hosting accounts (on our sites, the Cloudflare account).
  • Domain in your business's name, transfer lock on, auto-renew on.
  • Protect your email, since it resets every other account.
  • Form protection against spam bots, and form emails going to a shared inbox you read.
  • Off-site backups of the site files.

The domain registrar is the crown jewel. Whoever controls your registrar and DNS controls where your domain points: your website, and usually your email too. Someone in that account can point your domain at a copy of your site, or take it offline, without ever touching the site files. So on a static site, the most important security step isn't on the website at all. It's two-factor sign-in on the registrar and DNS accounts, and the domain registered in your name. Our guide to domain, hosting and email ownership walks through setting that up.

A finger entering a code on a phone
Turn on two-factor sign-in for your registrar and email first. Photo: Jakub Zerdzicki / Pexels

The accounts that matter more than the website

On every platform, your website depends on a handful of other accounts. People protect the website and forget these, and they're often the easier way in.

AccountWhat someone could do with itProtect it with
Domain registrarPoint your domain anywhere, take your site and email offline, or transfer the domain awayTwo-factor sign-in, a unique password, the domain in your business's name, transfer lock on
DNS (often the registrar, sometimes a host like Cloudflare)Send your visitors to a fake site, or redirect your emailTwo-factor sign-in, and as few people with access as possible
Business emailReset the password on every other account on this listTwo-factor sign-in. This is the master key to everything else
Website admin (WordPress, builder)Change or deface the site, add spam pages, install malwareTwo-factor sign-in, one login per person, the lowest role that does the job
Hosting accountReplace or delete the whole site and its backupsTwo-factor sign-in, and backups stored somewhere else
Google Business ProfileChange your phone number, hours or address on GoogleTwo-factor on the Google account, and owners you trust
Payment account (Stripe, PayPal, Square)Change where payouts goTwo-factor sign-in, and alerts on account changes

If you can only do one thing today, turn on two-factor sign-in for your email and your domain registrar.

Write these down: which accounts you have, which email each is registered to, and who has access. Check the list once a year, and whenever someone leaves. Our website maintenance checklist puts that review on the calendar.

For two-factor sign-in, an authenticator app or a hardware key is stronger than a text message code, but a text code is far better than nothing. Store the backup codes somewhere safe and offline, so losing a phone doesn't lock you out.

Form spam and form security

Every public form gets found by spam bots eventually. Spam is mostly a nuisance, but it buries real enquiries, and a form that can be abused to send email can get your domain's mail flagged as junk. Good protection is invisible to customers:

  • A honeypot field. A hidden field people never see but bots fill in. Anything that fills it is dropped.
  • A challenge that runs in the background, such as Cloudflare Turnstile or Google reCAPTCHA, which checks for a bot without making real people solve puzzles.
  • Checks on the server, not just in the browser. A bot can skip anything that only runs on the visitor's side.
  • Rate limits, so one source can't send hundreds of submissions in a minute.
  • Tight file uploads. If a form accepts files (plans, photos, artwork), limit the types and sizes, and never let uploads run as code on the server.

Just as important is what you ask for. Don't collect card numbers, Social Security numbers or health details through an ordinary contact form. Take payments through a payment provider's own checkout, and if you need sensitive information (patient intake, for example), use a tool built and contracted for it. Our healthcare and dental page touches on that. Our guide to forms and lead tracking covers making sure every real enquiry actually reaches you.

HTTPS: what it does and doesn't do

HTTPS is the padlock in the address bar. It's standard now, and browsers label sites without it "Not secure", which costs you trust on any page with a form. Certificates are widely available for free, so there's no reason to go without.

What it does: it encrypts the connection between the visitor's browser and your site, so nobody on the same coffee shop wifi can read what they type into your form, and it confirms the visitor reached your real domain.

What it doesn't do: it says nothing about whether the site itself is secure or the business is legitimate. A hacked site can have a perfectly good padlock. Scam sites use HTTPS too.

Three things to check:

  • Typing your domain with http:// should redirect to https:// automatically.
  • The certificate should renew automatically. Click the icon next to the address and look at the expiry date once a year.
  • Every image and script on the page should load over HTTPS too. If not, browsers may show a warning or block them.

What to do if you're hacked

If your site is showing spam, redirecting visitors, or Google is warning people away, work through this in order. Don't start by deleting things: you can destroy the evidence of how they got in.

  1. Write down what you see, with screenshots and the time. Note any warnings from Google, your host or customers.
  2. Secure your email first, from a device you trust: change the password and turn on two-factor sign-in. Then do the same for the registrar, hosting and website admin accounts.
  3. Call your host or provider. They can often tell you what changed and when, and may have clean backups.
  4. Remove logins you don't recognise, on the website and every account above.
  5. Restore from a clean backup taken before the problem started. This is why off-site backups matter: a backup on the hacked server may be hacked too.
  6. Close the hole, or it happens again within days. Update everything, remove the plugin or theme that let them in, and change every password.
  7. Check Google Search Console for security issues, and once the site is clean, request a review so warnings come off.
  8. Think about your customers. If personal information may have been exposed, talk to a lawyer about whether you have to notify anyone.

Worked example

Say a small dental office in Wayzata runs WordPress. The site was built five years ago, the office shares one admin login, and a gallery plugin hasn't been updated in two years. One week, patients mention that searching for the practice shows odd pages about pharmacy discounts.

They follow the steps. Their host confirms new files appeared a month ago. The most recent clean backup is from six weeks ago, stored off the server, so they restore it, remove the gallery plugin, update everything else, and give each staff member their own login with two-factor sign-in. Search Console shows a security issue; once the site is clean they request a review.

The real cost wasn't the cleanup. It was a month of patients seeing spam under the practice's name. The fix that would have prevented it (updates, separate logins, two-factor) costs almost nothing.

If this is happening to you right now and you're stuck, tell us what you're seeing. We'll tell you plainly what to do first.

The short list to keep

Security for a small business isn't about buying more tools. It's about closing the ordinary gaps, on a schedule:

Every site, every platform

  • Two-factor sign-in on email, registrar, DNS, hosting and the website admin.
  • One login per person, lowest role that works, removed when they leave.
  • Software updated promptly, or a setup with nothing to update.
  • Backups off the server, restore tested.
  • Forms protected from bots, and no sensitive data through plain forms.
  • HTTPS on every page, renewing automatically.
  • A written list of every account the site depends on, and who owns it.

If you'd rather not carry the list yourself, our care plans include off-site backups, security monitoring at the edge, uptime monitoring and form upkeep on a site with no plugins and no admin login to attack. We look after businesses from Elk River to the west metro. Either way, start with two-factor on your email and registrar today.

Want a straight answer for your business?

Every Stonekept build is custom-coded, hosted on Cloudflare and kept on a monthly plan. Prices are public: builds from $2,200 with care from $199/mo. See pricing or tell us about your project and we'll give you an honest read, even if that's not us.

Questions

Quick
answers.

Why would anyone hack a small business website?

Usually not for your data. Automated tools break into any site with a known hole, then use it to host spam pages, redirect visitors to scams, send junk email or spread malware. Your site's good standing with Google is what they're after.

Is WordPress secure?

It can be, if it's kept updated, has few well-maintained plugins, uses two-factor logins and has off-site backups. Most hacked WordPress sites are ones nobody was updating, not WordPress itself failing.

Are static websites more secure?

They have a much smaller attack surface: no database, no admin login on the site and no plugins to patch. You still need to protect the domain registrar, DNS and email accounts, which control where the site points.

Do I need a security plugin?

On WordPress, a security plugin or a firewall from your host adds a useful layer, but it doesn't replace updates, two-factor logins and backups. Builders and static sites don't use plugins.

How do I stop spam from my contact form?

Use a hidden honeypot field, a background bot check such as Cloudflare Turnstile or reCAPTCHA, server-side checks and a rate limit. Most spam stops without your customers ever seeing a puzzle.

What should I do first if my website is hacked?

From a trusted device, change your email password and turn on two-factor sign-in, then do the same for the registrar, hosting and website. Then contact your host, restore a clean backup, and fix how they got in.

Does HTTPS mean my website is secure?

No. HTTPS encrypts the connection between the visitor and your site, which you need, but it says nothing about whether the site itself has been kept up to date or hacked.

Let's build something lasting

Nothing to patch,
nothing to guess.

Tell us what you need and we'll map out the right approach on a free discovery call.

StudioBuffalo, Minnesota
ServingTwin Cities west metro