Why WordPress Plugins Need Updates
Plugins add features WordPress doesn’t have on its own: forms, SEO tools, online stores, calendars, backups. Think of them like apps on your phone. Your banking app needs updates now and then for new features, security fixes, or changes to the phone’s operating system. Plugins update for the same three reasons. Security is the one that matters most. Outdated plugins are one of the most common ways WordPress sites get hacked (we cover the rest in how we secure WordPress sites), which is why WordPress’s own Site Health screen flags “You have plugins waiting to be updated” as a critical issue.Step 1: Make a Backup You Can Actually Restore
Before you touch anything, make sure there’s a recent backup and that you know how to restore it. Many good hosts back up your site every day automatically. SiteGround, the host we use and recommend, includes daily backups on every plan and lets you make an on-demand backup right before you update. (Affiliate link.) Plenty of cheaper hosts don’t, so find out what yours does before you need it. (More on that in how to choose WordPress hosting for a small business.) Backup plugins work too, but I prefer host-level backups. A backup plugin runs inside the same WordPress site you’re about to change, so if the site breaks badly, the plugin you’d use to restore it may be broken along with it.Step 2: Check Site Health
Go to Tools > Site Health. It takes a minute and catches problems that make updates fail:- An outdated PHP version: newer plugin versions often require a newer version of PHP (the language WordPress runs on). If Site Health says your PHP is outdated, ask your host about upgrading before you update plugins.
- Background updates not working, which usually means scheduled tasks aren’t running.
- Inactive plugins and themes you can delete. Every plugin you remove is one less thing to update and secure.
Step 3: Know Which Plugins Depend on Each Other
This step seems unnecessary until it bites you. Some plugins are add-ons for other plugins, and updating one without the other can break things.
Gravity Forms and its Mailchimp add-on. The add-on depends on the main plugin, so they should be updated together.
Step 4: Read What the Update Changes
On the Plugins screen, each plugin with an update shows a “View version details” link. Click it, especially for big plugins and anything other plugins rely on.
Check the version details before you click “update now.”
- A feature that used to be free now requires a paid license, often because the plugin was sold to a new company.
- Some add-ons no longer work with the new version.
- The plugin was rewritten, and existing settings or designs won’t carry over cleanly.
- The new version requires a newer version of PHP or WordPress than your site has.
- The plugin has to be reconnected to Google, Facebook, Instagram, or another service after updating, or it stops showing data.
Step 5: Test Big Updates on a Staging Site
A staging site is a private copy of your website where you can try updates without affecting the live one. Many managed WordPress hosts include it (on SiteGround, staging starts with the GrowBig plan). For major version updates of WooCommerce, your page builder, or a membership plugin, update on staging first, click around, then repeat on the live site.Step 6: Update One Plugin at a Time
Go to Dashboard > Updates or the Plugins screen, check the box next to a single plugin, and update it. Then load your homepage and one or two key pages before moving to the next. It’s tempting to select all and update everything at once. Don’t, at least not on a site you care about. If ten plugins update together and something breaks, you won’t know which one did it. One at a time turns a mystery into a two-minute fix.What to Do If an Update Breaks Your Site
If a plugin update causes a fatal error, visitors may see a message like this:
The WordPress “critical error” screen.
- Check the site admin’s email. Since WordPress 5.2, fatal error protection emails the admin address a recovery mode link. Use it to log in and deactivate the plugin that caused the error.
- No email? Connect with your host’s file manager or FTP and rename that plugin’s folder in
wp-content/plugins. WordPress deactivates it, and the site usually comes right back. - Still broken, or not sure what changed? Restore the backup from Step 1.
Step 7: Test the Things That Make You Money
I see so many people update plugins and skip this step. You don’t need to click every page, but hit the big ones:- Submit your contact or quote form and confirm the email arrives.
- If you sell online, add something to the cart and get as far as checkout.
- Check the homepage and a key service page on your phone.
- Use a private or incognito window so you aren’t seeing a cached old version.
Automatic Updates Are Fine for Small Plugins
Since WordPress 5.5, you can turn on auto-updates plugin by plugin from the Plugins screen. WordPress checks for them twice a day and emails the site admin after each update attempt. Since WordPress 6.6, if an automatic plugin update causes a fatal error, WordPress rolls that plugin back to the previous version and emails you about it. My take: auto-updates are fine for small, well-maintained plugins that don’t depend on anything else. Keep them off for WooCommerce, page builders, membership plugins, and anything with add-ons, and update those by hand using the steps above. Auto-updates are also no substitute for backups, and they won’t tell you if an update quietly broke a form.How Often Should You Update Plugins?
Plugin updates come out constantly, but most aren’t urgent security fixes. Brand-new releases sometimes ship with bugs that get patched a day or two later, so there’s no prize for updating within the hour. A good rhythm for most business sites:- Once a month: run through the steps above for everything.
- Right away for security releases. Read the changelog when an update appears, and consider a Google Alert for the names of your most important plugins so you hear about vulnerabilities quickly.

