Purpose

To ensure all website updates, enhancements, and fixes are tested safely before being applied to production, minimizing risk, avoiding downtime, and protecting revenue-critical workflows.



When to Use a Staging Environment



All of the following must be implemented and tested in a staging environment before going live:


• Plugin updates

• WordPress Core updates

• WooCommerce updates and extensions

• Functionality enhancements or new features

• Bug fixes impacting behavior or workflows

• Any change affecting templates, login, checkout, search, filters, or interactivity


⚠️ Do NOT perform these directly in production, particularly on busy or ecommerce sites.



When You May Work Directly in Production



The only exception is content-only edits that do not touch functionality, templates, or plugins, such as:


• Creating a new page in draft form

• Editing text or media on existing content

• Changing page content that does not affect logic or UX patterns


If at any point functionality is modified or templates are affected, move the work to staging first.




Staging Workflow Steps


1. Create or Update in Staging


• Make all changes in the staging site

• Install/test plugin updates

• Implement and QA code changes

• Verify layout tweaks and integrations


How to create or clone a staging site on Pressable:

→ Official Pressable guide: How to Clone a Website to StagingHow to Clone a Website to Staging 



2. Internal Review


Developer Review

• Ensures all functionality works

• Checks for errors, regressions, and UI issues


Project Manager Review

• Confirms scope is met

• Validates staging site reflects requirements


3. Client Review



• Share staging environment with the client

• Obtain written approval before scheduling production deployment




Production Deployment Steps


Schedule the Deployment


If the update may cause any downtime or maintenance notices:

• Coordinate a time outside peak traffic

• Notify the client in advance of date/time and expected impact


Push Changes Live


Put the production website in maintenance mode >> https://pressable.com/knowledgebase/wordpress-maintenance-mode/

• Deploy/stage merge to production

• If you’re using a Pressable staging site, reference the Push a Staging Site into Production documentation. 

https://pressable.com/knowledgebase/pushing-staging-to-production/   <<  ⚠️⚠️⚠️ Use this process with caution on websites that are frequently updated or ecommerce sites.

Pushing a staging site to production can overwrite the database, which may result in the loss of live data such as orders, customer accounts, form submissions, or content changes made on production.

Always review database sync options carefully and confirm timing before proceeding. ⚠️⚠️⚠️


Post-Deployment Testing


• Verify critical workflows (checkout, login, forms)

• Confirm plugin updates didn’t break dependencies

• Validate UI across key pages




Client Notifications



Before deployment

• Explain expected impact, timing, and maintenance windows


After deployment

• Confirm the update is complete

• Note any observations or follow-up recommendations




Additional Notes


• If client data may be overwritten (e.g., WooCommerce orders), plan timing accordingly and communicate clearly. 

• If you need Pressable staging assistance or a refresher, consult the Pressable Staging and Staging Sites KB in your internal Pressable SOP section and link it here.




Links



Pressable Staging Guide (how to create a staging environment)

https://pressable.com/knowledgebase/how-to-clone-website-to-staging/ 


Pressable Staging to Production Deployment Guide

https://pressable.com/knowledgebase/pushing-staging-to-production/