WordPress plugins are what turn a basic site into something functional. Contact forms, SEO settings, caching, security — almost everything beyond the core theme comes from a plugin. Most people have no problem clicking install. The problems start when they do it without thinking.
I’ve seen sites slow down after an update, break after a deletion, or accumulate twenty inactive plugins nobody noticed were still running. None of that is inevitable. Installing and removing plugins correctly takes an extra two minutes each time and prevents most of the issues that come up later.
Quick Answer
Go to Plugins > Add New Plugin, search for the plugin, click Install Now, then Activate. After activating, go directly to the plugin’s settings and configure it. To remove a plugin, deactivate it first, then delete it. Never skip the deactivation step — and don’t assume deletion removes everything the plugin ever wrote to your database.
Why This Matters
Plugins touch every part of your site — performance, SEO, security, and functionality. A plugin installed carelessly can conflict with another plugin, slow down page loads, or introduce a vulnerability. Most WordPress sites accumulate plugins over time; some get installed to test something and never removed. The WordPress Plugin Directory now lists nearly 70,000 free plugins — up from around 60,000 just a couple of years ago — and quality varies enormously across that range, so checking a plugin before installing matters more as the directory keeps growing rather than less.
How to Install a WordPress Plugin from the Directory
Step 1: Go to Plugins > Add New Plugin
From your WordPress dashboard, navigate to Plugins > Add New Plugin. This opens the plugin browser connected to the official directory.
Step 2: Search and Check Before Installing
Use the search field to find what you need — by name if you know the plugin, or by function (“contact form”, “image compression”) if you’re exploring options. Before clicking install, check three things on the listing:
- Last updated — a plugin untouched for over a year is worth a second look, and one untouched for two-plus years is a real risk, not just a minor concern
- Tested up to — confirms compatibility with your current WordPress version; a plugin that lags two or more major core releases behind is a compatibility gamble even if it happens to still work today
- Active installations — more installs generally means more community testing and faster bug fixes, though a smaller, actively-updated plugin still beats a larger, stale one
Step 3: Install Now, Then Activate
Click Install Now. WordPress downloads the plugin files to your /wp-content/plugins/ directory. The plugin is not active yet. Click Activate once the install completes — this is when the plugin’s code starts actually running on your site, registering its hooks into WordPress core.
Step 4: Configure the Plugin Settings Immediately
Activating a plugin without configuring it is one of the most common mistakes on new sites. Most plugins work at a basic level out of the box, but the useful behaviour usually requires a few settings to be correct. Find the plugin’s settings page immediately after activation and go through the options.
Step 5: Test Your Site
After activating any new plugin, load a few pages and check they render correctly — the homepage, a post, and any checkout or form pages if relevant. Plugin conflicts can show up immediately or only on certain page types. If you’re making changes to a live site, a WordPress staging site lets you test plugins before they affect real visitors.
How to Install a Plugin Manually
Some plugins — usually premium or custom-built ones — aren’t listed in the directory. These are distributed as .zip files and installed manually.
Go to Plugins > Add New Plugin, click Upload Plugin at the top, choose the .zip file from your computer, and click Install Now. Once uploaded, click Activate. Manual installs work identically to directory installs once activated — the only difference is that WordPress won’t notify you of updates automatically, since it has no directory listing to check against.
How to Delete a WordPress Plugin Properly
Step 1: Deactivate First
Go to Plugins > Installed Plugins, find the plugin you want to remove, and click Deactivate. This stops the plugin from running without removing anything yet. Deactivating first gives you a checkpoint — if something breaks, you know that plugin was handling something important.
Step 2: Delete
After deactivating, the Delete link appears below the plugin name. Click it. WordPress removes the plugin’s files from your server. If you’re removing a plugin that handled something critical — redirects, forms, SEO meta — verify the functionality is properly replaced before deleting.
Step 3: Understand Why Some Plugins Leave Data Behind
Deletion removes a plugin’s files, but not necessarily its data. WordPress gives plugin developers a specific mechanism for cleanup: an uninstall.php file in the plugin’s own folder, or a call to register_uninstall_hook(), either of which WordPress runs automatically the moment you click Delete — but only if the developer actually wrote that cleanup code. A well-built plugin removes its own options, custom database tables, and post meta at this point. A poorly-built one simply has no uninstall routine at all, so its settings rows, custom tables, and orphaned meta stay in your database indefinitely, invisible until you go looking for them or a database-cleanup tool flags them.
This is also why deactivating and deleting are meaningfully different actions, not just two clicks in the same flow. Deactivation calls a separate register_deactivation_hook() that typically just stops scheduled tasks and clears temporary caches — it’s not expected to touch your permanent data. Deletion is the point where a plugin either cleans up after itself or doesn’t. If you notice stray settings or database entries after deleting a plugin, that’s the uninstall hook either missing or incomplete, not something you did wrong.
Practical Tips
Keep your plugin count low. Every active plugin adds overhead. Most sites don’t need more than ten to fifteen well-chosen plugins to cover everything they need. The guide to essential tools for a new website covers the core set worth installing.
Update plugins regularly. Outdated plugins are one of the most common entry points for WordPress security issues. Run updates at least weekly. For a safe update process that covers plugins, themes, and core, updating WordPress safely covers the right order and what to check.
Install and test one plugin at a time. If you install several at once and something breaks, you won’t know which one caused it. One at a time makes troubleshooting straightforward.
Remove anything you’re not using. An inactive plugin is less of a risk than an active one, since its code isn’t running — but it still sits on disk and can still contain a known vulnerability if it’s outdated, since a vulnerability scanner checking your file system doesn’t care whether the plugin is switched on. Delete anything you installed to test and decided against.
Common Mistakes
Skipping the compatibility check. If a plugin hasn’t been tested with your current WordPress version, treat that as a risk — especially on live sites with forms or ecommerce.
Deleting without deactivating. This can occasionally cause PHP errors or white screens depending on how the plugin is built. Always deactivate first.
Not configuring after activating. A plugin that’s active but not configured may not be doing anything useful, or worse, may be doing something unintended with its default settings.
Ignoring update notifications. The Plugins screen shows when updates are available. Leaving plugins on old versions for weeks or months is one of the most avoidable security risks on a WordPress site.
Free vs Premium Plugins
Free plugins from the directory are suitable for most use cases. Use a premium plugin when you need dedicated support, more advanced features, or integrations that the free version doesn’t cover. Premium plugins aren’t inherently safer or better — it depends entirely on the developer, and a premium plugin sold outside the directory doesn’t go through the same public code review that a directory listing does. Check reviews, update history, and support responsiveness before buying.
Before installing a new plugin, it helps to know how to troubleshoot WordPress plugin conflicts — so you can quickly isolate the cause if something breaks after activation.
Conclusion
Check compatibility before installing, configure settings immediately after activating, and test your site. When removing plugins, deactivate before deleting, and don’t assume a clean uninstall — a quick look through your database options table after removing something significant costs a few minutes and confirms there’s nothing left behind. Applied consistently, that process prevents most of the common WordPress plugin problems that slow sites down or create security gaps. Plugin management is one of the foundational maintenance habits covered in the step-by-step guide to building a WordPress website.
Etienne Basson works with website systems, SEO-driven site architecture, and technical implementation. He writes practical guides on building, structuring, and optimizing websites for long-term growth.