[Relevance] •When the user is outside a fresh viewport, take the VIEWPORT as location intent. All results inside the viewport area are Excellent. If there are many results inside the viewport, the results outside the viewport should be rated as Bad. •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. •If viewport is STALE, rating is based on USER LOCATION. | GL 2.3.2. Implicit Location GL 5.11. Rating for User Inside and Outside Viewport |
[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) Please don’t be too harsh/too lenient when evaluating on distance. | GL 1.3.3. Result Relevance Rating |
[Relevance] If the query is category (hotel) query with location modifier the single result that exactly matches the query can be rated as Navigational. Any possible results (hotel) returned in the locality of would be rated Excellent, completely satisfying the ‘Category with Location Modifier’ query. If there are many results in the locality, results outside of the locality should be rated as Bad. | GL 10.7.1 Category Queries with Location Modifier |
[Relevance] If the query is a transit station and the return result is the exact match and unique result, the Relevance is Navigational. If the return result is the transit station located in the requested location, but this station is not the unique train station, the Relevance is rated as Excellent. If the return result is the transit station located in the neighbouring location, the Relevance is eligible Good if there are not many results in the requested location. | GL 5.17.1. Transit Queries (Stockport station example) |
[Relevance] Please differentiate between the General Location Modifier (locality or postal code) and Specific Location Modifier (street, full address). The results outside of the Specific Location Modifier are rated Bad. | GL 10.6.3.2 Specific Location Modifier |
[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. •However, if there is no results for the chain business inside the requested location, the closest branches outside the location can be eligible for Excellent. Remember: •User and viewport location should always be ignored when there is a location modifier •Ratings must always be based on possible real-world results | GL 10.6.3. Chain Business with Location Modifier |
[Relevance] When a user types in the name of a business or a POI along with its address they expect to see the business mentioned in the query as part of the result. If the result is the address alone and DOES NOT mention the business the user cannot be certain that the query and the result refer to the same thing. This is why the result’s relevance should be Bad. | GL 10.6.1 Non-Chain Business [[Gary Danko] |
[Relevance] If the return result is unique and it is the intended result, the Relevance is rated as Navigational. If the user is looking for a Business/POI but the result is another Business/POI which is no related to the queried Business/POI, the Relevance should be rated as Bad. | GL 5.2. Satisfying User Intent |
[Relevance] If the query is a coordinate query, all the features within 50 meters radius of this coordinate are eligible for Excellent. | GL 10.8.2 Coordinate and “My Location” Queries |
[Relevance] If the query are two locations, returning either of the individual location should be Excellent. However, if the return result is a random business, it doesn’t satisfy the user intent and should be rated as Bad. | GL 10.8.1. Routing Queries |
[Relevance] If the query for a District. The return result is the Sub-district that has the same name only satisfy the secondary intent and should be rated as Good. | CSGL 3.6. Duplicate address component |
[Relevance] If the query are ปัม๊ เอ็นจวี ี (NGV station) or ปัม๊ แอลพจี ี (LPG station), NGV or LPG station are the only intent. If the result is the stations offering only gasoline returned, it does not satisfy intent and should be rated Bad. | CSGL 3.13.1 Relevance ratings for filling station |
[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] When a query is clearly for a straightforward category, results must also belong to that category. If the query is the airport and the result is the terminal of the airport, rate Bad due to the user intent. | GL 10.7.3. Clear Categories |
[Relevance] If the query is a store with specific level of service but the result has a lesser degree of service, the highest possible rating is Good. | GL 5.19. Relevance – Service-Level Mismatch [Walmart] example |
[Relevance]: If the query is a street/ locality and the result return a random POI or government offices on the street/locality, the result is irrelevant and should be rated as Bad. However, if the result is a transit station within the locality, the result is still satisfying user’s secondary intent and should be rated as Good. | GL 5.14. Unexpected Results |
[Relevance]: If the query is for a mall and the result is the store inside the mall, this should be rated Bad. This store is inside the requested mall, but users will have no way of knowing this simply from looking at the result. | GL 5.1.8 Lack of Connection |
[Name] If the result name has formatting or misspelling issue (does not match with official name), the name is rated as Partially Correct. Please always use official resources to verify the business name. | GL 6.3. Partially Correct |
[Name] For entity indication, if the name is missing entity indication and it can be confusing, it should be rated as Partially Correct. | CSGL 3.8 POIs name accuracy rating |
[Name] When the classification is wrong, the final Name Accuracy rating is always Incorrect. This is true whether the result name is Correct, Partially Correct, or Incorrect. | GL 6.3.2 Incorrect Classification |
[Address] Please always refer to the official website when there is official website. Also, please refer to the required components of address in CSG Section 2. | CSG 2 Required Component |
[Address] If street name/street number are return for natural feature, the result is too specific and should be rated as [Incorrect – Other Issue]. | GL 8.3.1. Natural Features |
[Address] Transit Station is one of the POIs without an expected address. Only sub-district and larger administrative levels are mandatory, while the rest are optional. | GL 8.3.2. POIs Without an Expected Address |
[Pin] Please use multiple resources and street imagery to verify the pin location. If the pin drops on the street but still within Half’n’Half rule from the house / building, the pin is rated as Approximate. If the pin drops on a building that has another street name, the pin is rated as Wrong. | GL 9. Pin Accuracy |