DIGITAL EXPERIENCE / WORDPRESS RESCUE

Your WordPress stopped. We go where the problem actually is.

500 error, Critical Error, white screen, broken plugin, database, access or configuration failure. With hosting access, we investigate the cause to recover and stabilize the environment.

500 ErrorCritical ErrorWP-AdminPluginsDatabaseMalware
THE SYMPTOM IS ONLY THE SURFACE

When WordPress fails, random clicking is rarely the best strategy.

A visible error may originate in a plugin, theme, PHP version, memory, permissions, database, server, cache, incomplete update or custom code. Fixing only the symptom can hide the cause and create another failure later.

First we understand what broke. Then we decide what needs to change.

WordPress Rescue is a technical recovery and stabilization intervention. We work from evidence: logs, files, databases, configuration and recent environment history whenever those are available.

ACCESS IS PART OF THE DIAGNOSIS

To recover a website, we need to reach the environment where the failure lives.

In many incidents WordPress itself is unavailable, so a wp-admin user alone may not be enough.

!Technical recovery requires access to the website hosting environment.
01

Hosting panel

Lets us inspect files, PHP versions, logs, databases, backups, resource limits and other essential settings.

02

FTP / SFTP

May be required to inspect, isolate, replace or recover files when the administration panel does not respond.

03

Database

Connection failures, corrupted tables or administrator users may require direct MySQL/MariaDB access or an equivalent tool.

04

SSH / console

When available, terminal access can accelerate logs, permissions, WP-CLI and controlled operations.

Credentials should not be sent through the form.

The form is for triage only. After the initial review, RADIAL will explain which accesses are actually required and the appropriate channel for sharing them.

10 COMMON PROBLEMS

What usually breaks — and how we can help.

The symptoms below are common, but the actual cause is confirmed only after diagnosis in the environment.

01
STANDARD

500 / Internal Server Error

What you see

The browser shows a 500 error and the website or wp-admin stops loading.

How we investigate and help

We inspect logs, PHP, .htaccess, plugins, theme, memory, permissions and recent changes to isolate the source.

02
STANDARD

WordPress Critical Error

What you see

“There has been a critical error on this website” appears after an update, installation or change.

How we investigate and help

We enable safe diagnostics, identify the component generating the exception and define rollback, correction or replacement.

03
STANDARD

White screen / blank page

What you see

The site loads blank without a clear error message.

How we investigate and help

We check fatal errors, memory, PHP compatibility, theme, plugins, cache and premature code output.

04
ADVANCED

wp-admin unavailable

What you see

The public site may load, but the admin loops, blocks the user or returns an error.

How we investigate and help

We inspect authentication, cookies, URLs, permissions, users, database, security plugins and server settings.

05
STANDARD

Broken or incompatible plugin

What you see

An update or installation breaks pages, checkout, forms or the whole site.

How we investigate and help

We isolate the plugin without relying on wp-admin, inspect dependencies and PHP version, and assess rollback, correction or replacement.

06
ADVANCED

Corrupted or incompatible theme

What you see

Layout disappears, functions break or the site stops after a theme change or update.

How we investigate and help

We inspect parent theme, child theme, functions.php, templates, dependencies and changed files to recover the visual layer safely.

07
ADVANCED

Database connection error

What you see

WordPress shows “Error establishing a database connection” or loses access to content and settings.

How we investigate and help

We validate database service, credentials, host, privileges, wp-config.php, server capacity and table integrity.

08
CRITICAL

Corrupted database

What you see

Tables return errors, content disappears, queries fail or WordPress behaves inconsistently.

How we investigate and help

We map the extent of corruption, assess backups, perform viable repairs and rebuild structures when technically possible.

09
CRITICAL

Hacked website or malware

What you see

Redirects, unknown files, strange users, spam, browser blocks or security alerts.

How we investigate and help

We investigate changed files, users, persistence, vulnerable plugins and entry points; remove identified threats and recommend hardening.

10
ADVANCED

Site broke after an update

What you see

WordPress, a plugin, theme or PHP is updated and features stop working immediately or shortly afterward.

How we investigate and help

We compare versions, logs and dependencies, recover a stable combination and plan the correct update when necessary.

DIAGNOSIS FIRST

We do not promise a repair before we know the problem.

The first technical hour is used for diagnosis and initial intervention. If the incident can be resolved in that period, the service may end there. If the failure requires more work, we explain the situation and estimate the next steps before continuing.

01Controlled access02Preservation / backup when possible03Logs and evidence04Cause isolation05Recovery06Stabilization
The goal is not only to make the page load again. It is to reduce the chance of the same issue returning because an active cause was left behind.
TECHNICAL HOURLY RATE

Different levels of complexity require different levels of intervention.

Classification is confirmed after triage. The values below are reference hourly rates for WordPress Rescue.

01DIRECT INTERVENTION

Rescue Standard

Common failures with a relatively localized cause and low reconstruction risk.

R$ 190/ hour
  • 500 error caused by plugin
  • Simple Critical Error
  • Incompatible plugin
  • Point configuration issue
  • White screen with identifiable cause
03HIGH COMPLEXITY

Rescue Critical

Incidents with high risk, integrity loss or partial technical reconstruction.

R$ 320/ hour
  • Corrupted database
  • Malware and compromise
  • Recovery without reliable backup
  • Heavily modified files
  • Critical structure reconstruction
01

Minimum billing of 1 technical hour to begin diagnosis.

02

After the first hour, continuation may be billed in 30-minute increments.

03

If diagnosis indicates a larger reconstruction project, we present a separate scope before proceeding.

04

Licenses, third-party services, infrastructure, migration or external resources are not included in the technical hour unless expressly stated.

HOW RESCUE WORKS

Enter, understand, recover, stabilize.

The process is technical, but communication should remain simple.

01

Triage

You provide the website address, visible symptoms and which accesses are available.

02

Controlled access

We request only the accesses required to investigate the incident safely.

03

Preservation

When possible, we verify backups or create a copy before higher-risk changes.

04

Diagnosis

Logs, files, database, versions and settings help locate the actual cause.

05

Recovery

We apply the appropriate intervention: isolation, rollback, repair, replacement or technical reconstruction.

06

Stabilization

We validate operation and indicate updates, security, backup or changes needed to reduce recurrence.

RECOVERY IS NOT REDESIGN

Rescue has a clear mission: return the environment to a stable state.

If the incident reveals a technically unviable structure, we separate recovery from rebuilding so scope and expectations remain clear.

01

Recover

Restore operation and address the identified cause with the smallest coherent intervention.

02

Stabilize

Correct risks directly related to the incident and indicate what should be updated or reorganized.

03

Rebuild

When database, code or architecture do not allow safe recovery, a separate rebuild project may be recommended.

FAQ / WORDPRESS RESCUE

Questions from people who simply want the site working again.

01Do I need hosting access?+

Yes. Real recovery usually requires hosting-level access. wp-admin alone may not be enough, especially when WordPress itself is unavailable.

02I only have a WordPress username and password. Can you still help?+

We can triage, but recovery may be limited. If the issue is PHP, files, database, permissions or server-related, hosting access must be obtained from the provider or technical owner.

03Should I send my password through the form?+

No. Never send passwords through the diagnosis form. After triage, we explain what credentials are required and how to share them.

04Can you fix any 500 error?+

A 500 error is a generic symptom. Many cases are simple, but others involve server, database or custom code. Diagnosis determines the cause and recovery feasibility.

05What if I do not have a backup?+

We can still investigate and attempt recovery of the current environment. However, no backup increases risk and may limit options, especially with database corruption, compromise or missing files.

06Do you work with any hosting provider?+

We can work with different providers as long as the environment provides enough access and tools for diagnosis. Provider restrictions may limit some interventions.

07My site was hacked. Does Rescue cover that?+

Yes, as a high-complexity incident. Work may include identifying and removing malicious files, suspicious users and visible vectors, plus hardening recommendations. No internet-connected environment can be promised absolute invulnerability.

08How long does recovery take?+

It depends on the cause. A broken plugin may be fast; database corruption or malware requires deeper work. The first hour exists to turn a symptom into a technical diagnosis.

09If the site cannot be recovered, is diagnosis still billed?+

Yes. Technical diagnosis is performed even when the conclusion is that recovery is not safe or economically reasonable. We explain alternatives before any additional project.

10Do you update every plugin and WordPress during Rescue?+

Only when that is part of a safe solution. Updating everything indiscriminately during an incident can create new conflicts. We stabilize first, then plan required updates.

11Can I migrate hosting at the same time?+

Yes, but migration is a different scope. If the current infrastructure contributes to the issue, we can evaluate migration after stabilizing or preserving what is recoverable.

12Does Rescue include redesign or new features?+

Not as standard scope. Rescue is recovery and stabilization. Redesign, new pages, e-commerce, integrations and evolutionary development are separate projects.

REQUEST DIAGNOSIS

Tell us what happened. We start from the symptom.

You do not need to know the technical name of the problem. Tell us what you see, when it started and what changed recently, if you know.

!

Do not send passwords through this form.
RADIAL will request the necessary accesses only after initial triage.

Do you have hosting access?
Is there a recent backup?