Make recovery possible first
Before updates or configuration changes, confirm that a current backup includes the database and required files, is stored separately from the hosting account and can be restored by an authorised person. Test restores in an isolated environment rather than experimenting on the live site.
Keep the hosting, domain and primary administrator recovery routes up to date. Document who can act if the regular maintainer is unavailable. Do not place recovery secrets in a shared content document.
Accounts and updates
A workable maintenance rhythm
| When | Action | Keep as evidence |
|---|---|---|
| Before a change | Back up and identify the affected journey. | Backup location and rollback owner. |
| After an update | Test the homepage, forms, purchases and login. | What was changed and what was tested. |
| Regularly | Review accounts, pending updates, alerts and restore readiness. | Date, owner and unresolved issues. |
| After a suspected incident | Preserve logs, contain exposure and involve the host or specialist. | Timeline and exact actions taken. |
Check the surrounding hosting
Use HTTPS, keep supported server software and protect hosting and registrar accounts as carefully as WordPress itself. Restrict unnecessary access and avoid broad permission changes without understanding the host’s requirements. Security plugins can help, but installing several overlapping tools is not a substitute for clear ownership.
For the authoritative baseline, read WordPress’s hardening guidance. Follow host-specific instructions for server settings rather than copying commands from an unrelated setup.
If the site may be compromised
Record what was observed and when. Contact the hosting provider or a qualified incident responder, preserve relevant logs and isolate affected access as appropriate. A random scan result is not enough to determine the full scope or declare a site clean.
After containment, review account credentials, vulnerable components and the restoration source. Retest important journeys using the audit checklist; do not immediately restore a backup whose integrity is unknown.