---
title: "Publishing Content to Production Best Practices"
slug: "pushing-content-to-production-best-practices-1"
updated: 2026-01-16T11:49:49Z
published: 2026-04-17T05:23:45Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.whatfix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Publishing Content to Production Best Practices

The content that you create and save on Whatfix needs to be published to the Whatfix CDN servers before it is available to your users. You might be able to view the content using the Preview mode or the See Live option (during content creation), but for the content to be live and reflected on your end user's application, you must perform a Publish action.

Here are some best practices to keep in mind when you're publishing your content to Production.

  Authorize and delegate responsibility
  
    

Ensure that you have the Account Manager role to publish content to Production. You can also maintain an updated list of authorized users for content deployment. For more information, see [Whatfix User Roles](/studio/docs/whatfix-user-roles).

    

  

  Review and configure settings
  
    

Before publishing, review and ensure that all Advanced Customization and Style settings are configured as required. Confirm that all configurations are set to be publisheded to production along with the content and/or widgets.

    

  

  Verify content readiness
  
    

Verify that all publishing content is in the **Ready** stage. When publishing linked content, ensure both the content and associated widgets are in the Ready stage to avoid any inconsistencies.

    

  

  Prioritize content testing
  
    

Prioritize content testing and ensure that any potential issues are addressed before publishing the content.

    

  

  Review Summary pop-up
  
    

Before publishing, review the Summary pop-up to verify that only the intended content is being published. Confirm that the content matches the planned deployment and no unintended changes are included. For more information, see [Summary Pop-ups for Push to Production](/studio/docs/summary-pop-ups-for-push-to-production).

    

  

  Use Publish changes 
  
    

Publish changes, such as global themes and configurations, User Actions, and other account-level changes, and more, without having to publish any content or widgets to Production along with them. Go to an empty Ready stage and click **Publish changes**. Review your changes in the popup that appears, and click **Push to production**. For more information, see [Should I do a Push to Production for any content changes?](/studio/docs/should-i-do-a-push-to-production-for-any-content-changes)

  

  Adopt a release management approach
  
    

```
  Plan and execute push to Production in a release management fashion rather than publishing every single update. Consolidate multiple changes into well-organized releases to streamline the deployment process.
```

    

  

  Organize Content or Widgets using Folders 
  
    

Group content or widgets that you want to display to users belonging to the same geography, having the same user roles, and more. Publish the Folder to Production to ensure all related content and/or widgets is published together. For more information, see [Organize Content/Widgets using Folders](/studio/docs/organize-contentwidgets-using-folders).

  

  Ensure version control
  
    

Ensure that the correct version of the content is selected for deployment. Avoid publishing outdated or incorrect versions by double-checking the version details. For more information, see [Content Versioning](/studio/docs/content-versioning).

  

  Monitor and check notifications
  
    

After publishing content to Production, check your email and the [notification center](/studio/docs/notification-center) to confirm that the content has been successfully published.

    

  

  Periodically review content using Auto Testing
  
    

To ensure end users' workflow does not get impacted after publishing to production, use Auto Testing to automatically test your Flows and generate an extensive report to help fix broken Flows.

For more information, see [Test Whatfix Content](/studio/docs/testing-whatfix-content).

## Related

- [Selective Publishing](/selective-publishing.md)
- [Organize Content and Widgets using Folders](/organize-contentwidgets-using-folders.md)