Backups & maintenance · Guide
How to Update Your WordPress Website Safely (Core, Plugins, Themes and PHP)

Short answer
To update your WordPress website, take a full backup, then go to Dashboard > Updates and update WordPress core, followed by plugins and themes. Test the site's key pages, forms and checkout afterwards. For important sites, try updates on a staging copy first, update one plugin at a time, and keep your PHP version supported by your host.
Key takeaways
- Always take a full backup before updating.
- Dashboard > Updates shows core, plugin, theme and translation updates.
- Update one item at a time on important sites, testing in between.
- Staging sites let you test updates without risking the live site.
- Keep PHP on a supported version; it affects speed and security.
Why should you update your WordPress website?
Updates fix security holes, bugs and compatibility issues and add features, so skipping them leaves your site more exposed and harder to maintain over time.
Most hacked WordPress sites run outdated plugins or themes. The OWASP Top 10 lists vulnerable and outdated components as a major web risk.
Updates also keep the site compatible with newer browsers, PHP versions and services such as payment gateways.
Regular small updates are easier and safer than one huge catch-up after months.
When many updates pile up, a single problem is harder to trace because so much changed at once.
The WordPress documentation on updating WordPress covers the official process.
What should you do before updating?
Take a full backup of files and database, note which plugins and themes have updates, read changelogs for major version jumps, and pick a quiet time.
Store the backup off the server, such as in cloud storage.
Many hosts take daily backups, but check how long they keep them and how quickly you can restore one.
Check that you can restore the backup. An untested backup may fail when you need it.
Write down which version of each plugin you are running before updating. It makes rollbacks much easier if something fails.
| Step | Why |
|---|---|
| Full backup | Lets you undo anything |
| Read changelogs | Spot big changes early |
| Quiet time | Fewer visitors affected by problems |
| Staging test | Catches conflicts safely |
How do you update WordPress core?
Go to Dashboard > Updates and click Update to the latest version, or the update button in the notice at the top of the dashboard; WordPress downloads and installs it automatically.
The site enters maintenance mode for a short time during the update.
Do not close the browser tab or navigate away until the update finishes, or the site can stay stuck in maintenance mode.
Minor security releases often install automatically. Major versions may need you to click update unless auto-updates are on.
Major releases bring new features and occasionally change how the editor or themes behave, so read the release notes first.
With WP-CLI, the wp core update command updates core from the command line.
What about translation updates?
Translations for WordPress, plugins and themes update separately, also from Dashboard > Updates, and they are low risk because they only change text.
Keeping them current matters on multilingual sites, where outdated translations show untranslated strings after updates.
How do you update plugins?
On Dashboard > Updates or the Plugins screen, select plugins with updates and click Update; on important sites, update them one at a time and check the site after each.
Premium plugins need an active license to receive updates.
Some premium plugins update through their own dashboard screens. Check them separately if they never show up in Dashboard > Updates.
If updates do not appear, our guide on plugin updates not showing explains the common causes.
Remove plugins you no longer use. Inactive plugins can still carry security risks.
Fewer plugins also means fewer updates, which makes each maintenance session quicker.
How do you update themes?
Update themes from Dashboard > Updates or Appearance > Themes; if you edited theme files directly, those changes will be lost, which is why custom code belongs in a child theme.
Our explainer on what a child theme is shows how to keep changes safe.
Block theme style changes made in the Site Editor are stored in the database and survive theme updates.
Check the site design after a theme update, especially headers, menus and shop pages.
If your theme is no longer updated by its developer, plan a move to a maintained theme before it becomes a security problem.
Should you turn on automatic updates?
Automatic updates suit trusted, well-maintained plugins and minor core releases, while complex plugins such as page builders or store extensions are better updated manually after testing.
Our guide on enabling automatic updates for plugins shows the per-plugin settings.
WordPress emails the admin address after automatic updates, so you know what changed.
Read those emails. They are often the first sign that an update failed or was rolled back automatically.
Combine auto-updates with daily backups and uptime monitoring.
Uptime monitoring alerts you quickly if an automatic update takes the site down overnight.
How do you update PHP?
Change the PHP version in your hosting control panel to a newer supported version, after checking that your plugins and theme are compatible.
PHP versions stop getting security fixes after a few years. The PHP project's supported versions page shows which are still maintained.
Our guide on updating the PHP version walks through the steps and checks.
Test on staging first, because old plugins can break on newer PHP.
Turn on debug logging while testing a new PHP version, so warnings appear in the log before they become fatal errors.
How do you test after updating?
Visit the homepage, key pages, a post, the contact form, the shop and checkout if you have one, and log in and out, checking for errors and layout problems.
Submit a test form and confirm the email arrives.
If you run a membership or learning site, log in as a test member and check that restricted content still works.
Clear caches so you see the updated site, not an old cached copy.
Purge your CDN cache as well if you use one, since it can keep serving old scripts and styles.
Check Tools > Site Health for new warnings.
Look at your site in a private window and on a phone too. Some problems only appear for logged-out visitors or on mobile layouts.
What if an update breaks your site?
Roll back the item that caused the problem, restore your backup, or disable the plugin by renaming its folder, then report the issue to the developer.
Our guide on fixing a site broken after a WordPress update covers recovery steps.
Our guide on rolling back a plugin update shows how to return to the previous version.
If the site shows a maintenance message forever, our guide on being stuck in maintenance mode explains the quick fix.
How often should you update?
Check for updates at least weekly, apply security updates as soon as possible, and schedule larger updates for a regular maintenance window.
A short weekly routine prevents risky backlogs.
Put the routine in a calendar so it happens even in busy weeks. Ten minutes a week is usually enough for small sites.
Our WordPress maintenance checklist puts updates alongside backups and security checks.
Keep a simple log of what you updated and when. It helps link any later problem to a specific change.
Agencies and busy sites often use a monthly maintenance window for major updates and test them on staging first.
Tell clients or your team when the window is, so nobody publishes or launches campaigns during updates.
Do WooCommerce sites need extra care?
Yes. Stores should test updates on staging, update WooCommerce and its extensions together when compatible, run any database updates it asks for, and place a test order afterwards.
Our guide on updating WooCommerce safely covers the store-specific steps.
Avoid updating during sales or peak traffic.
Check payment gateway extensions especially closely. A broken checkout costs sales every minute it stays broken.
How do you use a staging site for updates?
Copy the live site to staging, run all updates there, test thoroughly, then repeat the same updates on live, or push staging to live if your host supports it.
Our guide on setting up a staging site shows the common methods.
Refresh staging from live before testing, so it matches the current site.
Block search engines and real payments on staging, so tests do not create duplicate pages in search results or real charges.
Frequently asked questions
How do I update my WordPress website?
Back up the site, then go to Dashboard, Updates and update WordPress core, plugins and themes. Test key pages, forms and checkout afterwards.
Is it safe to update WordPress?
Yes, when you back up first and test afterwards. For important sites, test updates on a staging copy and update one plugin at a time.
Should I update plugins or WordPress first?
Commonly WordPress core first, then plugins and themes. Read changelogs, because some plugins need a new core version and others need updating before a major core release.
How often should I update my WordPress site?
Check for updates at least weekly, apply security updates quickly, and plan larger updates in a regular maintenance window with backups and testing.
What do I do if an update breaks my site?
Roll back the plugin or theme that caused it, disable it by renaming its folder, or restore your backup, then report the problem to the developer.
Sources
- Updating WordPress WordPress.org Documentation
- wp core update WP-CLI Command Reference
- Supported Versions PHP
- A06:2021 Vulnerable and Outdated Components OWASP
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


