A WordPress update should be routine. You click update, wait a few seconds, and expect the site to carry on as normal.
Sometimes it does not.
You might see a blank white page, a critical error message, a broken layout, missing images, a plugin warning, or a site that loads for visitors but will not let you into the admin area. For a small business, that is not just a technical nuisance. It can mean lost enquiries, a broken booking form, customers losing confidence, and a very uncomfortable feeling that one click has taken the website down.
The important thing is this: do not reset WordPress as your first move. Do not delete plugins at random. Do not restore an old backup until you know what you are restoring over.
Work through the checks below in order.
First, write down what changed
Before trying to fix anything, make a quick note of what happened.
Write down:
- The time the update was run
- Whether it was WordPress core, a plugin, a theme, or several updates together
- The exact error message on screen, if there is one
- Whether the public website is broken, the admin area is broken, or both
- Whether contact forms, checkout, or bookings are affected
- Whether anyone else made changes at the same time
This sounds basic, but it matters. If you ask your host or developer for help, this information can save half an hour of guesswork.
If your site still loads, take a screenshot before changing anything. If it does not load, copy the error message exactly.
Check whether it is a front-end or admin problem
There are two different situations.
If the public website is broken but you can still access /wp-admin/, you may be able to fix the problem from inside WordPress.
If both the website and admin area are broken, the issue probably needs file-level access, hosting control panel access, or help from your hosting provider.
Try these separately:
- Visit your homepage in a private browser window
- Visit a few important pages directly, such as your contact page
- Try logging in at
/wp-admin/ - Check the website on mobile as well as desktop
Sometimes only one page is broken because a page builder, form plugin, or template has failed. Sometimes the whole site is down because a plugin or theme has triggered a PHP error.
Look for the most recent plugin or theme update
Most WordPress breakages after updates are caused by one of three things:
- A plugin update conflicts with another plugin
- A theme update changes how the site displays
- WordPress core updates and an old plugin is no longer compatible
If you can still access the admin area, go to the plugins screen and look for anything updated today. If the issue started immediately after one plugin updated, that plugin is your first suspect.
Do not deactivate everything at once unless the site is completely unusable. Change one thing, test, then move to the next. If you turn off five plugins at once and the site comes back, you still do not know which one caused the problem.
A calm process beats frantic clicking.
If you see a critical error, check your email and logs
WordPress often sends an email to the site administrator when a fatal error happens. The subject may say something like "Your Site is Experiencing a Technical Issue".
That email can include:
- The plugin or theme that triggered the error
- The file path involved
- A recovery-mode link
If you receive a recovery-mode link, use it carefully. It can let you log in and deactivate the problem plugin without touching the rest of the site.
If no email arrives, check your hosting error logs. Many hosting control panels include a section for PHP errors or site logs. You are looking for a recent error mentioning a plugin folder, theme folder, or PHP version problem.
This is one of the reasons managed WordPress hosting helps, or why being on a managed VPS can matter: your host can usually see the server-side error even when WordPress itself will not load.
Disable the likely plugin safely
If you know which plugin caused the problem and you can access WordPress, deactivate that plugin from the plugins screen.
If you cannot access WordPress, the safer route is to rename the plugin folder through your hosting file manager or FTP. For example, if the plugin folder is:
wp-content/plugins/example-plugin
rename it temporarily to:
wp-content/plugins/example-plugin-disabled
WordPress will treat the plugin as unavailable and disable it. If the site comes back, you have found the likely cause.
Do not delete the plugin folder unless you have a backup and know whether the plugin stores settings or data. Deleting is not the same as disabling.
Check the theme if the layout is broken
If the site still loads but looks wrong, the theme or page builder may be the issue.
Common signs include:
- Header or footer layout broken
- Buttons or menus not displaying correctly
- Page builder sections missing
- CSS styles not loading
- Mobile layout suddenly wrong
Clear any caching first. That includes your WordPress caching plugin, server cache, CDN cache, and browser cache. A site can look broken simply because old CSS and new template files are being mixed together.
If clearing cache does not help, check whether the theme updated at the same time as WordPress or a page builder plugin. Theme and builder updates often need to be tested together.
Do not restore a backup too early
A backup is there to protect you, but restoring too early can make a small problem bigger.
Before restoring, ask:
- What time was the last good backup taken?
- Will restoring it remove orders, enquiries, bookings, or form submissions made since then?
- Is the problem definitely in the website files, or is it a cache, PHP version, or plugin compatibility issue?
- Can the broken plugin be disabled instead?
If your website is a simple brochure site and no content has changed since the backup, restoring may be straightforward. If the site takes payments, bookings, form enquiries, or customer logins, restoring needs more care.
For more detail on what your hosting backs up and how to trigger a restore, see our website backup guide.
Check forms after the site comes back
Once the website loads again, do not stop immediately. Test the parts of the site that generate business.
At minimum, check:
- Contact forms
- Booking forms
- Checkout pages
- Login pages
- Newsletter signups
- Any page that sends an email notification
A WordPress update can appear fixed while a form plugin or SMTP setting is still broken. Send yourself a test enquiry and confirm it arrives. If it does not, our guide to WordPress contact forms not sending emails walks through the email side.
This is the part many people miss. The site looking normal is not the same as the site working properly.
How to prevent the same problem next time
You cannot prevent every WordPress update issue, but you can reduce the risk.
Before running updates:
- Make sure you have a recent restorable backup
- Update plugins one at a time, not all at once
- Update during a quiet time, not just before a campaign or busy trading period
- Check the website after each important update
- Keep unused plugins and themes removed
- Avoid plugins that have not been updated for a long time
If your site is business-critical, use a staging copy for larger changes. That lets you test updates away from the live site before customers see anything.
When to ask your host for help
Ask for help if:
- You cannot access the WordPress admin area
- The site shows a critical error and you do not know which plugin caused it
- You are not sure whether restoring a backup will lose enquiries or orders
- The issue affects email, contact forms, or checkout
- The same plugin keeps breaking after every update
- You do not have a recent backup
A good host should be able to help you identify whether the issue is WordPress, PHP, a plugin, a theme, caching, or the server environment.
Eazyhosting looks at the whole setup: WordPress, hosting, backups, email delivery, SSL, DNS, and the business impact. If your WordPress site has broken after an update and you are not sure what to touch first, get in touch before resetting anything.
For ongoing support, see WordPress Hosting for small businesses that want the website maintained, backed up, and supported without having to become WordPress technicians.