Blog Contact us WhatsApp (opens WhatsApp)

Web Design 8 min read

Website Broke After an Update? Here's What to Do Next

If your website broke after an update, stop and do not click anything else. Check your admin email for a WordPress recovery link, turn off the plugin that was just updated, or restore the backup taken just before the update. Breaks after an update usually come from one plugin, theme or add-on clashing with the rest, and they can be fixed without rebuilding your site.

What you do next depends on two things: what you can actually see, and whether you can still log in to your WordPress dashboard. This guide helps you read the symptoms, take the safe first steps, avoid the moves that make things worse, and decide when to hand it over. It finishes with how to stop the next update doing the same thing.

Why do websites break after an update?

A WordPress website is not one piece of software. It is WordPress itself, a theme, a page builder such as Elementor, and usually a collection of plugins from different developers, all running on your host’s server. An update to any one of them can clash with the others.

The usual culprits:

  • A plugin that no longer fits. One plugin updates and expects something the others do not provide yet, or the other way round. WordPress’s own guidance says serious errors commonly come from incompatible or faulty plugins or themes.
  • A page builder add-on falling behind. Elementor sites often use add-on packs for extra widgets. When Elementor updates and an add-on has not caught up, layouts, sliders or forms can break.
  • Custom changes being overwritten. If someone edited a theme’s files directly in the past, an update can quietly replace their work.
  • Server software changes. Hosts periodically upgrade the software that runs WordPress, and older plugins or themes can stop working when they do.

None of this means you did anything wrong by updating. It means the pieces moved out of step, and the job is to find which one.

What are you seeing, and what does it mean?

Start by matching what you see to the likely cause. This tells you the first safe step and whether it is a job you can try yourself.

What you seeWhat it usually meansFirst safe stepTry it yourself?
“There has been a critical error on this website”A plugin or theme has crashed WordPressCheck your admin email for the recovery linkYes, if the email arrives
A completely blank white pageSame kind of crash, without the messageCheck your email, then ask your hostUsually a call
“Briefly unavailable for scheduled maintenance”An update started but did not finishWait a few minutes, then refreshIf it stays, call your host
Pages load but the layout is brokenStyles out of step after an update, or a cached old versionClear caches, then Elementor’s tools (below)Yes
One feature missing, such as a form or sliderA single plugin or add-on has brokenTurn off that plugin and check the pageYes, carefully
You cannot log in at allA crash is blocking the dashboard tooRecovery email, then your hostUsually a call

If your site takes payments or bookings, treat any of these as urgent. A contact form that silently stops sending can cost you enquiries for weeks before anyone notices.

What should I do first if my website broke after an update?

Work through these in order and stop as soon as the site is back.

  1. Write down what changed. Which update, roughly when, and what broke. It saves time whoever ends up fixing it.
  2. Check your admin email, including spam. When WordPress hits a crash, it emails the site’s admin address a special link to log in using Recovery Mode. This pauses the faulty plugin or theme for you only, so you can get into the dashboard and see which item failed. WordPress warns this email can land in spam or not arrive at all.
  3. Turn off the item that failed. In Recovery Mode, or in the dashboard if you can still get in, go to Plugins and deactivate the one that was just updated or named in the error. Deactivating does not delete it or its settings.
  4. Clear your caches. Your browser, any caching plugin and your host may all be showing you an old copy. Clear them and check the page in a private browser window.
  5. On an Elementor site, use Elementor’s own tools. Elementor’s help pages suggest clearing its files and data from Elementor’s Tools settings after updates, and using Safe Mode to check whether the problem comes from your theme or another plugin. Elementor advises a full backup before changing settings.

If you get the site back by deactivating a plugin, that is a stopgap, not the fix. Something you rely on is now switched off, and it needs updating, replacing or reconfiguring properly.

Should I restore a backup?

Often, yes. Restoring the backup taken just before the update is usually the quickest and safest way to get back to a working site. Some hosts take daily backups and can restore one for you.

Before you do, check two things:

  • How old is the backup? Anything added since it was taken is lost when you restore: blog posts, page edits and, most importantly, shop orders or form entries stored on the site. A backup from an hour ago is great. One from three months ago may cause a new problem.
  • Does it include everything? A proper backup covers both the files and the database, which holds your content. A files-only backup will not bring your pages back.

Restoring also puts the old versions back, so the update will want to run again. Do not rerun it until you know which piece clashed, or you will end up back where you started.

What should I not do?

Some reactions feel sensible in a panic but make recovery harder.

  • Do not keep clicking update. Running more updates on a broken site adds more changes to untangle.
  • Do not delete plugins to see what happens. Deactivating keeps the settings. Deleting can lose them, and some plugins remove their data when deleted.
  • Do not reinstall WordPress or switch themes on a whim. A new theme changes how every page looks and can break far more than it fixes.
  • Do not restore a very old backup without thinking. You could swap one problem for another by wiping out months of orders, enquiries or edits.
  • Do not leave it broken over the weekend. A site showing an error tells every visitor you are not around.

When should I stop and call someone, and who?

Stop if you cannot get into the dashboard, if the recovery email never arrives, or if you have tried the steps above and the site is still broken. Beyond that point the fixes involve server file access and error logs, where a wrong move can make things worse.

Who to call depends on the problem:

  • Your host if the site shows a blank page or a stuck maintenance message, if you need a backup restored, or if the server itself might be the issue. Hosting support can see error logs and file systems you cannot.
  • A WordPress developer if the site loads but something is broken, if a plugin clash needs tracing and fixing properly, or if the host has restored a backup and you need the updates applied safely.

When you call, share the notes from step one: what was updated, when, and what you see now. It turns a vague “my site is broken” into something that can be fixed quickly.

How do I stop updates breaking my site again?

Keep updating. Skipping updates leaves known security holes open and makes the eventual catch-up bigger and riskier. The fix is to update safely:

  • Back up first, every time. Files and database, stored somewhere other than your own server.
  • Update one thing at a time, and check the site after each one, so you know exactly which update caused a problem.
  • Test big updates on a copy. A staging site is a private copy of your website where updates can be tried without touching the live one. Some hosts include one.
  • Know what updates itself. Since WordPress 5.5 you can switch automatic updates on or off plugin by plugin. Automatic updates are convenient, but they can run when nobody is around to spot a problem.
  • Trim the plugin list. Every plugin is another thing that can clash. Remove anything you no longer use.
  • Watch the important bits. After updates, check your contact form actually sends and any payments go through, not just that the homepage loads.

In our experience of looking after WordPress and Elementor sites, the ones that break after updates are rarely the ones with a careful routine. They are the ones where updates pile up for months and then all run at once.

How we can help

We have spent over ten years building and fixing Elementor and WordPress websites, across more than 500 sites. If your site is broken right now, our existing website help service is for exactly this: fixing, improving or rescuing the site you already have, without starting again.

If you would rather not think about updates at all, our website maintenance plans include managed hosting, automatic backups, security monitoring, updates, uptime monitoring and priority support, so updates are handled carefully and someone is watching if anything goes wrong. And if your site is working but you are not sure how fragile it is, start with a free website audit and we will tell you honestly where it stands.

Frequently asked questions

Why did my site break when I did not update anything?
WordPress plugins and themes can be set to update themselves, and some hosts run updates for you. Check the Plugins screen for which items have automatic updates switched on, and ask your host whether they updated anything recently.
Should I stop updating my website?
No. Updates fix security holes and keep everything working together, so a site left un-updated becomes riskier over time. The answer is to update safely, with a backup first and one change at a time, not to stop.
How long does it take to fix a website after a bad update?
It depends on what broke. Turning off one faulty plugin can take minutes, while a clash buried in a page builder add-on or custom code takes longer to trace. A good developer will look first and give you a clear estimate before starting.
Will I lose my content?
Usually not. A broken update affects the code that displays your site, not the pages, posts and images stored underneath. The main risk is restoring an old backup, which can wipe out anything added since it was taken.
Can I undo a WordPress update?
Yes, in most cases. The safest way is to restore a backup taken just before the update. Rolling a single plugin back to its previous version is also possible, but it is a temporary fix until the clash is properly sorted.