Once you are finished building your search experience, it is time to publish it to review or go live in the proper environment.

As is standard in web development, with Yext your sites come with two environments:

1. Staging - where you “stage your changes” as you’re developing new features or building the site from scratch
2. Production - “production ready"

You always want to test your changes in staging before you push to production to make sure you catch any errors before they go live for other users to see.

To publish to staging or production in Pages:

1. Click Pages in the navigation bar and click on your desired site.
2. Depending on the type site your building Search on, steps will vary:
   • Pages
     1. Click Deploys.
     2. Locate the deploy you want to publish.
     3. Click the arrow next to the Preview button for that deploy. It will open a dropdown where you will select one of the following:
        • Publish to Production
          • Production is not automatically updated and you must manually publish a deploy to production. You should thoroughly QA your experience in staging before publishing it to production.
        • Publish to Staging
          • Note that, by default, any new deploys are already published to staging. This allows anyone with the staging link to see the most up-to-date version of a recently added change.
   • Classic Pages (Legacy)
     1. Click on the View Environment button within either the Staging or Production Environment.
     2. Click on the New Publish button in the top right corner. A dialog box appears.
     3. Select a Git Reference. Choose from one of the tags in the dropdown.
        • Note: this is a Tag assigned during the Commit Code Changes in Search Frontend Theme process (you can also learn more in the Navigate the Code Editor training unit) or added afterward by clicking into a “recent commit” on a branch.
        • If you’re publishing to Staging you can assign this to the master branch. However, you should never assign to master when publishing to Production.
3. Click Continue.
4. Now you can view your staging or production environment by clicking on the links.
   • Pages will show this at the top of the deploys screen.
     
   • Classic Pages (Legacy) shows these under the Custom Development section.