EXPLANATION | RELEVANT GL SECTION |
[Relevance] If the query is a full address and the return result is only the street without street number. The Relevance should be rated as Acceptable. | GL 10.1. Specific address, [12112 sugarloaf key, st tampa fl, 33626 example] |
[Relevance] If the query is a chain business and user’s location intent is not expressly stated in the query, the viewport is fresh, and user is outside the viewport, Results are expected in or near the viewport area. All relevant results inside the viewport are eligible for a rating of Excellent. | GL 2.3.2. Implicit Location (viewport: fresh, user: outside viewport) GL 5.11. Rating for User Inside and Outside Viewport |
[Relevance] When the user is within a fresh viewport, take the user location as location intent. Results inside the area CANNOT be rated Bad because of distance alone. | GL 2.3.2. Implicit Location (viewport: fresh, user: within viewport) |
[Relevance] If the query contains words like “near me”, “nearby” or “nearest”, the USER LOCATION, not the viewport location, should be considered the explicit location intent. | GL 2.3.1. Explicit Location (nearest/nearby starbucks example) |
[Relevance] Please always remember to 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). Demotions due to distance depend on the query and its context. (Many/few possible results, rural/urban area, etc) | GL 5.4 Distance GL 5.11. Rating for User Inside and Outside Viewport |
Please don’t being too harsh/too lenient when evaluating on distance. | |
[Relevance] When a query is for a chain business with a location modifier, the user location and viewport can be ignored because the user has provided the location that they are expecting the result to be returned in. If the query for a chain business includes a location modifier that points to a single unique branch of that business, that specific branch can be eligible for a Navigational rating. When there are multiple results available for the location modifier, the highest possible rating for all Results will be Excellent. IMPORTANT: When the location modifier is general, results outside the requested location are demoted based on how many results there are inside it. Please review 10.6.3.1. General Location Modifier | GL 10.6.3. Chain Business with Location Modifier |
[Relevance] The highest relevance rating most category query results will receive is Excellent. You need to determine the user’s intent based on the query Primary Intent Secondary Intent Unlikely Intent | 10.7. Category Queries |
[Relevance] The criteria described above should be applied to understand the transit queries. Additionally, if it is determined that a query has a clear navigational intent, all other results will be Bad. If a result is promoted to Navigational for prominence, other results that could potentially satisfy the user intent should be demoted further for distance and prominence. | 5.17.1 Transit Queries |
[Relevance] Straightforward queries can have unexpected results which at first glance might not fit the query intent. For these kinds of results, consider: •Is there a logical relationship between the query and the result? •How likely is it that the user is going to be looking for this result given the query and location intent? | 5.15 Unexpected Results |
[Relevance] Straightforward queries can have unexpected results which at first glance might not fit the query intent. For these kinds of results, consider: •Is there a logical relationship between the query and the result? •How likely is it that the user is going to be looking for this result given the query and location intent? | 2. Understanding User Intent 5.2. Satisfying User Intent |
[Relevance] If a query and the result are considered associated entities, the result will be rated as having a secondary intent and qualify for a rating from Good to Bad. This association goes both ways: The | 5.13 Associated Entities |
user query may be for the smaller entity and the result is the larger entity or the user query is for the larger entity and the result is a smaller entity within it. | |
[Relevance] Generally, for partial addresses, users are looking for the location closest to their position or within/ near the fresh viewport. Some general considerations: •Exact location that exists returned very close to the user or within a fresh viewport is eligible for Navigational, unless other addresses that satisfy the user intent are also very close. •Results that are farther away from an ideal result but can potentially satisfy the user’s intent can be rated as high as Good (Distance/Prominence) •Results are demoted based on distance. •Results are demoted based on the density of potential results in a given area •Results that are too far away will be rated Bad (Distance/Prominence) | 10.2.1 Non-specific address |
[Relevance] When a query does not specify the type of service level, any relevant result can be rated Excellent. When a query requested a generic service level, a result that offers more service than requested should receive and initial rating of Excellent. When a query requests a specific service level which is not reflected in the result, give an initial rating of Good and demote as necessary depending on | GL 5.18 Service-Level Mismatch |
how well the result would satisfy the user intent. |