How to Set Up a WordPress Staging Site and Push Changes Live Safely
A staging site lets you test updates on a copy before customers see them. Learn how to create one, lock it down…
WordPress auto updates can save you from old, vulnerable plugins or surprise you with a broken site. Learn what is automatic by default and a risk-based way to choose.
WordPress auto updates sit between two kinds of pain. Leave them off, and an old plugin with a known security hole sits on your site for months. Switch everything on, and one bad update can break your checkout while you sleep. The right answer is rarely “all” or “nothing”. This guide shows what WordPress updates by itself, what you can switch on, and a simple risk-based way to decide plugin by plugin.
According to the WordPress documentation, WordPress core applies minor and security updates automatically on most sites, while plugin and theme auto updates, available since WordPress 5.5, are off until an administrator switches them on, one plugin or theme at a time. Our recommendation: make sure you have a restore point, turn on auto updates for simple low-risk plugins, and keep anything that touches payments, checkout, memberships or forms on a manual, tested update routine. Then check that scheduled updates actually run.
How this guide was prepared: the facts follow the WordPress documentation and core announcement listed under Sources, read on October 21, 2026. The risk grouping in this guide is our own recommendation, not a WordPress rule. Hosts and plugins can change how updates behave, and we did not test this on your site.

| What you see | Likely cause | Start with |
|---|---|---|
| No “Automatic updates” column on the Plugins screen | WordPress older than 5.5, or disabled by host or plugin | Step 1 |
| Plugins stay outdated for weeks | Auto updates are off and nobody updates manually | Steps 3 and 4 |
| Site broke after an update you did not run | A plugin auto-updated with no restore plan | Steps 2 and 5 |
| “Next update” never changes | WordPress cron is not running correctly | Step 6 |
| You get emails about failed updates | A plugin or theme could not be updated | Step 7 |
| Site Health says background updates are not working | Permissions, blocked connection or host restriction | Steps 1 and 6 |
The documentation says plugin and theme auto updates were introduced in WordPress 5.5, and that core minor and security updates have long been automatic by default. Open Dashboard → Updates and the Plugins screen. If you see an “Automatic updates” column, each plugin shows its state and a link to enable or disable it. For themes, open Appearance, select a theme and look for “Enable auto-updates” in the theme details. If these controls are missing, the documentation says it probably means your host or a plugin has partly or completely turned the feature off. Site Health (Tools → Site Health) also reports problems with background updates, as explained in our WordPress Site Health guide.
This is the step people skip. Before you enable auto updates, you need a recent backup of files and database and a way to restore it. A backup you have never tried to restore is a hope, not a plan. Know where the backup is, how long a restore takes, and who does it. If your host offers one-click restore or staging, learn how it works now, not during an outage.
This grouping is our own suggestion. Low risk: simple plugins whose failure would be annoying but not costly, such as a security scanner or a small utility. Medium risk: SEO, caching and performance plugins, which can change how pages look or load. High risk: anything involved in checkout, payments, memberships, bookings, forms that collect leads, and page builders that control your layout. Core WordPress security updates stay automatic. Write the list down; you will use it every month.
On the Plugins screen, use the enable link for each plugin, or select several and use the bulk action. The documentation says you can turn auto updates off again with the same link, and that by default WordPress runs auto updates twice per day, with the time until the next run displayed under the link. Start with a few plugins, watch for a few weeks, then decide about the medium-risk group.
For plugins that touch money or leads, read the changelog, update on a staging copy, test the real flows (checkout, login, forms), and only then update the live site. Our guide how to update WordPress plugins safely gives a routine. If an update ever breaks the site, see WordPress 500 internal server error after a plugin update for the way back. Do not leave important plugins months behind, because that is its own security risk. The point of manual is control, not neglect.
The documentation warns that auto update scheduling relies on WordPress cron tasks, and that depending on your server, installation or plugins it may not work correctly. If the “next update” time never changes, or Site Health reports failing background updates or loopback requests, check with your host whether WordPress cron runs, and whether a security rule blocks it. A host can sometimes run cron from a server scheduler instead of on page loads.
The documentation says WordPress sends email notifications about plugin and theme auto update results, including when some succeeded and some failed. Make sure those go to an inbox someone actually checks. Once a month, spend ten minutes: look at what updated, test the key pages, and move plugins between groups. This review is part of regular WordPress maintenance.
Core minor and security updates are automatic on most sites, per the documentation. Plugin and theme auto updates must be switched on by an administrator.
They are safer than ignoring updates, and riskier than tested updates for important plugins. That is why we suggest deciding per plugin.
Yes, with the same link you used to enable them, or the bulk action.
Deactivate the plugin, restore the backup if needed and read the log. See our guides on the critical error screen and finding the plugin that broke your site.
Take ten minutes: list your plugins, mark the high-risk ones and turn on auto updates for the safe few. If your WordPress auto updates behave strangely, send your host the Site Health message and the update emails. If you would like a person to look, wpallsolution offers independent plugin support. We cannot promise results without seeing your setup.
Last reviewed: October 21, 2026. WordPress is a trademark of the WordPress Foundation. wpallsolution is not affiliated with or endorsed by the WordPress Foundation or Automattic.
A staging site lets you test updates on a copy before customers see them. Learn how to create one, lock it down…
Most break-ins start at the login screen. Use this practical checklist for passwords, two-step login, admin accounts, attempt limits and HTTPS.
Care plans give agencies steady work after launch. See how white label WordPress maintenance works, what to include and what to agree…
Black FridayCyber Monday sale
Before you go,
Our biggest discount of the year on the first payment of every maintenance plan.
BF2026 at checkout