Understand the difference between Autocomplete and Search
Autocomplete is more lenient than Search.
Please note that in Search, we presume to know the user intent and return only the results thatwould satisfy the user intent.
However, in Autocomplete you need to consider the possibility of the query being incomplete and provide a more broader search base for the user.
Also note that prominence is very important while rating Autocomplete results.
Please note that this document was made in November 2023. Guideline sections in this document refer to Autocomplete Guidelines September 2023. If there is any conflict between this document and a later version of the guidelines, please follow the latest version of the guidelines.
If the user’s location intent is not expressly stated in the query, for example [chinese fo] or [479 margarita a], use the user location, Viewport location, and viewport age to determine the area of expected suggestions.
Viewport User tocation Intent
Viewport | User | Location intent |
---|---|---|
Fresh | Inside viewfport | When the user is within the fresh viewport, take the user lotnation as location intent. Suggestions are generally expected in or near the viewport and suggestions inside the area cannot be rated Bad for distance alone. |
OutsideViewport | Suggestions are expected in or near the viewport area. All relevant suggestions inside the viewport are eligible for a rating of Excellent. If no suggestions can be found in or near the viewport, use the user location as a secondary location intent. | |
Milissing | When the user is missing, the viewport remains the location intent. | |
Stale | Inside viewfport
| When the viewport is stale, consider only the user location as Icication intent. |
Outside | ||
Missing | Use the stale viewport as location intent when the user is missing. | |
Viewport Age Missing | Present or Missing | Consider the viewport fresh when the viewport age is missing. |
Missing entirely | Present | The user location sets the location intent when the viewport is not present. |
Missing | When the user and viewport are missing, the test locale becomes location intent with a strong focus on prominent suggestions. |
Query | 50 mac | User Location | -43.53607177734375, 172.6666259765625 |
Viewport Age | STALE | Viewport Centre | -43.5076652688626, 172.556065593958 |
In this example the viewport is STALE, so it should be ignored. The implicit location intent is the user’s location.
Suggestion 2 is a bit further from the user than the closest matching addresses, so its relevance is Good.
1.2.2 Suggestion Relevance Rating
The relevance rating will take user intent into consideration as well as distance/prominence. Relevance is always rated independently of any data (name/classification or address) inaccuracies. This means that when rating relevance, we always assume that the suggestion exists (even if research reveals the location is closed) and that the data presented is correct.
Always rate against the real world: If there is a better result available but it is not shown, demote the existing result(s) considering the missing one(s)
1.2.2 Suggestion Relevance Rating
Query | Clevedon ch | User Location | -36.97998046875, 175.01220703125 |
---|---|---|---|
Viewport Age | STALE | Viewport Centre | -36.9885568855491, 174.8681136081 |
Street imagery shows that Clevedon Chocolate Shop no longer exists. However, we ignore this when rating relevance. We assume that the suggestion exists and that the presented name and address are correct.
If the business still existed, it would satisfy a primary user intent. It would also be one of the closest possible suggestions to the user.
There is no reason to demote relevance for this suggestion, so it is rated Excellent.
4.3.2 Distance
Generally, the farther away the suggestion is from the location intent, the less desirable it becomes. This is especially true for queries highly dependent on distance to the user/viewport, like chain businesses, hospitals, pharmacies, or grocery stores.
Because a user can be provided with multiple similar suggestions, the closest entities providing the expected services should be considered the best options. As suggestions get farther away, they should |.
be considered less relevant and demoted accordingly. The context of each situation should be used to determine what constitutes a close or far suggestion. Factors which can affect distance demotions Include:
Query | Hom | User Location | -36.60369873046875, 174.6990966796875 |
Viewport Age | Fresh | Viewport Centre | -36.5990658478074, 174.69437062575 |
Distance refers to the direct distance from one point to another and is measured via a straight line. There is no need to account for the actual distance required to travel from one point to the other, such as driving distance.
4.3.2 Distance
Query | Hom | User Location | -36.60369873046875, 174.6990966796875 |
Viewport Age | Fresh | Viewport Centre | -36.5990658478074, 174.69437062575 |

Suggestion 2 is some distance from the user compared to other possible suggestions including another street called Homestead in Red Beach (suggestion 1).
The relevance of suggestion 2 should be demoted to Good or Acceptable. There are not enough possible suggestions in the area to justify demoting it to Bad.
4.3.2 Distance
Query | Hom | User Location | -36.60369873046875, 174.6990966796875 |
Viewport Age | Fresh | Viewport Centre | -36.5990658478074, 174.69437062575 |
Clevedon can be interpreted as an explicit location and the above query suggestions include it as a location modifier, so they match the user query. Chanel and Chatime are chain businesses, so they fulfill the suggestion expectations described in guidelines section 2.2.2. However, we also need to check the search performance by comparing their closest results against all possible suggestions.
Research shows that Chanel and Chatime have no stores in or particularly close to Clevedon, so the relevance of these suggestions is Bad.
The prominence of a feature refers to its popularity, including the number of people visiting and media sources referencing it. Prominence can vary based on the test locale and even local knowledge. Consider the following list to get a general idea of the concept of prominence, ordered from the most prominent to the least prominent:
Suggestions with high prominence may still be relevant even when far away from the user. Suggestions with low prominence, on the other hand, may not be as relevant even if they are close to the user.
Once you’ve decided how relevant the suggestion is based on user intent, consider the suggestion in the context of all possible suggestions in the real world. Each suggestion is given a rating based on Prominence and distance to the user or viewport. The table below shows how they interact: Far distance and low prominence receive low ratings, while prominent suggestions close to the user or viewport receive high ratings
“<2-
* Medium distance away compared to similar prominent suggestion
** Far distance away compared to similar prominent suggestion
close to the user or viewport receive high ratings.
4.3.4 Distance vs Prominence
The user is inside the FRESH viewport, so the location intent is the user location.
Suggestion 1 is a small town. It matches the query, but it is far away and not prominent enough that the user in Takanini is likely to be interested in it when there are multiple possible business and street suggestions near them.
Relevance is Acceptable or Bad.
4.3.4 Distance vs Prominence
The user is inside the FRESH viewport, so the location intent
is the user location.
Suggestion 3 is further from the user than another suggestion
and it is a small street that is not very prominent, so its relevance is demoted to Good.
4.3.4 Distance vs Prominence
The location intent is the user location because the user is inside the FRESH viewport. Suggestion 1 is quite far away, but it is a government region so will at least be known in the country. There is not really anything closer to the user that matches the query and has similar or greater prominence, so suggestion 1 is rated Excellent or Good.
Suggestion 4 is closer to the user than suggestion 1 but less prominent since it is just a town and people outside the area may not be familiar with it. There is another existing town that matches the query and is significantly closer to the user so suggestion 4’s relevance is demoted to Good.