Technical web intervention
Hacked, offline or unstable website recovery
I work on WordPress, PHP and VPS-hosted websites that no longer respond, show a 500 error, have been compromised or behave suspiciously.
Situations covered
Hacked WordPress site
Injected files, suspicious accounts, compromised plugins, modified theme or abnormal behavior.
Redirects and SEO spam
Redirects to other websites, unwanted indexed pages, hidden content or degraded Google results.
Blank page or 500 error
PHP, WordPress, plugin, theme, .htaccess, permissions or server configuration diagnosis.
Broken site after an update
Controlled rollback, PHP compatibility fix, partial restoration or recovery from backup.
Unstable hosting
Log analysis, saturation, SSL, DNS, Apache/Nginx, PHP-FPM, database or file permission issues.
Return to a trusted state
Cleanup, basic hardening, backups, checks and follow-up after the site is back online.
Intervention method
- Diagnosis
Visible symptoms, logs, hosting, CMS, database, DNS and SSL when needed. - Current-state backup
Before cleaning, I preserve what may help understand and recover the site. - Cleanup or restoration
Removing injections, restoring from a clean backup or applying targeted fixes to affected files. - Cause correction
Looking for the entry point: vulnerable plugin, password, file permissions, obsolete version or unused access. - Updates and hardening
CMS, themes, plugins, PHP version, permissions, accounts, backups and basic settings. - Final checks
Navigation, forms, console, visible indexation, absence of redirects and critical page checks.
Useful information to send
- Website URL and affected page URL if the issue is specific.
- Error message, screenshot or clear description of the behavior.
- Hosting, FTP/SFTP, SSH, WordPress or database access when available.
- Existing backups and date of the last known working state.
- Recent changes: update, migration, plugin, theme, DNS, SSL or hosting.
Clear limits
I do not promise full recovery without usable access or a healthy backup. The goal is to quickly establish what can be recovered, bring the site back online when possible, then reduce the risk of the incident happening again.
Covered environments
- WordPress
- PHP
- MySQL / MariaDB
- Apache
- Nginx
- PHP-FPM
- Debian
- SSL
- DNS
- Server logs
- Search Console
- Backups
FAQ
What should I do if my WordPress site is hacked?
Avoid deleting files immediately. First, diagnose the issue, preserve the current state when possible, identify modified files, clean or restore the site, then fix the entry point.
How long does it take to bring a site back online?
It depends on the available access, server state, CMS and backups. A simple outage can sometimes be fixed quickly, while a deep compromise requires more complete analysis.
Can a website be recovered without a backup?
Often yes, but not always completely. The diagnostic phase determines whether the files, database or hosting environment allow a reliable recovery.
Does a 500 error mean the site has been hacked?
No. A 500 error can come from an update, an incompatible PHP version, a plugin, a theme, a .htaccess file or a server issue.
How do you prevent the issue from coming back?
After recovery, the CMS, extensions and themes should be updated, unused access removed, passwords reinforced, permissions checked and usable backups put in place.
Need to bring a website back online?
The most useful first step is to send the URL, the main symptom and the access you have.