Skip to main content
Tools & automation projects
Tools & automation

WordPress recovery toolkit

Structure the recovery of a hacked WordPress website, from analysis to relaunch.

Born from website recoveries carried out for Reproléman, this toolkit automates repetitive WordPress analysis, backup and reconstruction tasks. I am developing it to prepare fixes and migrations through a traceable workflow, with checks before relaunch.

How the tool works

Input to analyse

Website files, data and backups

  1. Analyse
  2. Rebuild
  3. Verify

Output

Documented recovery and relaunch checks

My role
Design and development
Status
Tool in development
Technologies and scope
PythonWordPressAutomationSecurityMigration
The need

Turn a complex recovery into verifiable steps

Recovery after hacking requires understanding what to keep, what to replace and how to verify the result. The toolkit organises this workflow and handles repetitive processing while retaining decisions specific to each website.

A tool built from real projects

The WordPress recoveries carried out for Reproléman provided the development context: several existing websites, content to preserve and environments to rebuild or migrate.

Reusable scripts operated during the project

I develop the analysis, collection, backup and reconstruction tools. Site-specific details are described in profiles; the scripts run the processing steps and report their progress to guide recovery.

The workflow

Understand the existing website before rebuilding

  1. Collect and examine the website's components

    The inventory, collected files and selected data feed an isolated static analysis. Comparisons and indicators help prepare recovery decisions.

  2. Prepare a rebuilt candidate

    The workflow distinguishes components to replace from a trusted source, content to preserve and items requiring review. Configurations and data are prepared for the destination environment.

  3. Check before and after relaunch

    Staging and migration operations rely on verified backups and the project's decisions. File, data and HTTP response checks accompany publication.

Features being developed

Automate repetitive recovery work

Inventory and analysis reports

Collection results and comparisons are brought together in reports that distinguish findings, exclusions and items still to review.

Backups and verified restoration

The recovery workflow includes encrypted file backups and data exports, with integrity and restoration checks before recovery operations.

Reconstruction and migration preparation

The scripts prepare the components, retained content, configurations and URL adaptations required for the website's chosen environment.

Tracking long-running operations

Progress states and logs help track transfers and prepare to resume after an interruption by checking the effects of operations already started.

Design decisions

Automation that retains project decisions

Analyse without running compromised code

Collection is separate from analysis. The website's files are treated as data in an isolated environment, without running their PHP or WordPress code.

Separate planning from execution

A report prepares the actions; reconstruction and relaunch have their own checks. Each website's specific details and decisions remain documented.

The output

A recovery workflow documented from start to finish

  • Analysis reports and a site-specific recovery plan
  • A rebuilt WordPress candidate for the selected environment
  • Progress records and relaunch checks

In development

SEO audit toolkit

Turn SEO findings into an action plan tailored to the website.

PythonSEOAnalysis across different CMS platforms

Your project

Let's build the tool missing from your workflow.

Start with a concrete example: a repetitive task, a file or an analysis to produce. We will look at the available data and the expected result to define a custom tool.