Talk to a person. We reply within one working day.

SEO and AI search
Web
AI
Resources
WorkAboutStart a project

WordPress care · 21 Nov 2026 · 7 min read

WordPress updates: how to update core, themes and plugins safely

Updates keep a WordPress site secure, and they also occasionally break it. A short routine of backup, test and check makes both risks manageable.

The short answer

To update WordPress safely, take a backup first, apply updates to a staging copy where you can, then update the live site at a quiet time and check key pages, forms and checkout. Update core, themes and plugins one group at a time. Automatic updates suit minor, low-risk changes; check the current documentation for what yours covers.

Why WordPress updates matter, and why they scare people

WordPress updates fall into three groups: the core software, the theme that controls the design and the plugins that add features. Each is maintained by different people on different schedules, and each needs updating. Many updates fix security problems, and running old versions is one of the most common reasons small sites are compromised. That is the case for updating promptly.

The case for caution is also real. A site is a stack of parts written by different authors, and a change to one can clash with another. A plugin may not yet work with a new core version. A theme may rely on a feature that has been changed. The usual result of a bad update is a visible fault, such as a white screen, a broken layout or a form that stops sending, though it can also be subtle.

The answer is not to avoid updating. It is to update with a routine that makes mistakes cheap to undo. That means a backup you trust, a way to try the change before it reaches visitors and a short check afterwards. This guide describes that routine in plain terms, and it applies whoever does the work, whether that is you, a freelancer or an agency.

Should I turn on automatic updates?

It depends on the kind of update and on how closely the site is watched. WordPress has built-in support for automatic updates of core, plugins and themes, and the current documentation describes which are on by default and which you can switch on. Check it, because defaults and settings have changed over the years.

A sensible approach is to treat the three groups differently.

WhatAutomatic updatesReasoning
Core, small security releasesUsually fine to leave onThey are designed to be low risk, and delay leaves holes open
Core, larger releasesUpdate manually after testingBigger changes are likelier to clash with plugins and themes
PluginsOn for simple, well-known ones if the site is monitored; manual for anything that handles payments, bookings or formsA faulty plugin update can affect revenue
ThemesManual, especially if the theme has been customisedUpdates can overwrite changes made directly to the theme files

Automatic updates are a trade: you accept some risk of a fault in exchange for less risk from missed security fixes. If you turn them on, make sure that something tells you when the site breaks. An automatic update that fails at night and goes unnoticed until the morning is the worst combination. Our guide to setting up uptime monitoring alerts explains how to be told quickly.

How do I test before updating?

The safest place to test is a staging site, which is a private copy of your live site where changes do not affect visitors. Many hosts offer a one-click staging copy, and some plugins can create one, so check what your hosting provides. If you have no staging option, ask your developer or host how to make one, because it will pay for itself the first time an update misbehaves.

  1. Take a full backup of files and database, and confirm you know how to restore it. A backup you have never tried to restore is a hope, not a safeguard.
  2. Read the notes for each update. Plugin and theme authors usually describe what changed, and they sometimes warn about compatibility.
  3. Apply the updates to the staging copy, one group at a time: core first, then plugins, then the theme, unless the notes say otherwise.
  4. Test the pages and actions that matter: the home page, a service page, the contact form, search, the checkout if you have one and the login.
  5. Look at the site on a phone as well as a computer, using the approach in our guide to cross browser and device testing.
  6. If everything works, repeat the updates on the live site at a quiet time, then check the same pages again.

If staging is not possible, update live but reduce the risk. Update one thing at a time, so that if something breaks you know which update caused it. Avoid updating a handful of plugins at once and then trying to work out which of them is at fault. Choose a time when you or your developer can respond, not the end of a Friday.

Plugins deserve extra care

Plugins are the most common source of update trouble, simply because there are so many of them and they are written by different people. Each one you add is another thing to update and another possible point of failure. That is one reason to keep the number small, and our guide on how many WordPress plugins is too many covers how to decide.

Before updating a plugin, check whether it is still maintained. A plugin that has not been updated for a long time, or that has been removed from the official directory, is a risk. Replace it with a maintained alternative or remove the feature, because an abandoned plugin cannot be patched when a problem is found.

Take extra care with anything that touches money or personal data. Payment, booking, membership and form plugins deserve a manual update after testing, not an automatic one. Also watch for updates that need a database change, which the plugin usually announces. Those are harder to undo, so make sure the backup is fresh.

Finally, remove plugins and themes you do not use. Deactivated plugins can still contain security problems, so deletion is safer than leaving them switched off.

What do I do if an update breaks the site?

Stay calm, and work from the simplest fix to the most complex. First, find out what changed. If you updated one thing at a time, the culprit is obvious. If you updated several, start with the one most likely to be involved.

  1. Check whether the problem is real and current: reload the page, clear the browser cache and try another device.
  2. If you can still sign in to the dashboard, deactivate the plugin you just updated, or switch back to a default theme, and see if the site recovers.
  3. If you cannot sign in, ask your host or developer to rename the plugin's folder through the file manager or file transfer, which turns it off without the dashboard.
  4. If the cause is not clear, restore the backup taken before the update. This is the quickest way to bring the site back.
  5. Once the site is working, redo the update on staging and look for the cause, or wait for the plugin author to release a fix.
  6. Write down what happened and what fixed it.

Many WordPress versions show a message when a fatal error occurs and can send an email to the administrator with details. Check the current documentation for what your version does, and make sure the administrator email address belongs to someone who reads it. Some hosts also keep error logs, which a developer can read to find the cause.

If the site stays down and you cannot fix it, contact your host's support and your developer straight away. A calm, specific description of what you changed and when saves a lot of time.

A simple update routine

Routines work better than good intentions. A light routine for a small site might look like this: check for updates weekly, apply security updates promptly, test larger updates on staging, keep a note of what was updated and when and review the whole site every few months. If that is too much to remember, write it in a shared calendar.

Updates also affect how a site performs and how visitors experience it, so it is worth checking speed afterwards. Plugin and theme changes can alter loading, which links to the ideas in Core Web Vitals explained. Search engines also change, and while updates to your site and updates to Google are different things, it helps to understand how to respond to Google algorithm updates so that you do not confuse one for the other when traffic moves.

Do not forget the parts that sit underneath WordPress. The hosting environment, the version of the programming language it runs on and the security certificate all need attention. Domains also need attending to, and our guide to domain renewal and expiry covers the one renewal that can take the whole site offline.

If you would rather hand the routine to someone else, a maintenance arrangement from a website development team such as Liftup Technologies can cover updates, backups and checks. Ask what is included, how updates are tested and what happens if one fails, and agree it in writing.

Related guides

Questions and answers

Should I turn on automatic WordPress updates?

Small security releases of core are usually safe to leave automatic. Larger core releases, customised themes and plugins that handle forms, bookings or payments are better updated by hand after testing. Whatever you choose, set up monitoring so a failure is noticed quickly, and check the current documentation for your version.

How do I test a WordPress update before applying it?

Make a staging copy of the site, apply the updates there, and test the home page, forms, search, login and checkout. Many hosts offer staging, so check what yours provides. If you have none, update one item at a time on the live site after a backup.

What should I do if an update breaks my site?

Find which update caused it and deactivate that plugin or theme if you can reach the dashboard. If not, ask your host or developer to turn it off through the file manager, or restore the backup taken before the update. Then retest on staging.

How often should I update WordPress?

Check weekly, apply security updates promptly and test larger updates before applying them. Leaving updates for months makes each one bigger and riskier, so a small regular routine is safer than occasional large catch-ups.

Do I need a backup before every update?

Yes. A recent backup of files and database is what makes an update low risk, and you should know how to restore it. A backup that has never been tested is not something to rely on.

Why not just avoid updating to keep things stable?

Old versions collect known security problems and can stop working with newer hosting software. Avoiding updates feels safe but increases risk over time. A tested routine is safer than staying still.

Tell us what you are building.

A short call, a written plan and a fixed quote. No obligation.

Get a free quote