During an outage, repeated untracked edits make recovery harder. The first useful step is to record the symptom and protect the current state.
What to check
- Record the exact failure
- Preserve current files, database, and logs
- Limit unnecessary updates or reinstalls
What the results mean
Prioritize restoring essential customer actions, then investigate the root cause once service is stable.
Stabilize before trying fixes
Record which URLs fail, when it started, and the last known change. Preserve site files, database, logs, and any working backup. Avoid a string of plugin updates or reinstallations while the failure is unclear. If forms or sales are affected, set a temporary communication path so customers can still reach the business.
Restore the most valuable functions first
Use the error and recent changes to narrow the cause. Prioritize the homepage, service details, contact form, and checkout if applicable. Once the immediate outage ends, test related pages and document what actually broke, what was changed, and what would make the next recovery faster.
What if the site may be infected?
Preserve evidence, limit compromised access, and investigate the entry point before putting a possibly infected backup back online.
Greg Grigorian
If this issue affects inquiries or day-to-day work, get the cause checked and the important customer paths tested after repair. Greg can handle the website work directly.