---
title: "Pushing Content to Production Best Practices"
slug: "pushing-content-to-production-best-practices"
updated: 2026-08-13T09:24:21Z
published: 2026-08-13T09:24:21Z
canonical: "support.whatfix.com/pushing-content-to-production-best-practices"
stale: true
---

> ## 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.

# Pushing Content to Production Best Practices

The content that you create and save on Whatfix needs to be pushed 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 Push to Production.

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

---

Expand the following accordions for more details:

**Authorize and delegate responsibility**

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

**Review and configure settings**

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

**Verify content readiness**

Verify that all publishing content is in the **Ready** stage before initiating the push. When pushing 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 pushing the content.

**Review Summary pop-up**

Before confirming the push to Production, review the Summary pop-up to verify that only the intended content is being pushed. 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 push any content/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 [Push Whatfix content and widgets to Production](/hub/docs/push-whatfix-contents-and-widgets-to-production).

**Adopt a release management approach**

Plan and execute a 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. Push the Folder to Production to ensure all related content and/or widgets is published together. For more information, see [Organize Content or 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 pushing 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 pushing content to Production, check your email and the [notification center](/studio/docs/notification-center) to confirm that the content has been successfully published.