Updating WordPress is usually a good thing. New versions can improve security, performance, compatibility, and functionality.
But if a website has been sitting untouched for years, updating everything at once can create serious problems.
Older WordPress websites often contain outdated plugins, abandoned themes, old PHP versions, custom code, and integrations that may no longer work with current software.
Before I update an older WordPress site, I want to understand exactly what is running behind the scenes and what could break.
Here are the main things I check before making major updates.
I Start With a Full Backup
Before changing anything, I want a complete backup of the website.
That should include:
- website files
- WordPress database
- uploads and media
- theme files
- plugin files
- configuration files
The backup needs to be stored somewhere separate from the live website.
A backup is only useful if it can actually be restored, so I also want to know how the site would be recovered if an update causes a problem.
I Check the Current WordPress Version
If a site is several years behind, the jump to the current WordPress version may be significant.
I look at:
- the current WordPress version
- how many major versions behind it is
- whether the active theme supports current WordPress
- whether the installed plugins are still maintained
A site running an old WordPress version may also be running outdated server software, which can complicate the update process.
I Review the PHP Version
WordPress runs on PHP, and older websites often use PHP versions that are no longer supported.
Before changing PHP, I check whether the site’s:
- theme
- plugins
- custom code
- forms
- payment integrations
are compatible with the newer version.
Changing PHP first without checking compatibility can cause parts of the site—or the entire site—to stop working.
I Review Every Plugin
Plugins are one of the biggest risk areas on an older WordPress website.
I look at each plugin and ask:
- Is it still actively maintained?
- When was it last updated?
- Is it compatible with current WordPress?
- Is it still being used?
- Is there a better replacement?
- Is it creating a security risk?
Inactive plugins matter too.
If a plugin is no longer needed, I usually prefer removing it rather than leaving unnecessary software installed.
I Check the Theme
Older themes can be just as important as old plugins.
I look at:
- when the theme was last updated
- whether it is still supported
- whether it depends on old plugins
- whether there is a child theme
- whether custom changes were made directly to theme files
If someone edited the original theme files directly, updating the theme could overwrite those changes.
That needs to be understood before clicking Update.
I Look for Custom Code
Older sites often contain custom CSS, PHP snippets, tracking code, form scripts, or other modifications added over the years.
Some of that code may still be necessary.
Some may no longer be used.
Before making major changes, I want to know what custom code exists and where it is located so nothing important disappears unexpectedly.
I Check Forms and Email Delivery
Contact forms are easy to overlook during an update.
I test:
- contact forms
- quote forms
- notification emails
- confirmation emails
- file uploads
- spam protection
- SMTP configuration
A website can appear to update perfectly while quietly stopping form notifications.
That is why testing important functions matters just as much as checking the visual design.
I Check Payment and Donation Features
If the site accepts payments, donations, registrations, or other transactions, those integrations need extra attention.
I check:
- payment gateways
- API connections
- checkout forms
- confirmation pages
- notification emails
- SSL certificates
These are not areas where I want to discover a problem after the live site has already been updated.
I Look for Security Issues
A site that has not been maintained for years deserves a security review before major updates.
I look for things such as:
- outdated administrator accounts
- suspicious users
- abandoned plugins
- unusual files
- spam comments
- outdated security plugins
- failed login activity
- old backups stored publicly
Updating WordPress is important, but it does not automatically solve every security problem that may already exist.
I Prefer Updating in Stages
On an older site, I generally do not update everything at once.
A safer approach is to make changes in stages.
For example:
- Create and verify the backup.
- Review server and PHP compatibility.
- Update low-risk plugins.
- Test the site.
- Update the theme if appropriate.
- Test again.
- Update WordPress core.
- Test the entire site again.
That makes it much easier to identify which change caused a problem if something stops working.
I Test the Website After Every Major Change
After updates, I check more than the homepage.
I test:
- desktop layout
- tablet layout
- mobile layout
- navigation
- forms
- buttons
- links
- images
- login functionality
- payment or donation features
- important internal pages
A successful update means the website still works for real visitors—not just that WordPress says the update completed.
Sometimes an Update Turns Into a Redesign
There are times when an old WordPress website has accumulated so many outdated components that updating it is no longer the best long-term solution.
If the theme is abandoned, the plugins are obsolete, the design is difficult to use on mobile devices, and the site has become hard to maintain, rebuilding may make more sense than continuing to patch an aging setup.
That does not mean every old website needs a complete redesign.
It means the decision should be based on the condition of the site, not simply on how old it is.
Planning to Update an Older WordPress Website?
If your WordPress website has not been maintained in a long time, avoid updating everything at once without first understanding what is installed and how the site is configured.
A careful review can reduce the risk of downtime, broken forms, plugin conflicts, and other unexpected problems.
If you want help reviewing an older WordPress site before making major updates, start your project or learn more about my website design and support services.
