WordPress Security Checklist: 15 Settings to Change on Day One

A fresh WordPress install is secure in the narrow sense — core is well tested — but wide open in practice: a guessable admin account, a public login page, comments switched on, and no backup at all. This wordpress security checklist fixes that in about an hour, using settings already in your dashboard plus two free plugins.

Work through the 15 items in order — the first three build your safety net. Prices are in US dollars, checked on 19 November 2026.

In this guide

WordPress security checklist dashboard with a shield, padlock and checklist on a laptop screen

First, Build Your Safety Net

Security work starts with the ability to recover, so the first three items here come before any hardening.

1. Update WordPress core to 7.1.5

WordPress 7.1.5 was released on 18 November 2026, fixing 20 security issues in core — including a privilege-escalation flaw that WordPress says could lead to remote code execution, two SQL injection flaws, and a Multisite privilege-escalation issue. WordPress recommends updating immediately; version 7.2 is planned for 8 December 2026, but do not wait for it — see the official announcement on wordpress.org.

Go to Dashboard > Updates and click Update Now, then update every plugin and theme too: an out-of-date plugin is a far more common entry point than out-of-date core. Leave automatic background updates on for minor releases.

2. Set up automatic backups with UpdraftPlus

A backup is the only item on this wordpress security checklist that can undo a hack. Install UpdraftPlus (free) from Plugins > Add New, then go to Settings > UpdraftPlus Backups and connect Google Drive or Dropbox. Never store your only backup on the same server as your site.

Schedule daily database backups and weekly file backups on a small site, daily for both on a busy one. UpdraftPlus Premium starts at $70 a year for up to 2 sites (Personal plan, checked 19 November 2026) and adds incremental backups and automatic backups before updates. That is the safety net this wordpress security checklist is built on.

3. Run a restore drill before you need one

Once your first backup completes, restore it to a staging copy or a local test install and confirm the site actually loads — in UpdraftPlus, use Settings > UpdraftPlus Backups > Existing Backups > Restore.

Time the drill — if it takes 40 minutes while you are calm, it will take longer at 2 a.m. during a real incident. Write down the steps and keep them with your login details.

WordPress backup and restore with a cloud, a database and a shield

Lock Down Logins and Users — WordPress Security Checklist Essentials

Most WordPress attacks are automated scripts trying common passwords against the login page, thousands of times a day. These five settings in this wordpress security checklist make that attack expensive and mostly pointless.

4. Replace weak passwords with a password manager

Every account needs a unique password of at least 16 characters, generated, never reused. Go to Users > Profile > Account Management, click Generate Password, and save it in a password manager.

Do this for Administrator and Editor accounts first, then for everyone else: one weak author password is enough to compromise a whole site, because the attacker only needs the weakest account, not yours.

5. Turn on two-factor authentication

Two-factor authentication (2FA) means a stolen password alone is not enough to log in. Wordfence includes 2FA free: go to Wordfence > Login Security and enable it for every Administrator, then for Editors. Each user scans a QR code with an authenticator app.

Keep your recovery codes somewhere safe, and test the login once with 2FA on before you log out, so you know it works.

6. Delete or rename the "admin" username

Half of every brute-force attack guesses the username "admin" first. If your site still has an account called "admin", remove it — a basic wordpress security checklist step: create a new Administrator with an unusual username under Users > Add New, log in as it, then delete "admin" under Users > All Users and assign its posts to the new account.

Also check Users > Profile and change the Display name publicly as setting so it does not reveal your username — your author archive URL uses it, so a matching display name hands attackers half of your login for free.

7. Limit login attempts

WordPress lets anyone try to log in as many times as they like — exactly what brute-force bots want. Wordfence free adds login-attempt limiting: go to Wordfence > All Options > Brute Force Protection and lock out an IP after 5 failed attempts for at least 1 hour.

Check the lockout log occasionally: a sudden spike can be an early warning that your site has been noticed.

8. Change your login URL

Every bot knows your login page lives at /wp-login.php and /wp-admin. Moving it removes you from the laziest 90% of automated attacks: use a plugin such as WPS Hide Login and set the new URL to something unguessable, for example /my-secret-door-482/.

After changing it, update your bookmarks and tell your team, and keep a note of the new URL somewhere safe — the old one will return a 404.

WordPress security settings with two-factor authentication and a strong password

Close the Back Doors in WordPress Core

WordPress ships with several features most sites never use — each one a small extra door, and this part of the wordpress security checklist closes the ones you do not need.

9. Disable XML-RPC if you do not use it

XML-RPC is an old remote-publishing protocol at /xmlrpc.php. Unless you publish from the WordPress mobile app or a tool that needs it, you do not need it — but attackers use it for brute-force attacks, because one request can test hundreds of passwords. Disable it under Wordfence > All Options > General Wordfence Options, as this wordpress security checklist advises.

Check first whether anything you use depends on it: Jetpack and the WordPress mobile app both use XML-RPC, so if you rely on either, leave it enabled.

10. Disable file editing from the dashboard

By default, an Administrator can edit theme and plugin files from Appearance > Theme File Editor and Plugins > Plugin File Editor — so anyone who gains admin access can edit your code directly. Close that hole by adding one line to wp-config.php, above "That’s all, stop editing!":

define( 'DISALLOW_FILE_EDIT', true );

Edit wp-config.php through your host’s file manager or FTP, never through the dashboard editor you are about to disable. After saving, the editor menu items disappear — but theme and plugin updates still work.

11. Set correct file permissions

File permissions decide who can read, write, and execute each file on your server. The safe values are 644 for files, 755 for directories, and 600 or 640 for wp-config.php, which holds your database password. Change them in bulk with your host’s file manager or an FTP client.

Never set anything to 777: anyone on the server could write to the file. If a plugin asks for 777, find another plugin.

12. Harden your comment settings

Spam comments can carry malicious links that damage your search rankings and your readers’ trust. Go to Settings > Discussion and turn on Comment author must fill out name and e-mail, hold comments with two or more links for moderation, and require manual approval for a first-time commenter.

Also uncheck Allow link notifications from other blogs (pingbacks and trackbacks) unless you actively use them — pingbacks have been abused for denial-of-service attacks.

Add the Layers Only a Plugin or Host Can Provide

The settings above are free and built in. These last three items on the wordpress security checklist add the monitoring and encryption WordPress core does not provide.

13. Install and configure Wordfence

Wordfence is the most widely installed WordPress security plugin, with over 5 million active installations, and its free version covers the essentials: a firewall, a malware scanner, brute-force protection, and 2FA. Install it from Plugins > Add New and enable the firewall in Wordfence > Firewall > Manage Firewall using "Extended Protection" mode.

The main difference between free and paid is timing: free users receive firewall rules and malware signatures 30 days after Premium users. Wordfence Premium costs $149 a year for one site (checked 19 November 2026) and adds real-time rules and signatures, the real-time IP blocklist, country blocking, and priority support. Wordfence has announced Premium will rise to $199 a year from 3 December 2026 — see Wordfence’s pricing announcement.

14. Force HTTPS and add security headers

HTTPS encrypts traffic between your visitors and your server, and Google treats it as a ranking signal. Most hosts now offer a free SSL certificate — check your hosting panel first. Our guide to the best hosting for a small business website explains what to look for. Once the certificate is active, go to Settings > General and make sure both addresses start with https://, then install Really Simple SSL to redirect remaining HTTP traffic.

Security headers are extra instructions your server sends to browsers — the most useful are Strict-Transport-Security (HSTS), X-Content-Type-Options, and X-Frame-Options. Many hosts set these for you; if yours does not, Really Simple Security can add them. Headers are a small but real part of this wordpress security checklist.

15. Schedule regular malware scans

A security plugin only helps if it actually runs, which is why scanning has its own step in this wordpress security checklist. In Wordfence, go to Wordfence > Scan > Scan Options and Scheduling and set a full scan to run at least weekly — daily on a site that takes payments or publishes often.

When a scan finishes, read the results the same day. Unknown files in wp-content/uploads are a common sign of a backdoor, because that folder should only contain media. If a scan finds something you do not recognise, restore from a clean backup (item 3).

WordPress Security Checklist: Free vs Paid

Is the free tier enough? For a new site with no income, yes. The free tiers of Wordfence and UpdraftPlus cover every setting here; what you pay for is speed — faster threat intelligence, faster backups, and a human to call when things go wrong.

Feature Wordfence Free Wordfence Premium ($149/yr) UpdraftPlus Free UpdraftPlus Premium ($70/yr)
Firewall and malware scanner Yes Yes, real-time rules — —
Two-factor authentication Yes Yes — —
Country blocking and IP blocklist No Yes — —
Scheduled backups — — Yes Yes
Incremental backups — — No Yes
Priority support No Yes No Yes

All prices checked 19 November 2026. Wordfence Premium rises to $199 a year from 3 December 2026. UpdraftPlus Premium covers up to 2 sites ($70 a year), 10 sites ($95), 35 sites ($145), unlimited sites ($195), and Gold ($399 with 50 GB of storage).

Do These First: Your Prioritised Summary

If you only have 30 minutes, do these five and come back for the rest.

  1. Update to WordPress 7.1.5 (item 1) — a security release from 18 November 2026 that patches 20 issues. Two minutes of work.
  2. Set up a daily backup to remote storage (item 2) — the only setting that undoes a hack. This is the heart of the wordpress security checklist.
  3. Turn on 2FA and use generated passwords (items 4 and 5) — this alone defeats almost every brute-force attack. Few wordpress security checklist steps pay off this fast.
  4. Delete the "admin" username and limit login attempts (items 6 and 7) — cheap, permanent, and effective.
  5. Install Wordfence and enable the firewall (item 13) — free, and it covers the monitoring the other settings do not. That is the whole wordpress security checklist in miniature.

Then work through items 8 to 12 and 14 to 15 in a second sitting. If you are still setting up, our guide on how to start a WordPress website walks through the full setup, and our how to speed up WordPress guide covers performance. That is the full wordpress security checklist, done.

Frequently Asked Questions

Is WordPress secure out of the box?

WordPress core is well maintained — version 7.1.5 was released on 18 November 2026 to fix 20 issues. But a default install has a guessable admin username, a public login page, no 2FA, and no backup.

Do I need a paid security plugin?

Not on day one. Wordfence free covers a firewall, malware scanning, brute-force protection, and 2FA, and UpdraftPlus free covers scheduled backups. Pay $149 a year for Wordfence Premium when your site earns money or holds customer data — the value is real-time threat intelligence, not the 30-day delay free users accept. That is the honest answer for any wordpress security checklist.

Will changing my login URL break my site?

No, as long as you remember the new address and update your bookmarks: the plugin only redirects the standard /wp-login.php address, and your dashboard, posts, and plugins are untouched. Do not treat a hidden login page as a substitute for strong passwords and 2FA — it is one layer of the wordpress security checklist, not the whole defence.

How often should I back up my WordPress site?

Daily for the database and at least weekly for files on a small site; daily for both on a busy site or a shop. Keep at least one backup off the server and restore-test it at least once.

What should I do first if my WordPress site gets hacked?

Do not panic-delete files. First, change all passwords and revoke sessions. Second, restore the most recent clean backup from before the hack. Third, run a full Wordfence scan, update everything, and check for unknown admin users under Users > All Users. Then work through this wordpress security checklist again from item 1.

Conclusion

Security is not a plugin you install once; it is a set of habits you repeat. This wordpress security checklist gives you the day-one version: update immediately, back up somewhere safe, lock down logins with 2FA, close the doors you do not use, and let a scanner watch the rest.

Revisit this wordpress security checklist every three months; our SiteGround vs Hostinger comparison shows how a good host handles SSL, backups and updates.

3 thoughts on “WordPress Security Checklist: 15 Settings to Change on Day One”

Leave a Comment