Module Assessment | Yext Hitchhikers Platform

You must include a first name and last name in your profile to create challenge environments.

Background

Now that you’ve set up your site, it’s time to review the search quality and make some refinements. Let’s run some searches and see what changes we can make to optimize the experience. You’re looking at top search terms and want the results to look good (maybe you pulled the top search terms from your site before you implemented Yext Search or maybe your Search experience has been live for a couple months and you pulled the top search terms for it).

Your Challenge

Navigate to Search > Brand Search > Test Search. Run the following top-searched queries. As you run the searches, take note whether the results returned are what you’d expect.
- order online
- locations that accept reservations
- upcoming events
- restaurants near me
- phone number for Miami location
- jobs
Search 5-10 other queries as well.
Navigate to the Search Logs screen. 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! The query “jobs“ should be returning jobs! Hiring can be hard and no results means you just lost a lead!
- Optimization: Write up an email draft to your HR department to request content for jobs so you can add it to your experience. We will work on this more in the next challenge!
The query “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 try ”location 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 includes “restaurant” and “location”. Run the query again in Test Search to make sure it updates (could be a short delay).
- You remember that you created a field called Restaurant Features and have this data filled out already with “Accepting Reservations” as a feature. You just need to add it to the searchable fields. Add Restaurant Features (c_restaurantFeatures) as an inferred filter on the Restaurants vertical. Run the query again in Test Search to make sure it updates (could be a short delay).
The query “phone number for Miami location” surfaces the Miami location, but the entity preview doesn’t have the restaurant’s phone number. You may decide to display this on the frontend, but you also want to showcase the phone number to directly answer the user query.
- Optimization: Add a direct answer for the phone number field on the Restaurants vertical.
- To do this in the UI, navigate to the Verticals screen and select the Restaurants vertical from the dropdown. Find the Direct Answers section. Next to Eligible Fields click + Add / Update Fields and select the mainPhone field.
- To do this in the JSON editor, navigate to the Edit as JSON screen and find the restaurants vertical. Add an object for directAnswers like so:
```
"restaurants": {
  "directAnswers": {
    "fieldValues": {
      "eligibleFields": [
        "mainPhone"
      ],
      "predictionMode": "CLASSIFIER"
    }
  },
}
```
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?

Module Assessment

+<% util.points %> points

Weekly Challenge Streak: <% util.streakWeekly %>

You must include a first name and last name in your profile to create challenge environments.

Challenge account expires in <% util.expirationHours > 24 ? Math.round((util.expirationHours * 1.0) / 24) : util.expirationHours %> <% util.expirationHours > 24 ? (Math.round((util.expirationHours * 1.0) / 24) == 1 ? 'day' : 'days') : (util.expirationHours == 1 ? 'hour' : 'hours') %>.

Challenge account has expired. Please create a new account.

Report Card

Add locations to the synonym set

Add Restaurant Features as a searchable field for the Restaurants vertical

Add Main Phone as a direct answer field for the Restaurants vertical

Previous Submissions

Attempt #<% submission.attemptNumber %>

<% submission.date %>

Score: <% submission.numericScore %>

Pending

<% elem.innerText %>