Security is an ongoing process. A small monthly routine prevents many compromises and makes recovery much faster when something goes wrong.
Before you begin
Sign in through the official client area and keep account-specific values from your activation email available. Make a backup before changing production data or configuration.
Steps
- Back up before changes: Create a restorable file-and-database backup before core, theme, or plugin updates.
- Update supported software: Apply stable updates promptly and replace extensions that are abandoned or incompatible.
- Reduce attack surface: Delete unused plugins and themes, limit administrator accounts, and use unique passwords with two-factor authentication.
- Protect traffic and forms: Force HTTPS, use spam controls, validate form handling, and keep secrets outside public files.
- Monitor health: Review administrator users, file changes, scheduled tasks, error logs, and security alerts.
- Test recovery: Periodically restore a backup to a safe staging location so the recovery process is known before an incident.
Important notes
- A security plugin complements updates and sound configuration; it does not replace them.
- Never edit production files before preserving a known-good copy.
When to contact support
Contact support if the documented controls are unavailable, the service reports an account-level restriction, or the issue continues after these checks. Include the affected domain or service, the exact error, a timestamp with timezone, and the steps already tried. Never include passwords, one-time codes, private keys, or complete payment details.
