Staging and preview links provide private, protected environments where you inspect, test, and approve digital deliverables before live release. Managed by our Technology and Creative departments, these links replicate production environments without affecting your live operations or public audience.
Purpose and environment setup
Every web development, interactive build, or complex digital asset built by Xylora Studios undergoes review on an isolated server before production release. We do not test or validate unfinished work on live environments.
When a milestone reaches the review phase, the Technology department generates an ephemeral or persistent staging instance. This instance features:
- Isolated databases populated with dummy or sanitised records.
- Third-party APIs and payment processors configured to sandbox or test modes.
- Search engine suppression using strict `noindex, nofollow` meta tags and robots directives to prevent search engine indexing.
- Access restrictions, typically enforced through password gates or basic HTTP authentication.
Creative and design reviews that do not require full code environments use locked preview links through our design staging tools. These allow frame-by-frame or layout review before assets move into the Technology department for build.
The review sequence
To keep projects moving predictably, reviews follow a structured sequence:
1. Notification and delivery: Once internal quality assurance passes, Operations & Client Services issues the staging link and access credentials directly to your project thread in the Ask Xylo chat. 2. Client validation: You review the staging link against the agreed functional specification and brief. You must test forms, interactive elements, user journeys, and responsive layouts across your team's standard hardware and browsers. 3. Consolidated feedback: Compile feedback into a single, structured punch list rather than disjointed messages. Detail the device, browser, operating system, and the exact steps required to replicate any unexpected behaviour. 4. Remediation: The Technology department addresses logged items within standard studio hours (Monday to Thursday, 09:00-17:00 GMT). First replies to flagged issues arrive within our standard 24-hour target. 5. Sign-off: Once all logged items are resolved, you provide formal sign-off in the Ask Xylo chat to permit production deployment.
Client responsibilities and input
A staging site requires active testing from your side. When inspecting staging and preview links, you must supply:
- Any third-party sandbox credentials required for testing (such as staging CRM API keys or test merchant accounts).
- Clear, reproducible bug reports, including full-screen screenshots or screen recordings where visual glitches occur.
- Timely feedback within the review window allocated in your project timetable to keep scheduled launch dates intact.
Failure cases and troubleshooting
Staging environments behave differently from production environments in specific, deliberate ways. If you encounter issues while reviewing, check these common failure cases:
- Stale browser cache: Changes pushed by our developers may not appear immediately if your browser caches older stylesheets or scripts. Perform a hard refresh (`Ctrl + F5` on Windows; `Cmd + Shift + R` on macOS) or review the link in a private browsing window.
- Authentication prompts: If your credentials fail to load the site, verify you are entering the HTTP basic auth credentials provided in the Ask Xylo chat, not your website user account details.
- Transactional emails: Test transactional emails (such as order receipts or password resets) sent from staging environments will use test mail catchers or deliver to a dedicated sandbox inbox to prevent emails going to real customers.
- Third-party integrations: Staging environments deliberately avoid calling live production webhooks. Do not expect real payments to clear or live customer databases to update during staging tests.
If a preview link fails to load entirely, alert our team via Ask Xylo. We investigate infrastructure issues during standard studio hours.
Staging review checklist
Before submitting your sign-off to Operations & Client Services, verify the following points:
- [ ] Cross-device testing: Have you checked the staging link on desktop, tablet, and mobile screen sizes?
- [ ] Navigation and links: Do all header, footer, and contextual links navigate to the correct staging destinations rather than external production domains?
- [ ] Form submissions: Have you completed all forms and verified that validation rules and on-screen success states trigger correctly?
- [ ] Dynamic content: Are placeholder texts, test names, and sample images replaced with your approved assets?
- [ ] Browser compatibility: Have you verified functionality in Safari, Chrome, and Firefox?
- [ ] Final sign-off: Has your primary decision-maker reviewed the build and recorded approval in writing via Ask Xylo?