Introducing BetterShield: a free WordPress security plugin
Updated by Nazmul Hasan Rupok on
A list of security warnings tells you something needs attention, then leaves the work with you: what each one means, what to change, and what that change might break. BetterShield is a free WordPress security plugin that takes the next step. It finds what is open on your site, explains it in plain language, and, where a one-click fix exists, closes it once you approve.
It is available from WordPress.org.
Quick summary
- 72 read-only checks give your site a score out of 100 and a grade from A to F.
- 30 one-click hardening fixes, all but one off until you choose them, each with a preview first.
- A way back in if you are locked out: a recovery link, printed codes and safe mode.
- Two-factor, passkeys, login protection, an activity log and file checks are included.
- Optional external services stay off until chosen. The default file and plugin checks contact WordPress.org and, for supported WPDeveloper Pro plugins and Ultra, the publisher’s checksum servers.
The idea: close what is open
BetterShield starts from one question: what on this site is open that does not need to be? An administrator account nobody has used in six months. The dashboard file editor left on. Installer tools left behind after a migration.
For each finding, it tells you what it is, why it matters and what could break if you act on it. Where a one-click fix exists, it shows exactly what the fix will change, and all but one of the fixes wait for your choice. A check that could not run is never counted as a pass.
Leave with one verified improvement
You do not need to turn on every option to make progress.
- Recover
Save a usable way back in.
- Review
Read the finding and its limits.
- Verify
Make one change, test the result.
Recover
- What this means
- Confirm the recovery email actually arrived and keep recovery material outside WordPress. Do this before changing sign-in.
- Your next check
- Know how to contact the host if WordPress itself cannot run.
Review
- What this means
- Choose a relevant finding, inspect its evidence and identify what could depend on the current behavior.
- Your next check
- Separate an actionable setting from an unverified check or a dependency you intentionally keep.
Verify
- What this means
- Use the preview, apply the selected fix, then exercise the affected workflow. The score is a summary, not proof of safety.
- Your next check
- Record the result and rollback path before choosing the next improvement.
How this free WordPress security plugin works, in three steps
1. Run the audit and read your score
Activation runs a read-only audit straight away: 72 checks across Sign-in & accounts (26), Public information about your site (16), Updates & extensions (11), Server (8) and Site settings (11). Nothing on the site is changed to produce the result.
The score combines 60 points for setup essentials and 40 for site health. Setup findings use their own item weights; other findings reduce site health by severity. Any open critical finding caps the total at 74. A snoozed finding still counts; a finding marked not applicable does not.
On BetterShield › Overview, the Findings card opens on Worth doing first: up to three open findings, those with a one-click fix first, then the heaviest. Apply fix applies a fix, and How to fix shows why a finding matters and what could break. On Findings, Remind me later snoozes a finding for 7 or 30 days, and Not applicable sets aside one that will never apply. All 72 are on the checklist, and the Score and findings guide covers both screens.
2. Preview a fix, then apply it
BetterShield has 30 one-click fixes across Protection › Hardening and Protection › Login & Access. All but one start off: Server detail protection is on from activation.
Press Preview the change to see what a fix would do; the preview changes nothing. Then turn the switch on. To take the fix off, turn the switch off, and any files it wrote are put back as they were.
Two fixes say up front what taking them off cannot reach. Sign everyone out on demand signs other people out, and those sessions stay ended. Strict HTTPS (HSTS) (HSTS) stays in browsers that saw a long setting until it expires, so start with five minutes. See the Hardening guide.
3. Keep a way back in
At activation, BetterShield emails a single-use recovery link to the site’s admin address. Open it and press Pause protection and continue: safe mode pauses BetterShield’s protections for one hour, your settings stay as they are, and the next link is issued straight away.
A link lasts 90 days. On Protection › Recovery you can replace it, and Issue recovery codes gives you eight printed, single-use codes that work without email. Before any change to how people sign in, BetterShield checks that one of these works. For a sign-in fix or a two-factor requirement it also wants them checked within the last day, and offers Go ahead anyway, which is logged. See the Locked out guide.
Sign-in protection, two-factor and passkeys
A few protections start at activation, and each can be switched off: refusing other plugins’ requests to cloud-metadata addresses, sign-in attempt limits (by default, 5 failed sign-ins in 15 minutes pause that connection for 15 minutes), a hidden bot check on the login, registration, WooCommerce account and comment forms, and limits on public forms.
Two-factor works with any authenticator app, with 10 single-use backup codes, and is never enforced until the app is proven to work. You can require it by role, with a 14-day grace period by default. Passkeys sign people in with a fingerprint, face or device PIN, and only the public half of the key is stored. See the Login & Access and Two-factor and passkeys guides.
Activity log, file checks and incidents
- Activity log: sign-ins, account and role changes, password resets, and plugin, theme and core changes, with who and when. Filter, search and Export CSV, with 30 days of history. Each finished day is sealed, so an edit or deletion opens a high-severity finding.
- File changes: WordPress core and directory plugins are compared with the official copies WordPress.org publishes. Put the official file back restores a changed file, and yours is kept in quarantine, never deleted. Your theme, wp-config.php and .htaccess are watched for changes.
- Incidents: related access and file changes are grouped into one incident. Prepare response plan lists actions; nothing changes until you press Apply selected actions, and BetterShield checks again afterward.
AI assistants, with you in charge
BetterShield has a built-in MCP server, so an assistant such as Claude, ChatGPT, Cursor or Codex can read your site’s security. On Agents › Connect, Three steps to a connected assistant has a switch for each step, all off by default:
- Let my agent read security information offers 27 read-only abilities, from your score and findings to the activity log and file check.
- Let agents act: changes that can be undone right away, anything heavier once you agree is optional.
- Let an assistant connect to this site opens the connection.
With changes allowed, the fixes that reverse right away apply directly. Heavier changes, such as the sign-in fixes or putting a changed file back, arrive as a plan a person agrees to. Creating accounts or credentials, changing recovery options, weakening two-factor or alerts, lifting lockouts and deleting log rows never happen through a connection. Limits: 5 changes of one kind and 30 plans per hour, counted for each connection. See Connect an AI assistant.
BetterShield Hub for many sites
BetterShield Hub is a free, optional dashboard for people who look after several sites. Connect each site from BetterShield › Hub, choose Read this site only or Read this site and apply fixes that can be undone, and approve it on the site’s own consent page. Hub’s browser interface shows a plan before applying or undoing a finding fix. Its free workspace also offers baselines, client reports, shared alerts and status pages. The optional Hub link sends events and heartbeats; it is separate from the approved reading connection and optional account-free vulnerability-advisory requests. Disconnect on the site ends its Hub connection. The free plugin needs no Hub account. See BetterShield Hub.
Hub also offers a Monday or daily workspace summary grouping the updates reported across your sites. An agent that cannot open a browser can use an approval link and a six-digit code. On connected Ultra sites, supported Cloudflare rule actions show the site’s plan before you confirm them.
What leaves your site
BetterShield contacts WordPress.org for core and directory-plugin file checks. Supported WPDeveloper paid plugins also use publisher checksums, without an account. Those checks send the version and plugin information needed for the request, without intentionally sending account emails or usernames. External services still receive ordinary connection metadata such as the server or proxy address.
With Ultra installed, file checks can also contact bettershield.ai for its publisher checksums. Other optional contacts wait for your choice, including vulnerability intelligence and usage data (asked once in Quick Setup, where Skip sends nothing), the breached-password check, your own AI provider and BetterShield Hub. What BetterShield contacts lists what each one sends.
Checks and limits
The free plugin does not scan for or remove malware. Ultra adds optional, targeted request protection through a usable Hub link and applicable current rules. Vulnerability checks are optional. With consent in Settings, BetterShield asks BetterShield Hub for published advisories using Wordfence Intelligence data and matches versions on your site. No Hub account or paid license is required. A failed refresh is shown as unavailable or stale, never as a clean result.
BetterShield Ultra
BetterShield Ultra adds premium features for the sites you manage. It needs the free plugin on the same site and adds things like two-factor setup at sign-in for chosen roles, trusted devices, Slack and webhook alerts, a scheduled client report, temporary access, access reviews, settings watch and up to 365 days of activity history, with 90 as the default. Everything above is in the free plugin. See Ultra.
How to get started
- Go to Plugins › Add Plugin, search for “BetterShield”, then install and activate it, or get it from WordPress.org. It needs WordPress 6.7 and PHP 8.0 or newer.
- Activation runs the first audit, emails your recovery link and opens Quick Setup.
- On Your way back in, tick I received the recovery email or press Download offline recovery codes.
- Review Quick Setup’s five initial fixes and their compatibility notes, then apply the ones that fit your site.
- Press Open the Overview and start with Worth doing first.
The Install and set up guide walks through every step.
What a useful first session should produce
Aim to leave the first session with a recovery method you can reach, a short list of relevant findings and one verified improvement. A higher score is a useful by-product, not the acceptance test.
Worked example (fictional): a small publication has a public author directory and no need for dashboard code editing. Its owner disables the file editor, verifies that ordinary editing and publishing still work, and keeps the author-directory dependency in mind before changing public user listing. The same owner leaves HSTS on its short trial instead of turning on every hardening switch at once.
A practical first-session record has four lines:
- Recovery: where the current link or codes are stored, and who can use the host account if WordPress cannot run. Record locations, not secret values.
- Priority: the finding selected and why it matters on this site.
- Change: the exact setting and the relevant dependency or exception.
- Verification: what you tested, what happened and how you would undo it.
Keep backups, software updates and hosting access in that plan. BetterShield’s audit and file comparisons cover defined checks; they do not prove a backup can be restored or that an unknown compromise has been removed. If you are installing it because something already looks wrong, preserve the relevant records and use the first-hour response guide alongside the setup process.
Common mistakes
- Changing sign-in before saving a way back in. Keep the recovery email or printed codes somewhere off the site first.
- Starting HSTS at six months. Use five minutes first. A long setting stays in browsers after you turn the fix off.
- Two plugins doing the same job. Use Quick Setup to choose which plugin keeps login limits and two-factor.
- Deleting the plugin to remove fixes. Saved settings and written server rules can remain after deletion, but runtime controls need the plugin to run. Undo unwanted server rules before removal and verify the remaining protections.
Frequently asked questions
Is BetterShield really free?
Yes. The audit, all 30 fixes, two-factor, passkeys, login protection, the recovery link, the activity log, incident response, the file check and the MCP server are free. There is no account and no payment.
Will the fixes break my site?
Each fix previews what it will change and, except the cloud-metadata block, stays off until you turn it on. Turning it off removes what it changed. Where that cannot reach everything, such as sessions ended by a key change, the fix tells you first.
What happens if I lock myself out?
Open your latest recovery link and press Pause protection and continue. BetterShield’s protections pause for one hour and your settings stay as they are. Printed codes work without email, and wp bettershield recover does the same from WP-CLI.
Conclusion
BetterShield is built for the moment after an audit: you know what is open, you see what a fix will change, and you decide. Apart from refusing requests to cloud-metadata addresses, no hardening fix is switched on until you choose it, and recovery should be prepared and tested before you need it.
The features page has the full list, and support is there if you get stuck.