WordPress

WordPress Security Checklist: 20 Steps for 2026

A practical WordPress security checklist for business owners: what to do today, weekly, monthly and quarterly to keep plugins, logins and backups safe.

SJ SinanSJ Sinan9 min read
In this article

Most small business owners only think about WordPress security after something goes wrong. A client calls to say your site shows a strange pharmacy ad, Google marks it as dangerous, or your host suspends the account for sending spam.

This WordPress security checklist helps you avoid that day. It’s written for owners and marketing managers, not security experts, and it’s split into what to do today, every month and every few months.

Quick answer: A good WordPress security checklist covers six areas: keep WordPress, plugins and themes updated; remove anything you don’t use; lock down logins with strong passwords and two-factor authentication; run automatic off-site backups; use a firewall; and give each user only the access they need. Most hacks come from outdated plugins.

Why Small WordPress Sites Get Hacked

Hackers rarely pick your site by hand. Automated bots scan millions of sites for known weak spots, then break in wherever they find one.

The weak spots are mostly plugins. Patchstack’s State of WordPress Security in 2026 report counted 11,334 new vulnerabilities in 2025, 42% more than the year before. It found 91% of them in plugins, 9% in themes, and only 6 in WordPress core.

The same report found that heavily exploited flaws were used in attacks a median of just 5 hours after they became public, and 46% of vulnerabilities had no fix from the developer when they were disclosed. That’s why “I’ll update next month” isn’t a plan.

WordPress Security Checklist at a Glance

How oftenTaskTime needed
Once (today)Two-factor login, strong passwords, firewall, backups, remove unused plugins2 to 3 hours
WeeklyApply plugin, theme and core updates15 minutes
MonthlyCheck users, test a backup restore, review security alerts30 minutes
Every 3 monthsReview plugins, PHP version, hosting and admin access1 hour

Do These Today

1. Update Everything

Update WordPress core, every plugin and every theme. Turn on automatic updates for minor core releases and for well-maintained plugins. For plugins that run your shop or forms, update on a staging copy first.

2. Delete What You Don’t Use

Deactivated plugins and unused themes can still be attacked, because their files remain on the server. Delete them. Keep one default theme as a backup and remove the rest.

3. Replace Abandoned and Nulled Plugins

If a plugin hasn’t been updated in over a year, find a maintained alternative. Never install “nulled” (pirated) premium plugins or themes. They often come with hidden malware, and they never get security updates.

4. Lock Down Logins

  • Use a unique, long password for every admin account, saved in a password manager.
  • Turn on two-factor authentication for every user who can publish or change settings.
  • Limit login attempts to slow down password-guessing bots.
  • Don’t use “admin” as a username.

The official WordPress hardening guide recommends two-step authentication on top of strong passwords.

5. Set Up Off-Site Backups

Backups are your insurance. Run them daily for active sites and store copies somewhere other than your hosting account, like cloud storage. A backup stored only on the hacked server can be infected or deleted along with it. If the worst happens, my guide on how to fix a hacked WordPress site walks through the cleanup step by step.

6. Add a Firewall

A web application firewall (WAF) blocks known attacks before they reach WordPress. You can use a cloud firewall like Cloudflare, or a security plugin with a firewall such as Wordfence or Patchstack. Don’t rely on your host alone. Patchstack’s tests found standard hosting defenses blocked only 26% of attacks on known WordPress vulnerabilities.

7. Use HTTPS Everywhere

Make sure your SSL certificate is active and that every page loads over https://. Most hosts include a free certificate.

Harden the Setup

8. Disable the File Editor

Add this line to wp-config.php to stop anyone from editing plugin and theme code from the dashboard:

define( 'DISALLOW_FILE_EDIT', true );

If an attacker gets into an admin account, this removes one easy way to plant malicious code.

9. Check File Permissions

The WordPress hardening guide recommends 644 for files and 755 for folders. Your host can check this for you.

10. Keep PHP Up to Date

Old PHP versions stop getting security fixes. The official PHP support table lists which versions are still supported. You can see yours under Tools, Site Health, Info.

11. Give Users the Lowest Role They Need

A writer needs the Author or Editor role, not Administrator. Remove accounts for former staff, freelancers and agencies the day the work ends.

12. Protect Forms From Spam

Add a CAPTCHA or honeypot to contact, comment and registration forms. Turn off user registration if you don’t need it.

Every Month

  1. Apply all pending updates, and read the changelog for big plugins first.
  2. Review the user list and remove anyone who no longer needs access.
  3. Test one backup by restoring it to a staging site. An untested backup isn’t a backup.
  4. Check Google Search Console for security issues and manual actions.
  5. Read the alerts from your security plugin or firewall.

Every Three Months

  1. Review every plugin: is it still needed, updated and well reviewed?
  2. Check your PHP version and hosting plan.
  3. Change shared passwords and check who has access to your hosting, domain and DNS accounts.

What Your Host Does and What You Do

Many owners assume their host handles security. Good hosts protect the server, but the site is still your job.

Usually the hostUsually you (or your developer)
Server software and operating system updatesWordPress, plugin and theme updates
Network firewall and DDoS protectionUser accounts, passwords and two-factor
Basic server backupsOff-site backups you control and test
Free SSL certificateChoosing safe, maintained plugins

If keeping up with this list feels like too much, a WordPress maintenance plan covers updates, backups and monitoring for you. My guide to WordPress maintenance cost explains what that usually costs. For the full routine beyond security, see my WordPress website maintenance checklist.

Frequently Asked Questions

Do I need a security plugin for WordPress?

Most small sites benefit from one, mainly for the firewall, login protection and alerts. But a plugin can’t make up for missed updates or weak passwords. If you already use a cloud firewall like Cloudflare and your host scans for malware, you may only need a light plugin for login protection and two-factor authentication.

How often should I update WordPress plugins?

Check for updates at least once a week, and apply security updates as soon as they come out. Attackers can start using a public flaw within hours. For important plugins like WooCommerce or form builders, test the update on a staging site first, then update the live site the same day.

Is WordPress itself secure?

WordPress core is well maintained and had very few reported vulnerabilities in 2025, according to Patchstack. Most hacked sites are broken into through outdated or poorly coded plugins and themes, weak passwords or old PHP versions. A WordPress security checklist like this one focuses on those weak points.

How do I know if my WordPress site has been hacked?

Common signs include unknown admin users, strange redirects, spam links or pages you didn’t create, a Google “This site may be hacked” warning, or a host alert about malware. Check Google Search Console’s security issues report and run a scan with your security plugin or host’s malware scanner.

How much does it cost to keep a WordPress site secure?

Basic protection can cost almost nothing if you do the work yourself with free tools. Premium security plugins usually cost around $100 to $300 a year. A maintenance plan that includes updates, backups and monitoring typically costs a monthly fee, which is far less than cleaning up a hacked site and recovering lost rankings.

Should I change the WordPress login URL?

It can cut down automated login attempts and the noise they create, but it isn’t real protection on its own. Attackers can still find a hidden login page. Strong unique passwords, two-factor authentication, limited login attempts and up-to-date plugins matter much more. Treat a custom login URL as a small extra, not a security plan.

Do I need two-factor authentication on WordPress?

Yes, at least for every administrator account. WordPress doesn’t include two-factor authentication by default, so add it with a trusted plugin. Even if a password is stolen or guessed, the attacker can’t log in without the second code. It takes a few minutes to set up and blocks one of the most common ways sites get taken over.

Final Thoughts

You don’t need to be a security expert to keep WordPress safe. Most of the work in this WordPress security checklist is simple and regular: update quickly, delete what you don’t use, protect logins, and keep tested backups somewhere safe.

Save the checklist, set a monthly reminder, and work through it. If you’d like me to review your site’s security setup, send me a message with your website and I’ll tell you what needs fixing first.

Found this useful? Share it:
SJ Sinan

Written by

SJ Sinan

Web Developer, SEO Specialist & Digital Marketer

I build fast WordPress and Next.js websites, rank them on Google and run Meta and Google Ads for businesses around the world. Everything I write here comes from real client work.

Comments

Be the first to share your thoughts or ask a question.

Leave a comment

Your email will not be published. Comments appear after review.

Free consultation

Want Me to Do This For You?

Tell me about your business and goals. I will suggest the right service and send you a clear, fixed quote.

  • Free 30-minute strategy call
  • Honest advice, even if you need less
  • Fixed quote within 24 hours