Fix Once: The Settings That Close the Common Doors
Most WordPress security work falls into two piles. One pile is settings you correct a single time. The other is checks you repeat on a calendar. The first pile blocks the automated attacks that hunt for old plugins, easy logins, and files anyone can write to, and this guide is for owners of live sites who want to know which pile each task belongs in, and which tasks they would rather hand off.
Updates for Core, Plugins, and Themes
Most compromises start with software that is behind on patches. WordPress documentation says minor and security releases of core install themselves, while plugins and themes update on their own only in special cases the WordPress security team controls for critical vulnerabilities (WordPress upgrade documentation, checked October 2026). Everything else sits until a person clicks Update.
Close that gap in two ways. Switch on automatic updates for plugins you trust, and give the remaining ones a fixed weekly slot rather than a good intention. Batches of updates are also the usual cause of broken sites, so test a large batch on a staging copy first. When one does take a site down, the white screen of death guide shows how to find the fatal error.
Delete Plugins and Themes You Have Stopped Using
Deactivating a plugin does not make its code safe. The files stay on disk, and a vulnerable file can often be requested straight from the browser without WordPress loading it. A theme you moved away from works the same way. Delete both.
Then look at what remains. In the Plugins screen, check the last-updated date on each one. A plugin untouched for years, or one the WordPress.org directory has closed, will never ship the patch you are waiting for.
Paid plugins carry a second risk. A lapsed license usually stops updates without any banner on the site, so the security fix simply never arrives. Keep a list of each paid plugin and its renewal date, or have the renewals managed for you.

Accounts, Passwords, and Roles
The WordPress hardening guide advises against easily guessed usernames such as admin and recommends two-step authentication (WordPress hardening guide, checked October 2026). In practice that means a different password for every person, a password manager so the rule is livable, and the lowest role that still lets each person work. Someone who writes posts needs Author, not Administrator.
Then open Users and read the whole list. The accounts that cause trouble are the ones that outlived their purpose: a former employee, an old agency login, a login made for a single task two years ago. You should be able to name every Administrator.
Switch Off the Built-In File Editor
Out of the box, an administrator can edit plugin and theme PHP from the dashboard. A stolen login therefore becomes code running on your server in one step. The hardening guide's remedy is one line in wp-config.php: define( 'DISALLOW_FILE_EDIT', true );.
The same guide lists permissions of 755 for directories and 644 for files, and says wp-config.php should be readable only by you and the web server, which usually means 400 or 440. Read what your host actually applies instead of assuming it matches.
SFTP Over FTP, and HTTPS on Every Page
Plain FTP sends your password unencrypted. The hardening guide recommends SFTP, and most clients need only a protocol setting changed. The same thinking applies to visitors: serve every page over HTTPS, redirect the HTTP address, and let the certificate renew automatically. When a certificate lapses, every visitor sees a browser warning until someone fixes it.
Guard Wp-config.php and the Database Prefix
This file holds your database credentials and secret keys. The hardening guide gives two options: move it one directory above the WordPress install, or block web access with a rule in .htaccess, such as <Files "wp-config.php"> Require all denied </Files>. A server that is not Apache needs the same rule in its own syntax.
The guide also suggests replacing the default wp_ table prefix, which it says can stop at least some SQL injection attempts. On a new build that is a cheap choice. On a site with years of data it means renaming tables and updating option rows, so take a database backup immediately before you try it, or skip it.
A Filter in Front of the Site
A web application firewall sits at the network edge and screens requests before WordPress sees them. It cuts down on scanners probing for known vulnerable plugin paths. It cannot help when an attacker has a valid password, or exploits a plugin flaw with a request that looks ordinary. For that reason it supports the settings above and replaces none of them. Edge protection covers the firewall, bot, and cache rules for a domain.
Keep Checking: What Needs a Calendar
Settings drift. An update flips a default, a developer adds a login, the host bumps a PHP version. This second half is about catching those changes before a visitor does.
Restore a Backup Before You Need One
Until you have restored a backup, you only believe it works. Confirm it includes the database and not just files, that it lives somewhere other than the server it protects, and how many days of history it keeps. Suppose a site was infected three weeks ago. A seven-day window then holds only infected copies.
Retention is the number people forget. Backups overwritten after a week cover a bad update and nothing slower. Also settle who performs the restore when the dashboard will not load, and write the steps down. Do one practice restore to a staging copy so the first attempt is not in the middle of an outage.
Malware Scans and File Change Checks
A scanner compares your files with known-good copies and known-bad patterns. Run it daily. The risk window is the time between a file changing and anyone noticing, and a monthly scan leaves that window open for weeks. A report alone does not finish the job. Someone must read it, remove what it found, close the entry point, and scan again.
Test the Page, Not Only the Server
An uptime monitor tells you the server answered. It stays green while the contact form has disappeared or the checkout button has stopped rendering. Add a check that loads your key pages and compares what is on them, plus a test that submits the form. These catch the quiet damage that follows a plugin update, the kind that costs weeks of leads before anyone looks.
Watch the PHP Version
Hosts retire old PHP versions on their own schedule, and a plugin that fell behind can fail the day that change lands. Look at the version your site runs every few months and try an upgrade on staging before the host forces one. Unsupported PHP versions also stop getting security fixes from the PHP project, a separate reason to move.
The One-Hour Quarterly Review
Book an hour four times a year and walk the same list. List each plugin and theme and delete anything unused. List each user and remove anyone who should not be there. Confirm that the newest backup exists, and restore it to staging if a year has passed. Check the PHP version, the certificate expiry date, and the renewal date of each paid plugin. Finally, open the contact form, submit it yourself, and confirm the message arrives.
Write down what you find, even when the answer is nothing. A dated note listing which items changed lets the next person, or you in twelve months, trust the list without starting over.
If You Find a Compromise Today
Order matters here. First, turn on maintenance mode so visitors stop receiving the infection. Second, back up the infected state for later study. Third, change every administrator password and replace the secret keys and salts in wp-config.php, which signs everyone out. Fourth, restore from a copy that predates the problem, update everything, and hunt for the account or file the attacker used. Cleaning only the symptom and leaving that entry point open is why the same infection returns two weeks later.
Questions Owners Ask About This List
How long does the fix-once half take? On a typical site, an afternoon, mostly spent on the user audit and the hosting checks. Restoring a backup to staging adds more time the first time.
Is a security plugin enough? A plugin can scan files and limit login attempts. It will not renew your license, restore a backup, or tell you the contact form broke. Treat it as one item on the list.
Should I change the table prefix on an old site? Usually no. The gain is small and the risk is real, so reserve it for new builds.
What if my host already does some of this? Ask for specifics: backup retention in days, whether the database is included, and how often files are scanned. Then fill the gaps yourself.
Who should have Administrator? Only people you can name who need to change plugins, users, or settings. Everyone else gets a lower role.
Handing the Checklist Off
Our WordPress maintenance plans run updates for plugins, themes, and core on a schedule, take backups every 24 hours with 180 days of cloud retention, scan for malware every 24 hours, and monitor uptime around the clock. Visual checks on key pages and form checks twice a day cover the quiet breakage, and firewall protection and offsite activity logging are included. If you would rather have hosting and upkeep under one roof, managed WordPress hosting puts the site behind an enterprise firewall at the network edge, and WordPress Pro combines hosting, updates, speed, and security. The wider WordPress services page lists the rest.









