Skip to main content

Walkthrough · Beginner · 20 minutes per cycle

How to Update WordPress Safely

Keep everything current without gambling on what each update might break — a hands-on walkthrough in plain words that names the classic mistake before you reach it.

The short answer

One line covers it: keep everything current without gambling on what each update might break — a beginner-level job of roughly 20 minutes per cycle.

Below are the precise steps, the classic stumble, and one tip from the support desk. Wherever the platform already does a step for you, the guide says so rather than handing you a machine's chores.

By the Hosting & Domains team · Reviewed 18 August 2026

Beginner

Skill rating

Quick

Time budget

5

Steps in total

24/7

Support on call

No technical background needed. This walkthrough was written for first-timers, proven on our own hardware, and honest about which parts are genuinely tricky rather than merely unfamiliar.

A promise before step one: nothing here is a one-way door. Any step with teeth is flagged, and the way back is printed beside it.

The route, mapped end to end

Over the whole job, you will take a snapshot first, without exception, work in the right order, rehearse the risky ones, walk the site afterwards and automate the low-risk layer.

No part of this needs code or a terminal unless the guide says so plainly — and where it does, the exact commands are printed. The step-by-step is below, with the surrounding sections supplying the context that makes it hold.

The error nearly everyone hits

Stopping updates in the name of stability. A site left months behind steadily gathers the very vulnerabilities that cause the instability the freeze was meant to avoid.

Forewarned is genuinely forearmed here. This one mistake accounts for most of the frustration the topic ever causes — and it disappears entirely once somebody points it out.

The support desk's own short cut

A quarter of an hour each week beats a marathon twice a year. Small differences are easy to diagnose when they misbehave, and the backup-update-check loop becomes second nature quickly.

A minute spent now repays itself every time this job comes round again — and like almost every hosting job, come round it will.

What a Hosting & Domains plan spares you

Steps that never deserved your time are taken out: certificates issue and reissue themselves, the installer handles application setup, the daily copy absorbs the what-ifs, and per-site settings live in a panel rather than a configuration file. The guide covers the remainder — the part that is actually about your site.

Stopped mid-guide at an awkward hour? That is exactly what round-the-clock support is for — say which step you are on and we take it from there.

A WordPress build coming together on a plan that keeps it patched

Why this job is shorter on our plans

Every walkthrough in this library is run on the platform we actually operate — cPanel, LiteSpeed, NVMe, one-click installs — so the instructions match your screen rather than gesturing at it from a distance.

Support means a person at any hour, and the remit covers the awkward practical questions other hosts hand straight back.

  • Every step checked exactly as published
  • The snag named before it arrives
  • The dull steps taken out of your way
  • People reachable at any hour you stall

Why Hosting & Domains

Standard on every plan

Taken from real tickets

These guides came out of the support queue, so every snag flagged is one people genuinely hit.

The snag, flagged up front

The classic error for this particular task is named before step one, which is how 20 minutes per cycle stays 20 minutes per cycle.

The dull parts automated

SSL, backups and installs look after themselves here, leaving the guide to cover only what is genuinely yours.

Help that keeps your hours, not ours

Stuck on step three at midnight? Support answers at any hour, mid-walkthrough included.

Works exactly as printed

Every step is proven on the platform we run — none of the 'your host may vary' hedging.

Jargon never charges you

Every term is defined on the spot or linked to the jargon buster — nothing assumes prior knowledge.

Quick Start

Order placed to site online

  1. 1

    Take a snapshot first, without exception

    One manual backup turns every update from a gamble into something you can undo. This step is the whole safety model; the rest is order and attention.

  2. 2

    Work in the right order

    Plugins, then themes, then core. Read the changelog on anything important, because a 'tested up to' value behind your WordPress version is the warning you get in advance.

  3. 3

    Rehearse the risky ones

    Major version jumps, page-builder releases and WooCommerce updates all deserve a run-through on staging. Our WordPress plans include staging sites for exactly these afternoons.

  4. 4

    Walk the site afterwards

    Homepage, one deep page, a contact form, and checkout where there is one. Two minutes of clicking finds the quiet breakage that would otherwise sit unnoticed for a month.

  5. 5

    Automate the low-risk layer

    Let minor core releases and low-risk plugins update themselves while you keep manual control of the few that carry weight. Selective automation beats either extreme of everything automatic or nothing ever.

Built In

Fitted to every plan

  • People on the support desk every hour of every day
  • LiteSpeed caching in the server itself rather than bolted on by plugin
  • Spam and virus screening on every mailbox by default
  • A renewal figure identical to the one you registered at
  • Staging copies for trying a change before it goes live
  • DDoS filtering absorbed at the network edge
  • WebP image optimisation built in, at no extra charge
  • A daily copy, with restores you run yourself from the panel
  • 99.9% uptime as the target, watched around the clock
  • No set-up charge at any point, and no joining fee

Frequently Asked

The questions that come up most

Should everything update automatically?

For minor core releases and low-risk plugins, yes. Major versions and anything near checkout, memberships or page building deserve a manual pass on staging. Update tools that compare before-and-after screenshots can even take that judgement off your hands.

The site broke straight after an update — what first?

Restore the pre-update backup at once, which is minutes of work from the panel. Then reproduce and diagnose on staging, away from an audience. Debugging live while visitors arrive is the wrong way round: recover first, investigate second.

What is the refund position if I change my mind?

Shared, business, WordPress and WooCommerce hosting get thirty days, and reseller gets seven. VPS and dedicated servers are built to order the moment payment lands, so they sit outside the guarantee — as do domain registrations, where the registry charges the instant the name is secured. Inside the window one request returns the hosting fee, with no retention script to sit through.

What is the uptime commitment, and what happens in a month that misses it?

99.9% — and if a month falls below that through a fault on our side, our terms entitle you to a pro-rated credit; ask and we apply it. Calling it a target rather than a contractual SLA is a deliberate choice. Hardware and network faults surface through platform monitoring, usually before the first customer notices.

Keep reading

  • How to Fix the WordPress White Screen

    Identify what's producing the blank page and clear it step by step — intermediate level, about 20–40 minutes.

  • How to Transfer a Domain

    Shift a domain between registrars while the website keeps running untouched — beginner level, about roughly 15 minutes of work, and up to 5 days before the transfer completes.

  • Best Joomla vs WordPress

    The same call put as a buyer's guide: what to verify, what to ignore, and the plan we would sign.

  • WordPress Hosting

    WordPress looked after for you — LiteSpeed caching, staging copies and a daily backup.

  • Magento Hosting

    Plans carrying the memory and PHP headroom Magento genuinely asks for.

Changing hosts? Run through our checklist first.

A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.

What arrives is the checklist, and then the occasional note on keeping a site quick. Leave whenever you like; the privacy policy covers the rest.

Start on a plan priced without games.

Free SSL, a free migration, renewals billed at the original rate, and people on support around the clock. That is the whole of it.

View WordPress Hosting plans