Maintenance loop · Beginner · 15 min weekly
How to keep site software updated — A Weekly Update Pipeline With a Rollback That Works
Patching only feels risky when there is no way back — build the clone, apply, verify, promote loop once and the weekly quarter-hour becomes genuinely uneventful.
The short answer
Turn patching into a pipeline with four fixed stages — inventory, clone, apply and verify, promote — and the weekly fifteen minutes stops being a gamble, because every stage has a defined output and the last one has a tested way back.
The inventory is wider than most people keep: core, plugins, themes, and the runtime itself. PHP version is an update, and an unsupported one is a security gap that no plugin screen will ever warn you about. wp plugin list --update=available and cPanel's MultiPHP screen between them cover the whole surface.
By the HostingFast team · Reviewed 24 August 2026
Beginner
Assumed level
Quick
Weekly time
5
Steps to done
24/7
Engineers on call
Fifteen minutes a week, at a fixed time, is the entire commitment. Small batches are what make failures attributable; a quarterly heroic update session is what makes them mysterious.
WP-CLI over SSH is available on every shared tier here, and WordPress Toolkit is on board for the clone-and-promote part. The business tiers include staging copies as standard.
The inventory includes the runtime
Core, plugins and themes are the obvious three, and wp core check-update plus wp plugin list --update=available lists them in seconds. What people forget is the layer underneath: the PHP version your site runs on. An end-of-life PHP release stops receiving security fixes entirely, and nothing inside your application will mention it.
For a Composer project the dependency tree counts too. composer outdated tells you what has moved, and composer audit flags advisories against what you have installed. Both belong in the same weekly window as the plugin screen.
The loop: clone, apply, diff, promote
WordPress Toolkit will clone the live site to a staging copy, and the business tiers include staging copies in the plan. Apply the updates on the clone, then walk the paths that matter — not the homepage, which is the least likely thing to break. A checkout, a form submission, a logged-in view, a template with a custom field.
Then promote. The value of the loop is not that updates never break anything; it is that when they do, they break somewhere nobody is buying anything, and you find out before your customers do.
What to automate, and what to hold back
Minor core releases and well-maintained plugins can update themselves, and the security fixes that matter most travel down exactly that channel — often while you are asleep. Turn that on and stop thinking about it. Softaculous will also take a backup before each update it applies, which costs nothing.
Hold manual control over anything touching checkout, payment, a page builder or a custom template. Those are the updates where a visual diff genuinely matters, and where the fifteen minutes you spend looking is repaid the one time in twenty that something shifts.
Rollback is the feature you are actually buying
Every plan takes a daily backup, Nitro takes one every six hours, and the restore runs from your panel without a ticket. That is your rollback. The important part is that you have used it once, deliberately, on a day when nothing was wrong — an untested restore is a belief rather than a plan.
Add one measurement to the promote step: take a TTFB reading before and after. An update that adds two hundred milliseconds to your response time is a regression, and it is much easier to attribute on the day it lands than a month later when nobody remembers what changed.
The maintenance tooling included on our plans
WordPress Toolkit is on board with updates handled for you, Softaculous manages the applications it installed, and per-site PHP switching lives in the control panel — so the whole inventory is manageable from one account.
Staging environments for testing changes before they ship are included on the plans that carry them, and the business tiers include staging copies as standard.
- The runtime counted as part of the inventory
- A four-stage loop with a defined output per stage
- Automation split from the updates that need eyes
- A rollback you are told to test before you need it
Why HostingFast
Standard on every plan
A pipeline, not a chore
Four stages with defined outputs, so the weekly session has a beginning and an end rather than an open-ended risk.
PHP counted in
The runtime is part of the inventory, because an end-of-life PHP release is a gap no plugin screen will report.
Command-line first
wp core check-update, wp plugin list and composer outdated give you the whole picture without clicking through three screens.
Clear automation boundary
What can safely self-update and what needs a human looking at it, with the reasoning rather than a blanket rule.
Tested rollback
Daily backups on every plan and six-hourly on Nitro, plus the instruction to actually use a restore once before you need one.
Performance kept in scope
A TTFB reading either side of the promote step, so a slow update is caught on the day it shipped.
Quick Start
From order to online
- 1
List what is behind, from the command line
wp core check-update, wp plugin list --update=available, wp theme list --update=available, and your PHP version from cPanel's MultiPHP screen. On a Composer project add composer outdated. Two minutes, complete picture.
- 2
Take the snapshot you would genuinely restore
The panel's backup, not a copied folder. Every plan takes one daily and Nitro every six hours, but taking one immediately before a batch means your rollback point is minutes old rather than hours.
- 3
Apply on the clone and walk the real paths
WordPress Toolkit staging, or the staging copy included with the business tiers. Then test a checkout, a form, a logged-in view and a custom template — the homepage is the least informative page you could click.
- 4
Promote, then measure what you promoted
Push it live, then check the error log and take a TTFB reading against your baseline. An update that costs two hundred milliseconds is a regression you want to catch today, not in a quarterly review.
- 5
Retire whatever you keep deferring
The plugin whose update you have postponed three weeks running is telling you something. An abandoned or fragile component is a scheduled incident; replace it rather than granting it a permanent exemption.
Built In
Loaded onto every plan
- WordPress Toolkit on board, with updates handled for you
- Staging environments for testing changes before they ship
- Full SSH access with WP-CLI, Git and Composer on every shared plan
- Per-site PHP version switching from the control panel
- Softaculous auto-update with a backup taken before each update
- Daily backups on every plan, six-hourly on Nitro, restored by you
- Imunify protection while you are between patches
- NVMe SSD storage behind a LiteSpeed cache on every tier
- Money-back cover: 30 days on hosting plans, 7 on reseller
- Human support on duty every hour of every day
Frequently Asked
What people ask us most often
How do I run WordPress updates from the command line?
Over SSH, which is included on every shared tier. wp core check-update shows what is available, wp plugin update --all applies the plugin batch, wp theme update --all does themes, and wp core update handles core itself. Add --dry-run first if you want the list without the action. The advantage over the admin screen is that it scripts cleanly, so the same three commands work across every site you run.
Which updates should never apply automatically?
Anything that renders your money-making path or your layout: payment gateways, checkout extensions, page builders and the theme itself. Those are the updates where a visual diff on a staging copy earns its keep. Minor core releases and small, well-maintained utility plugins are the opposite case — the risk of applying them automatically is far lower than the risk of leaving them for a fortnight.
How do I tell whether an update made the site slower?
Take a TTFB reading before and after: curl -o /dev/null -s -w 'ttfb %{time_starttransfer}\n' against your key templates, three runs each, logged out. Do it as part of the promote step and you have attribution on the day. Do it a month later and you have a slow site and twenty candidate causes. On Nitro, PHP X-Ray on CloudLinux Pro will point at the specific slow call rather than leaving you to bisect.
Does changing the PHP version count as an update?
Yes, and it is the one people leave out. An end-of-life PHP release stops receiving security fixes, and your application will never mention it. Switch versions per site from the control panel, test on a staging copy first because a major PHP jump can surface deprecations in old plugin code, and keep the version in the same weekly inventory as everything else.
Keep reading
How to Move a Website to a New Domain
Move a site to a new hostname without losing the rankings you already have.
How to Choose a WordPress Theme
Choose a theme on what it costs to render, not on what the demo looks like.
Software Startups — Hosting Guide
How a startup's stack choices play out on shared hosting with real limits.
Domain Names
Registration, renewal and delegation, with your first year free on annual plans.
Web Hosting
NVMe behind a LiteSpeed cache, with SSH, staging and per-site PHP included.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Patch on a platform with a rollback in it.
WordPress Toolkit and staging, WP-CLI over SSH, per-site PHP switching, daily backups you restore yourself, and support answering at any hour.
View Domain Names plans