Automated SiteGround WordPress Update Check
Every Monday, WebRun signs in to SiteGround, opens each WordPress install on the account, records the core version, the plugin updates waiting, and the PHP version in use, confirms a recent backup exists, posts the out-of-date sites to Slack, and drafts a client note in Gmail.
How do I keep every WordPress site on my hosting account up to date?
Every Monday, WebRun signs in to SiteGround, opens each WordPress install on the account, and records the core version, plugin updates waiting, and the PHP version in use. It checks a recent backup exists, posts the out-of-date sites to Slack, and drafts a client note in Gmail.
- Every install's version state is known before an update is attempted
- Sites without a recent backup are flagged before anyone touches them
- Client notes arrive drafted, ready to review and send
Built for web agencies · freelance developers · site maintainers · IT teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
my.siteground.comin a real browser with your saved login - no setup, no API keys. -
1
SiteGround - read versions on every site
siteground.com
WebRun opens SiteGround to read versions on every site. - Sign in to SiteGround and list every site on the account
- For each WordPress install record the core version, the plugins with updates waiting, and the PHP version the site runs on
- Check when the most recent backup was taken and note anything without a fresh one
Done when Every site has its core, plugin, PHP, and backup status recorded.
-
2
Gmail - draft the client update note
gmail.com
WebRun opens Gmail to draft the client update note. - Draft a short note per client site explaining what is out of date and what you propose to update
- Include the backup date so the client can see the work is safe to schedule
- Leave every note in Drafts. Nothing is sent to a client until you approve it
Done when A client note is drafted in Gmail for each site that needs work.
-
3
Slack - post the patch list
slack.com
WebRun opens Slack to post the patch list. - Post the patch list to your team channel, furthest behind first
- Show each site with its core version, plugin updates waiting, PHP version, and last backup date
- Flag any site with no recent backup as do not update until backed up. WebRun never runs an update itself
Done when This week's patch list is in Slack with backup warnings marked.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it run the updates for me?
No. WebRun reports what is out of date and whether a backup exists. Applying core, plugin, and PHP updates stays with you, because an update can break a live site.
Does it email clients on its own?
No. Client notes are left in Gmail Drafts for you to read, edit, and send. The Slack post is internal to your own team.
Why does it check the backup date?
Because updating without a recent backup is the risky part. Any site whose last backup is stale is marked do not update until backed up, so the safe ones are obvious.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.