Best practices for safely performing maintenance on Kinsta-hosted WordPress sites. The core principle: always confirm backups exist before touching anything. Kinsta's automatic backup system makes this straightforward, but the steps below should be followed every time.
When working on a client site we don't host ourselves, we have no control over the server environment and limited visibility into what's been changed. A mistake without a restorable backup can be expensive and relationship-damaging. This workflow was formalized after scoping maintenance work on the [1] site in February 2026.
Before making any changes, log into the Kinsta dashboard and confirm automatic backups are enabled and recent.
Navigation path:
Kinsta Dashboard → Sites → [Client Site] → Live → Backups
If backups are present and current, it is safe to proceed. If not, do not begin work until a manual backup is created or the client confirms their backup situation.
Note: Kinsta's automatic backups are not always visible from within the WordPress admin panel itself (under Tools or elsewhere). You must check the Kinsta dashboard directly.
Backend work (database cleanup, plugin fixes, SEO audits) requires more than WordPress admin access. Confirm you have one of the following:
Where to find credentials:
Kinsta Dashboard → Sites → [Client Site] → User Management or Info tab
If SSH credentials are not already set up, you may need to create a new server user or request access from the client. Do not assume WordPress admin login is sufficient for backend operations.
Kinsta sites may use different plugins and configurations than WP Engine-hosted sites. Before running any automated tools or scripts, audit the active plugins:
| Task | Access Required | Notes |
|---|---|---|
| SEO metadata fixes | WordPress admin | Can be done via plugin or bulk editor |
| Database cleanup (orphaned data, transients, autoload) | SSH / WP-CLI | Cannot be done reliably from WP admin alone |
| Broken link repair | WordPress admin | Use Ahrefs or similar to identify; fix in editor |
| Plugin updates | WordPress admin | Test on staging first |
| Image optimization | WordPress admin or SSH | Bulk tools require SSH for large sites |
| Cache clearing | Kinsta dashboard or admin bar | Kinsta cache must be purged from dashboard |
If you only have WordPress admin login (no SSH, no hosting dashboard access), the following are not possible:
This is the same limitation encountered with [2] after their unauthorized DNS migration — front-end login exists, but backend tooling is completely blocked.
Kinsta accounts typically require two-factor authentication (2FA). Ensure the following are stored in LastPass before starting a session:
If a Kinsta account requires email verification as an additional step, coordinate with whoever owns the team email inbox before scheduling maintenance work.