A fatal PHP error
An updated plugin calling a function that no longer exists, a theme written for PHP 5.6 running on 8.3, or nulled code with a broken class. The error log names the file and line. Everything after that is deduction, not luck.
Emergency repair
Blank page, fatal error, endless maintenance mode — I find the actual fault, restore service, and stop it from happening again.
From the outside, every dead WordPress site looks the same: a white page, a spinner, or a 500. Underneath, they are different jobs. A blank screen is usually a PHP fatal thrown by a plugin or theme. A 500 means the request died before WordPress produced anything — often .htaccess, file permissions, or memory. A stuck “Briefly unavailable for scheduled maintenance” notice is a half-finished update that left the .maintenance file behind.
Guessing costs hours you do not have. I read the error log first, reproduce the failure, and work backwards to the line of code or server setting that caused it. Where the site is already down, the priority is a tested recovery point — then a proper fix, rather than a rollback that leaves the same bug waiting for the next update.
An updated plugin calling a function that no longer exists, a theme written for PHP 5.6 running on 8.3, or nulled code with a broken class. The error log names the file and line. Everything after that is deduction, not luck.
A page that builds too much in memory, an unbounded query, or a host that quietly lowered the PHP memory limit. The site works until one heavy request takes the process down.
A partial update, a corrupted wp-config.php, a stray character in .htaccess, or wrong file permissions after a migration. The server refuses to serve anything at all.
A crashed table, changed database credentials, or a MySQL outage on the host. WordPress connects, fails, and shows the same generic error as a code fault.
PHP error log, server log, and WP_DEBUG_LOG on a copy. No plugin roulette until I know what actually failed.
Plugins deactivated at database or CLI level, a stock theme in place, then bisect until the fault is one named thing.
Files or database — whichever holds the fault — restored from the most recent verified point, not the newest automatic backup that may already be broken.
Patch, replace, pin or roll back the component responsible, then confirm the site runs clean on current PHP.
Templates, forms, checkout and admin screens tested. You get a short written summary of what broke and what changed.
Yes. With SFTP or SSH access I can disable plugins and switch themes at the file level, or through the database if needed. You do not need a working login for me to start.
Only if the fault is server-side. Most fixes need WordPress admin plus SFTP. For server work I ask for a temporary panel account rather than your main credentials, and you can revoke it afterwards.
Only when a clean recovery point is the fastest safe route. A restore can also restore the bug, so I check what the backup contains first. If a targeted fix is faster, that is what I do.
Emergency requests are triaged in the order they arrive, usually within a few hours during the working day. You get a realistic start time before any work begins.
I will say so plainly and lay out the options: rebuild, partial rebuild, or recover what is intact. You are not billed for a fix I could not deliver.
Emergency fix
A short diagnosis is free. If the fault is outside this service, you will be told which one applies — or that the site is not worth repairing.
Or email hello@wordpressfixe.com — first reply within 1 business day.