Step 6: Publish to Production


Now that your experience is thoroughly reviewed and ready to go live, you can go ahead and publish your site to production! Remember that when you publish to Production, you will select a specific commit tag (the latest version that was reviewed on staging). From the review period, our latest commit had the tag 08-31-vST-2:

Final Changes

Publishing to production is a very similar process to the publish on Staging, except we’ll publish a specific commit tag instead of master.

Publish Your Latest Commit Tag

  1. The latest version on your staging site should be published to production. Go to Pages > Sites in the navigation bar and click on your site. Then, click View Environment in the Production Environment section.

Open the Production Environment 2. Click New Publish in the upper right and select your latest commit tag. In the example below, we’ve named our commit 08-31-vST-2:

Final Changes 2 3. Once the publish goes through, your Production publish status should indicate “Success”:

Final Changes 3

Update Search Configuration Labels

  1. Check that your Search Configuration labels are up to date. In the navigation bar, click on Search and choose your search experience. Then, scroll down to Deployment in the navigation bar and select Configuration Labels.

  2. Make sure that PRODUCTION is on your latest version (for example, if Staging is on LATEST (14), Production should be on 14). By updating your Search Configuration label, you are ensuring that your Production URL is reflective of your latest backend configuration.

Check configuration labels

Review Your Production URL

Client-Hosted JS Snippet

If you selected the JS Snippet Integration path, you will need to make sure you append to your in-platform Production URL. For example, if your domain is, your final, integration-ready URL is

Important: The REPLACE_ME_PRODUCTION_URL in the integration snippet will include in the URL.

   <div id="answers-container"></div>
   <script src="REPLACE_ME_PRODUCTION_URL/iframe.js"></script>

Yext-Hosted Subdomain

If you selected the Subdomain Integration path, you should now be able to navigate to your chosen subdomain (that you configured in Step 2) and see your full results page. If the page is giving you an error, your IT team likely needs to complete the CNAME record step as discussed in the “Determine Integration Path” step.