Hi Team!
We’re in the process of building a ‘Find a Financial Advisor’ search experience. We’re really excited to build a solution that allows our customers and prospects to ask natural language questions and find the right advisor for them!
We’re only interested in surfacing Financial Advisors within this particular experience. We loved what we read in the Facets training module and are really excited to take advantage of this functionality, as well as the new Maps UI. With that being said, is it possible to hide the ‘All’ tab in the search results page (image below)? We don’t want to confuse our customers by providing both a Universal and a Vertical search experience for the same content.
We’ve been playing around in the new Code Editor and have tried removing the Index file as it was our understanding that the Index file powered Universal search. However, this has lead to a number of other errors, and we’re no longer confident that this is the right approach.
We’re also open to hiding the Navigation Bar altogether given that there is only one vertical (Financial Advisors). I’ve tried hiding the Nav Bar by including the following line of CSS .yxt-Nav-container { display: none;}. While this hides the Nav Bar, the search results still default to Universal Search and does not solve the issue above.
Are there any resources or guides available on this topic that someone could point me to?
Thank you!
Austin
1 Like
Hey Austin,
We’ve been seeing this use case come up more often where we really just need to search for one vertical. I’ve outlined steps below. You can see some examples in action by checking out our new Guides page and Admin Code Snippets page.
1. Set the vertical search as the index page. As you mentioned, it would be great to take advantage of the features only found on Vertical Search. However, you’ll need to have an index.html page for any website because it is the default page when no page is specified (i.e. a user goes to the URL www.domain.com instead of the page www.domain.com/search). As you’ve seen, you’ll run into errors if you don’t have an index.html page.
To remedy this, you can add your vertical page and name it index (i.e. you’ll have a pages > index.html.hbs and a config > index.json file. This allows your vertical search to act as the default page and keep all the functionality of the vertical search, such as facets. You can delete the original index pages that are structured as universal search.
2. Hide the navigation bar. To easily hide the navigation bar, you can comment out the components in your newly created index.html.hbs file. The two lines you need to comment out are:
{{> templates/vertical-grid/script/navigation }}
{{> templates/vertical-grid/markup/navigation }}
Let us know if you have any questions as you implement this!
1 Like
@Kristy_Huang this is AMAZING, thank you so so much!
The new Guides and Admin Code Snippets pages are awesome resources, just bookmarked both of those. Appreciate you sharing those as well!
Austin
1 Like
Hi Team,
I have an interesting question from an e-comm prospect. Is there a way for us to not have an “all” tab and all default searches display under the product tab? My thought is this needs to appear as a traditional ecommerce search solution that also is robust and handles other content types. So if I type in anything the default is I get an ecom experience but if i am really looking for a recipe or something I have the option to select that tab.
Currently they have the following verticals: products, faqs, recipes and videos. Let me know if additional information is needed, would appreciate the help.
Hey Sarah,
Very interesting use case! You can approach this the same way as the first step here. Set the products vertical as the index page. Keep the navigation bar so that you’ll still be able to navigate to other verticals. Hope this helps!
Hey Kristy,
Thank you so much for your quick response. I was able to configure it but had two additional questions:
- Can we move Products vertical to the left so its “first”
- Promo banners are now not showing up… how can we fix that?
Thank you so much for all your help in advance!
Hey Sarah,
You’ll lose all the functionality of universal search if you use this approach, so we recommend keeping the ALL tab if you need that functionality (especially if your search experience has multiple entity types vs. Austin’s example above is just a single search). The universal search would then direct users to the vertical that is most relevant for their query.
-
If you would like the product vertical to always appear first, you could use a query rule to boost the product vertical. Use criteria searchTypes = "ALL" and action BOOST_VERTICAL_INTENT.
-
If you used this Admin Code Snippet to create a promotion vertical, the results will only show up on universal search and not vertical search because they fall under a different vertical. If it’s okay for these promo banners to show up for all searches, you could add a static alert banner as in this example in the Page Layout unit. If you want the promo banners to be dynamic based on search query, I’d recommend keeping universal search in.
Hi Kristy,
This is fantastic! Thank you so much 
