Module Assessment | Yext Hitchhikers Platform
Background
Turtlehead Tacos has officially launched & integrated their Search Experience with their main website. Consumer queries are now being logged in analytics! Let’s take a look and see what changes we can make to optimize the Search Experience.
Your Challenge:
Stage the site.
- Navigate to Pages > Turtlehead Tacos Search > Deploys.
- Make sure the most recent deploy is published to staging. If it is not, click the dropdown on the right and select “Publish to staging”.
Go to your staging URL to access your Search experience. Input the following queries into your Search Experience so we have data to work with in the platform. As you run the searches, take note whether the results returned are what you’d expect.
- community stories
- order online
- locations that accept reservations
- upcoming events
- restaurants near me
- phone number for Miami location
- jobs
Search 5-10 other queries as well.
Go to Search > answers > Search Logs. Open each search log in a new tab to review the queries. For each query:
- Mentally note whether the results look good or need review. For example, if there are no results or the results are not relevant to the query, you’ll want to make adjustments to improve the results. In those cases, what do you think is the issue? Is it an issue with the Knowledge Graph, configuration or algorithm?
Now that you’ve reviewed the queries, let’s start improving!
order online
is not pulling in the delivery FAQ!- Optimization: Create a one way synonym from “order online” –> “delivery”. Test your change on your staging experience to make sure it updates (could be a short delay).
jobs
should be returning jobs! Hiring can be hard and no results means you just lost a lead!- Optimization: Write up an email draft recommending to Turtlehead Tacos to add jobs to their experience. This is a post-launch optimization recommendation and one of many more to come!
locations accepting reservations
should be returning the restaurants vertical and ideally only those restaurants that are accepting reservations, but it’s not doing either. You can trylocation accepting reservations
which at least returns restaurants, but not filtered to those accepting reservations like the search calls for.- Optimization: This seems like a two-fold problem:
You need to tell the algorithm to treat locations the same way it would treat restaurants. Add “locations” to the existing synonym set that starts with “location”. Test your change on your staging experience to make sure it updates (could be a short delay).
You want to make sure that if someone searches for restaurants accepting reservations you only surface those that are to make sure customers get the best answer possible. You remember that you created a field called Restaurant Features and have this data filled out already! You just need to add it to the searchable fields. Add Restaurant Features (c_restaurantFeatures) as an NLP filter on the restaurants vertical. Test your change on your staging experience to make sure it updates (could be a short delay).
- Optimization: This seems like a two-fold problem:
Make any other changes to optimize the experience based on the queries you ran. Which of the other ones need improving and how can you improve them? Use the feedback button to tell us what else you did!
After you’ve verified these changes in staging, update your production label to your latest configuration version.