GoBuildWP Cloud · Updates
Update all WordPress sites, and review the changes before they run.
Update all WordPress sites you look after from one place. GoBuildWP Cloud lists pending updates and asks you to confirm the exact plugin and theme changes. On eligible sites with Pro, guarded updates check selected URLs and attempt file recovery when those checks fail. Review the backup options and each site's update mode before starting.
Free shows what is pending, Pro updates from Cloud, Sites need GoBuildWP Free 1.18.0+
What needs updating
app.gobuildwp.com- shop.example
- 4 pending · safe update
- clinic.example
- 2 pending · plain update
- blog.example
- WordPress core 1 behind
- Same plugin, 6 sites
- Update on all 6…
Representative sites. Nothing runs until the confirm screen.
Why it exists
Updating twenty sites should not mean twenty logins
Most update work is not the click, it is the round of logging in to every site to find out which ones need it. Cloud does the round for you.
Each connected site tells Cloud which plugins and themes have a newer release, using the check WordPress already runs. You open one screen and see the whole picture: which sites are behind, and which plugin is behind on most of them.
From there, with a Pro licence, the same screen runs the updates. You can be as narrow or as broad as the day allows: one plugin on one site, everything on one site, one plugin wherever it is installed, or every pending update everywhere. All four go through the same review before anything happens.
How it works
Updates in 4 steps
See what each site needs
Pending plugin, theme and core updates for every connected site, grouped by site or by plugin, with installed and new versions side by side.
Pick as much as you want
Tick single updates, take one site's whole list, roll one plugin out to every site that has it, or select everything everywhere.
Confirm the exact list
A confirm screen lists every update per site and its update mode, including whether a file-recovery attempt is supported. Nothing starts before you confirm.
Back up, update, check
When Back up each site first is ticked, Cloud requests a fresh backup and waits for a reported success. Eligible sites with Pro compare selected URLs and health checks before and after updating, then attempt file recovery if those checks detect a failure. Check the site's result before moving on.
Safety
What keeps it safe, and where it stops
Built in
- You see and confirm every single update before Cloud starts any of them
- With the backup option selected, sites Cloud can back up wait for a reported new successful backup and are skipped if none arrives within 30 minutes; sites it cannot back up skip that step
- On eligible sites with Pro, failed selected checks trigger a file-recovery attempt. A retained copy can support undo for 7 days, subject to expiry and installed-version checks
- One update at a time per site, so a site is never in the middle of two
- Each site's safety profile still applies: a Read Only site refuses, a site that needs a person's approval waits for it
What it does not do
- WordPress core is shown but not updated from Cloud; use the site's own wp-admin
- On a site with only GoBuildWP Free, an update runs without a backup check or rollback, and the confirm screen says so
- Cloud does not fetch packages itself: each site downloads from its usual update source
- Guarded updates exclude GoBuildWP itself, protected companion plugins and single-file plugins. A failed file restore is reported; recovery is not guaranteed
- HTTP and health checks do not establish that every layout, checkout, form or database migration still works. Test those workflows separately; file recovery does not restore the database
Free and Pro
What you get without Pro, and with it
| Feature | Cloud Free | With a GoBuildWP Pro licence |
|---|---|---|
| See pending updates on every site | Yes | Yes |
| Update from Cloud, one site or all of them | Locked | Yes |
| Back up first, from Cloud | No | Yes, on sites with GoBuildWP Pro and UpdraftPlus or BackWPup, or All-in-One WP Migration with GoBuildWP 1.18.2+ and Pro 1.12.2+ |
| File recovery after failed selected checks | No | Attempted for eligible updates on sites with GoBuildWP Pro |
Cloud has no price of its own: it comes with every GoBuildWP Pro licence. Pro pricing
FAQ
Questions about Cloud updates
The rest of Cloud: backups, safety policies, team and clients, seo report, and how Cloud connects your sites.
Can GoBuildWP Cloud update all my WordPress sites at once?
Yes, with a Pro licence linked to your Cloud account. Update all on all sites takes every pending plugin and theme update on every connected site, shows you the full list, and runs it once you confirm. You can also pick single updates, one site, or one plugin across sites.
What happens if an update breaks a site?
For an eligible guarded update on a Pro site, selected URLs and health checks are compared before and after. A detected failure triggers an attempt to restore the saved plugin or theme files; a failed restore is reported. These checks do not cover every visual or business workflow, and file recovery does not restore the database. Free-only sites use plain updates without this recovery path, as shown on the confirm screen.
Is it safe to let Cloud update client sites?
Cloud only asks; each site decides. A site's safety profile and approval settings apply to updates started from Cloud exactly as they do to any other call, and every update lands in the site's change log.
Do I need Pro to use the Updates screen?
No. Without Pro you see every pending update on every connected site and can open each site's own Updates screen from there. Updating from Cloud is what needs Pro.
Find out which sites are behind, in one screen.
Connect up to 3 sites free and see every pending update. Add Pro when you want Cloud to run them.