Staging Sites and Making Changes Safely

Overview

When a change is big enough to be risky — a redesign, a major plugin change, a theme swap, or anything you're not 100% sure about — you don't have to test it on your live site. StretchWP supports staging: a managed copy of your site where you can try changes safely, then sync the good ones to live. Staging is set up and managed by the Stretch team so the copy and the sync are handled cleanly.

What staging gives you

A safe sandbox. A staging copy mirrors your live site so you can experiment without visitors seeing broken pages or half-finished work.
Test-then-promote. Once a change works on staging, it can be synced to live — so what you ship is exactly what you tested.
Cleanup when you're done. A staging copy can be deleted once its purpose is served, keeping your fleet tidy.

The staging workflow

Request a staging copy. Contact the Stretch team (or start from the Staging action on the Sites launcher) and ask for a staging copy of a specific site. The team creates it as a managed operation.
Make your changes on staging. Use one-click Log in to work in the staging copy's wp-admin — apply the redesign, test the plugin, rework the layout — without touching live.
Verify on staging. Click through the affected pages and features on the staging copy until you're confident.
Sync to live. When the changes are ready, ask the team to sync staging to live. What you tested becomes what visitors see.
Delete the staging copy. Once the change is live and confirmed, the team can remove the staging copy.

Steps: a safe redesign

Back up first. Confirm a recent snapshot on the Backups tab so you have a fallback (see Backups and restore).
Request staging. Ask the Stretch team for a staging copy of the site.
Redesign on staging. Log into the staging copy and rebuild the pages you're changing.
Review with stakeholders. Share the staging copy for sign-off before anything goes live.
Sync and verify. Have the team sync staging to live, then check the live site's Health (HTTP 200, TLS valid) and click through the changed pages.
Clean up. Ask the team to delete the staging copy.

Example

An agency is rebuilding a client's homepage. They confirm a fresh backup, then ask the Stretch team for a staging copy of harbor-cafe. On staging, they rebuild the homepage and new menu, and send the staging link to the client for approval. Once approved, the team syncs staging to live; the agency verifies the live homepage looks right and Health is green, then asks the team to delete the staging copy. The client's live site was never in a broken state during the rebuild.

Tips

Back up before you start. Staging plus a recent snapshot gives you two independent safety nets.
Use staging for anything you'd hesitate to do live. Redesigns, theme changes, and major plugin changes are ideal candidates.
Get sign-off on staging. The staging copy is the perfect place for stakeholders to approve before you promote to live.
Sync in one direction. Staging is for building and testing; sync to live when it's ready. Avoid making conflicting edits on live while a staging change is in flight.

Troubleshooting

A staging action shows failed on Events. Staging create, sync, and delete run as managed jobs; note the job type and error and share them with the Stretch team.
Live changed while I was working on staging. If someone edited live during your staging work, tell the team before syncing so they can reconcile rather than overwrite recent live changes.
I synced and something's wrong on live. Because you kept a backup, ask the team to restore the pre-sync snapshot while you investigate on staging (see Backups and restore).

FAQ

Can visitors see my staging copy? Staging is a working copy for you and your team, not a public site. Use it to test and to share for internal approval.

Do I set up staging myself? Staging is created, synced, and removed by the Stretch team as managed operations, so the copy and the promotion are handled cleanly. You request it and do your work in the copy.