# WordPress site out of date? Catch up on updates safely

> Your WordPress site is far behind on updates. We update it in safe steps on a staging copy, replace abandoned plugins and test before anything goes live.

## Why does this happen?

A site falls behind when updates stop being routine. Each skipped update makes the next one riskier, so it gets put off again, until the Updates screen holds a long list nobody wants to touch. The way out is a planned catch-up: a full inventory, a staging copy, updates in a safe order, and tests after every step.

The reasons we see most often:

- **An update broke the site once.** After that, every Update button feels like a gamble, so nobody presses it.
- **Nobody owns the site any more.** The developer or agency that built it moved on, and the owner was never shown how updates work.
- **Premium licences lapsed.** Many premium plugins and themes only show updates while the licence is active, so the dashboard looks calmer than it really is.
- **The server’s PHP is old.** WordPress refuses updates whose requirements your site does not meet. Plugins show “This update does not work with your version of PHP”, and Dashboard, Updates can say you cannot update WordPress until PHP is newer.
- **Plugins were abandoned.** Their authors stopped releasing updates, or WordPress.org closed them. WordPress does not warn you about either on the Plugins screen. A closed plugin simply never shows an update again.

## Try this first

Nothing here presses an Update button or changes a setting, so it is safe on a live store.

1. **Take stock before you press anything.** Open Dashboard, Updates to see every waiting update for WordPress, plugins and themes. Then open Tools, Site Health. It flags waiting updates, and its Info tab shows your PHP version under Server. Write the list down or take screenshots.
2. **Look for abandoned plugins.** On the Plugins screen, click “View details” under each plugin and note “Last Updated” and “Compatible up to”. If a plugin has no “View details” link, search for it on WordPress.org. A plugin page that warns it has not been tested with recent releases, or says the plugin has been closed, goes to the top of your list.
3. **Check that a backup really exists.** In your hosting panel, find the most recent backup and confirm it includes the files and the database. If your host offers a download, keep a copy somewhere other than the server. Do not restore anything.
4. **Find out what your host offers.** In your hosting panel or its help pages, look for a staging tool and the list of PHP versions your plan can run, and note both. Do not switch PHP yourself yet; on an old site that alone can take it down.

Stop there and hand it over if WooCommerce, your payment gateway, your theme or your page builder is a major version or more behind, if any plugin has been closed, or if Dashboard, Updates says you cannot update because of your PHP version. Those are the updates that break stores when they are done in one go.

## Why does the order of updates matter?

Every component states which WordPress and PHP versions it needs. If WordPress is too old, newer WooCommerce releases will not install. If PHP is too old, WordPress itself will not update. Update the wrong thing first and you are left with a half-updated site that is harder to fix than the old one.

On staging we work out the order your requirements allow, update one step at a time and test after each. On WooCommerce stores that includes the database updates that run after WooCommerce updates, the template overrides in your theme, and a check that every extension that handles orders is compatible with your order storage setting before anything about it changes.

## What happens on the live site?

The live site keeps working while we test. When staging is clean, we take a fresh backup and repeat the same tested steps on the live site at a quiet time. On a store we never copy the staging database over the live one, because that would erase orders placed in the meantime. Afterwards we check your key pages, place a test order and send you a report listing every version change and every plugin we replaced. To stay current from then on, every care plan includes [BoltPress Security](https://boltpress.co/wordpress-security/): updates run on a schedule with a backup first, and roll back automatically if the site fails its health check.

## Is my site behind?

Our free [WordPress audit](https://boltpress.co/wordpress-audit/) shows outdated and abandoned plugins and whether your WordPress version is current. Our post on [what is silently breaking your site](https://boltpress.co/5-things-silently-breaking-your-wordpress-site-right-now/) explains why that matters.

If one recent update has already broken the site, start with [site broken after an update](https://boltpress.co/fix-wordpress/site-broken-after-update/). If your host is retiring your PHP version, see the [PHP upgrade fix](https://boltpress.co/fix-wordpress/php-version-upgrade/), and once you are current, [security hardening](https://boltpress.co/fix-wordpress/wordpress-security-hardening/) closes the other common gaps. Every other problem is on the [Fix WordPress](https://boltpress.co/fix-wordpress/) page.