When a WordPress website breaks, the worst thing you can do is start guessing.
A lot of problems get made worse because someone clicks around too quickly, updates random plugins, changes settings without knowing what caused the issue, or starts switching things off with no clear plan.
The safest approach is to slow down, work through a few sensible checks, and try to narrow down what changed.
This is especially important for small business websites, where a broken contact form, damaged layout or plugin conflict can quickly start costing enquiries.
First: what does “broken” actually mean?
Before doing anything, be clear about what has actually gone wrong.
A WordPress site can be “broken” in different ways, for example:
- the whole site is down
- the homepage looks wrong
- a page layout has broken
- the mobile version is not displaying properly
- a contact form has stopped working
- the admin area is inaccessible
- the site is very slow
- part of the website has disappeared
- buttons, menus or plugins are no longer working
That matters because different problems usually point to different causes.
1. Check whether anything was recently updated
This is one of the first things to ask.
A lot of WordPress issues happen straight after:
- plugin updates
- theme updates
- WordPress core updates
- hosting or PHP version changes
- new plugins being installed
- design or content edits made through a builder
If the problem appeared immediately after one of those changes, that gives you a strong starting point.
Even if the update itself is not the exact cause, it often points you in the right direction.
2. Check if the problem affects the whole site or just one part
Try to work out whether the issue is site-wide or limited to one feature.
For example:
- does the whole website look broken?
- is it only one page?
- is it only the contact form?
- is it only mobile?
- is it only the admin area?
- is it only logged-in users seeing the issue?
This matters because a single broken service page suggests something very different from a site-wide white screen or fatal error.
3. Check the front end and the admin area separately
Sometimes the website still loads, but the WordPress admin area is broken.
Other times the admin is fine, but the front end is damaged.
Check both:
- the public website
- the WordPress dashboard
- key pages
- the mobile version
- important features such as forms or popups
This helps narrow down whether the issue is mainly visual, functional, or more structural.
4. Check if caching is making the issue look worse or hiding changes
Caching can confuse things.
Sometimes the site is actually fixed, but an old cached version is still showing. Other times the cache needs clearing after updates and layout changes. In some cases, caching plugins or server caching can also contribute to problems.
Check:
- browser cache
- caching plugin settings
- CDN cache if one is being used
- server-side cache if the host provides it
This is not always the cause, but it is common enough to rule out early.
5. Check the most important business-critical functions first
If the site matters to the business, do not just look at the homepage and assume everything is fine.
Check the things that actually affect enquiries or sales, such as:
- contact forms
- booking forms
- checkout
- quote request forms
- phone buttons on mobile
- menus and navigation
- key service pages
- product pages
These are the areas where hidden problems can do real damage without being obvious straight away.
6. Check for plugin conflicts
Plugin conflicts are one of the most common reasons a WordPress site breaks.
This often happens when:
- one plugin update clashes with another
- a plugin no longer works properly with the theme
- a page builder conflicts with another tool
- the site is carrying too many plugins doing similar jobs
Typical warning signs include:
- broken layouts
- missing functionality
- forms failing
- parts of the site disappearing
- slow admin or front-end performance
- strange errors after updates
If a plugin conflict is likely, it is better to work through it methodically rather than switching things off randomly on a live business site.
7. Check the theme and page builder
A broken layout is not always a plugin issue.
Sometimes the problem sits in:
- the active theme
- theme custom settings
- page builder updates
- builder-specific widgets or modules
- custom CSS that no longer behaves properly after an update
If the site uses Elementor, WPBakery, Divi or a similar builder, this is a common area to investigate.
Layout problems often come from the interaction between the theme, the builder and recently updated plugins.
8. Check whether the issue is only on mobile
A lot of WordPress problems are not obvious on desktop.
The site may look fine on a laptop but be broken on mobile because of:
- collapsed layout sections
- oversized images
- broken menus
- spacing issues
- buttons falling out of place
- theme or builder responsiveness problems
Always check the mobile version when something looks off.
A business can lose enquiries simply because the mobile contact path is broken while the desktop view appears normal.
9. Check the contact form properly
This deserves its own check because forms often “look” fine while not working properly.
Do not just look at the form. Test it.
Check:
- whether the form submits
- whether the message actually sends
- whether the message arrives in the inbox
- whether confirmations or autoresponders still work
- whether anti-spam or captcha tools are blocking valid submissions
A broken contact form is one of the most expensive silent problems a small business website can have.
10. Check for server or hosting issues
Sometimes the problem is not really WordPress at all.
Possible hosting-related causes include:
- PHP version incompatibility
- memory limits
- file permission issues
- server outages
- SSL problems
- broken email sending configuration
- database connection issues
If a site suddenly throws fatal errors, goes blank, or starts behaving erratically after no obvious site changes, hosting and server environment checks become more important.
11. Check whether there is a recent backup
Before making bigger changes, check whether a usable backup exists.
This is important because if the problem gets worse, a recent backup gives you a safer recovery option.
A backup does not solve the cause by itself, but it gives you protection while you diagnose the issue.
If there is no recent backup, that changes how cautiously the site should be handled.
12. Check the error message, but do not rely on it blindly
If WordPress shows a visible error, read it carefully.
Examples include:
- critical error messages
- plugin-related fatal errors
- database connection messages
- PHP warnings
- missing file notices
These can be useful clues, but they do not always tell the full story. Sometimes the visible message is only the end result of a deeper compatibility issue.
Still, it is always worth checking what the site is actually saying before making assumptions.
13. Work out whether the site needs a fix or a rebuild
Not every broken WordPress website needs rebuilding.
A lot of sites can be recovered or improved with the right fixes.
However, sometimes a website has deeper issues such as:
- years of neglected updates
- too many plugins
- poor original setup
- messy page builder history
- repeated patch-on-patch fixes
- outdated structure and content
In those cases, the problem may not just be one error. It may be a sign that the site has become fragile overall.
That is why diagnosis matters first.
A simple WordPress troubleshooting checklist
If a WordPress site breaks, this is a sensible order to follow:
First checks
- what exactly is broken?
- was anything recently updated?
- is it the whole site or just one part?
- does the admin area still work?
- does the issue affect desktop, mobile, or both?
Key business checks
- test contact forms
- test key service pages
- test menus and buttons
- test checkout or booking flow if relevant
Technical checks
- clear cache
- check plugin conflicts
- check theme and page builder
- check hosting/PHP issues
- check for recent backups
- review any visible errors
That is a much safer approach than randomly changing things until something happens.
What not to do when a WordPress website breaks
A few things usually make the situation worse:
- updating more plugins without a plan
- changing multiple settings at once
- deleting plugins or files too quickly
- editing live business sites carelessly
- ignoring backups
- assuming the problem is only visual
- not testing forms or mobile
The aim is to isolate the cause, not create three more problems while trying to solve one.
When it is better to get help
If the website matters to the business, it is usually worth getting help when:
- you are not sure what caused the problem
- the site is live and business-critical
- enquiries, bookings or sales are affected
- the site uses lots of plugins or builder tools
- there is no backup
- previous updates have already made the site unstable
A quick fix done badly can easily create a bigger mess.
Final thoughts
When a WordPress website breaks, the first job is not to panic.
The first job is to work out:
- what is actually broken
- what changed recently
- whether the issue is visual, functional or technical
- what the safest next step is
That alone can save a lot of wasted time and prevent a bad situation from getting worse.
Need help fixing a WordPress website?
I help small businesses fix broken, outdated and underperforming WordPress websites.
That can include:
- plugin conflicts
- broken layouts
- contact form problems
- mobile display issues
- WordPress updates
- general website fixes and support
If your WordPress website has broken and you want a practical fix without unnecessary hassle, take a look at my website pricing or get in touch.
Need help with your website?
I work directly with small businesses on web design, WordPress fixes, Shopify support and local SEO. No agency overhead.
Get in touch →