WordPress rescue library
Diagnose first. Preserve recovery options. Change one thing at a time.
These resources help owners describe an incident, protect evidence, separate symptoms, and define a verifiable recovery target before production work begins.
WordPress Rescue Triage Matrix
Separate availability, admin, checkout, security, data, and performance incidents. Capture the right evidence and choose the narrowest safe test.
Use the triage matrix →Before requesting help
Prepare the details that shorten discovery.
01What is the most useful incident description?
Name the exact user path, expected result, observed result, first known failure time, last known good time, affected users, and every recent site, hosting, DNS, account, payment, or provider change.
02Should we update plugins first?
Not automatically. Record the current state and preserve a recoverable copy first. A bulk update can erase evidence, introduce another variable, or make a rollback point harder to identify.
03What should not be sent publicly?
Do not send passwords, API keys, private source, database exports, payment data, personal-data exports, recovery codes, or production secrets.
Controlled rescue
Bring the incident brief and smallest critical user path.
Faith Forge Labs can help verify authority, evidence, rollback, scope, and acceptance before a production repair.