Recover a WordPress client site after a failed update

Direct answer

Freeze further writes, preserve evidence and choose whether a separate restore rehearsal is safer than an immediate rollback.

Use a bounded WordPress recovery decision instead of making a production rollback from memory.

Illustrative example

Illustrative example: a WordPress content site fails after a plugin update. The operator records the visible failure, checks the last known compatible WordPress backup set and restores files plus database into a separate target before asking the client to approve a production action.

Work through the decision

1. Record the WordPress plugin, theme or core change, its time and the user journey that failed.
2. Pause unrelated updates and identify the last compatible WordPress files, database and configuration.
3. Restore to an isolated target where possible and test the affected journey.
4. Get the agreed approval before changing production, then record the outcome and remaining gaps.

What this does not establish

A backup label is not evidence that a WordPress restore will work. Test the actual combination of files, database and configuration.

Technical reference: WordPress backup documentation. Check the installed software and operating context before applying any command or change.