A staging copy gives you a place to review a website change before deciding to publish it. Confirm the environment, access restrictions, test data and responsibilities before work begins; availability and scope follow the service agreement.
Confirm access and test data for the staging copy, review the change and make a deliberate decision about publishing it.
- Restricted test access
- Review the change
- Approve publication
Before creating or refreshing a copy
- Identify the live source and the intended test destination. Agree what a refresh would overwrite.
- Check access restrictions before copying personal, customer or unpublished information.
- Decide which data can be sanitised and which integrations need test accounts.
- Prevent unintended customer emails, live payments, order fulfilment or external automation from a test copy.
Confirm access protection: a separate hostname does not make a site private. Robots and noindex rules control indexing; authentication or another actual access restriction controls who can reach the content. Ask which protection is configured for your environment.
A review with a clear handoff
- Define the change. List the pages, code, content or settings being changed and the expected result.
- Record the baseline. Capture the current behaviour, relevant versions and the recovery route.
- Test the copy. Review important pages on a phone and desktop, then check forms, logins, search and the affected application functions using authorised test activity.
- Approve the result. Record who reviewed it, what passed and any known limitations.
- Agree publication. Review the exact files or data being promoted, new live activity since the copy, timing and the rollback decision.
- Check the live result. Repeat the agreed acceptance checks after an authorised publish.
A copy can become out of date
New orders, enquiries, users and edits may arrive on the live site while staging work continues. A publish should account for that activity. Do not assume a whole-database replacement will preserve it, or that a refresh will preserve unfinished staging work.
Standard and premium staging
The published offer includes standard staging where agreed for the website. Premium staging uses separate server resources and is scoped and priced separately. Confirm the actual isolation, capacity, refresh method and access controls before a large import, runtime change or heavy test.
The service terms and security disclosure describe the published arrangement and its limitations. Request confirmation of the specific environment's protection; this guide does not change the agreement or imply every staging copy is private by default.
Staging questions
Can I use real customer data in a test copy?
Use only data needed for the agreed test, with appropriate access restrictions and sanitisation. Review external integrations before allowing the copy to send anything.
Is a publish the same as copying everything?
Confirm the implementation and the exact files or database changes. The plan must account for live activity and the recovery route.
Does passing staging remove every launch risk?
No. Production configuration, real traffic and external services can differ. Keep an approved publish plan and repeat the key checks afterwards.
Useful alongside the review
- Backup and recovery scope
- Migration and cutover planning
- Agency responsibilities and approvals
- Why staging helps with website changes
Discuss a staging and change-review plan
Tell us the public site URL, platform and the work you need. We will confirm the scope and responsibilities before quoting.
Ask about your site