Keeping WordPress, your plugins, and your themes up to date is the simplest way to keep a site secure. Wordify Automated Safe Updates does that for you. Each update gets a verified restore point first, a health check afterwards, and an automatic rollback if the site doesn't come back clean.
Is it on for my sites?
New Wordify accounts have Automated Safe Updates on from day one. Existing accounts are being switched on in stages, and you'll get an email when your team is included.
To check a site, open the site, then under WordPress select Updates. The card at the top of the page says On or Off.
To check your whole team, open the Dashboard. The Site Health card shows how many sites use Automated Safe Updates and links to the ones that don't.
Turn it on or off for a site
Open the site, then under WordPress select Updates.
Use the switch on the Automated Safe Updates card.
A task appears on your Tasks page while the change is applied. It usually takes a moment.
To turn it on for several sites at once, open Sites, tick the sites, open Actions, and choose Turn on Automated Safe Updates. You can keep each site's existing plugin and theme settings, or set everything to update automatically. Staging and development sites start with Automated Safe Updates off, so tick Include staging and development sites if you want them covered.
Turning it off hands control back to you at any time. Nothing else on the site changes.
What happens on each update
Restore point. Wordify takes a restore point and verifies it. If the restore point can't be verified, nothing on the site changes, and the update waits for the next run.
Apply. The update is applied inside the site's update window.
Health check. Wordify loads the site and checks it still works.
Roll back if needed. If the site doesn't pass its health check, Wordify restores it to the restore point and puts that release on hold. A newer release clears the hold.
If a site is already down when a run is due, Wordify pauses Automated Safe Updates for that site rather than changing a site that isn't healthy. Updates resume on their own once the site is back to normal. There is nothing to switch back on.
Choose when updates run
Routine updates run inside an update window, a quiet period you control. Until you set a window of your own, Wordify uses 2:00 AM to 5:00 AM UTC, every day.
On the Updates page, find Update Window.
Click Set a custom window to choose the days, hours, and timezone for this site, or Change team default window to change it for every site on the team.
Click Save.
To hold everything still for a while, for example during a sale or a launch, add a Blackout Period with a start date, an end date, and an optional reason. Automated Safe Updates pauses on that site for those dates.
Security updates
When an update fixes a known security vulnerability, it can go out as soon as it's available instead of waiting for the update window. This is on by default.
On the Updates page, find Security Updates.
Choose Immediately or Next update window for this site, or leave it on the team default.
Click Save.
Security updates are always applied. This setting only controls when. With Next update window selected, they run first, before other updates.
WordPress core
On the Updates page, find WordPress Core Updates.
Choose one of:
Minor & security only (recommended). Wordify applies same-series releases automatically, for example 6.5.1 to 6.5.2: the minor and security fixes.
All updates (including major). Wordify also applies new major versions automatically, for example 6.5 to 6.6, with a verified restore point and an automatic rollback if the site fails its health check.
Off. Wordify never applies core updates automatically, including security releases. Core updates are still listed for you to apply yourself.
Click Save.
Plugins and themes
Each plugin and theme has its own Update automatically switch.
Open the site's Plugins or Themes page.
Use the Update automatically switch on each item, or tick several and choose Update automatically or Stop updating automatically from the bulk actions.
On the Themes page, click Save when you're done.
Anything set to update automatically is included in Automated Safe Updates. Anything switched off waits for you.
For plugins and themes you add later, the New Plugins & Themes setting on the Updates page decides whether they're kept updated automatically. It's on by default, and you can change it per site or for the whole team.
See what was updated
Open Tasks and look for Automated Safe Updates entries. Each one lists the site, the packages, and the version each update moved from and to.
Open a run to see the outcome for each update: Applied, Didn't apply, Not attempted, Waiting, or Rolled back, along with the restore point and health check steps.
On the site's Updates page, the last run is summarised at the top with a View this run link.
Anything that needs a decision from you appears in Site Health on the Dashboard, and you get an email when Wordify has protected a site or an update didn't apply.
Updating manually
You can still apply any update yourself from the Plugins, Themes, or Updates pages. Tick Safe Update in the update dialog and Wordify runs a health check before and after the update, then rolls the update back automatically if the site goes down. On core and bulk updates, Safe Update takes a full backup first and verifies the site afterwards.
Troubleshooting
An update says “Didn't apply”. The update was attempted but the new version never became active, so the site stays on the previous version and nothing else changed. The most common cause is a paid plugin or theme whose licence has lapsed. Renew the licence and Wordify keeps retrying on its own.
A release is “On hold”. The update was applied, didn't pass its health check, and was rolled back. Wordify won't retry that release. A newer release is tried as normal. If you want to move ahead anyway, run the update manually.
Updates are “Paused”. The site was down when a run was due. Fix the site, and updates resume automatically.
A run shows “Not attempted”. A gate stopped the update before anything was applied: a blackout period, a closed update window, or a restore point that couldn't be verified. It's picked up again in the next run.
Need help?
If anything here doesn't match what you see, or a site isn't behaving after an update, contact support from the Support link in the Console. We're available 24/7 and respond within an hour.