Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Staging

Create a WordPress staging environment in Hostinger hPanel to test plugin, theme, and code changes safely, then push them to production when ready.

An isolated copy of your WordPress site for testing changes before they hit production — plugin updates, theme edits, content drafts, code tweaks.

Note: Staging is available on WordPress sites and is plan-gated — entry-level plans see an upgrade prompt. Creating a staging environment can take up to 15 minutes, and WordPress multisite is not supported.

Create a staging environment

  1. Open your WordPress site in hPanel.

  2. Click Staging in the left menu.

  3. Click Create staging.

  4. Name it (e.g., staging-v2).

  5. Click Create.

Hostinger clones your files and database. The staging URL appears in the Staging panel (usually a subdomain like staging-<hash>.<your-domain>).

Test your changes

Edit on staging freely — install plugins, update themes, try new content, run wp-cli. Production stays untouched.

Push staging to production

Warning: This overwrites your live site. Create a backup of production first so you can roll back.

  1. Go to Staging.

  2. Click Push to live (or Sync to production).

  3. Choose what to sync:

    • Files only — site files, no database (themes, plugins, uploads)

    • Database only — posts, settings, users; no files

    • Full sync — both

  4. Confirm.

Pull production to staging

Refresh staging with a fresh copy of production data:

  1. Go to Staging.

  2. Click Pull from live.

  3. Confirm.

Staging is overwritten with the current production state.

Delete staging

  1. Go to Staging.

  2. Click Delete next to the environment.

  3. Confirm.

Production is unaffected.

SSL on staging

Staging gets its own SSL certificate automatically — no configuration needed.

When to use it

  • Major plugin or theme updates

  • WordPress core version bumps

  • Before enabling a new plugin on a live site

  • Content rehearsal before a launch

  • Testing PHP version changes

Troubleshooting

Staging URL is blank Clear your browser cache; staging uses a different cookie path from production. If still blank, check AI Troubleshooter on the staging site.

Push to live failed partway Restore production from Backups. Staging remains intact for another attempt.

Last updated: July 22, 2026

PreviousWordPress Security
NextCopy Website

Last updated

Was this helpful?