Home Website SecurityWordPress Website Security Checklist

WordPress Website Security Checklist

by Iffaris
12 views 19 minutes read
WordPress security checklist for protecting a website from hackers and malware

A hacked website rarely announces itself. One morning your rankings slip, a customer reports a strange redirect, or your host suspends the account, and suddenly you are paying for a cleanup that could have been avoided. The good news is that most WordPress compromises are not sophisticated attacks. They come from outdated plugins, weak passwords, careless permissions and missing backups. A practical WordPress security checklist closes those gaps before an attacker finds them.

This guide gives you a complete WordPress security checklist with 35 steps, grouped by area so you can work through it in a single afternoon and then repeat the important parts every month. Whether you manage one brochure site or a portfolio of client websites, the same principles apply. Each step explains what to do, why it matters, and how to do it without breaking your site.

Why Every Site Owner Needs a WordPress Security Checklist

WordPress powers a huge share of the web, and that popularity makes it the most attractive target for automated attacks. Bots do not care whether your site is a small plumbing company or a large publication. They scan thousands of domains an hour looking for known vulnerabilities, exposed login pages and weak credentials. If your site matches the pattern, it gets attacked.

A written WordPress security checklist turns security from a vague worry into a repeatable process. Instead of asking whether your site is “secure enough,” you can see exactly which controls are in place and which are missing. It also makes handovers easier. When a developer, a freelancer or a new team member takes over, the WordPress security checklist shows the standard your site is held to.

Security also protects your search visibility. Google flags hacked sites, injects warnings into results, and can remove pages entirely when spam or malware is detected. Recovering lost rankings takes far longer than the cleanup itself. If you want a deeper look at what an infection looks like in practice, read our guide on WordPress malware and how to detect and remove it.

How to Use This WordPress Security Checklist

Do not try to perfect everything at once. Work through the WordPress security checklist in three passes:

  • Pass one, the essentials: updates, strong logins, two-factor authentication and backups. These steps stop the majority of real-world attacks.
  • Pass two, the hardening layer: firewall, file permissions, user roles and security headers.
  • Pass three, the ongoing routine: scanning, logging and monthly reviews.

Before you start, take a full backup and make a note of your current plugins, themes and user accounts. If you are building a brand new site, it is easier to apply this WordPress security checklist during setup. Our WordPress website setup guide shows where security fits into a clean installation.

Part 1: Hosting and Server Security

Your site is only as safe as the server it runs on. Even a perfectly configured WordPress installation can be compromised through a weak hosting environment, so the first section of any WordPress security checklist starts here.

1. Choose a Security-Focused Host

Look for a host that offers server-level firewalls, malware scanning, isolated accounts, automatic backups and a clear incident response process. Cheap shared hosting that packs hundreds of sites onto one account is a common cause of cross-site infections, where one neglected site on the server infects its neighbours. Managed WordPress hosting costs more, but it usually includes protections that would otherwise require paid plugins.

2. Run a Supported PHP Version

Old PHP versions stop receiving security patches. Check your hosting dashboard and move to a currently supported release, then test the site on a staging copy before switching. Newer PHP versions are also faster, which helps your WordPress website speed as a bonus.

3. Use SFTP or SSH Instead of FTP

Plain FTP sends your username and password in clear text. Switch to SFTP or SSH for every file transfer, and disable standard FTP accounts you no longer use. This single change removes an easy credential-theft opportunity.

4. Force HTTPS Across the Entire Site

An SSL certificate encrypts the data moving between your visitors and your server, and browsers now warn users away from sites without one. Install a certificate, redirect all HTTP traffic to HTTPS, and fix mixed-content warnings. If you need a refresher on how certificates work, our explainer on SSL certificates and why your website needs HTTPS covers the basics.

Part 2: Updates, Plugins and Themes

Outdated software is the number one entry point for WordPress attacks. Every plugin you install adds code you did not write and cannot fully audit, which is why this section carries the most weight in any WordPress security checklist.

5. Keep WordPress Core Updated

WordPress releases security patches regularly. Minor releases install automatically on most sites, but major versions often need a manual push. Update promptly, and test on staging first if the site is business critical.

6. Update Every Plugin Promptly

Most successful WordPress hacks exploit a known vulnerability in a plugin that already has a patch available. The window between a vulnerability being published and attackers exploiting it is often measured in hours. Enable automatic updates for trusted plugins, or review updates at least weekly. Skipping this step undermines every other item on your WordPress security checklist.

7. Update Your Themes

Themes contain PHP code just like plugins do. Keep your active theme updated, and if you use a child theme, check that parent theme updates do not break your customisations.

8. Delete Unused Plugins and Themes

Deactivated plugins can still be exploited because their files remain on the server. Remove anything you are not using. Keep one default theme as a fallback and delete the rest. A smaller codebase means a smaller attack surface, and your admin dashboard becomes easier to manage too.

9. Vet Plugins Before You Install Them

Before installing a plugin, check the number of active installations, the date of the last update, the support forum activity and whether it is compatible with your WordPress version. Avoid plugins that have been abandoned for a year or more. Our guide on how to choose the right WordPress plugins walks through a simple evaluation process.

10. Never Use Nulled or Pirated Software

“Free” copies of premium plugins and themes are one of the most common sources of backdoors. They often contain hidden code that gives the distributor access to your site. If you cannot afford a premium tool, use a legitimate free alternative from the official repository.

Part 3: Login and Admin Security

The login page is the front door of your site, and bots hammer it constantly. Brute-force attacks, credential stuffing and password-guessing tools run around the clock. This part of the WordPress security checklist makes that door much harder to force.

11. Retire the Default “admin” Username

Attackers assume your administrator account is called “admin.” Create a new administrator with a unique username, move your content to it, and delete the old account. Also make sure your public author URL does not reveal the login name.

12. Use Strong, Unique Passwords

Every account on your site needs a long, random password that is not reused anywhere else. A password manager makes this painless. Aim for at least sixteen characters, and never share credentials over email or chat. Weak passwords can cancel out the rest of your WordPress security checklist.

13. Enable Two-Factor Authentication

Two-factor authentication stops an attacker even when they have your password. Require it for every administrator and editor account, using an authenticator app rather than text messages where possible. For many sites, this is the single most effective control on the entire WordPress security checklist.

14. Limit Login Attempts

By default, WordPress lets someone try unlimited passwords. Install a login-limiting feature, or use your firewall, to lock out an IP address after a handful of failed attempts. This turns a brute-force attack from a minutes-long job into an impractical one.

15. Protect or Move the Login URL

Changing the default /wp-login.php address will not stop a determined attacker, but it removes a large amount of automated bot noise. You can also restrict access to the login page by IP address if only a few people need it. For a complete walkthrough, see our dedicated guide on how to secure your WordPress login and admin area.

16. Add CAPTCHA and Idle Session Timeouts

A CAPTCHA on login, registration and comment forms blocks simple bots. Pair it with automatic logout for idle sessions so an unattended laptop does not become a security hole.

Part 4: User Roles and Permissions

More people with more access means more risk. Many breaches begin with a low-level account that was granted far more power than it needed. Treat access control as a core pillar of your WordPress security checklist.

17. Apply the Principle of Least Privilege

Give each person the lowest role that lets them do their job. Writers need the Author or Contributor role, not Administrator. Reserve administrator access for the one or two people who truly manage the site. Least privilege is one of the cheapest wins in any WordPress security checklist.

18. Audit Your User List Every Quarter

Open the Users screen and look for accounts you do not recognise, old contractors, and any administrator that should not exist. Unknown administrator accounts are a classic sign of compromise.

19. Give Every Person Their Own Account

Shared logins make it impossible to know who changed what, and they make it harder to revoke access cleanly. Create individual accounts, even for short-term freelancers.

20. Remove Access the Day Someone Leaves

When a developer, agency or employee finishes working with you, deactivate their account the same day. Do the same for hosting, domain registrar, analytics and any connected third-party tools.

Part 5: Firewall, Scanning and Threat Protection

Updates and strong logins prevent most attacks, but a firewall and scanner catch what slips through. This layer of the WordPress security checklist adds active defence.

21. Install a Web Application Firewall

A web application firewall filters malicious requests before they reach WordPress. Cloud-based firewalls sit in front of your server and block bad traffic at the edge, which also reduces the load on your hosting. Plugin-based firewalls run inside WordPress and are easier to set up, though they use more server resources. A firewall is the layer of the WordPress security checklist that keeps working while you sleep.

22. Schedule Regular Malware Scans

Run automated scans at least weekly, comparing your core files against the official WordPress versions and checking for suspicious code in plugins, themes and uploads. Make sure scan alerts go to an email address someone actually reads.

23. Scan for Known Vulnerabilities

A vulnerability scanner tells you when a plugin or theme on your site has a published security flaw, even before an update is available. If you want to understand how these tools work and which ones are worth using, our partner site has a clear breakdown of the website vulnerability scanner options available to small business owners.

24. Block Bad Bots and Rate-Limit Requests

Aggressive crawlers and scrapers can slow your site and probe for weaknesses. Use your firewall or hosting tools to rate-limit suspicious traffic and block known malicious user agents and IP ranges.

Part 6: Backups and Recovery

Backups do not prevent attacks, but they decide how painful an attack is. A site with a clean, recent backup can recover in an hour. A site without one may lose everything. No WordPress security checklist is complete without a tested recovery plan.

25. Automate Your Backups

Manual backups get forgotten. Schedule automatic backups of both files and database. Daily backups suit most business sites, while busy shops and membership sites may need real-time backups.

26. Store Backups Off the Server

If backups live in the same account as your site, an attacker or a server failure can take both. Send copies to separate cloud storage such as a different hosting account, Amazon S3 or Google Drive. Offsite storage is a non-negotiable line in a WordPress security checklist.

27. Test Your Restore Process

A backup you have never restored is only a hope. At least twice a year, restore a copy to a staging site and confirm that pages, images, forms and logins all work.

28. Keep Several Restore Points

Malware sometimes sits quietly for weeks before it activates. Keep at least thirty days of backups so you can roll back to a version from before the infection began.

Part 7: Hardening Files, Database and Configuration

Hardening reduces what an attacker can do even after they get a foothold. These technical steps in the WordPress security checklist take minutes to apply and are worth doing on every site.

29. Disable the Built-In File Editor

By default, administrators can edit plugin and theme code from inside the dashboard. If an attacker gains admin access, that editor lets them plant malicious code instantly. Add the following line to your wp-config.php file to turn it off. It is a small change, but it earns its place on every WordPress security checklist:

define( 'DISALLOW_FILE_EDIT', true );

30. Protect wp-config.php and Sensitive Files

The wp-config.php file contains your database credentials and security keys. Restrict access to it through your server configuration, and block direct access to files such as .htaccess, readme files and backup archives that sometimes get left in the root directory.

31. Set Correct File Permissions

Folders should generally be set to 755 and files to 644, with wp-config.php set to 600 or 640 where your host allows. Permissions that are too open let other users or processes on the server modify your files.

32. Secure the Database and Disable XML-RPC if Unused

Use a unique database user with a strong password, and give it only the privileges WordPress needs. If you do not use the XML-RPC feature for remote publishing or certain apps, disable it, since attackers use it to amplify brute-force attempts.

33. Turn Off Directory Browsing

If directory listing is enabled, visitors can see the contents of folders such as /wp-content/uploads/. Disable it in your server configuration so files and folder structures are not exposed.

34. Add Security Headers

HTTP security headers tell browsers how to handle your content. Useful headers include Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options and a Content-Security-Policy suited to your site. Test your configuration with a free header-checking tool and adjust carefully so you do not block your own scripts. Headers are easy to forget, so keep them written into your WordPress security checklist.

Part 8: Monitoring and Ongoing Maintenance

Security is not a one-time project, and a WordPress security checklist is only useful if you return to it. New vulnerabilities appear weekly, and a site that was safe in January can be exposed by June. The final step of the WordPress security checklist is to keep watching.

35. Log Activity and Set Up Alerts

An activity log records logins, plugin installs, user changes and file modifications. When something suspicious happens, such as a new administrator created at 3 a.m., you will know quickly. Pair the log with uptime monitoring and make sure Google Search Console notifications reach your inbox, because Google often reports security issues there first. If you are new to the tool, our guide to the Google Search Console performance report is a good starting point.

Monthly WordPress Security Checklist Routine

Once the 35 steps of the WordPress security checklist are in place, maintenance becomes a short monthly routine. Here is a compact version of the WordPress security checklist you can use as a recurring task:

  • Apply pending core, plugin and theme updates
  • Review the user list and remove stale accounts
  • Check the latest malware and vulnerability scan reports
  • Confirm backups ran and that offsite copies exist
  • Review login attempts and firewall blocks for unusual spikes
  • Verify the SSL certificate has not expired
  • Check Google Search Console for security or manual-action warnings

Adding these tasks to a wider monthly routine is smart, since security overlaps with performance and SEO health. Our WordPress maintenance checklist covers the full monthly process, and the technical review in our technical SEO checklist helps you spot crawl and indexing problems caused by hacks.

Common Mistakes That Undermine a WordPress Security Checklist

Even careful site owners slip up while following a WordPress security checklist. Watch for these frequent errors:

Relying on a single plugin. One security plugin is not a strategy. It will not fix weak passwords, outdated themes or poor hosting. A WordPress security checklist works because it layers several controls.

Ignoring staging. Updating blindly on a live site can break it, and fear of breakage is why many owners delay updates. Use a staging site so updates are safe to apply quickly.

Forgetting about small sites. An old test site or a forgotten landing page on the same server can be the weak link that exposes everything else. Include every property in your WordPress security checklist review.

Skipping the human factor. Phishing emails aimed at your team are a common route to your admin account. Train everyone who touches the site to spot suspicious links and requests.

Never checking the 404 and redirect logs. Sudden spikes in unexpected 404 errors or odd redirects can signal a compromise. Learn how to find and fix 404 errors for SEO, and treat unexplained changes as a warning rather than an annoyance.

What to Do If Your Site Gets Hacked

Even with a strong WordPress security checklist, no site is perfectly immune. If you suspect a compromise, act in this order:

  1. Stay calm and take a snapshot. Back up the infected site so you have evidence and can investigate later.
  2. Put the site in maintenance mode to protect visitors while you work.
  3. Change every password, including WordPress, hosting, database, FTP or SFTP, and your email account.
  4. Scan and identify the infection using a malware scanner and your hosting provider’s tools.
  5. Restore from a clean backup taken before the infection, or remove the malicious code manually if you are experienced.
  6. Update everything and remove the vulnerable plugin or theme that allowed the entry.
  7. Request a review from Google if your site was flagged, through Search Console. Keep a copy of your WordPress security checklist beside your backup and hosting credentials so recovery is faster.
  8. Review your WordPress security checklist and close the gap that let the attacker in.

For a detailed removal process, follow our walkthrough on how to detect and clean WordPress malware. If the work feels too risky to do alone, hire a professional cleanup service rather than guessing, because a partial cleanup often leads to reinfection within days.

Security Tips for Local Business and Service Websites

If you run a site for an electrician, plumber, appliance repair company or similar local business, your website is a lead-generation machine, and downtime costs real money. A hacked contact form can quietly redirect enquiries to a competitor or a scam page, and you may not notice for weeks. Prioritise the following on top of your standard WordPress security checklist, because a WordPress security checklist matters most where uptime equals revenue:

  • Test your contact and booking forms monthly, including the notification emails
  • Protect your Google Business Profile and website with separate, strong passwords
  • Monitor your phone-number click tracking for sudden drops
  • Keep a clean copy of your service pages so you can restore them quickly

For a broader overview aimed at small business owners, our partner site explains how to secure a website with practical tips that complement this WordPress security checklist. You can also explore its guide to website security in a maintenance plan and its website maintenance checklist for security and performance tasks.

Tools That Support Your WordPress Security Checklist

You do not need a long list of tools, but a few categories help you follow your WordPress security checklist with less effort:

  • All-in-one security plugins that combine a firewall, scanner and login protection
  • Backup plugins or host-level backups with offsite storage
  • Password managers for generating and storing credentials
  • Uptime monitors that alert you the moment the site goes down
  • Activity-log plugins that record every important change

Tools support your WordPress security checklist but never replace it. Choose tools that are actively maintained and well reviewed, and avoid stacking several plugins that do the same job, since overlapping features can conflict and slow the site. Remember that each security plugin is itself code that needs updating, so keep the list short and purposeful.

Final Thoughts

Website security does not require advanced technical skills. It requires consistency. The 35 steps in this WordPress security checklist cover hosting, updates, logins, permissions, firewalls, backups, hardening and monitoring, and together they block the overwhelming majority of attacks aimed at WordPress sites. Start with the essentials, build up to the advanced hardening steps, and turn the monthly routine into a habit. Treat your WordPress security checklist as a living document that grows with your site.

Print this WordPress security checklist, share it with your developer, and schedule time on your calendar to review it. A few hours of work today can save you from downtime, lost rankings and expensive emergency repairs later. Your site is a business asset, and it deserves the same protection as any other.

Frequently Asked Questions About the WordPress Security Checklist

How often should I review my WordPress security checklist?

Review the essentials such as updates, backups and scan results monthly, and perform a full audit of the entire WordPress security checklist every quarter. Check immediately after any major change, such as installing a new plugin, switching hosts or adding a new team member.

Is a security plugin enough to protect my site?

No. A security plugin is one layer, not a complete solution. Strong passwords, updates, backups, correct permissions and good hosting matter just as much. That is why a full WordPress security checklist covers every layer instead of relying on a single tool.

What is the most important step on the list?

If you only have time for three actions, keep everything updated, enable two-factor authentication, and set up automatic offsite backups. Those three steps prevent or recover from the large majority of incidents, and they form the core of any WordPress security checklist.

Can WordPress security affect my SEO?

Yes. Hacked sites can be flagged with warnings in search results, deindexed, or filled with spam pages that dilute your rankings. Following a WordPress security checklist protects the visibility you have worked to build.

Do small websites really get attacked?

Absolutely. Attacks are automated, so bots target sites by vulnerability rather than by size or popularity. A small local business site with an outdated plugin is just as likely to be hit as a large one.

How much does it cost to secure a WordPress site?

Many of the steps in this WordPress security checklist are free, including updates, strong passwords, two-factor authentication and hardening changes. Paid costs usually come from managed hosting, a premium firewall and offsite backup storage, which together are far cheaper than a professional malware cleanup.

Related Posts

Leave a Comment

Focus Mode