A solid foundation
A test environment with clear boundaries
A staging environment lets you try code, design and settings away from the live website. Be clear about which data has been copied and prevent the test site from sending real emails, taking payments or triggering external actions. A production copy may still contain active keys.
Restrict access to the test environment. A noindex instruction alone does not make a website private. Use test data and test settings for external services where possible. Agree who can open the copy and when it will be removed.
Publishing needs more than a copy button
Decide in advance what must go live: files, settings or database data too. While you test, the live site may receive new forms, accounts or orders. Overwriting the entire database could lose that newer information.
The Hostingot concept therefore centres on an identifiable test environment, a deliberate publishing step and a recovery path. Exact copying and publishing capabilities have not yet been set. Tell us which changes you need to make most often today.
Testing, publishing and recovery
| Step | Check before proceeding |
|---|---|
| Copying | Restrict access; disable real email and payment actions. |
| Publishing | Decide which parts change and preserve new live data. |
| Recovery | Have a usable recovery point and know what restoring will overwrite. |
A focused test in four steps
- Record the change, starting version and expected result.
- Check forms, login, mobile display and relevant integrations.
- Create a recovery point and review new live data before publishing.
- Repeat the same key actions on the live site after publishing.
Questions about staging
Is staging already part of my package?
No. This integrated feature is a concept and this page does not make it part of an existing package.
Does a staging environment replace a backup?
No. A test environment changes while you work. A backup preserves a chosen state for recovery; it serves a different purpose.
Can I always publish the entire test database?
That is risky when live data changes in the meantime. Decide which changes are needed and how to preserve new content, accounts or orders.
Read more from the source: Google Search Central · Control what you share
Which changes would you like to test more safely?
Tell us whether you mainly update plugins, change designs or run a shop. That helps us assess the staging workflow you need.