# WordPress security basics every site owner should know

URL: https://ekom.blog/wordpress-security-basics-every-site-owner-should-know/
Published: 2023-06-15 · Updated: 2026-11-03
Author: Ekom
Topics: WordPress

> Most hacked WordPress sites aren't targeted, they're just easy. Why security is an SEO issue too, and the handful of basics that do most of the work, without buying a pile of plugins.

Nobody thinks their small WordPress site is worth hacking. A bakery in Surulere, a church website, a freelancer's portfolio. Who'd bother?

Bots would. Most WordPress hacks aren't personal. Automated scripts scan millions of sites for known weaknesses: an old plugin, a weak admin password, a forgotten test install. If yours is easy, it gets hit. Then it's used to send spam, host scam pages or redirect your visitors somewhere unpleasant.

I think security gets treated as a "techy" topic site owners can ignore. It isn't. It's one of the few things that can wipe out your search traffic overnight, and the basics are not hard.

## Why it's an SEO problem, not just an IT problem

When a site is compromised, the damage usually shows up in search first:

- Spam pages appear on your domain (often in languages you don't speak, selling things you don't sell) and get indexed.

- Google may flag the site with a warning in the results or in Chrome, and visitors turn back before they arrive.

- Search Console shows a Security issue, and your traffic falls while it's there.

- Cleaning up can take weeks: removing the code, requesting a review, getting spam URLs out of the index.

All the content and SEO work in the world doesn't help if the site is serving someone else's pages.

## The basics that do most of the work

### 1. Keep everything updated

Most WordPress hacks use known holes in old versions of plugins and themes. The fix for the hole already exists. It just hasn't been installed.

- Update WordPress core, plugins and themes regularly. Weekly is a good rhythm.

- Turn on automatic updates for plugins you trust and that rarely break things. WordPress has supported this from the dashboard since version 5.5.

- Update PHP too. Your host's control panel usually lets you choose the version.

The worry is always "what if an update breaks the site?". Fair. That's what backups and staging sites are for, which brings us to...

### 2. Have backups you've actually tested

A backup you've never restored is a hope, not a backup.

- Back up files and the database.

- Store copies somewhere other than the same server (cloud storage, your host's off-site backup).

- Keep several days or weeks of history, so you can go back to before a hack started, not just yesterday.

- Try a restore at least once, on a staging site, so you know how it works before you need it at 2am.

### 3. Fewer plugins, better plugins

Every plugin is code from someone else running on your site. Fewer plugins means fewer doors.

- Delete plugins you don't use. Deactivated still means the files are on the server.

- Before installing, check when it was last updated, how many sites use it, and whether the developer answers support questions.

- Never use "nulled" (pirated) premium plugins or themes. They're a favourite way to hide malware. The free download is the price of your site.

I wrote about doing this audit properly in auditing your WordPress plugins.

### 4. Logins that aren't an open door

- Strong, unique passwords for every admin account. A password manager makes this painless.

- Two-factor authentication for anyone who can publish or install things. Several free plugins add it.

- No user called "admin". It's the first username bots try.

- Give people the lowest role they need. Writers don't need to be administrators. When someone leaves, remove their account the same week.

- Limit login attempts, either through your host, your security plugin or a small dedicated plugin.

### 5. HTTPS everywhere

An SSL certificate is free with most hosts now (often through Let's Encrypt). It protects logins and form submissions, and browsers warn visitors about sites without it. Make sure every version of your domain redirects to the https one.

### 6. A host that takes it seriously

Cheap shared hosting is fine for many sites, but ask: does the host scan for malware? Keep server software updated? Isolate sites from each other? Offer backups? I covered what to look for in choosing a WordPress host.

## Do you need a security plugin?

Plugins like Wordfence, Sucuri and others add firewalls, malware scanning and login protection. They can be useful, especially on shared hosting.

My view: they're a layer, not a strategy. A security plugin on a site with ten outdated plugins and a shared admin password is a lock on a door with no wall around it. Do the basics above first. Then add one security plugin if you want scanning and alerts, and don't stack several. They tend to clash and slow the site down.

## Signs something is wrong

- Search Console reports a security issue or a sudden jump in indexed pages you don't recognise.

- Searching site:yourdomain.com shows pages you never created.

- New admin users you didn't add.

- Visitors (often on mobile) say they were redirected somewhere strange.

- Your host suspends the account or warns about outgoing spam.

If you see any of these, change all passwords, restore a clean backup or get professional clean-up, update everything, then ask Google for a review in Search Console.

## Related reading

- Auditing your WordPress plugins before they slow you down

- Choosing a WordPress host for a content site

- The WordPress SEO checks I run first on any site

When did you last restore a backup of your site, rather than just make one? If the answer is "never", that's the job for this week.

---

From Ekom (https://ekom.blog/). More: https://ekom.blog/llms.txt
