Automated Hostinger WordPress Update Checks
Every Monday, WebRun opens your Hostinger panel, walks every website on the account, checks each WordPress install for an outdated core version, plugins, and themes, drafts a Gmail summary for the site owners, and books a maintenance slot in Google Calendar to do the work.
How do I check WordPress updates across all my hosted sites?
Every Monday, WebRun opens your Hostinger panel, checks each WordPress install for an outdated core version, plugins, and themes, and builds one patch list across every client site. It drafts a Gmail summary for the site owners and books a maintenance slot in Google Calendar, so nothing runs unpatched.
- One patch list replaces logging into every site by hand
- Outdated core versions are ranked ahead of routine plugin updates
- The maintenance slot is already on the calendar when Monday starts
Built for web agencies · freelance developers · WordPress maintainers · hosting resellers
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
hpanel.hostinger.comin a real browser with your saved login - no setup, no API keys. -
1
Hostinger - check every WordPress install
hostinger.com
WebRun opens Hostinger to check every WordPress install. - Open the Hostinger panel and list every website on the account
- For each WordPress install, read the core version and note whether a newer one is available
- List the plugins with updates waiting, and mark any that are inactive or abandoned
- List the themes with updates waiting, including the parent theme behind a child theme
- Note the hosting plan behind each site so shared resources are considered before a bulk update
- Rank the sites by how far behind they are, with core updates ahead of plugin updates
Done when Every WordPress install is listed with its outdated core, plugins, and themes.
-
2
Gmail - draft the owner summary
gmail.com
WebRun opens Gmail to draft the owner summary. - Draft an email per client summarising what is out of date on their site
- Say plainly which updates are security-related and which are routine
- Leave every email in Drafts. WebRun never emails a client and never runs an update on a live site
Done when A per-client summary sits in Drafts, unsent.
-
3
Google Calendar - book the maintenance slot
calendar.google.com
WebRun opens Google Calendar to book the maintenance slot. - Add a maintenance block to your own calendar sized to the number of sites needing work
- Put the site count and the highest-risk site in the event title
- List the sites in the event description so the slot opens ready to work
- Invite nobody. Any invitation to a client or a colleague is left for you to send
Done when This week's maintenance slot is on your calendar with the site list attached.
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 itself?
No. WebRun reads each install and reports. Applying a core, plugin, or theme update on a live client site stays a human job, done in your own maintenance window with a backup in place.
Does it email my clients?
No. It drafts a per-client summary in Gmail and leaves it in Drafts. You read it, edit the wording, and decide whether that client hears from you this week.
How does it rank which site to patch first?
Sites furthest behind come first, with an outdated WordPress core ranked ahead of plugin and theme updates, and security-related updates called out by name in the summary.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.