Understanding the Integration Phases | Yext Hitchhikers Platform
What You’ll Learn
In this section, you will learn:
- Learn the four integration phases in a Search implementation
Understanding the integration phases
When it’s time to go live, the Admin and Developer will work closely together to integrate Search onto a domain.
The role of the Admin is to make sure that the experience lives on a Production URL and to provide guidance and strategy around the search bar and the search results page.
The role of the Developer is to follow the Admin’s integration guidance and instructions, and to deploy code for the new search bar and search results page.
Integrating a Search experience can be broken up into four phases:
- Adding and/or updating a search bar on the main domain (in the header or through an “overlay” module) - Developer and Admin Action
- Adding a Search Domain - Admin Action
- Publishing the experience to Production (after completing QA in Staging) - Admin Action
- Standing up the search results page - Developer and Admin Action
Adding a search bar on the main domain (Developer and Admin action) A search bar can be added to the main domain either (a) through the header of the page or (b) through an “overlay” module. If you add a search bar to your header, you will link the user out to a separate results page where Search will be served. If you add a search bar through the “overlay” option, you can present Search inline, within the overlay panel, or you can use a redirect URL and link the user out to a separate search results page.
Add a Domain consists of adding a search domain to the Yext platform and assigning it to your Search site. The domain format you select will depend on your results page integration path (either JS Snippet or Subdomain).
Publishing the experience (Admin action) consists of standing up a search experience in Staging for testing and then in Production for integration. You already learned about how to publish to Staging in the ANS150: Frontend Overview module, and you’ll need to publish to production now that you’ve thoroughly QA’d the experience.
At a high level, the main difference between these two methods for standing up a search results page is the header/footer implication (due to the differences in how the search experience is surfaced). As the “JS Snippet” path injects the experience as a component on an existing search results page, it will maintain the integrity of the website’s native header/footer. With this path, any changes made to the header/footer will flow through as they are managed separately from the search experience. Alternatively, the “Subdomain” path surfaces the experience as the search results page (i.e. search results page now resolves to the search experience). With the “Subdomain” path, Yext will recreate the header/footer and workflow is required with Yext any time the header/footer is updated to ensure changes flow through.