Most website compromises are not sophisticated attacks. They are unlocked doors: an outdated plugin, a reused password, a form that accepts anything. This checklist covers the fundamentals that prevent the majority of incidents, in the order we apply them.
1. HTTPS everywhere
An SSL certificate is free (Let's Encrypt) or bundled with most hosting. There is no excuse left: browsers flag non-HTTPS sites as "Not secure", customers notice, and Google treats it as a baseline signal. Force all traffic to HTTPS with a permanent redirect.
2. Keep everything updated
Outdated software is the number one entry point, especially on platforms with plugins. Put update responsibilities in writing: who checks, how often, what gets logged. If your site is custom-built, ask your developer how they patch, good teams have an answer ready.
3. Backups you have actually tested
A backup is only real if you have restored from it. The minimum: automatic daily database backups, weekly file backups, stored off the web server, with one documented test restore per quarter. After a compromise, the restore point is the difference between a bad morning and a dead business.
4. Passwords and logins
Admin accounts need unique, long passwords and should not be named "admin". Add rate limiting on login attempts so machines guessing passwords get locked out. Where your team size justifies it, two-factor authentication on the CMS is cheap insurance.
5. Forms: the front door for bots
Every public form needs server-side validation (never trust the browser), protection against spam bots (hidden honeypot fields work well), and rate limiting per visitor. Forms that email raw input also need output escaping: that is how contact forms become spam relays.
6. Principle of least privilege
Content editors do not need administrator rights. Give each person the narrowest access that lets them work, and remove accounts the day someone leaves. Audit the user list quarterly, dormant accounts are standing invitations.
7. Watch your own site
Google Search Console's security reports, your hosting's malware scanner and a monthly manual look at your own pages catch most problems early. Cheap, boring, effective.
If you do only three things
- Turn on HTTPS with forced redirects.
- Set up automatic off-server backups and test one restore.
- Write down who updates what, and when.
Want a straight answer about your current site's posture? Request our security basics review: we will check these fundamentals and report in plain language, no scare tactics.
