GL Sections | Explanation |
10.1 Specific address | [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. See “Sugarloaf Key St” example |
10.2 Non-specific address | Generally, for partial addresses, users are looking for the location closest to their position or within/near the fresh viewport. Some general considerations: •The exact location that exists returned very close to the user is eligible for Navigational, unless other addresses that satisfy the user intent are also very close. •Exact location returned 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.3 Query Address does not exist | To be useful to the user, address results need to point to either a building with that address or a plot of land that has been officially assigned the address. Sometimes your research will show that a full query address does not exist (or no major search engine will be able to determine its exact location). In cases like this, you will see one of three types of results: • The closest verified address (on the same street and in the same city and state): Rate relevance as Excellent. •The same address as the query address: Rate relevance as Excellent and address as Incorrect – Address does not exist. The pin will be rated Can’t Verify. •The queried street without a street number: Rate relevance as Acceptable. •When a queried address does not exist, the answer to the question “Is there a navigational result for this query” will always be No. |
10.6.1 Non-Chain Businesses | Some businesses have only one location, so treat and rate them as navigational queries. The correct location should be rated Navigational, and any other results should receive Bad (User Intent). See “Klein High School” example |
| Explanation | |
|---|---|---|
10.6.2 Chain Businesses | A query for a chain business is generally not considered an explicit query and is therefore not eligible a for Navigational rating unless the query contains a location modifier that points to a single unique location. For this specific case, see “Aldi waco tx” and “Kate Spade New York” examples. Chain businesses are businesses that have more than one location, and include everything from national chains like Starbucks, Target, Auchan, Albert Heijn, and Boots down to small local chains. Distance evaluations should be based on chain business locations in the real world, not only the returned results. | |
10.7 Category Queries | [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 | |
2.3.1 Explicit Location | [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. “Food near me” for example. | |
2.3.2 Implicit Location | [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. | |
2.3.2 Implicit Location (viewport: fresh, user: outside viewport) | [Relevance] If the query is a chain business and user’s location intent is not expressly stated in the query, Results are expected in or near the viewport area. All relevant results inside the viewport are eligible for a rating of Excellent. | |
5.1.8 Lack of Connection | If the result does not satisfy the user intent either because there is no relationship between the query and the result or because the connection between the query and result will not be immediately obvious to the user, rate the result relevance Bad. | |
5.14 Unexpected Results | 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? |
GL Sections | Explanation • How likely is it that the user is going to be looking for this result given the query and location intent? |
5.15 Multiple Transit POIs with the Same Name | Many large transit POIs include multiple means of transportation at the same location. For example, large airports can have metro or train service within the same location, or train stations can be a hub for trains, metros, and buses. Other transit POIs at the queried transit POI should be treated as secondary intent with an initial rating of Good but can also be considered Acceptable if the result is less likely to satisfy the user’s intent. Additional demotions can be applied based on the prominence of the returned feature. See “hamburg airport” and “Embarcadero Station” examples |
5.16.1 Transit 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. See “BART daly city” example |
5.2. Satisfying User Intent
| Primary Intent Result satisfies the most obvious and likely user intent. Rating: Navigational or Excellent Secondary Intent: A result which is less likely to be the user’s intent. Results matching secondary intent are often not as prominent but still satisfy the intent of the query. Associated entity results are considered secondary intent (at best). Rating: Good (User Intent) Unlikely Intent A result which matches the query but is very unlikely to be the user’s intent. Rating: Acceptable (User Intent) Non-Relevant Intent There are issues that make the result useless for the user. Rating: Bad (User Intent) |
5.4 Distance | 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). |
| GL Sections | Explanation |
|---|---|
10.6.3 Chain Business with Location Modifier | 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. See “Starbucks san francisco”, “Aldi waco tx” and “Kate Spade New York” examples. 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 |
10.1 Specific address | [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. |