When a WordPress website stops responding, the first impulse is often to try everything: updates, disabling plugins, editing files or contacting several suppliers at once. Understandable as this is, it can erase clues and reduce the chances of a clean recovery.
“Down” describes an effect, not a cause. Observe what is happening and preserve the available state before intervening.
Record exactly what you see
Save the URL, time, screenshots and complete error text. Establish whether every page, only administration or one feature is affected. Try another network or device without repeatedly performing invasive operations.
A white page, a 500 error, a database message and an unreachable domain need different checks. The screen already forms part of the diagnosis.
Check domain, DNS and hosting
- Has the domain expired or is renewal approaching?
- Is the HTTPS certificate valid?
- Does the hosting panel report maintenance or limits?
- Are disk space or resources exhausted?
- Are email or other domain services affected?
If you cannot access the provider, do not immediately create new accounts or change DNS. Reconstruct ownership and responsibilities first.
Do not update blindly
An update may fix a vulnerability, but during an incident it can change files and databases, making the cause harder to identify. First obtain a copy of the current state, verify available backups and plan a rollback.
Collect access information without sending credentials through a public form
Hosting, WordPress, domain, database and external services may belong to different parties. List what exists and who controls it. Share credentials only after verifying the recipient and agreeing an appropriate channel.
When to seek help
A technician is needed when the website is critical, no verified backup exists, the issue involves databases or servers, unusual redirects appear or every attempt creates new symptoms.
SOS Yellow Lab starts with diagnosis. A contained problem may be resolved in the initial intervention; broader work receives a defined scope before additional costs.
What to send the technician
- URL and screenshots.
- Start time and last known change.
- Actions immediately preceding the incident.
- Hosting and domain providers.
- Backup availability and dates.
- Impact: whole website, payments, forms or private areas.
- The owner’s authorisation.
Preserve recovery options
During downtime, value comes from reducing uncertainty rather than clicking faster. Observe, preserve, reconstruct access and then intervene.