01 / GUIDE
Start with diagnosis, not random changes
When a WordPress site is down or behaving badly, the safest first step is to identify what changed and preserve a recovery route. Updating everything, deleting plugins or editing files directly on production can remove evidence and make a recoverable fault harder to untangle.
A controlled repair normally starts with backups or snapshots where available, error logs, recent changes, plugin and theme state, PHP compatibility, database health, DNS and SSL checks, and a clear reproduction of the fault.
02 / GUIDE
Common WordPress faults
Typical jobs include white screens, fatal PHP errors, plugin or theme conflicts, broken layouts after updates, slow admin areas, redirect loops, SSL problems, failed migrations, email delivery faults, database errors, compromised files and websites that only fail on certain devices or browsers.
03 / GUIDE
Repair or rebuild?
Most faults do not justify rebuilding an entire website. Repair makes sense when the site structure and codebase are fundamentally sound. Rebuilds become more attractive when the site is trapped on obsolete software, heavily modified without documentation, repeatedly compromised or so fragile that routine maintenance creates unacceptable risk.
04 / GUIDE
What PluginPip charges
PluginPip currently starts straightforward website or application repair work at £95, standard website migrations at £195 and more complex migrations at £395. Additional agreed technical work is priced separately where a fault needs deeper investigation.