Most hacked WordPress sites were not targeted by a clever criminal. They were found by an automated scanner that tried a known weakness in an outdated plugin, a reused password or an exposed login page. The attacker never knew or cared whose site it was. That is both the bad news and the good news: attacks are mostly mechanical, so a handful of sensible habits stops the large majority of them.
This is a complete guide to WordPress security for site owners, not just developers. You will learn how sites actually get compromised, which defenses matter most, what to harden step by step, how to choose tools, and what to do on the day something goes wrong. Each section links to a deeper guide when you want to go further.
One principle runs through everything below. Security is not a product you install. It is a set of layers, a routine and a plan. No plugin makes a neglected site safe, and no site is ever perfectly safe. The goal is to be a harder, less rewarding target than the next site, and to recover quickly if the worst happens.
Key takeaways
- Most compromises come from vulnerable plugins and themes, weak or stolen credentials, and neglected updates, not from WordPress core itself.
- Think in layers: hosting, updates, access control, a firewall, monitoring and backups. Each catches what the others miss.
- The best habits cost little: update promptly, delete unused code, use unique passwords with two-factor authentication, and give people only the access they need.
- Backups are your safety net, but only if they are stored off the server and you have tested a restore.
- Have an incident plan before you need one. Panic is expensive.
How WordPress sites actually get hacked
Understanding attack routes tells you where to spend effort. The most common ones are below, roughly in order of how often they matter for ordinary sites.
Vulnerable plugins and themes
WordPress core is maintained by a large team and receives security fixes quickly. The weak point is the ecosystem: tens of thousands of plugins and themes written by people with very different skills and time. A flaw in one plugin can expose every site that runs it, and automated scanners search the internet for exactly those sites within hours or days of a disclosure. Vulnerability databases and plugin security researchers publish such flaws regularly, which is the reason updating quickly matters so much.
Abandoned and nulled software
A plugin that no longer receives updates will never get its flaws fixed. And nulled software, meaning pirated copies of premium plugins and themes, is a classic way to get a backdoor installed. The few dollars saved are not worth it. Buy from the vendor, or choose a maintained free alternative.
Weak, reused and stolen credentials
Attackers run credential stuffing, trying email and password pairs leaked from other breaches, and brute force attacks against the login form. If you or any of your users reuse a password, a breach at an unrelated service can become a breach of your site. Two-factor authentication and unique passwords largely neutralize this.
Insecure hosting and server setup
On cheap shared hosting, a compromised neighbor account may in some setups be a route to yours, especially when accounts are poorly isolated. Outdated server software, weak file permissions and exposed control panels add to the risk. Quality hosting with account isolation, current software and server-level protections removes a lot of these concerns.
Compromised accounts through phishing
Someone emails your editor a convincing message, they enter their password on a fake login page, and the attacker is in. Training and two-factor authentication matter here more than any plugin.
Insecure custom code and exposed files
Custom snippets, old backup files left in the web root, exposed configuration files, debug logs, and directory listings all leak information or provide an entry. They are easy to avoid and easy to forget.
What attackers want
Few attackers want to deface your home page. The common goals are sending spam, hosting phishing pages, injecting hidden links for search spam, redirecting visitors to scam sites, stealing customer data, mining resources and using your server to attack others. Many compromises are invisible to you for weeks. That is why monitoring matters as much as prevention.
The layered security model
No single defense is perfect, so use several that fail in different ways.
- Hosting and server. Isolation, current software, server firewall, secure transport.
- Updates and software hygiene. Core, plugins and themes current, unused code removed.
- Access control. Strong unique passwords, two-factor authentication, least privilege.
- Hardening. Configuration choices that shrink the attack surface.
- Firewall and monitoring. Blocking known bad traffic and noticing changes.
- Backups and recovery. A tested way to return to a clean state.
You can have a decent site with layers one to three and six. Layers four and five add value on top. The mistake is to buy layer five, a plugin, and neglect layers one, two and six.
Layer 1: choose and configure hosting well
Hosting is the foundation. Good hosting prevents many problems you would otherwise have to patch yourself.
What to look for
- Isolation between accounts, so a problem on another site cannot reach yours.
- Current, supported PHP versions with an easy way to change them.
- Automatic server-level patching of the operating system and web server.
- A server or network firewall, and some protection against brute force and denial-of-service traffic.
- Free HTTPS certificates that renew automatically.
- Automated off-server backups with simple restore, though you should still keep your own.
- SFTP or SSH, not plain FTP.
- Helpful support that can assist after an incident.
Keep PHP current
Old PHP versions stop receiving security fixes. Running one is a risk even if everything else is perfect. Our guide to PHP versions and WordPress performance explains how to check your version and upgrade safely. The WordPress requirements page also recommends a modern release and notes that the oldest supported versions are end-of-life. See wordpress.org/about/requirements.
Use HTTPS everywhere
HTTPS encrypts traffic between visitors and your site, including login credentials. WordPress.org lists HTTPS support as part of its recommended requirements. Force HTTPS for the whole site and for the admin area, and fix mixed content warnings.
Use SFTP, not FTP
Plain FTP sends your password in the clear. The WordPress hardening documentation recommends SFTP for this reason. Disable any FTP accounts you do not use.
Layer 2: updates and software hygiene
This is the highest-return security task for most sites.
Update core, plugins and themes
The WordPress developer documentation on hardening says plainly: always run the latest version, since older releases no longer receive security fixes. See Hardening WordPress. Check for updates at least weekly, and quickly when a security fix is announced.
Decide how to handle automatic updates
Automatic background updates reduce your exposure window, but they carry a small chance of breaking something while you are not looking. The right answer depends on your site and your safety net. Read our risk guide to WordPress auto-updates for a decision framework. A common compromise: automatic updates for security releases and small plugins, manual updates with a staging test for complex or revenue-critical ones.
Test risky updates on staging
For shops, membership sites and anything with custom code, test major updates on a copy first. Our guide to staging sites shows how to create one and push changes safely.
Delete what you do not use
Deactivated plugins and themes still sit on the server. If they contain a vulnerability, an attacker may reach the file directly, even though it is not active. Delete unused plugins and themes, keeping at most one default theme as a fallback. Fewer components mean a smaller target and less to update.
Vet plugins before installing
Before adding a plugin, check these points on its wordpress.org page or the vendor site.
- When was it last updated, and is it tested with your current WordPress version?
- How many active installations does it have, and what is the support forum like?
- Does the author respond to bug and security reports?
- Is there a known vulnerability history, and how quickly was it fixed?
- Do you really need it, or does something you already have do the job?
For picking maintained tools by use case, see our use-case guide to the best WordPress plugins.
Avoid nulled themes and plugins
Never install pirated premium software. It is a leading way for malware to arrive pre-installed.
Layer 3: access control
Many compromises are not hacks at all. Someone simply logged in. Control who can log in and what they can do.
Strong, unique passwords
Use a password manager. Every account on your site should have a long, random, unique password. This includes hosting, domain registrar, email, SFTP and database accounts, not just WordPress logins. The email account used for password resets is especially sensitive, since controlling it means controlling everything it can reset.
Two-factor authentication
A second factor, such as a code from an authenticator app, a hardware key or a passkey, stops stolen passwords from being enough. Turn it on for every administrator and editor account, and ideally for all users who can publish. Our guide, how to add two-factor authentication to WordPress, compares the methods and shows how to roll it out without locking anyone out.
Least privilege
Give each person the lowest role that lets them do their job. Most contributors do not need to be administrators. Fewer powerful accounts mean fewer prizes for an attacker and less damage from a mistake. Read our guide to WordPress user roles and least-privilege access for a practical approach, including how to audit existing users.
Do not use the username admin
If an account is named admin, attackers already know half the login. Create a new administrator with a unique name, move the content over, and delete the old one. Also make sure the public author display name does not reveal the login username.
Limit login attempts
Rate limiting login attempts slows brute force attacks. Many security plugins and some hosts provide it. Combined with two-factor authentication, it makes password guessing close to pointless.
Review users regularly
Remove accounts for people who left, contractors whose project ended and test accounts. Check for administrators you do not recognize. Do this quarterly, and monthly on bigger sites.
Application passwords and API access
WordPress supports application passwords, which let tools and integrations use the REST API without your main password. They can be revoked individually. Review them in each user profile and remove the ones you do not recognize. If you use automation tools that control WordPress, such as NibWP, scope their access carefully and give the integration its own account with limited rights.
Layer 4: hardening WordPress itself
Hardening reduces what an attacker can do even after finding a small opening. The WordPress documentation covers these items in its hardening article. None is a cure on its own, so think of them as inexpensive extra locks.
File permissions
The documentation recommends that files be owned by your account and writable only by you, with the WordPress root, wp-admin, wp-includes and the plugins folder not writable by the web server where possible. A common baseline is 755 for directories and 644 for files, and a stricter setting for wp-config.php. Many managed hosts set this for you. If your host does, leave it alone. If you change permissions, apply them carefully, since wrong values can break updates and uploads.
Protect wp-config.php
This file holds database credentials and security keys. Restrict its permissions, and on Apache you can deny web access to it through an htaccess rule. You can also move it one directory above the WordPress root, although the documentation notes that experts disagree on how much this helps.
Disable the file editor
By default, administrators can edit plugin and theme code in the dashboard. If an attacker gets into an admin account, that is a direct way to run their code. Add this line to wp-config.php.
define( 'DISALLOW_FILE_EDIT', true );
The documentation states this will not stop an attacker who can upload files, but it may block some attacks and costs nothing. Edit code through SFTP or version control instead.
Consider disabling file modifications
A stricter setting, DISALLOW_FILE_MODS, also blocks plugin and theme installs and updates from the dashboard. It is strong, but it means all updates must be done another way, so use it only if you have a deployment process.
Unique security keys and salts
wp-config.php contains keys and salts used to protect login cookies. Make sure they are long, random and unique to your site. If you suspect a compromise, changing them logs everyone out, which helps cut off stolen sessions.
Change the default database prefix
Using a prefix other than wp_ offers a small amount of protection against some automated attacks. It is not a major defense, and changing it on an existing site is risky, so apply it mainly to new installs.
Limit database privileges
The WordPress documentation notes that you can restrict the database user to basic data operations, but revoking structural privileges can break updates, so do this only if you have tested backups. Never share a database user between sites.
Secure the XML-RPC and REST API where appropriate
XML-RPC is an older remote access interface that attackers sometimes abuse for brute force attempts. If you do not use it, for example with certain mobile apps or older integrations, you can block it at the server or through a plugin. The REST API is used by the block editor and many plugins, so do not turn it off wholesale. Restrict only what you understand.
Hide version information and disable directory listing
Removing version numbers from page source is a minor measure, and does not replace updating. Disabling directory listing, so browsers cannot list folder contents, is more useful. Most hosts already do it.
Protect the login page
Options include rate limiting, a CAPTCHA on login, IP allowlisting for admin if your team has fixed addresses, and moving the login URL. Moving the URL reduces automated noise but is obscurity, not security, so do not rely on it alone. For forms and registration, see our guide to stopping WordPress spam.
Security headers
HTTP headers such as HSTS, X-Content-Type-Options and a frame restriction add browser-side protection. A full content security policy is powerful but easy to misconfigure, so introduce it in report-only mode and test.
Disable PHP execution in uploads
The uploads folder should hold images and documents, not running code. Blocking PHP execution there stops a common step in attacks: uploading a script disguised as a file and then calling it. Hosts and security plugins can apply a rule for you.
Layer 5: firewalls, scanning and monitoring
This is where security plugins and services come in. They fall into a few groups, and understanding the groups makes choosing easier.
Web application firewalls
A firewall filters malicious requests before they reach vulnerable code. Cloud firewalls act at the DNS or network edge, before traffic reaches your server. Endpoint firewalls run as a plugin inside WordPress and filter after the request reaches your server. Edge firewalls reduce server load and block earlier, while endpoint firewalls understand WordPress better. Some hosts provide a firewall at the server level too.
Malware scanners
Scanners compare your files with known-good copies, and look for signatures of known malware. They are useful for detection, but they are a smoke alarm, not a fire door. Scanning inside the same server that was compromised can also be bypassed by a clever attacker.
Vulnerability monitoring
These tools check your installed plugins, themes and core versions against a database of known vulnerabilities and alert you. Because most compromises start with known flaws in outdated software, this is very high value for its cost. Some services also provide virtual patching, which blocks the exploit at the firewall until you can update.
Activity logs and file integrity monitoring
An activity log records who changed what: logins, plugin installs, user creation, setting changes. It lets you notice suspicious behavior and reconstruct what happened. File change detection alerts you when core files change unexpectedly.
Uptime and content monitoring
A free uptime monitor tells you when the site is down. Pair it with Google Search Console, which warns you about security issues and hacked content it detects. Check the Security issues report from time to time.
Choosing tools
Pick a tool by the job you need, not by marketing. Our full comparison, the best WordPress security plugins compared, breaks down the major options by features, cost and trade-offs. If you currently use the best-known free firewall plugin and wonder whether to switch, see Wordfence alternatives worth considering. Whatever you choose, run one main security plugin, not three. Overlapping firewalls and scanners slow the site and conflict.
The performance cost
Endpoint security plugins run on each request, so they use server resources. Cloud and edge protection moves that work elsewhere. Check how a tool affects your speed after installing it. For background on measurement, see how to read PageSpeed Insights.
Layer 6: backups and recovery
Every other layer can fail. A good backup turns a catastrophe into an inconvenience.
What a good backup strategy looks like
- It includes both files and the database.
- It runs automatically, at a frequency matching how often your content changes. A shop needs far more frequent database backups than a brochure site.
- It is stored off the server, in a separate account or cloud storage, so an attacker who controls the site cannot delete it.
- It keeps multiple generations, because you may not notice a compromise for days.
- You have tested a full restore.
Backups protect against more than hackers
Failed updates, accidental deletions, broken migrations and hosting failures all call for the same safety net. That is why backups are the single most useful layer for non-technical owners.
Choosing a backup tool
There are many good options, with different pricing, storage destinations and restore features. Our comparison of the best WordPress backup plugins helps you pick, and these UpdraftPlus alternatives are worth a look if you want something different from the most common choice. Also check what your host already provides, and treat it as an extra copy, not your only one.
Protect the backups themselves
The WordPress documentation suggests protecting backup integrity by encrypting them or keeping read-only copies. At the very least, keep them off the web root and out of public URLs. Old backup archives left in a web-accessible folder are a common leak.
Restore drills
Once or twice a year, restore a backup to a staging site and check that it works. A backup that cannot be restored is worth nothing, and you do not want to find that out in a crisis.
Protecting forms, comments and registrations
Spam is not just annoying. Spam submissions can carry malicious links, exhaust server resources and, in the case of open registration, fill your site with fake accounts that can be used later.
Practical steps
- Turn off open registration if you do not need it, or set the default role to the lowest one.
- Use a honeypot, rate limiting or a privacy-friendly CAPTCHA on public forms.
- Moderate comments, and close comments on old posts.
- Validate and limit file uploads in forms.
Our guide Stop WordPress Spam covers each of these in detail, including tools for comments, forms and registrations. If you use a form plugin, such as Fluent Forms, check the spam protection options it includes before adding more plugins.
Special topics
WooCommerce and payment security
Stores handle customer data and need extra care. Use a payment gateway that processes cards on its own hosted fields or pages, so card numbers never touch your server. Keep the shop plugins updated, restrict shop manager access and log administrative actions. A store also benefits from frequent database backups.
Multisite networks
One vulnerable plugin can expose every site in a network. Restrict who can install plugins, vet network-activated plugins strictly, and keep super administrator accounts to a minimum.
Agencies and freelancers
When managing many client sites, use a central dashboard or API to see update status, vulnerabilities and backups at once. Do not share one admin password across clients. Give each client site its own credentials and revoke access when a contract ends. Document your process so each site gets the same care.
Membership and community sites
These have many user accounts, so credential attacks and spam registrations are the main risks. Enforce strong passwords, offer two-factor authentication and monitor for unusual logins.
Developers and custom code
Escape output, sanitize input, check capabilities and verify nonces. These are the WordPress equivalents of locking doors, and most plugin vulnerabilities come from missing one of them. Keep code in version control and deploy through a pipeline when possible.
Signs your site may be hacked
Many infections are quiet. Watch for these signals.
- Unfamiliar administrator accounts.
- Unexpected redirects, especially on mobile or for visitors coming from search.
- Strange pages or links appearing in search results, such as pharmaceutical or gambling keywords.
- Browser or search engine warnings about a dangerous site.
- Your host suspending the account or reporting abnormal resource use or outgoing mail.
- Files changed that you did not change, or unknown files in the uploads or root folders.
- Sudden traffic drops, or unusual spikes.
- You or customers receive spam sent from your domain.
- Login problems, or password reset emails you did not request.
One sign alone may be innocent. Several together deserve an immediate check.
What to do if you are hacked
Stay calm and work in order. A full walkthrough is in our step-by-step recovery plan for a hacked WordPress site. The short version follows.
- Contain. Put the site in maintenance mode or take it offline if it is harming visitors. Tell your host, who can often help and may already have details.
- Preserve evidence. Make a copy of the infected site and logs before cleaning, so you can investigate how it happened.
- Change every credential. WordPress users, hosting, SFTP, database, email and any API keys. Do it from a clean computer. Regenerate the security keys and salts.
- Clean or restore. The safest route is restoring a backup from before the compromise, then updating everything. Alternatively, reinstall WordPress core, plugins and themes from fresh copies, and carefully inspect uploads, the database and wp-config.php.
- Find the entry point. If you do not close the hole, you will be reinfected. Look at logs, outdated plugins and recently added users.
- Harden and monitor. Apply the layers above, then watch closely for several weeks.
- Request a review. If Google flagged the site, use Search Console to request a review after cleaning.
- Notify if needed. If customer data was exposed, you may have legal duties to notify affected people and authorities, depending on your location. Ask a professional.
Clean-up or professional help
If you are not comfortable inspecting files and databases, pay a professional cleanup service or ask your host. Incomplete cleanups often leave backdoors that bring the infection back within days.
A security routine you can keep
Consistency beats intensity. A simple rhythm is enough for most sites, and our WordPress maintenance checklist has the full version. Here is a security-focused outline.
Weekly
- Apply pending updates, with a staging test for risky ones.
- Check that backups ran and are stored off the server.
- Skim security alerts and the activity log.
Monthly
- Review user accounts and roles.
- Delete unused plugins and themes.
- Check uptime reports and Search Console security issues.
- Scan for malware and vulnerabilities if you use a scanner.
Yearly
- Restore a backup on staging as a drill.
- Review hosting, PHP version, SSL and domain renewals.
- Re-evaluate your security tools and plugin list.
- Review who has access to hosting, domain registrar and DNS.
Security checklist
Foundation
- Quality host with isolation and a current PHP version.
- HTTPS on the whole site, with automatic renewal.
- SFTP instead of FTP.
Software
- WordPress core, plugins and themes up to date.
- No unused or abandoned plugins and themes.
- No nulled software.
- Staging for risky updates.
Access
- Unique, long passwords in a password manager.
- Two-factor authentication for administrators and editors.
- Least-privilege roles and a regular user review.
- No account called admin.
- Login attempt limits.
Hardening
- File editor disabled.
- Correct file permissions and a protected wp-config.php.
- No PHP execution in uploads.
- Directory listing off.
- Unused XML-RPC blocked.
Protection and recovery
- One main security tool, with a firewall and vulnerability monitoring.
- Activity log and uptime monitoring.
- Automatic off-site backups, with a tested restore.
- A written incident plan with contact details for your host.
Common security mistakes
- Believing a plugin makes the site secure. It is one layer.
- Delaying updates for months. Known flaws are exploited quickly.
- Keeping dozens of unused plugins. Each is extra surface.
- Sharing one admin login. You cannot track or revoke access.
- Giving everyone administrator rights. It makes every account a jackpot.
- Storing backups only on the same server. They go down with the site.
- Never testing a restore. The first test happens during an emergency.
- Running several overlapping security plugins. Conflicts and slowdowns follow.
- Ignoring alerts. An alert nobody reads protects nobody.
- Treating security as a one-time setup. It is a routine.
- Using nulled software. A backdoor is often included.
- Forgetting non-WordPress accounts. Hosting, registrar and email accounts are part of your attack surface.
Security and your search visibility
A hacked site can lose rankings fast. Injected spam pages, hidden links and malware warnings damage trust, and search engines may flag or demote the site. Recovery can take time even after cleaning. Security also supports good performance, since compromised sites often slow down. Treat it as part of your overall search strategy, as described in the complete WordPress SEO guide.
Guide map
This guide is the hub for WordPress security on WPMusk. Each article below goes deeper on one part.
- Best WordPress security plugins compared: a side-by-side look at firewalls, scanners and vulnerability tools so you can choose by need.
- Wordfence alternatives worth considering: options for sites that want a different approach to firewalling and scanning.
- Best WordPress backup plugins compared: how to choose a backup tool, destination and schedule.
- UpdraftPlus alternatives for reliable backups: other backup tools and when each makes sense.
- My WordPress site was hacked: a step-by-step recovery plan: the full incident response walkthrough.
- Add two-factor authentication to WordPress: methods, plugins and rollout advice.
- WordPress user roles and least-privilege access: how to assign and audit permissions.
- WordPress maintenance checklist: weekly, monthly and yearly tasks that keep a site healthy.
- Should you enable WordPress auto-updates?: weighing convenience against breakage risk.
- WordPress staging sites: creating and using a safe test copy.
- Stop WordPress spam: protecting comments, forms and registrations.
FAQ
Is WordPress secure?
WordPress core is maintained by a large security-minded team and is reasonably secure when kept updated. Most compromises come from outdated plugins and themes, weak credentials or poor hosting, not core itself. Because WordPress is so widely used, it is also a frequent target, so good habits matter more than the platform’s reputation.
What is the most important thing for WordPress security?
Keeping software updated is usually the biggest single factor, since attackers mostly exploit known vulnerabilities in old plugins and themes. Close behind are unique passwords with two-factor authentication, and tested off-site backups. If you do only three things, do those.
Do I need a security plugin?
Not strictly, but most sites benefit from one. A security plugin adds a firewall, vulnerability alerts, scanning or login protection, depending on the product. It supplements updates, backups and good access control. It cannot replace them. Choose one tool for the job you need, and avoid running several.
How do I know if my WordPress site has been hacked?
Common signs are unknown administrator accounts, unexpected redirects, strange pages in search results, browser warnings, unfamiliar files and a host warning about abuse. A scanner and activity log help detect changes. If you suspect a compromise, follow an incident plan and contact your host immediately.
How often should I update WordPress, plugins and themes?
Check at least weekly, and apply security updates as soon as practical, ideally within days. Use staging for complex sites. Automatic updates for minor and security releases can shorten the window of exposure, as discussed in our auto-updates risk guide. Delay no longer than you must.
Should I hide or change my login URL?
Changing the login URL reduces automated noise in logs, but it does not stop a determined attacker, because it is obscurity. It can be a nice extra, but your real protection should be strong passwords, two-factor authentication and rate limiting. Make sure you do not lock yourself out, and record the new address.
Are backups enough to protect my site?
No. Backups let you recover after something goes wrong, but they do not prevent attacks or stop data theft. They should be one layer among updates, access control, hardening and monitoring. They also only work if they are stored off the server and you have tested restoring them.
What should I do first if my site is hacked?
Contain the damage by taking the site offline or into maintenance mode, and contact your host. Keep a copy for investigation, change all passwords and keys, then restore a clean backup or rebuild from fresh files. Find and close the entry point, or the site will be reinfected. See our recovery plan for the full steps.
Conclusion and next steps
WordPress security is mostly about discipline, not magic. Know how sites actually get hacked, build the layers that stop those routes, keep a routine you can sustain and have a plan for the bad day. A site with current software, unique passwords with two-factor authentication, least-privilege users, a sensible firewall and tested off-site backups is a hard target and a fast recovery.
Start this week with three actions: update everything and delete what you do not use, turn on two-factor authentication for every privileged account, and confirm that a recent backup exists off your server. Then work through the guide map above, beginning with the plugin comparison if you need tooling and the recovery plan so it is ready before you need it.
Keep reading
Best WordPress Security Plugins Compared
Compare the best WordPress security plugins by job: firewall, scanning, vulnerability alerts and login protection, with trade-offs and a clear way to choose.
Wordfence Alternatives Worth Considering
Looking for Wordfence alternatives? Compare Solid Security, Patchstack, Sucuri, AIOS and host-level options by use case, trade-offs and gaps.
Best WordPress Backup Plugins Compared
Find the best WordPress backup plugin for your site. Compare UpdraftPlus, Duplicator, BackWPup, WPvivid, Jetpack and BlogVault by use case and restore.
UpdraftPlus Alternatives for Reliable Backups
Compare the best UpdraftPlus alternatives for WordPress backups, from Duplicator and WPvivid to BlogVault and Jetpack, and pick one that restores.
My WordPress Site Was Hacked: A Step-by-Step Recovery Plan
Hacked WordPress site? Follow this calm, step-by-step recovery plan: contain, back up, clean, reset access, find the cause and harden the site.
Add Two-Factor Authentication to WordPress
Set up two factor authentication WordPress sites can rely on: compare plugins, choose methods, enforce by role, and avoid lockouts with this guide.
WordPress User Roles and Least-Privilege Access
WordPress user roles explained, plus a practical least-privilege setup so freelancers, editors and clients get only the access they need.
WordPress Maintenance Checklist: Weekly, Monthly, Yearly
Use this WordPress maintenance checklist to keep your site secure, fast and recoverable, with clear weekly, monthly and yearly tasks.
Let your AI assistant do this for you
Open the ready prompt with step‑by‑step instructions for running it through NibWP.