Say you run a small plumbing firm with a WordPress site. A friend tells you it’s secure because the browser shows a padlock. It isn’t, or not in any way that matters to an attacker. The padlock means traffic between visitor and server is encrypted. It says nothing about whether your login page, plugins or backups are in decent shape. These website security tips UK owners can actually use start where the padlock stops.
What does the padlock actually protect?
The padlock shows that a site uses HTTPS, so data in transit between the browser and your server is encrypted and the certificate matches your domain. That is all. It does not scan for malware, stop password guessing or patch a vulnerable plugin.
Free certificates from Let’s Encrypt, and the ones bundled with most hosting plans, made HTTPS the default, which is good. It also means criminals get padlocks too. A phishing site can have a perfectly valid certificate. Treat HTTPS as the entry ticket, not the defence.

Do I need two-factor authentication on my website login?
Yes, for every account that can change content, install plugins or see customer data. Two-factor authentication (2FA) means a stolen or guessed password alone is not enough to get in.
Most compromised small sites fall to weak or reused passwords, not clever exploits. Add 2FA to your CMS admin, your hosting control panel and your domain registrar account. The last two get forgotten, and losing either is worse than losing the site itself. An authenticator app is better than SMS codes. Also remove accounts for people who have left, and give contractors the lowest role that does the job.
What are security headers and should I bother?
Security headers are instructions your server sends with each page that tell the browser to behave more cautiously, which blocks whole classes of attack for very little effort. They are worth setting up, and a developer can do it in an afternoon.
The ones I’d look at first:
- Strict-Transport-Security (HSTS): tells browsers to only ever use HTTPS for your domain.
- Content-Security-Policy: limits which scripts and resources a page may load, which helps against injected code. It is the fiddliest to get right, so test before enforcing it.
- X-Content-Type-Options: stops browsers guessing file types.
- Referrer-Policy: controls how much URL information leaks to other sites.
- Frame protection (X-Frame-Options or frame-ancestors): stops other sites embedding yours to trick visitors into clicking.
Free online header checkers will grade your site and show what is missing. Be careful with Content-Security-Policy on a shop, because payment and analytics scripts can break if the policy is too strict.
How often should I update my website?
Apply security updates to your CMS, themes, plugins and server software as soon as practical, ideally within days of release, and review everything at least monthly. Outdated plugins are among the most common ways small WordPress and WooCommerce sites get compromised.
Update discipline is boring and it works. Keep a short list of what is installed, delete anything unused (a deactivated plugin can still be exploited if its files remain), and avoid abandoned plugins that have not been updated in a long time. If updates frighten you because they once broke the site, the fix is a staging copy where you test changes first, not leaving things unpatched. Many hosts offer one-click staging.
What makes a backup sensible?
A sensible backup is automatic, stored away from your web server, kept for several weeks and proven to restore. If the backups live on the same server as the site, an attack or hosting failure can take both.
Daily is right for most brochure sites. A shop taking orders may need more frequent database backups, since a day of lost orders is painful. Keep at least one copy with a different provider. Then, once or twice a year, actually restore one to a test environment. A backup you have never restored is a hope, not a plan.
What else is worth doing for small business sites?
Choose hosting that patches its servers, offers a web application firewall and supports current PHP versions, since cheap bargain plans often skimp here. Limit login attempts, or rename or protect the default admin URL if your CMS allows it. Use unique, long passwords through a password manager.
If you collect customer data, remember UK GDPR: a breach that puts people at risk may need reporting to the Information Commissioner’s Office, normally within 72 hours of becoming aware of it. The government’s National Cyber Security Centre also publishes free, plain-English guidance for small organisations.
My suggested order of work: switch on 2FA today, run a headers check this week, set a monthly update slot in your diary, and restore a backup to a test site before the end of the month.
Frequently Asked Questions
Is a free SSL certificate good enough?
For encryption, yes. A free certificate from Let’s Encrypt encrypts traffic just as well as most paid ones. What it does not provide is protection against hacked plugins, weak passwords or malware, so you still need the other measures.
How do I know if my WordPress site has been hacked?
Warning signs include unfamiliar admin users, strange redirects, odd pages in search results, a host warning, or Google flagging the site as unsafe. A security plugin scan and your host’s malware scanner can help confirm it. Restore from a clean backup if needed.
Do small businesses really get targeted by hackers?
Yes. Most attacks are automated and hunt for known weaknesses such as outdated plugins and weak logins, regardless of size. The UK government’s Cyber Security Breaches Survey regularly reports that many businesses experience attacks or breaches.
How often should I back up my website?
Daily suits most business sites. An ecommerce site with frequent orders may need database backups several times a day. Store copies off the server and test a restore periodically so you know they work.
Should I use a security plugin on WordPress?
A reputable security plugin can add login limits, file scanning and firewall rules, which is useful. It does not replace updates, 2FA and backups. Install only one, from an actively maintained developer, to avoid conflicts and slowdowns.




Leave a Reply