Contents8 sections
Level: Beginner · Time: about 15 minutes · Cost: free
Marcus books his food truck through his website — weddings, markets, the Saturday spot by the park. One Friday evening he found a shiny new events plugin mentioned in a forum post, installed it in four clicks, and went to bed happy. By Saturday morning, his busiest day of the week, the booking form was a blank white page. The plugin was fine, mostly. It just did not get along with the one his site already used — and nobody noticed until the customers did.
Nothing about that story needed to happen. The plugin was not a scam, the site was not badly built, and Marcus did nothing foolish — he just skipped the fifteen minutes of looking that would have caught it. This tutorial is those fifteen minutes: a short routine to run every time you install a WordPress plugin, so the story ends with the form still working.
What you need
- A WordPress site you can log in to as an administrator.
- About 15 minutes, start to finish.
- A way to back your site up — your host’s backup tool or a backup plugin. Step 5 takes the actual backup; if you have neither set up, that step tells you what to do first.
1. Start with the job, not the plugin
Before you search for anything, say the job out loud in one sentence: “I need visitors to be able to book a table,” or “I need my images to load faster.” If you cannot say the job in one sentence, you are not shopping yet — you are browsing, and browsing is how sites end up with forty plugins and nobody remembers why.
Then ask the two free questions. First: does WordPress already do this? A surprising amount of what people install plugins for — embedding videos, image galleries, scheduling posts, building menus — is already built into WordPress itself. Second: does your theme already do it? Many themes quietly include sliders, galleries, social buttons, and contact forms of their own. Installing a second one to do the same job gives you two lots of code loading on every page and, sooner or later, an argument between them — which is exactly what happened to Marcus.
If the job is real and nothing you already have does it, now you may go shopping.
2. Read the plugin page like a food label
Every time you install a WordPress plugin from wordpress.org, its page tells you nearly everything — if you read the small print instead of the headline. The headline is marketing. The small print is the label. Here is what to check, in order:
- Last updated. Plugins are software, and software rots. A plugin updated within the last few months is being looked after. One that has not been touched in two years is a garden shed in winter: it might be fine inside, but nobody has checked. Walk past.
- Tested up to. The page shows which WordPress version the plugin has been tested with. If your site runs a much newer WordPress than the plugin claims to support, the author has not confirmed it still works — you would be the test.
- Active installations. A plugin running on 100,000 sites has had 100,000 chances for its worst bugs to be found by somebody else. A plugin on 40 sites has not. New and small is not automatically bad — every good plugin started small — but it raises the value of everything else on this list.
- Ratings — and read the one-star reviews. Five-star reviews tell you people are happy. One-star reviews tell you why people left, and that is where the useful information lives. Ignore the furious ones with no details. Pay attention when several people describe the same specific problem: “broke my site after the last update” once is an accident; five times is a pattern.
None of these alone decides anything. Together they take about ninety seconds and they catch most of the trouble before it reaches your site.
Found one that passes? Installing it is the easy part. In your dashboard, go to Plugins → Add New, search for its name, and click Install Now, then Activate. If you bought a plugin and have it as a file on your computer instead, use the same screen: click Upload Plugin at the top, choose the file, then Install Now and Activate. Either way — not yet. There are four more checks first, and they start with the author’s kitchen.
3. Skim the support forum before you need it
Every plugin page links to its support forum — the place users go when something breaks. You are not reading it for the problems; every plugin has problems. You are reading it for the answers.
Look at the recent threads. Are they answered? How fast, and by whom? A healthy forum shows the author (or their team) replying within a few days, asking sensible questions, and marking threads resolved. A worrying forum shows months of questions with no reply at all — which tells you exactly what your own 2 a.m. emergency would look like. Ten threads all reporting the same unfixed bug is the other warning sign: that is not bad luck, that is the current state of the plugin.
Think of it as walking past a restaurant and looking through the window. You are not judging the food. You are judging whether anybody is in the kitchen.
4. The one rule with no exceptions
Never install a “nulled” plugin — a paid plugin being given away free on some download site. This is the one rule in this tutorial with no exceptions and no judgement calls.
Here is why. A paid plugin costs money because somebody built it and sells it. A site offering it for free is not being generous; it is running a business, and the business is you. Nulled plugins are one of the oldest delivery routes for malicious code there is: the plugin works, mostly, while quietly adding hidden admin accounts, spam pages, or a back door for later. You save the price of the plugin and hand a stranger the keys to the building — the worst trade on the internet.
If a plugin is worth having, it is worth buying from the people who made it, or finding a free alternative you can get from wordpress.org. There is no third option that ends well.
5. Back up before you click Install
A backup is the undo button for everything in this tutorial. Most plugin installs go fine. The one that does not will go wrong at the worst possible moment, on the busiest day, in front of a customer — Marcus can confirm the scheduling. So before you install anything new, take a fresh backup, and take it properly:
- Run a full backup — files and database — using your host’s backup tool or your backup plugin. On most sites this takes a few minutes, not seconds; start it and let it finish.
- Check it actually completed. Look for the “backup complete” message and today’s date and time on the backup. A backup that stopped halfway is a story you do not want to star in.
- Find the restore button now, while nothing is wrong. You do not have to use it — just know where it lives, so the worst day does not also include learning a new screen. If you have never set backups up at all, that is today’s real job, ahead of any plugin: our WordPress Security Basics tutorial covers the settings that keep a site safe, backups included.
A few minutes of backup now is the difference between “the new plugin broke something, roll it back” and a very long evening.
6. One at a time, then go look at your site
Two things before the install itself. First, take your before picture: run your homepage through PageSpeed Insights (Google’s free speed-testing tool) and write the number down. Sixty seconds, and it gives the after-check in step 8 something honest to compare against.
Then install plugins one at a time. Always. Here is the whole reason: if you install four plugins and then your site breaks, you have four suspects and no witnesses. If you install one, check the site, install the next, and then something breaks — you know exactly who did it, and the fix is usually just deactivating that one plugin.
After each install, actually go and look at your site the way a visitor would. Open the homepage. Open one more page — a product, a post, the page the plugin was supposed to improve. Plugins mostly break things politely and visibly: a layout shifts, a menu doubles, a form stops sending. Two minutes of looking catches it while it is still a small story.
And if something does break badly — a blank white page, an error where your site used to be — do not panic and do not start deleting things at random. Our 500 Error Survival Guide walks through finding the cause calmly, in about ten minutes.
7. Keep the herd small
This one is not part of install day — it is a once-a-month habit. Open your plugins list and read it like a stranger. For each one, ask: what job does this do, and is that job still being done? You will find plugins from a project that ended, a feature you tried for a week, a seasonal thing from last year. Delete what you no longer use — delete, not just deactivate.
That last part matters. A deactivated plugin is not gone; its files are still sitting on your site, and vulnerable code in an inactive plugin can still be a way in for an attacker, because the files can often be reached directly even when the plugin is switched off. Deactivation parks the car. Deletion takes it off the road. If a plugin is not doing a job, it should not be in the building.
There is no magic number of plugins — a site with thirty well-kept plugins is healthier than a site with five abandoned ones. The herd rule is not about the count. It is about every single one of them earning its place: a real job, a living author, and a recent update.
8. The five-minute after-check — the last step, every time
Back to install day, and the step the whole routine ends with. The plugin is in and the site looks right; spend five more minutes on the checks that catch the slow problems:
- Do the important thing. Whatever your site exists to do — take an order, send a contact form, book an appointment — do it once, yourself, start to finish. Plugins love to break the one form that matters while leaving everything else looking perfect. This is the check that would have saved Marcus’s Saturday.
- Compare the speed. Run PageSpeed Insights again and compare it with the before picture you took in step 6. One plugin rarely sinks a site, but some add heavy scripts to every page for a feature that appears on one. Our Speed Up WordPress checks show how to read the result and what to do about it.
- Look at your dashboard. Some plugins arrive like a guest who rearranges your furniture: new menus, banners on every screen, a “quick setup” wizard holding your admin hostage. A little of this is normal. A plugin that will not stop advertising at you is telling you how it will behave forever.
- Write it down. Keep a simple list — a note, a document, anywhere — of what you installed, when, and what job it does. Six months from now, when you are staring at a plugin called something like “WP Ultimate Pro Plus” wondering whether it is safe to delete, that list is gold.
That is the whole routine: job first, read the label, check the kitchen, never nulled, back up, one at a time, small herd — and every install ends with the after-check. Fifteen minutes of this, every time you install a WordPress plugin, and plugins go back to being what they were supposed to be: the best thing about WordPress.
Common mistakes
- Installing three or four plugins at once, then having no idea which one broke the site.
- Judging by the star rating alone without reading the one-star reviews, where the real story lives.
- Downloading a paid plugin free from a “nulled” site — the saving is never worth the stranger it lets in.
- Deactivating instead of deleting plugins you no longer use, and leaving their files on the site.
- Skipping the backup “just this once” — it is always that once.
Tested on: WordPress 7.1.4 (November 2026). The screens named here — Plugins → Add New, Upload Plugin, the wordpress.org plugin pages — match that version.
Next read
- WordPress Security Basics: The Settings Every Site Owner Should Fix Today — the settings that keep the whole site safe, not just the plugins.
- Speed Up WordPress: 8 Checks That Actually Move the Needle — plugins are one of the eight; here is the full list.
- The 500 Error Survival Guide — for the day something breaks anyway. Stay calm; it is fixable.