Navigating Search| Hitchhikers Platform
What You’ll Learn
In this section, you will learn:
- What information the Search Overview Screen provides
- How to navigate to the Experience backend
- How to navigate to the Pages frontend
The Search Overview screen is designed to be the one-stop shop to check in on the health and activity of your search experience. Here you’ll find high-level analytics, as well as a stream of the latest searches in the “Recent Searches” module.
You can choose to filter this screen by Experiences (assuming you have multiple), Traffic Type (internal or external) or Configuration Labels (staging environment or production environment) using the top navigation filter. You can also filter the Recent Searches module to a specific vertical (it defaults on Universal searches). We’ll cover the Search Overview screen in more depth in the Saerch Analytics module.
In the All Search Experiences screen, you can view and manage your Experiences. As you’ve learned, you can have one Experience or you may have multiple Experiences depending on your requirements.
If you have more than one Experience, you’ll see a screen like this:
Once you click into an Experience, you’ll see five main sections in the navigation bar:
- Home and Experience Details
In the Home section, or when you first click into an experience, you’ll land on a full screen Test Search, where you can test your search experience without having to configure a frontend. Test Search allows you to toggle between universal and vertical tabs to visualize the results an end-user may see for a given query. Similar to the frontend experience, you will also be able to view and apply facets on the vertical results in order to test their impact on the search results. You can learn more about Test Search in the How to Create and Edit a Search Configuration unit
In the Experience Details section, you’ll find a checklist for building your Search Configuration along with various materials to help you with your iterations, including a Test Search panel on the right. There is also an overview of the experience, including the Experience Key, API Key, and the option to link the staging or production URLs of the site that’s hosting the experience.
In the Analysis section, you will find different ways that you can look at Search Logs and Search Terms in order to understand search behavior and optimize over time. There are a number of tools in here for Admins to understand what is being searched, how the algorithm interpreted a search, and so on. You’ll learn more about these in the Search Analytics, Debugging, and Post-Launch Optimization modules.
In the Configuration section, you will find where you create and manage your Search Configuration. You’ll learn more about this starting in the Search Configuration Overview module. You can edit your Search Configuration directly in the UI or optionally through JSON syntax.
In the Training section, you will be able to give the algorithm feedback on its predictions so it will learn to improve over time. Rejecting a prediction fixes it immediately and also helps ensure similar mistakes don’t happen in the future. You can train the algorithm on featured snippets, NLP filters, and spell checking.
In the Deployment section, you will see a history of your Search Configuration versions and deploy specific tags to the Staging and Production versions of your site. You can also run configuration version comparisons here.
All settings in Search exist at the Experience level so that each experience can be configured independently. The first place you should look if you’re trying to figure out how to turn on or off an Search-related setting is in the individual Experience.
You should be familiar with how to navigate to the Pages product from the Pages track. However, with Search you’ll be working within the “Custom Development” screens.
When you’re looking to make changes to the frontend of your search experience, navigate to Pages and select the relevant Site. You’ll make most of your changes in the Code Editor, which allows you to view and commit code to the Github Repository that houses your Search frontend code.