We're afraid to update WordPress core in case the site breaks.
Not updating is riskier long-term than a controlled update. Test on staging, take a snapshot, then production.
Try this first
- 1Take a full backup (files plus DB) and a hosting snapshot if available. Two safety nets beat one.
- 2Update on staging first, never production. Click through every key flow: contact, login, checkout, forms. Not just the homepage.
- 3Read the core changelog for the new version. Major versions can break the REST API or block editor.
- 4Check plugin compatibility. A plugin that hasn't been updated in years is usually first to break on a core major.
- 5Run the production update in a quiet window, not Friday afternoon. Someone stands by to roll back within 15 minutes.
- 6Post-update: watch error logs and analytics for 24 hours. A conversion dip or 500 spike points to a latent issue.
When to bring us in
Complex site (custom theme, many hooks, custom plugins)? An experienced WP engineer for the first update after a long pause pays back.
See also
- WordPress, plugins and theme have gone 6+ months without updatesOut-of-date WP is the number-one entry for malware. Don't just hit 'update all', back up first.
- Theme update broke the layout or threw a fatal errorThemes overwrite custom CSS on update unless you use a child theme.
- WordPress shows a blank screen after a plugin install or updateWSOD (white screen of death) is usually one crashing plugin. You isolate it.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.