VIQQStudio
Call
Developer troubleshooting a WordPress site on a laptop

WordPress

WordPresswhitescreenorbrokensite-whattofixfirst

When your WordPress site crashes after an update - white screen, 500 errors, or broken layout - here's the order we use to restore it without a full rebuild.

By VIQQ StudioUpdated June 20266 min read

Key takeaways

  • Isolate plugin conflicts
  • When to roll back updates
  • When repair beats redesign

Try it yourself first

Work on staging or enable maintenance mode first - disable one plugin at a time so you know what broke the site.

A WordPress site that was fine yesterday and shows a white screen today is usually a plugin, theme, or PHP conflict - not a reason to throw away the whole build.

This guide is the triage order we use for Miami businesses before we quote a scoped repair.

DIYsteps

  1. 1Step 1 - Confirm the symptom

    • White screen front and admin = fatal PHP error (display off).
    • 500 after update = plugin, theme, or PHP version conflict.
    • Layout broken only on mobile = CSS or page builder responsive settings.

  2. 2Step 2 - Isolate the cause

    • Disable the last plugin changed - or rename wp-content/plugins via FTP.
    • Check hosting error logs and PHP memory limit.
    • Roll back one plugin or theme version before rebuilding anything.

  3. 3Step 3 - Restore safely

    • Fix on staging, then push live.
    • Document which plugin/version failed so auto-update doesn't repeat it.

Whatownersusuallysee

Blank white page on the front and sometimes the admin - classic fatal PHP error with display off.

HTTP 500 after auto-updates, or layout broken only on mobile after a theme tweak.

Forms stopped sending after a contact plugin update - related but often faster to fix.

Fixorderthatsavestime

Enable staging or maintenance mode, reproduce the error, disable the last plugin changed - binary search if needed.

Check PHP error logs and hosting resource limits - shared hosts choke on heavy plugins during updates.

Roll back one version on the offending plugin or theme before chasing a full migration.

Whenrepairisenoughvsrebuild

Repair fits when content, URLs, and SEO equity are worth keeping - most local service sites under 30 pages.

Rebuild when the theme is abandoned, plugin stack is unmaintainable, or speed/security can't be fixed without starting over.

We document cause and prevention so the same plugin auto-update doesn't break production twice.

Commonquestions

Can you fix a site you didn't build?

Yes - most repair jobs are on existing WordPress installs. We need admin and hosting or SFTP access.

How fast can WordPress repair happen?

Simple plugin conflicts often same business day. Deeper theme or database issues may need staging - we confirm after a quick look.

Still broken?

Getascopedrepair-norebuildpitch

Stop DIY if: No FTP/hosting access, database errors, or white screen persists after plugin isolation - book WordPress repair from $199.

We isolate plugin/theme conflicts, roll back safely, and restore your site - scoped repair, not a forced rebuild.

WordPress site repairfrom $199Plugin conflict fixAsk a question first

Rate this guide

Was this helpful? Your stars help other readers.

4.93 reader ratings

Rate this article

Share

Pass this guide to someone who needs it.