In this task, the query is “Gamma a”. The suggestion is a result for a GAMMA store in Hilversum. At a glance it might look like this result matches the query, but it actually does not match the second part of the query. The user hasn’t finished the query and continued typing for a reason. The user is probably looking for a specific branch, or a store near a specific location that starts with “a”.
Research shows that there are several stores in Amersfoort, and there are also several GAMMA
stores in Amsterdam. These are much more likely to satisfy intent.
Both the location and name of the store in our result do not match the second part of the query. This is an issue that makes the suggestion very unlikely to satisfy intent. Relevance is demoted to Bad, because of a user intent issue.
A similar issue can also be found for address queries. When the user looks for an address and includes several different address components, it strongly suggests that address components that appear before the last component of the query are complete. The user probably won’t look for an address by only including half of the street name.
Query: Heidelberg 1
Result:
Heidelberglaan 1,
Utrecht, Nederland
Type: Address
In this example, the query is “Heidelberg 1”. The suggestion is an address result for Heidelberglaan 1 in Utrecht. This address looks like it matches the query, but it’s unlikely that this is the address the user is looking for. Research shows that there is an existing address that perfectly matches the query, which is Heidelberg 1 in Borne.
https://www.postcode.nl/7621BN/1
Because the user has already included other components after the street name, it’s very unlikely that the user is looking for Heidelberglaan 1. Because of this, Relevance is demoted to Bad.