Website security is often seen as the developer’s job: “they set everything up.” But when the site is hacked, the customer base leaks or a server goes down along with its data, the business takes the hit. Here are 10 checks an owner can run in half an hour, with no technical knowledge, to see how well the website and data are protected.
Why this is the owner’s question, not just the developer’s
Most hacks aren’t targeted attacks on a specific company. Automated bots scan thousands of sites every day looking for typical holes: an outdated plugin, a weak password, an exposed admin panel. So “we’re small, nobody will bother with us” doesn’t hold.
What a business loses after an incident:
- Sales. While the site is down or showing someone else’s content, there are no leads or orders.
- Data. Without a working backup, orders, customers and content have to be restored by hand — or can’t be restored at all.
- Trust and search. Google may flag an infected site with a warning for visitors. You can check this in the Security issues report in Google Search Console.
Work out what each hour of downtime actually costs, using your own figures:
Calculator
How much your website’s downtime costs
Enter your average online sales figures. A simplified estimate: orders are spread evenly over the day
Enter orders and average order value to see the result
Result
One hour of downtime costs 0
Over 0 hours of downtime you lose 0 in revenue.
A day without the website — 0.
And that’s before the ads still sending traffic to a site that’s down, and customers who went to competitors and may not come back.
10 website and data security checks
For each one: what to check and how to do it without technical knowledge.
- Access is registered to the company. The domain, hosting or server, code repository and email should be registered to the company, not to a developer or a former manager. Check who the domain is registered to and who owns the accounts.
- Passwords and two-factor authentication. Unique passwords for the admin panel, hosting, registrar and email, plus login confirmation via an app or SMS. One stolen password without 2FA — and an attacker is already in.
- Who has access. List everyone who can log into the admin panel, server or analytics. Former employees and contractors should lose access on the day the work ends.
- CMS, plugin and server updates. Outdated WordPress, OpenCart or plugins are the most common reason sites get hacked. Ask when the site and server software were last updated.
- HTTPS and the certificate. The site should open only over https, and the SSL certificate should renew automatically. Browsers show visitors a site with an expired certificate as unsafe.
- Backups kept off the server. Backups should run automatically — daily or weekly, depending on how often your data changes — and be stored separately from the main server.
- Tested restores. A backup nobody has tried to restore is just hope. Ask to be shown that a working version of the site really comes back from a copy.
- 24/7 monitoring. Someone should know the site is down within minutes, not hear it from customers the next morning.
- Attack protection. DDoS protection, a website firewall and blocking of password guessing stop most automated attacks before they reach the site.
- An incident plan. Who is responsible, whom to call, where the backups are and how long recovery takes. Once the site is down, it’s too late to look for this.
Also think about customer data outside the website: spreadsheets with your customer base forwarded in messengers are a risk too. We wrote about this in “How to move off Excel: when spreadsheets slow your business down”.
5 questions for your developer or hosting provider
If a contractor looks after your site, forward them these questions. Clear answers to all five are a good sign; “I’ll need to check” is a reason to look closer.
- Where are backups stored, how often are they made and how many versions are kept?
- When did you last check that the site really restores from a backup?
- Who currently has access to the server, admin panel and database?
- How will you know the site is down, and how quickly will you start restoring it?
- When were the CMS, plugins and server software last updated?
Quiz: how well protected is your website
Answer 10 questions — the result will show your level of protection and the specific gaps to close first.
Quiz · 10 questions
How well protected are your website and data
Answer all questions to see your result
Result · 0/10
A good level of protection
The basics are in place. The key is to keep it regular: updates, backup checks and access reviews.
Result · 0/10
There are weak spots
The foundation is there, but the gaps above are exactly where incidents usually come from. Close them first.
Result · 0/10
Your website and data are at risk
There are many gaps, and each could cost you downtime or lost data. Start with an express audit: we’ll show what to close first.
Backups: how they should be set up
Backups are the last line of defence: if everything else fails, they are what gets the business running again. But only if they are set up properly.
How backups should be set up
Frequency depends on how quickly your data changes. An online store taking orders every day needs daily copies; a brochure site updated once a month can live with weekly ones.
How often to check what
| When | What to check |
|---|---|
| Continuously, automatically | Uptime monitoring, backups, attack protection |
| Monthly | CMS, plugin and server updates, overall server health |
| Quarterly | The access list, a test restore from backup, whether the incident plan is up to date |
| When someone leaves or a contractor changes | Remove access, change passwords, check who owns the domain and server |
Most of these checks don’t need the owner’s involvement: the team that runs your site and server takes care of them. Your job is to know they happen and to get a report on them.
From practice: holes closed — then a move to our servers
Clients have come to us more than once with vulnerabilities on their websites. We closed the holes quickly, and afterwards the clients moved their projects to our servers: with monitoring, attack protection and backups kept separately from the main server. Since then, these projects have had no security problems.
How we move a site without downtime is covered in “How to migrate a website to a new host without downtime”.
The site was hacked: what to do in the first hour
- Don’t delete everything. Traces of the hack help find the hole the attacker came through.
- Change the passwords for the admin panel, hosting, database and email, and end all active sessions.
- Take the site offline while you restore it, so visitors don’t get malicious content.
- Restore from a clean backup — a copy made before the hack.
- Close the vulnerability: update the CMS and plugins and remove unnecessary access. Otherwise the site will be hacked again.
- Check Google Search Console: if the site was flagged as unsafe, request a review once it’s clean.
How we keep projects secure
On our servers, basic protection is on by default, not “on request”:
- Backups kept separately from the main server. The client chooses the frequency: daily or weekly.
- 24/7 uptime monitoring and a monthly server health check.
- DDoS protection, an SSL certificate and access only for those who need it.
- Updates and fixes as part of project support: a response within an hour, often in 5–10 minutes.
Server plans and specs are on the Cloud & Servers page.
Not sure your website and data are protected?
We’ll start with a free express audit: we’ll check access, updates, backups and protection and show what to close first.
FAQ
How can I check my website’s security without technical knowledge?
Run 10 checks: who the domain and server are registered to, whether two-factor authentication is on, who has access, when the last updates were, whether HTTPS works, where backups are kept and whether restores have been tested, and whether there is monitoring, attack protection and an incident plan.
How often should a website be backed up?
It depends on how often your data changes. An online store or CRM with daily orders needs daily copies; a rarely updated site can make do with weekly ones. The key is to store copies separately from the main server and to test restores.
Why do hackers target small business websites?
Most attacks are automated: bots scan thousands of sites looking for typical holes such as outdated plugins or weak passwords. The size of the business doesn’t matter to them.
What should I do if my website has already been hacked?
Change all passwords, take the site offline while you restore it, restore from a clean backup made before the hack, and close the vulnerability with updates. If Google flagged the site as unsafe, request a review in Search Console once it’s clean.
Can a website built by another team be secured?
Yes. We take on projects on any stack: we run an express audit, close vulnerabilities and, if needed, move the site to our servers with backups, monitoring and attack protection.
Updated November 18, 2026 · Figures current as of the update date