Should I Auto Update WordPress Plugins?

Answered by SiteHale — a managed WordPress SEO and site-health service that runs automated optimization and monitoring for WordPress site owners.

The Real Trade-Off Behind the Update Badge

You log into your dashboard and the little red bubble next to Plugins says 7 again. You updated everything last week. Maybe one of those updates once broke your contact form, so now you hesitate every time. Or maybe you’ve ignored the bubble for months and you’re starting to worry that’s worse. Deciding whether to auto update WordPress plugins comes down to which risk you’d rather manage: a site that breaks occasionally after an update, or a site that sits exposed to known security holes.

Outdated plugins are one of the most common ways WordPress sites get compromised. When a vulnerability is disclosed, attackers scan for unpatched sites within days, sometimes hours. Automatic updates close that window without you lifting a finger.

The downside is real too. Plugins sometimes conflict with your theme, with other plugins, or with your PHP version. An update can quietly change a layout, break a checkout page, or disable a feature you rely on, and you may not notice until a customer tells you.

The good news is that it isn’t all-or-nothing. WordPress lets you enable auto-updates plugin by plugin, so you can automate the low-risk ones and keep manual control over the few that hold your site together.

When to Auto Update WordPress Plugins (and When Not To)

Sort your installed plugins into two groups. This takes about ten minutes and makes the decision almost automatic.

Good candidates for auto-updates:

  • Security plugins such as firewalls and login protection. Patches here are time-sensitive.
  • Small, single-purpose plugins like SVG support, redirects, or cookie notices. They touch little and rarely conflict.
  • Well-maintained plugins with a clean track record, meaning frequent releases, a large install base, and recent compatibility with your WordPress version.
  • Plugins you can’t keep up with manually. An automated update beats one you’ll forget for six months.

Keep these on manual updates:

  • WooCommerce and payment gateways. Major versions can change database structures or checkout behavior.
  • Page builders like Elementor or Divi, where an update can shift layouts sitewide.
  • Membership, LMS, and booking plugins that store critical data or handle logins.
  • Plugins you’ve customized or that have add-ons depending on them.
  • Premium plugins with spotty changelogs or a history of breaking releases.

For the manual group, read the changelog before updating and, ideally, test on a staging copy first. Many hosts offer one-click staging in their control panel.

How to Turn On Automatic Plugin Updates

Since WordPress 5.5, per-plugin auto-updates are built into the core software. You don’t need an extra plugin, and the process is identical whether you manage your site from Windows, macOS, or anything else with a browser.

  1. Go to Plugins > Installed Plugins in your dashboard.
  2. Find the Automatic Updates column on the right.
  3. Click Enable auto-updates next to each plugin from your low-risk list.
  4. To do several at once, tick their checkboxes, choose Enable Auto-updates from the Bulk actions dropdown, and click Apply.

WordPress checks for updates roughly twice a day using its built-in scheduler, WP-Cron. Because WP-Cron runs when someone visits the site, very low-traffic sites may update less predictably. If that’s you, ask your host about setting up a real server cron job.

A few things to check if the column is missing or the links won’t work:

  • Your host may manage updates. Some managed WordPress hosts disable the toggle and handle updates themselves.
  • A constant may be blocking it. Look in wp-config.php for AUTOMATIC_UPDATER_DISABLED set to true.
  • Premium plugins usually need an active license key before they can update at all, automatically or otherwise.

You can confirm everything is working under Tools > Site Health, which flags background update problems.

Building a Safety Net for When an Update Goes Wrong

Automatic updates are only safe if you can recover quickly. Put these protections in place before you enable them.

  • Daily off-site backups. Use your host’s backup tool or a plugin like UpdraftPlus, and store copies somewhere other than your server. Test a restore once so you know it works.
  • Watch your email. WordPress sends a notice after each auto-update, listing what changed and whether anything failed. Make sure the admin email under Settings > General is one you actually read.
  • Keep WordPress current. Version 6.6 and later can automatically roll back a plugin auto-update that causes a fatal error, which prevents the worst outcomes.
  • Use uptime monitoring. A free service will alert you within minutes if the site goes down.

If an update does break something and you can’t reach the dashboard:

  1. Check your inbox for a Recovery Mode email from WordPress. Its link lets you log in and deactivate the faulty plugin.
  2. If there’s no email, connect with an SFTP client (FileZilla and Cyberduck both run on Windows and Mac) or your host’s file manager.
  3. Open wp-content/plugins and rename the problem plugin’s folder, for example to pluginname-off. WordPress will deactivate it.
  4. Install the previous version, or restore your backup, and switch that plugin to manual updates going forward.

Does Your Site Have This Problem?

Every check in this article runs automatically on the sites we look after. You can run the same health checks on your own site in seconds with the free SiteHale plugin — no account, nothing transmitted anywhere. Or have us do it: we’ll crawl your site and send you a written report, free.

Get My Free Site Report

Proven on our own sites first

Every automation runs on our own sites before any client site

25+ years in IT

Built by a 25-year professional IT team

$49/mo flat

Everything included — no tiers, no upsells

Leave a Comment