Pause and back up
Take a full backup before changing anything. Preserve the logs too.

A 500 error is a symptom, not a diagnosis. The fastest route is the error log, the last change and a staging copy—not disabling plugins on the live site and hoping. This guide shows the order we use.
The audit is an external check. It cannot read your PHP error log; a diagnosis needs hosting or administrator access.
Do not start by disabling random plugins on production.
Take a full backup before changing anything. Preserve the logs too.
Check the hosting PHP error log and WordPress debug log. A fatal line is worth more than ten guesses.
Update, theme edit, PHP change or host migration? Reproduce it on staging.
If the live site must be restored, restore first and investigate from a copy.
Apply the verified fix, test the affected pages and record what changed.
The error message narrows the list; these are the frequent candidates.
An old theme or plugin calls code removed by the host’s PHP upgrade.
A fatal after a partial update or a conflict between two extensions.
Wrong ownership or permissions can stop WordPress loading.
A bad redirect or handler rule can fail before WordPress boots.
A failed update or corrupt table can stop the bootstrap.
Memory or process limits can look random until the log says otherwise.
A useful report is not “the site is broken”.
The page or area that fails.
The visible error and any PHP fatal line.
The last update, edit, host or PHP change.
Hosting and WordPress access via an agreed method—never in a public message.
The latest backup and whether it has been tested.
Whether email, forms, checkout or only the front end is affected.
“They actually explained what they were doing instead of just billing us for it. Our booking site has paid for itself twice over.”
What to do next and what not to do.
Common causes include a PHP version mismatch, a broken plugin or theme, file permissions, a corrupted .htaccess rule, database errors or a failed update. The PHP error log is the fastest way to narrow it down.
A fatal PHP error with display_errors off, so the page returns nothing visible. Logs and a staging copy are safer than editing production files to find it.
If the site was working before a recent change and you have a tested backup, restore to staging first so you can compare and identify the cause without taking the live site down again.
No. A fatal WordPress error requires hosting or administrator access to logs and files. The public audit can show external symptoms, not the PHP error itself.
The next useful question, based on what you are dealing with.
Send the error message, last change and access route. We will confirm the diagnostic scope and quote before changing the live site.