WordPress backups: a 3-2-1 strategy that holds up
A backup is only worth something on the day it saves you. Here is the 3-2-1 rule, the right frequency and the test that proves it…
Category
Monitoring and response
Spot a hack, read your logs, clean up and restore a WordPress site, then watch the warning signs so you can react earlier next time.
Scanner bots in your logs: /.env, /phpmyadmin, how to read them and respond
Bots look for /.env, /wp-config.php.bak or /phpmyadmin on every site. Learn to read your logs and turn this noise into a signal.
Cleaning up a hacked WordPress site: the step-by-step procedure
An eight-step procedure, based on WordPress.org and CERT-FR, to clean up a hacked WordPress site without reinfection: from isolation to the Google review request.
Site flagged as dangerous by Google: understanding Safe Browsing and getting off the list
A red screen in front of your site? What a Google Safe Browsing flag means, who shows it, how to get it lifted at Google, Microsoft…
Hacked WordPress site and SEO: spam, deindexing and review
Japanese pages, pharma spam, invisible redirects: how SEO spam exploits a hacked WordPress site, how to spot it in Search Console and how to get a…
Has my WordPress site been hacked? Signs, checks and tools
The signs of a WordPress hack, the cloaking that hides it from the administrator, and a method to check: Search Console, WP-CLI checksums, hidden accounts, logs.
WordPress site hacked: how to respond and fix it
The response plan after a WordPress hack: the first ten minutes, the severity grid, the credentials to change, what to reinstall, the Google review, GDPR breach…
How to tell if my WordPress site is hacked: 8 infections to hunt down
The eight most common infections of a WordPress site and, for each one, the symptom, the command or tool that confirms it and the false positives…