Update Plugins Across WordPress Sites from GoBuildWP Cloud

What the Updates screen shows

Open Updates in your Cloud account at https://app.gobuildwp.com. Four counts sit at the top: sites with updates, sites with a WordPress core update, plugin updates and theme updates. Below them, each site that needs something has a card listing every pending item with the installed version and the new one, the time WordPress last checked, and an Open in wp-admin link to that site's own Updates screen.

Switch between By site and By plugin or theme. The second view groups one release across every site that needs it, so a plugin that is behind on eight sites shows as one entry with eight sites under it.

The lists come from each site's own WordPress update check, read from what WordPress has already stored, so a site answers Cloud without asking wordpress.org or any other source. Sites report every 15 minutes. A site needs GoBuildWP Free 1.18.0 or newer to report at all; older sites are named in a note at the top of the screen. Update the plugin on those sites, then use Check now on the site's page in Cloud.

• GoBuildWP Free 1.18.0 or newer on every site
• No site named in the not-reported note
• A recent WordPress check time on each card

Who can update from Cloud

Everyone in the workspace can see the list. Updating from Cloud needs a GoBuildWP Pro licence linked to the Cloud account, on any Pro plan. Without one, Update selected, Update all on all sites and each card's Update all are shown but locked and marked Pro; Open in wp-admin still works.

Owners, admins and members can update. A client you invited sees pending updates on the sites shared with them and no buttons at all.

WordPress core is listed for information only. Cloud updates plugins and themes, not WordPress itself, so update core from each site's wp-admin.

Choose what to update

There are four ways in, and all of them end on the same confirm screen. Tick single updates in the By site view and select Update selected. Use Update all on a site's card for everything that site needs. In the By plugin or theme view, Update on all updates one release on every site that needs it. Update all on all sites takes every pending plugin and theme update on every site.

Cloud checks each picked item against what the site last reported before planning anything, so an update someone has since applied in wp-admin drops out instead of running twice, and a selection cannot name anything the site did not list as pending. One run takes up to 500 updates.

The confirm screen

Nothing runs until you confirm. The screen lists every update grouped by site, with the version change, and labels how each one will run.

Safe update, auto-rollback: the site has GoBuildWP Pro. For eligible updates, it checks backup freshness, keeps a zipped file copy and compares selected URLs and health checks before and after the update. Detected failures trigger a file-recovery attempt; a failed restore is reported. This is not a full visual, checkout or database test, and the copy does not restore database changes.

Plain update, no rollback: the site has only GoBuildWP Free. WordPress's own updater runs and the old version is not kept.

If a site offers Cloud no update tool, because its safety profile or a switched-off ability rules it out, a red note names each update left out and the site it is on. The button at the bottom states how many items on how many sites will run.

• Every row is an update you meant to pick
• You know which rows are plain updates
• Nothing important is in the left-out note

Backups before an update

Two options sit above the button, both ticked by default. Back up each site first makes Cloud start a backup with the site's UpdraftPlus, BackWPup or All-in-One WP Migration, then look every minute, for up to 30 minutes, for a newer successful backup. Only when it appears do that site's updates start. If none lands in time, that site's updates are recorded as not run and the other sites carry on. The option covers sites with GoBuildWP Pro and UpdraftPlus, BackWPup or All-in-One WP Migration (All-in-One WP Migration needs GoBuildWP 1.18.2 or newer and Pro 1.12.2 or newer); any other site's card says why it can't be backed up from Cloud, and it updates without this step.

Require a recent backup applies to safe updates. A site with GoBuildWP Pro then refuses to update unless UpdraftPlus, Duplicator, BackWPup or All-in-One WP Migration finished a successful backup in the last 24 hours. Untick it to update anyway; the safe update still keeps its rollback copy and attempts file recovery when selected checks fail; restoration can fail and does not reverse database changes.

What happens on each site

After you confirm, Cloud opens the run with one row per site. A site runs one update at a time, never two at once, and each result is added to its row as it finishes: updated, rolled back, refused or not run, with the site's own reason.

Cloud passes the confirmation on, because a person confirmed that exact update, but the site's rules still decide. A Read Only site refuses. A site whose approval mode is set to a person approving waits until someone approves in its wp-admin. Each update is recorded in the site's change ledger like any other call.

A safe update can be undone from the site's change ledger for 7 days. A plain update cannot be undone through GoBuildWP; restore from a backup instead. The run and its results stay in Cloud for 30 days.