Staging
Create a WordPress staging site before touching production.
Use GET to copy the current production site into staging. Test theme changes, plugin updates, page edits, or imported development work before deciding whether anything should go live.
What this page covers
Prepare a place to test WordPress changes.
The free core creates staging, supports migration into staging, and keeps backups available. The paid add-on is reserved for publishing reviewed staging changes to production.
Recommended flow
Create, review, and publish only when needed.
- Install the free core plugin from WordPress.org.
- Create or refresh staging from production with GET.
- Review updates, edits, or imported development work on staging.
- Confirm the result and keep a backup before production publishing.
- Use the PUSH add-on only when the reviewed changes should go live.
Use cases
How this page fits into real WordPress release work.
Each feature page answers the operational questions an administrator checks before production data changes.
Feature FAQ
Questions to answer before using this workflow.
Does GET change production?
No. GET prepares or refreshes staging from production. It does not publish staging changes to production.
Do I need the paid add-on to create staging?
No. Staging creation is part of the free core workflow.
When should I refresh staging?
Refresh when production has changed and the staging copy is no longer a reliable base for testing.
Can I stop before overwrite?
Yes. Difference review appears when both sides have newer changes that need an administrator decision.
Next step
Try WordPress staging creation with the free core first.
Purchase timing can stay tied to the moment you actually need staging-to-production publishing.