Asset 1 99
Asset 1 99
March 2025
1. Introduc+on ..............................................................................................................................................5
[Link] Rating Tool ....................................................................................................................................................................................................5
[Link] Work4low...............................................................................................................................................................................................11
[Link] Interface ................................................................................................................................................................................................13
[Link]-Level Navigational Result Question ............................................................................................14
[Link]-Level Rating Checkboxes...........................................................................................................14
[Link] Relevance Rating .......................................................................................................................15
[Link] Relevance Demotion Checkboxes..............................................................................................17
[Link] Accuracy........................................................................................................................................17
[Link]..............................................................................................................................................17
2. Understanding User Intent .......................................................................................................................18
[Link] Types .......................................................................................................................................................................................................18
[Link] Expectation............................................................................................................................22
[Link] Types .......................................................................................................................................................................................................22
[Link] Intent ..................................................................................................................................................................................................24
[Link] Location .....................................................................................................................................24
[Link] Location .....................................................................................................................................24
3. Ra+ng the Query-Level Naviga+onal Result Ques+on ...............................................................................25
4. Ra+ng Result-Level Issues ........................................................................................................................25
[Link] Name/Title in Unexpected Language or Script.....................................................................................................................26
[Link] of Business/POI Results..............................................................................................................27
[Link] of Address Results .........................................................................................................................30
[Link]/POI is Closed or Does not Exist .............................................................................................................................................30
[Link]/Does Not Exist vs. Inaccurate Name and Address ....................................................................31
[Link] Relevance of Closed/Non-Existing Business/POI ......................................................................31
[Link]/POI Status is PERMANENT_CLOSURE ................................................................................................................................31
[Link] Status Shown ...................................................................................................................................32
[Link] Shown as PERMANENT_CLOSURE .........................................................................................32
5. Relevance ................................................................................................................................................32
[Link]-Result Connection..............................................................................................................................................................................33
5.1.1. General Connection ..............................................................................................................................34
5.1.2. Abbreviation/Alternate Name Connection .............................................................................................34
5.1.3. Category Connection ...........................................................................................................................34
5.1.4. Spell Correction Connection .................................................................................................................35
5.1.5. Transit Intent Connection ......................................................................................................................35
5.1.6. Special Character Connection ..............................................................................................................35
5.1.7. Address-Result Connection ..................................................................................................................36
5.1.8. Lack of Connection ...............................................................................................................................36
5.2. Satisfying User Intent ....................................................................................................................................................................................38
[Link].........................................................................................................................................................................................................39
[Link] ................................................................................................................................................................................................................40
[Link] vs. Prominence ...............................................................................................................................................................................42
[Link] Possible Results ....................................................................................................................................................................................42
[Link] Possible Results.......................................................................................................................................................................................45
[Link] Possible Results and Greater Distance ..........................................................................................................................................46
[Link] Areas .........................................................................................................................................................................................................47
[Link] – User Intent Deviation ............................................................................................................................................................48
[Link] for User Inside and Outside Viewport ...................................................................................................................................49
[Link] Address Does Not Exist ................................................................................................................................................................51
[Link] vs. Municipality .....................................................................................................................................................................................52
[Link] Results ......................................................................................................................................................................................52
5.15. Multiple Transit POIs with the Same Name ......................................................................................................................................54
[Link] and Transit Intent ...............................................................................................................................................................................55
[Link] Queries ....................................................................................................................................56
[Link] vs. Stations ................................................................................................................................59
[Link] Intent .................................................................................................................................................................................................61
[Link]: Service-Level Mismatch ......................................................................................................................................................61
[Link] Relevance When the Result Status is PERMANENT_CLOSURE ...................................................................................64
[Link] PERMANENT_CLOSURE Status........................................................................................64
[Link].Expected PERMANENT_CLOSURE Status: Navigational Query......................................................................................................66
[Link].Expected PERMANENT_CLOSURE Status: All chains closed in area ............................................................................................68
[Link] PERMANENT_CLOSURE Status....................................................................................69
[Link].Unexpected PERMANENT_CLOSURE Status: Open Options are Nearby ....................................................................................70
6. Name and Category Accuracy ...................................................................................................................71
[Link] Not Applicable (n/a) .........................................................................................................................................................................71
[Link] Names .....................................................................................................................................................................................................72
6.2.1. Correct Name........................................................................................................................................72
6.2.2. Partially Correct Name..........................................................................................................................76
[Link]. Minor and Moderate Misspellings and Missing or Extra Words .....................................................................................................76
[Link]. Service-Level Mismatch ....................................................................................................................................................................................79
[Link]. Holding Name and Corporate Structure ....................................................................................................................................................79
6.2.3. Incorrect Name .....................................................................................................................................80
6.3 Result Category .................................................................................................................................................................................................83
6.3.1. Correct Category...................................................................................................................................83
6.3.2. Incorrect Category ................................................................................................................................84
6.4. Can’t Verify .........................................................................................................................................................................................................86
6.5 Transit Names ...................................................................................................................................................................................................86
6.6. Parking Names .................................................................................................................................................................................................87
6.7. Final Name and Category Accuracy Rating (Summary Table).....................................................................................................88
7. Address Accuracy: Components and Issues ..............................................................................................89
[Link] Components .....................................................................................................................................................................................89
[Link] Number........................................................................................................................................89
[Link]/Apt ..................................................................................................................................................91
[Link] Name...........................................................................................................................................92
[Link]-Locality and Administrative Subdivisions........................................................................................93
[Link]...................................................................................................................................................94
[Link] or State ......................................................................................................................................94
[Link] Code ...........................................................................................................................................95
[Link] ..................................................................................................................................................95
[Link] Does Not Exist .................................................................................................................................................................................96
[Link]/Script Issue in Address ............................................................................................................................................................96
[Link]-Speci4ic Issue ...................................................................................................................................................................................97
[Link]-Specific Issue vs. Correct with Formatting Issue .....................................................................97
[Link] Issue ..........................................................................................................................................................................................................97
[Link] with Formatting Issue ...................................................................................................................................................................98
[Link]’t Verify ..........................................................................................................................................................................................................98
[Link]’t Verify for Street Number ...............................................................................................................99
[Link]’t Verify for Street Name ..................................................................................................................99
8. Address Accuracy: Result Expecta+ons ...................................................................................................100
[Link]/POI Result ....................................................................................................................................................................................100
[Link]/POI Address Research and Resources................................................................................100
[Link] Official Addresses ..............................................................................................................101
[Link].Department Addresses ....................................................................................................................................................................................101
2
[Link].Result Missing the Street Address ..............................................................................................................................................................103
[Link].P.O. Box, Mailing Addresses, and Management Of4ices ......................................................................................................................104
[Link]/POI with Moving Locations ...............................................................................................105
[Link] ..................................................................................................................................................105
[Link] Type Results ..................................................................................................................................................................................106
[Link] Result.....................................................................................................................................106
[Link] Formats..................................................................................................................................106
[Link] Result ........................................................................................................................................107
[Link] Result......................................................................................................................................107
[Link] Code Result ..............................................................................................................................108
[Link]/Region/Territory Result ...............................................................................................................108
[Link] Result .....................................................................................................................................108
[Link] Without an Expected Address ..............................................................................................................................................108
[Link] Features ..................................................................................................................................108
[Link] Without an Expected Address .....................................................................................................110
[Link].Minimum Address Component ....................................................................................................................................................................110
[Link].Of4icial Address Present ..................................................................................................................................................................................111
[Link].No Of4icial Address ............................................................................................................................................................................................113
9. Pin Accuracy ..........................................................................................................................................115
[Link] Rating Options ........................................................................................................................................................................................115
[Link]..................................................................................................................................................115
[Link]. Does the available evidence indicate the result’s precise location? ............................................................................................116
[Link] .........................................................................................................................................116
[Link] Door .............................................................................................................................................117
9.1.4. Wrong..................................................................................................................................................117
9.1.5. Can’t Verify (Smallest Identified Area).................................................................................................118
9.2. Research Expectations ...............................................................................................................................................................................119
9.2.1. Research Resources...........................................................................................................................119
9.2.2. Best Available Evidence......................................................................................................................119
9.3. Boundaries of the Feature ........................................................................................................................................................................120
9.3.1. Half ’n Half and Tennis Rules..............................................................................................................121
9.3.2. Boundaries in Shared Spaces ............................................................................................................122
[Link]. No Next Door for Shared Spaces.................................................................................................................................................................124
9.3.3. Map View Layers ................................................................................................................................125
[Link]. Satellite Imagery vs. Vector Map ................................................................................................................................................................125
9.3.4. Pin Display Issues...............................................................................................................................126
[Link]. Leaning Buildings .............................................................................................................................................................................................126
[Link]. Pin Missing or Falls on 0,0.............................................................................................................................................................................129
[Link] Rooftop .................................................................................................................................................................................................129
[Link] Property with Multiple Buildings ........................................................................................143
[Link] Rooftops ..........................................................................................................................................................................................144
[Link]-Rooftop Rating .......................................................................................................................144
[Link] Rating ....................................................................................................................................151
[Link].Single-Complex Campus ..................................................................................................................................................................................154
[Link].Dispersed Campus .............................................................................................................................................................................................157
[Link] Without a Rooftop ......................................................................................................................................................................160
[Link] Features ..................................................................................................................................160
[Link] Divisions .......................................................................................................................163
[Link]..................................................................................................................................................164
[Link] Lots and Structures .....................................................................................................................................................................166
[Link] POIs .....................................................................................................................................................................................................167
[Link], Tram, and Streetcar Stops...........................................................................................................169
[Link] POI with Multiple Rooftops/Platforms ......................................................................................170
[Link] POIs with a Single Rooftop ......................................................................................................173
[Link] Transit Stations ..............................................................................................................173
3
[Link].How to Establish an Entrance Polygon .....................................................................................................................................................174
[Link].Examples ................................................................................................................................................................................................................175
[Link] to Rate Results ..............................................................................................................................179
10.1.Speci4ic Address ..........................................................................................................................................................................................179
[Link]-Speci4ic Address ................................................................................................................................................................................194
[Link] Address Does Not Exist ..............................................................................................................................................................202
[Link] of Interest ...........................................................................................................................................................................................204
10.5. Understanding Multiple Query Interpretations: Beyond Viewport and User Location ..............................................208
10.6. Business Queries........................................................................................................................................................................................211
10.6.1. Non-Chain Businesses .....................................................................................................................212
10.6.2. Chain Businesses .............................................................................................................................215
10.6.3. Chain Business With Location Modifier ............................................................................................219
[Link]. General Location Modi4ier ..........................................................................................................................................................................219
[Link]. Speci4ic Location Modi4ier ..........................................................................................................................................................................227
10.6.4. Back Office and Businesses with No Physical Location ...................................................................231
10.6.5. Business/POI Does Not Exist ..........................................................................................................233
[Link] Queries ........................................................................................................................................................................................234
[Link] for Distance with User Inside Viewport..............................................................................235
[Link] for Distance with User Outside Viewport ...........................................................................237
[Link] for Distance with Fewer Possible Results .........................................................................239
[Link] Queries and User Intent .....................................................................................................241
[Link] Queries and Prominence....................................................................................................242
[Link] Query with Location Modifier..............................................................................................242
[Link] Results for Category Queries........................................................................................244
[Link] Categories ................................................................................................................................248
[Link] Categories ..................................................................................................................................249
[Link] Query: Parking .................................................................................................................254
[Link] Results with PERMANENT_CLOSURE Status ...................................................................................................................258
[Link] PERMANENT_CLOSURE Status......................................................................................258
[Link] PERMANENT_CLOSURE Status..................................................................................259
[Link] Query Types .....................................................................................................................................................................................261
[Link] Queries .................................................................................................................................261
[Link] and “My Location” Queries ..............................................................................................263
[Link] Results .........................................................................................................................................................................................265
[Link] Ra+ng Tips ......................................................................................................................................273
[Link]’s the relevance when query is business/POI name and address and the result is only the address? .......273
[Link]’s the relevance when the query is a street name and the result is a single business on that street? ........273
[Link] do I know what the location intent is when user is outside/inside a fresh viewport?......................................274
[Link] do I know what the location intent is when user is outside/inside a stale viewport? ......................................275
[Link] full address result does not exist. How do I rate it? ...........................................................................................................275
Appendix: Release Survey ..........................................................................................................................277
4
1. Introduction
Welcome to Maps Search Evaluation. These guidelines will teach you how to use the evaluation tool
and rate Maps Search results.
For each task, you will be presented with a search query and the results that are provided to Maps
users. The goals of this task are:
• Search Relevance and Search 2.0: To determine how well the results satisfy the user’s
query (result relevance)
• Search 2.0 only: To check the data accuracy (name, address, and pin location) of the results
Note: Examples shown in this document reflected real locations at the time of creation. The
examples continue to demonstrate the rating principles described even if a business or point of
interest has changed.
This is the web-based rating tool used to rate Search 2.0 and Search Relevance queries.
5
Anatomy of the Tool
6
Name Screenshot Description
The query header shows:
Query: The term the user entered into the
search bar.
Viewport Age: How long ago the user
moved the viewport.
• A fresh viewport is indicated by the
word FRESH displayed in green
text.
Query Header • A stale viewport is indicated by the
word STALE displayed in red text.
Locale: The country and language
combination this query is for.
Country: Should match the country in the
Locale field. If it does not, defer to the
country found in the Locale field.
User Lat,Lng: The user’s location.
7
Name Screenshot Description
8
Name Screenshot Description
This device icon shows the center of the
user viewport at the time of the user
query. The purpose of the device icon is to
make it easier to find the user viewport. It
does not indicate the user's location.
9
Name Screenshot Description
Clicking any individual result or pin causes
a pop-up box to appear over the pin. The
text within the box may show additional
information and should only be used for
research purposes to help understand the
result:
Pop-up
Information • Phone number (for research only,
Box never call a business)
• URL
• Coordinates (latitude/longitude)
Copy to
Click to copy information to a clipboard
Clipboard
Drop
Location Pin
10
Name Screenshot Description
[Link] Workflow
Complete each step of the following workflow before you assign a rating.
Evaluate and rate each rating drop-down independently of the others. Rate result Relevance based
on whether the result fits the query intent, even if the result is closed or does not exist or has incorrect
Name, Address, or Pin data. If you are rating Search Relevance you will stop after you’ve rated result
relevance. If you are rating Search 2.0, you will continue by rating Name and Category Accuracy,
Address Accuracy, and Pin Accuracy individually.
Note: For any result in a Search 2.0 project, you may be asked to make all of the possible ratings,
some of them, just one, or none. This is expected and not a reason to escalate or release a task.
Rate each result on its own merits. Do not demote duplicate or very similar results.
11
12
1.3. Rating Interface
Your ratings and comments will be collected in the rating interface shown below. You will first answer
one top-level question about the query itself, then rate each individual result using the other
checkboxes and drop-downs.
13
1.3.1. Query-Level Navigational Result Question
You will answer a top-level question for each query to indicate whether there are any results in the
real world that would completely satisfy the user intent.
Answer to Query-Level
Query Explanation
Question
[Eiffel Tower] Yes There is only one result in the
real world that can completely
satisfy the user intent.
[Starbucks] No There is not only one result in
the real world that can satisfy
the intent of this query.
Note: If you are presented with a query that has no results, you must still answer this question and
submit your answer.
For each result, you will be presented with two high-level questions. These will allow you to highlight
any problems with the result.
High-level
Explanation Notes
question
Result is not in the language of the If you check this box, your rating for this
Result name/
query, the test locale, or the result result will be complete (all other questions
title is in
region (the expected languages) or is will be unavailable).
unexpected
in a mix of expected and unexpected
language or
languages (unless it is an official
script
company, chain, or brand name).
14
High-level
Explanation Notes
question
If you check this box, only the relevance
needs to be rated.
The relevance rating will take into consideration user intent as well as distance/prominence.
Relevance is always rated independently of any data (name/category, address, or pin) inaccuracies.
This means that when rating relevance we always assume that the result 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) while considering the missing one(s).
15
Relevance
Explanation Notes
Rating
16
1.3.4. Result Relevance Demotion Checkboxes
If you give a result a Relevance rating of Good or below, you will be presented with two checkboxes.
Use them to select the reason(s) for your rating:
If you are rating Search 2.0, once you've rated relevance, you’ll evaluate three result components for
data accuracy: Name, Address, and Pin.
1.3.6. Comments
Comments are mandatory for any result relevance rating of Good or below and for any data issues
not rated Correct/Perfect and should explain the reasons for all rating demotions. Be sure to:
• Include user intent: Indicate what you think the user intent is.
• Refer to the guidelines: If the demotion is due to a guideline instruction, note the guideline
section you used to make your decision.
• Include sources: If you find incorrect information in a result, your comment should include
the correct information and its source. Be sure that any links you include lead directly to the
information you provide. If they don’t, include a link to the source you used and explain how to
get to the information from there.
• Use URL shorteners when inserting long links into your comments
• Be concise: Don’t write elaborate comments. Be short and specific.
• Comment in English: Your comments will sometimes be reviewed or used by people who
are not familiar with your test locale or its language. Comments in English can be understood
by the widest possible audience.
17
Issue Expectations Example Rating and Comment
The comment should explain the Relevance -> Good (Distance/
reasoning behind your rating. A demotion Prominence)
Relevance may be due to distance from the user’s Comment: Demoted -1 for a few closer
Demotions location compared to similar results/ real world locations in the Middletown/
potential results, secondary intent, or Anchorage area
other reasons.
Address Accuracy -> Incorrect — Street
Number
Include a comment when you rate a
Comment: Correct street number is: 332
Name, Address, or Pin something other
W El Camino Real, Sunnyvale, CA 94087
than Correct or Perfect or you give a
Data Issues as found on the official site: https://
rating of Closed/Does not Exist or
[Link]/locations/sunnyvale
Unexpected Language.
Pin Accuracy -> Wrong
Comment: Wrong pin: correct location is:
52.368067, 4.895389
• User location
• User viewport
• Viewport age
User intent refers to the interaction between query, user location, user viewport, and viewport age.
The queries you are evaluating are real queries submitted by users. Because they are real, they can:
• Be misspelled
• Contain mistakes
• Be inconsistent
• Be ambiguous
• Be badly formatted
• Be, or contain, emojis
• Have no maps intent
The first step in the rating process is to make sure you understand the query.
If you see a foreign-language query, do not release the survey. Research the query or use an
online translation tool to find out what it means, then rate it as usual.
18
You will see several types of queries, including:
Address queries
Address queries contain all or part of a complete address, including street number, street name,
locality, state, country, and postal code.
Query Explanation
[717 E El Camino
This is an address query in the form of a full address. It contains a street
Real, Sunnyvale,
number, street name, locality, state and postal code.
CA 94087]
[Stevens Creek
This is an address query for a street. The user is looking for the location of
Blvd, Cupertino
this particular street.
CA]
This is an address query for a country. The user is looking for the location of
[Ireland]
the country of Ireland.
This ambiguous query could refer to New York city or New York state. You
[New York] will find more information on prominence, user location, and the viewport in
the following sections to help you determine the intent of this query.
A point of interest (POI) is a location that people find interesting or useful. POIs can be locally or
internationally known. These guidelines use a very broad definition of POI in which businesses are
also considered POIs.
Query Explanation
[London Bridge] This is a query for a famous POI in London.
[Danube River] This is a query for a river in Europe.
[Charing Cross
This is a query for a transit station in London.
Station]
[Union Square, SF] This is a query for a location in San Francisco.
19
Business queries
Query Explanation
This is a business query with a location modifier (Palo Alto). The user is
[Zola Palo alto] looking for a specific restaurant (Zola) in Palo Alto, CA. Queries can include
location modifiers, like city names, that make them more specific.
This is a business query with a request for a specific store in Sunnyvale, CA.
[Bookasaurus] The viewport and user location can help pinpoint the desired location for
such a query.
[Starbucks, 7 This is a query for a chain business followed by a specific address. Chain
Boulevard businesses are businesses that have more than one location, and include
Poissonnière, everything from national chains, like Starbucks, down to small local chains,
75002 Paris, like Burrito Boyz. Target, Auchan, Albert Heijn, and Boots are all chain
France] businesses.
This is a business query with a request for the chain business Target and
[Target sunnyvale]
location modifier of Sunnyvale, CA.
Category queries
Query Explanation
This query is for locations where fast food is served. Assume the user
[fast fod] wanted the correct version of the query when the query contains a simple
misspelling.
[bus stop] This query requests the locations of bus stops.
[coffee shops] This query requests the locations of businesses that sell coffee.
[gym] This query requests the locations of fitness centers.
[gas San This query requests the locations of gas stations with a location modifier of
Francisco] San Francisco.
A product or service query is a query about something that can be purchased at or is offered by a
business or POI. When researching results for these queries, be sure to confirm that the result
actually offers the product or service in a way that would be meaningful or helpful to a user with this
query.
For instance if a user had the query [salads], a steakhouse with one salad on its menu, would not be
20
very helpful, but the American restaurant Sweetgreen, which specializes in salads, would be.
Query Explanation
This query requests the locations of businesses that sell a specific type of
[vanilla latte]
coffee drink.
[deep-tissue This query requests the locations of businesses that offer a unique style of
massage ] massage.
This query requests the locations of businesses that sell pencil, pens,
[school supplies]
notebooks, and everything else students need for school.
This query requests the locations of businesses that offer truck tire repair
[truck tire repair]
services.
This query requests the locations of businesses where ATV tours are
[ATV tours]
available.
Not every hair salon offers perms, but this query requests the locations of
[perms]
ones that do.
[deep dish pizza This query requests the locations of places that sell a specific type of pizza
detroit] in a particular city.
Some queries are simply a set of coordinates or the words ”my location” (or something similar).
Query Explanation
[36.082857,
The user has specified a location using lat/long coordinates.
-115.172916]
[my location] The user has typed these (or similar) words to find out where they are.
Emoji Queries
Some queries are not made using words. Emojis represent the category they picture. Use the most
literal meaning.
Query Explanation
21
Query Explanation
Some queries have no maps intent. They include, but are not limited to, queries that:
Query Explanation
[eureka temperature] This is a weather query with no maps intent. Rate all results Bad.
22
Result Type Explanation Example
Businesses and POI type results
will show a name in the top field,
followed by an address and a
Business/POI
category. The same rating rules will
apply to both Business and POI
results.
These results can be one of
multiple address types, including
residential address or locality.
Instead of a business or POI name,
this kind of result will show the first
line of the address in the top field,
followed by the entire address
Address below. This type of result will not
include a category.
23
2.3. Location Intent
A result is considered most relevant when it is located in the user’s area of expected results. There
are two types of Location Intent:
• Explicit: The query is made clearly and indicates a specific location or area where results are
expected.
• Implicit: The location expectation is not as clear, so you must use context clues, in the form
of user location and viewport, to discover the area in which the user is expecting results.
When there is an explicit location mentioned in the query, you can ignore the user and viewport
locations. The user has told you exactly where they want to find results.
If the user’s location intent is not expressly stated in the query, for example [chinese] or [479
margarita ave], use the user location, viewport location, and viewport age to determine the area of
expected results.
24
Viewport User Location Location Intent
Results are expected in or near the viewport area. All relevant
results inside the viewport are eligible for a rating of
Fresh Outside Viewport
Excellent. If no results can be found in or near the viewport,
consider the user location a secondary location intent.
Missing When the user is missing, the viewport is the location intent.
Inside Viewport
When the viewport is stale, consider only the user location as
Outside Viewport location intent.
Stale
Use the stale viewport as location intent when the user
Missing
location is missing.
Viewport Age Present or
Consider the viewport fresh when the viewport age is missing.
Missing Missing
The user location sets the location intent when the viewport is
Present
not present.
Missing entirely When the user location and viewport are missing, the test
Missing locale becomes the location intent with a strong focus on
prominent results.
You will answer this question before you rate any results, since you don’t need to know what the
results are in order to learn if there’s a real-world result that could fully satisfy the user’s intent:
You will answer this question once for each query, whether or not any results are shown.
Below Left: Result name is Walmart Supercenter (in yellow box), address details are below (in green box).
Below Right: Result is an address, so the first line of the address appears in the yellow box as the Address title. All the
address details appear below it in the green box.
When all or part of a result name or title is in an unexpected language or script, users will not
understand it. In these cases, select the Result name/title is in unexpected language or script
checkbox. No further rating will be required.
Note: When the address details, found below the name/title, are in an unexpected language or script,
the result can still be understood and rated for relevance and name accuracy. For more on what to do
when the address details (not the name or title) are in an unexpected language or script, see
Language/Script Issue in Address.
Don’t consider minor spelling issues, such as missing or added diacritics (e instead of é), as
Unexpected Language/Script. This also applies to unnecessary or less relevant parts of a name or
title. Use this checkbox only to report issues that interfere with understanding the name/title and
issues listed in your Country Specific guidelines.
26
4.1.1. Name of Business/POI Results
Pay special attention to the language and script of brand and chain names. See your Country
Specific guidelines for more information.
27
Expected Language Explanation Example
The language of the test locale Expected language/script:
is generally considered an • Test locale: es_ES
expected language and script. • Result in California, USA
• Query: [college]
If the query is so short that the • Result name: Colegio Skyline
language cannot be identified,
assume that the query language The result name is in Spanish, which
is that of the test locale. matches the language of the test locale,
so this result title is expected and
Test Locale
When the test locale and the acceptable.
and
query locale differ, consider the
Query Locale
query locale an expected Unexpected language/script:
language, as it provides more • Test locale: en_US
detailed information. • Result in California, USA
In the example below, the • Query: [college]
Query Locale is set to English in • Result name: Colegio Skyline
Indonesia. Therefore English is
an expected language: “Colegio” is in Spanish, but the test locale
• Query Locale: en_ID is in English, so the result title is in an
• Test Locale: id_ID unexpected language.
Expected language/script:
• Test locale: en_US
• Result in Rio de Janeiro, BR
• Query: [beach]
• Result name: Praia de Copacabana
Result satisfies the category “beach” and
the result’s name is in Latin script and the
Portuguese language, which is the
language of Brazil.
The language/script of the
Result region result’s region is expected as
Unexpected language/script:
the result language. • Test locale: en_US
• Result in Rio, BR
• Query: [beach]
• Result name: Playa de Copacabana
Though the result name is in the same
script as the test locale and query
language, returning the name in Spanish
is unexpected language because the
language of Brazil is Portuguese.
28
Expected Language Explanation Example
Expected language/script:
• Test locale: ar_SA
• Result in Riyadh, SA
• Query: []ماكدونالدز
• Result name: McDonald's
29
4.1.2. Title of Address Results
Unlike business/POI results, address results do not have an actual name. Instead, the first line of the
address appears as the title. Rate Result name/title is in unexpected Language or Script when
the title (first line of the address) is in an unexpected language or script.
Address results often cannot be translated and are accepted in the original version of the result
location. Some features, however, are translated into the test locale’s language, especially for
bilingual or English-speaking areas. Although the preferred language is the test locale’s language, the
query language and language of the result’s location are also accepted.
• City
• State
• Country
Appropriate localization depends on the result itself and the language it is translated into. Research
and local knowledge will help you decide if the translation has been done appropriately.
Use the Address Accuracy Incorrect – Language/Script Issue checkbox if you find issues of this
nature in any of the address components in the address details (not the address title) of any result.
Use this checkbox when, after careful research you determine that a result is:
• Closed/non-existent
• Randomly moving (like a food truck without a fixed schedule)
• A non-recurring past event with no further significance that does not carry any maps intent
Important: If you rate a result as Business/POI is closed or does not exist, you must still give a
relevance rating as if the place were open or did exist.
Remember, this rating can only be applied to business or POI results, not to address type results.
30
Use this checkbox to indicate a POI has closed only if there is evidence to prove the business
indicated in the result is no longer operational.
When you can’t make a decision about business closure due to lack of resources, assume the
business could exist and rate the name, address, and pin accuracy as Can’t Verify (unless there is
an obvious data issue like a missing mandatory address component or a pin in the ocean).
Note: Businesses and POIs can close for construction, remodeling, vacations, or other reasons.
Treat all temporarily closed businesses as if they were open when the closure is announced
on the business/POI webpage or managed social media page. There is no limit to how long the
closure can be.
It is important to understand what the result really is before making your rating. If your research
reveals that the business has an incorrect name or address, use the drop-down rating options to
signal precisely what is wrong. Use the Business/POI is closed or does not exist checkbox only for
the specified purposes. See Unclear Results for more guidance and examples.
Never automatically demote to Bad simply because of closure. (You may find other reasons to
demote to Bad, but closure should not be the sole reason for the demotion.)
Note: No matter what is displayed in the status section of the tool, you must always research the
business/POI to determine whether it is open or not.
This chart shows the possible combinations of status displayed in TryRating plus a result’s actual
state based on your research.
31
Real-World State Confirmed by
TryRating Status Comments
Research
Rate relevance based on
Closed/Does not Exist PERMANENT_CLOSURE whether result is expected/
unexpected. See 5.19.
Rate relevance based on
Open/Exists PERMANENT_CLOSURE whether result is expected/
unexpected. See 5.19.
When no result status shown or the status is blank, you must research to determine whether the
business/POI is open or closed/does not exist in the real world. Use the Business/POI is closed or
does not exist checkbox when needed.
Rate the result relevance as if the business/POI were open or did exist. Use your best judgement to
determine how well the result satisfies user intent within the area of expected results.
When the result status is PERMANENT_CLOSURE, follow the research steps to determine if the
business in fact is open in real world or not, and use the Business/POI is closed or does not exist
checkbox when needed.
The relevance rating for a result with PERMANENT_CLOSURE status depends on whether this result
is expected or unexpected based on the specific relevance guidance in 5.19. Rating Relevance when
Status is set to PERMANENT_CLOSURE and 10.8. Permanently Closed Results
5. Relevance
Relevance for each result is found by assessing the relationship between:
Complete each step of this workflow before assigning your relevance rating.
• Rate each result individually and demote based on relevance and distance.
• 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).
• Ignore the order of the results and evaluate each one individually.
• Ignore duplicate results and rate them individually. Do not demote for repetition.
• If there are results that are extremely inappropriate or illegal, rate Bad. Identify such content
by determining if the result is likely to be embarrassing if seen by users.
32
Rate the relevance of each result without considering the accuracy of the name/category,
address, or pin.
When judging distance/prominence, ignore closed or nonexistent results.
Adult Content
For a result to satisfy a query to any degree, there must be some kind of relationship between them.
Your first task is to understand what this connection is.
Satisfying the user intent is only the first step in the rating process and covers the minimum
requirements for a result to be considered relevant.
33
5.1.1. General Connection
A result can satisfy user intent for multiple reasons, but most often the result satisfies the most
specific part of the query’s intent. This kind of relationship between query and result is called a
General Connection.
Type of
User Query Result Description
Connection
Satisfies Intent: Users are likely to start their
San Francisco search with the name of the brand “Marriott”.
[marriot] Marriott Union General Result satisfies user intent by providing a
Square Marriott close to a user/viewport located in the
San Francisco area.
Satisfies Intent: The user is looking for an
[Houston George Bush
General airport in the city of Houston. This is an airport in
airport] Intercontinental
Houston, which satisfies user intent.
Satisfies Intent: The query contains two
[london, different cities, so it’s likely a routing query.
London General
brighton] Returning either of the individual results is
expected and should be rated Excellent.
The query is an abbreviation or alternate name and the result provides the full and currently accurate
name.
Type of
User Query Result Description
Connection
Newark Liberty
Satisfies Intent: The international airport code
[ewr] International Abbreviation
for Newark Liberty International Airport is EWR.
Airport
Alternate Satisfies Intent: The result is the correct name
[sears tower] Willis Tower
Name of what was formerly known as the Sears Tower.
The query is a category and the result satisfies that specific category, which may or may not be
displayed within the information provided in the result.
Type of
User Query Result Description
Connection
Satisfies Intent: A category search for "food" in
[food] La Ciccia Category a viewport over San Francisco returns an Italian
restaurant there.
34
5.1.4. Spell Correction Connection
The query is misspelled and the result corrects that issue. This kind of connection only applies to
obvious issues when no result for the actual query exists at the user’s location or when the user intent
is clearly satisfied by the spell-corrected results.
This kind of correction also happens when a query address does not exist but the result address
does, correcting the issue and creating a match.
Type of
User Query Result Description
Connection
Spell Satisfies Intent: The result corrects the user's
[aple store] apple store
Correction spelling mistake.
Satisfies Intent: This query suggestion for the
Spell
Lodz Łódź Polish market adds the diacritics the user may
Correction
have missed when typing the query.
Satisfies Intent: When there is no "Clair St"
[23 Clair 23 Clair Spell within or around the viewport/user, consider a
street] Boulevard Correction “Clair Boulevard" that is close to the viewport/
user as the most likely intent.
The result satisfies the transit intent of the query. If the query indicates a specific transit system, the
result must match that system. There is also a transit intent connection when a station provides
access to more than one transit service and the queried one is included.
Type of
User Query Result Description
Connection
Satisfies Intent: Result satisfies user intent by
Richmond Transit providing a close station that runs the requested
[bart]
BART Station Intent transit service for a user/viewport located in the
Richmond area.
Always consider the specific language conventions. In general, user intent is satisfied when:
• The query contains a special character and the result is a valid variation (if applicable).
• The query does not include a special character but the result with special characters adds
value to the user and is therefore considered spell corrected.
• The country or language does not have the special character and it is generally perceived as
a form of expression or style (like “café” in English).
35
Type of
User Query Result Description
Connection
Satisfies Intent: "oe" is a valid variation for the
Special
[möllersdorf] Moellersdorf special character "ö" in the country/language of
Characters
the result (Germany/German).
When a query address and a result address are not exactly the same, the kind of connection they
have depends on their relationship:
• Street number is the same in both query and result but the unit number is different or missing:
• If neither address is a street extension, rate result relevance Good when:
▪ The query contains a unit number and the result does not.
▪ The result contains a unit number and the query does not.
▪ The query contains one unit number and the result contains another.
• The query is full address including street number and name and the result is the street name
only:
• Since this result is an unlikely secondary intent, rate relevance as Acceptable.
• Query is for a street [Main Street, Pleasanton, CA] result is just the locality (Pleasanton, CA).
• Rate the result relevance Bad as it does not satisfy the user intent.
Type of
User Query Result Description
Connection
357 Western
Satisfies Intent: The result does not include
[357 western Ave
Address the unit number requested in the query so its
ave suite 1] St. Johnsbury,
relevance is rated Good.
VT
357 Western Satisfies Intent: The result has the same
[357 western Ave Suite 2 street number but a different unit number from
Address
ave suite 1] St. Johnsbury, the address in the query, so its relevance is
VT rated Good.
Satisfies Intent: Instead of returning the full
Western Ave address requested, the result provides only the
[357 western
St. Johnsbury, Address street name. This is an unlikely secondary
ave suite 1]
VT intent, so relevance is demoted to an initial
rating of Acceptable.
Does not satisfy user intent: Instead of
[357 western
St. Johnsbury, returning the full address requested, the result
ave st. Address
VT provides only the locality. This does not satisfy
johnsbury]
the user intent, so relevance is rated Bad.
If the result does not satisfy the user intent either because there is no relationship between the query
intent and the result or because the connection between the query intent and result will not be
immediately obvious to the user, rate the result relevance Bad.
36
Type of
User Query Result Connectio Description
n
Santa Cruz Does not satisfy user intent: Research
[airport] Boardwalk None shows that there is no connection between the
Santa Cruz query and the result. Rate Bad.
Does not satisfy user intent: Result is for the
[Raging Waters
2333 South correct address, but does not include the
2333 South White
White Rd None business named in the query, so users will
Rd
San Jose have no way of knowing if this is truly
San Jose]
connected to the business or not. Rate Bad.
Does not satisfy user intent: Query is the
name of a business and result is for the
2333 South correct address, but does not include the
[Raging Waters] White Rd None business name. Users will have no way of
San Jose knowing whether or not this address is
connected to the business they asked for.
Rate Bad.
Does not satisfy user intent: Result is for a
Macy’s
store, not a mall. This store is inside the
2801 Stevens
[valley fair mall] None requested mall, but does not satisfy the intent
Creek Blvd,
of the query, which is the whole mall.
Santa Clara
Rate Bad.
Westfield Does not satisfy user intent: Result is for a
Valley Fair mall, not a store. This mall contains the
[macy’s] 2855 Stevens None requested store, but this result is the whole
Creek Blvd, mall, not the single store the user asked for.
Santa Clara Rate Bad.
Does not satisfy user intent: Result is for a
Costco
Costco gas station, not a Costco store. The
Gasoline
store and the station are at the same address
[costco] 1601 Coleman None
and share a brand name, but the result is not
Ave, Santa
what the user asked for and does not satisfy
Clara
the query intent. Rate Bad.
Does not satisfy user intent: Result is for a
Costco Costco store, not a Costco gas station. The
1601 store and the station are at the same address
[costco gas] None
Coleman Ave, and share a brand name, but the result is not
Santa Clara what the user asked for and does not satisfy
the query intent. Rate Bad.
37
5.2. Satisfying User Intent
The user’s intent can be determined by considering the query, the user’s location/viewport, and your
local knowledge. Sometimes queries are ambiguous or can have multiple interpretations.
In order to determine a query’s primary and secondary intent, look at the relationship between the
query and the result. Ask yourself:
For any Relevance Rating of Good or below, you must select the appropriate check box(es) to
indicate the reason(s)for demotion: User Intent and/or Distance/Prominence. If both reasons apply,
use both checkboxes.
Satisfying the user intent is only the first step in the rating process and covers the minimum
requirements for a result to be considered relevant. The rating determined by deciding how well
intent is met is called the Initial Rating. Distance and prominence will be considered next in order
to establish the final rating.
38
5.3. Prominence
Once you’ve made an initial rating by establishing that there is a relationship between the query and
the result and determining the intent type, consider the result’s prominence.
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 how to establish prominence, ordered from the most
prominent to the least prominent:
A result that may not directly appear to be user intent can be promoted for being internationally
prominent.
Relevance Navigational
39
Query Result Rating and Explanation
Agra
Uttar Pradesh, India Query is for a small locality in India and the result
satisfies the user intent.
Relevance Navigational
Japan The country of Japan is clearly the user’s
primary intent.
[japan]
Relevance Bad (User Intent)
(User is in
Seattle) Sarku Japan
401 NE Northgate Way A chain restaurant with “Japan” in its name does
Seattle, WA 98125 not satisfy the query’s primary intent (the country
of Japan) or any secondary intent (entities with
international prominence).
[Link]
Generally, the farther away the result is from the area of expected results, the less desirable it
becomes. This is especially true for queries highly driven by distance to the user/viewport, such as
chain businesses, hospitals, pharmacies, or grocery stores.
Because the user can be offered many possible results that are all very similar, the closest entities
providing the expected service can be considered the best options. Results which are farther away
are less relevant and should be demoted according to their additional distance. Defining what is close
and what is far depends on the context of each individual query. Factors affecting distance include:
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.
40
Viewport Location Intent (see section 2.3.2)
When the user is within a fresh viewport, the user’s location should be
used as the location intent. All ratings made should be based on the
user’s location. Results inside the fresh viewport may be demoted
based on distance to the user but they cannot be demoted by 3 (to
Bad) for distance alone.
Note: Consider the viewport fresh when the viewport age is missing.
When the user is outside the fresh viewport, the fresh viewport should
be used as the location intent. All ratings should be based on the fresh
viewport’s location and any results within the fresh viewport receive
No demotion for distance.
Note: If no results can be found in or near the viewport, use the user
location as a secondary location intent.
Note: If the user is missing, use the stale viewport as location intent.
Stale Viewport
41
Do not demote a result for distance when:
• This is the closest possible result, even if it is far away from the area of expected results.
• Other, closer results are found to be closed or non-existent.
Once you’ve decided how relevant the result is based on user intent, consider the result in the context
of all possible results in the real world. Use the distance to the user or viewport and the prominence
of the result to decide if a demotion should be applied.
A result’s fit to user intent, prominence, and distance should all be relative to the query and the
context around the query. Before deciding whether to demote because of prominence or distance, it’s
important to look at:
The following examples of multiple query/result pairs will demonstrate how to interpret the relationship
between distance, prominence, and satisfying the user’s intent. The examples address common
rating situations and explain how to evaluate the relevance of the results.
Some queries, like [starbucks], have many results that could satisfy the user. In cases like this,
distance is more important than prominence, so results that are closer to the user’s location/viewport
should be rated higher than results that are farther away. To illustrate the high density of Starbucks,
possible results are shown as purple dots.
42
User Inside Fresh Viewport
When the user is inside the viewport, consider all possible results, including real-world results not
returned for rating (purple dots), and demote by distance from the user.
Relevance Excellent
➄ Starbucks
140 Mason
Rate Excellent for Starbucks locations that are in
Street
close proximity to the user, even if they are
outside the viewport.
43
User Outside Fresh Viewport
When a user is outside the viewport, results are expected in or near the viewport. In cases where
there are a large number of possible results inside the viewport, even if they are not returned for
rating (purple dots), rate Bad for those outside it.
Relevance Excellent
Starbucks
865 Market Rate any Starbucks within the fresh viewport
Street Excellent when the user is outside the viewport.
[starbucks]
Relevance Excellent
User in Alameda with fresh Starbucks
viewport in San Francisco, CA 170 O’Farrell
St Rate any Starbucks within the fresh viewport
Excellent when the user is outside the viewport.
Relevance Excellent
Starbucks
264 Kearny St Rate any Starbucks within the fresh viewport
Excellent when the user is outside the viewport.
44
5.7. Few Possible Results
When the query has only a few results in the real world, be more lenient when considering distance.
Because there are only a few Zara clothing stores in Miami, results for the query [zara] are demoted
more leniently for distance than the many Starbucks locations in the example above.
Acceptable (Distance/
Relevance
Prominence)
Zara
7535 N Kendall
Dr, Miami The Zara store is located significantly further
away than the second closest stores and is
therefore rated Acceptable.
45
5.8. Few Possible Results and Greater Distance
Leniency on distance is acceptable when there are only a few possible results for the query in the
requested area. For example, a user close to Berlin queries for [Wartestraße], which is a street
name. There are only four streets in Germany called “Wartestraße” that can satisfy the user’s intent
and all four streets are returned as results. Because of the limited number of results, each result’s
relevance remains fairly high even over longer distances.
User and
➀ Wartestraße, Wartestraße in Gransee is the closest to the
Gransee user and viewport and is therefore the most
fresh viewport close to Berlin,
Germany relevant.
Relevance Good (Distance/Prominence)
➁ Wartestraße, Wartestraße in Siegen is far away from the
Siegen user, but is the second closest possible result.
46
5.9. Rural Areas
Results are often farther away in rural areas, but can still be considered relevant if there are no
reasonable results close to or within the fresh viewport. In a rural area, generosity can be applied to
ratings with respect to distance. The criteria for rating are similar to the [zara] example in the Few
possible results section, but with an emphasis on distance. Here is an example for the query
[american legion] in North Dakota.
Relevance Acceptable
Relevance Acceptable
47
5.10. Location – User Intent Deviation
When the location intent and user intent do not allow for a clear result (because either the user or
viewport are in an atypical location, like the middle of the ocean), rate with a focus on high
prominence. For example, the query [Hong Kong] in a test locale set to en_US with the viewport and
user location around Naples, Italy. There is no real change in rating if the user is inside or outside of
the viewport, or if the viewport is fresh or stale.
48
5.11. Rating for User Inside and Outside Viewport
The following two examples show the differences in rating when a user is inside and outside a fresh
viewport. The query is for a chain business called Great Wolf Lodge found across the United States.
The examples show all possible results within and around the large viewport.
In general, when the user is outside the fresh viewport, no result within the viewport is demoted for
distance. The only exception to this is when the viewport is large enough to include an unusually
large area, like an entire continent, and the results within it would not realistically be useful or
interesting to a user with this query.
(Note that even though the viewport in the example below is large, because of the limited number of
Great Wolf Lodges with it, the results still might be useful or interesting to a user with this query.)
49
When the user is inside the fresh viewport, the user's location is used as location intent and results
are demoted for distance.
50
5.12. Partial Address Does Not Exist
Relevance is always rated independently of any data (name, address, or pin accuracy) issues the
result may have. This includes results for addresses that do not exist in real life.
When judging distance for existing addresses do not factor in any returned non-existent addresses.
Evaluate distance separately for existent and non-existent addresses. Do not demote existing
address results when closer, non-existent addresses are returned.
For example, a user in Half Moon Bay, CA is looking for [2373 chestnut] and is presented with three
residential addresses. The address in San Francisco is the only one that actually exists. The results in
Oakland and Redwood City are not supported by the postal authorities and no evidence can be found
that the addresses in either city exist.
Note: For cases where the query is a unique full address that does not exist and the result matches
the query, see Query Address does not Exist.
Relevance Excellent
Relevance Good/Acceptable
(Distance/Prominence)
51
5.13. City vs. Municipality
In many cases, a city and a state/county/municipality (or other similar market-specific components)
have the same name, but the city is typically more prominent. In this case, the chances that a user is
looking for the state/county/municipality and not the city, are very small, but still a possibility.
Therefore, states, counties, and municipalities will be treated as a secondary intent and given an
initial rating of Good. Consider the relationship between the city and the municipality in terms of their
locale and adjust if necessary. On the other hand, if the query specifically requests the state/county/
municipality, that result’s relevance should be rated as Navigational and the city should be rated
Bad.
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?
52
• Prominence of the feature
• Transit intent
Promoting for prominence should only occur for internationally prominent POIs.
In the examples below, two ratings are provided for some results: Good and Acceptable. The
difference between the two ratings rests in how well the result satisfies user intent. Choose Good if
there is a strong likelihood that it will satisfy user intent and Acceptable if it is less likely to satisfy.
Relevance Navigational
[soho]
Soho
User and viewport in London, UK Query is for a neighborhood in London and the
London, UK result satisfies the user intent.
Mildreds Restaurant
45 Lexington St, Carnaby, Result is for a specific restaurant in Soho. It is
London W1F 9AN, UK very unlikely to satisfy the user intent.
Happy Lamb Hot Pot The query is for a street and the result is a
[stevens creek
blvd cupertino] 19062 Stevens Creek Blvd, specific business on that street. This specific
Cupertino, CA, 95014 result is unlikely to satisfy the broad intent of the
User and fresh
query.
viewport in Relevance Bad (User Intent)
Cupertino, CA 19062 Stevens Creek
Blvd The result includes a street number when the
Cupertino, CA, 95014 query is for a street, making this result too
specific for the more general query.
53
Query Result Rating and Explanation
[The Slanted Relevance Bad (User Intent)
Door
One Ferry Building #3
One Ferry Result is for the address and not the business
One Ferry Building #3 San
Building #3 requested in the query, so it does not satisfy the
Francisco, CA 94111
San Francisco, user intent.
California 94111]
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.
54
Query Result Rating and Explanation
Lufthansa Basis The result is for a small bus stop that seems to
22335 Hamburg, Germany service the Lufthansa training center. The result
does not share the same name as the queried
transit. Therefore, the result is not relevant.
Relevance Navigational
The query is for a unique transit station. The
Embarcadero Station result (a unique BART station) fully satisfies the
[Embarcadero
San Francisco, CA user’s intent.
Station]
Acceptable (User Intent &
User and fresh Relevance
Distance/Prominence)
viewport in San Jose,
CA Ferry Building & The result (a historic streetcar) name includes
Embarcadero Station the queried station name, but has low
San Francisco, CA prominence, given that there is a unique
Embarcadero Station. Therefore, the result
should be demoted based on user intent.
A non-transit POI can be associated with a transit POI with the same name. You can establish the
relationship between the two entities by using local knowledge, researching prominence, and
understanding how well the result satisfies user intent. This way you will learn whether the query has
a distinct navigational intent or if the prominence of the two POIs that share a similar name is so
strong that both can be the intent.
55
Query Result Rating and Explanation
Good/Acceptable
Mall of America Relevance (User Intent &
Station Distance/Prominence)
8240 24th Ave S
Minneapolis, MN 55425 Even though the station has the same name as
United States the POI, it is not prominent and therefore
demoted.
Relevance Excellent
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 (see [12th st
oakland bart] example below). If a result is promoted to Navigational, other results that could
potentially satisfy the user intent should be demoted further for distance and prominence (see [BART
daly city] and [stockport station] examples below). In general, the fewer the results that satisfy the
user intent, the farther away the results can be and still be considered relevant. The more available
results that can satisfy the user intent, the closer they need to be.
56
Query Result Rating and Explanation
Relevance Navigational
Daly City Station The query intent is for a BART station in Daly City.
Daly City, CA Research shows that there is only one BART station
in Daly City and its name is Daly City Station, so
this result fully satisfies the user’s intent.
Relevance Good (Distance/Prominence)
San Francisco
International Airport
Station The query intent is for a BART station in Daly City.
San Francisco This result fits intent as it is a BART station. This
International Airport, station is in a neighboring locality, but is farther
CA away than the Colma station and is demoted due to
distance.
57
Query Result Rating and Explanation
Relevance Navigational
Relevance Excellent
San Jose Diridon
Station
[san jose station] San Jose, CA The query intent is for a station in San Jose. There
are several stations in San Jose, but no stations with
User and viewport in a name that matches the query exactly, so we should
California rate every station within the queried locality equally.
Tamien Station There are two stations that match the user’s intent,
San Jose, CA so both results should be rated Excellent.
58
Query Result Rating and Explanation
Relevance Acceptable (Distance/Prominence)
This station is just outside of the requested locality, in
Sunnyvale Caltrain a neighboring locality. Even though the station is
Station outside of the requested locality, it provides a choice
Sunnyvale, CA of stations in the area for the user. The fewer choices
there are available, the farther away the results can
be and still be relevant.
Relevance Bad (Distance/Prominence)
Palo Alto Train Result is far from the queried station. The farther
Station away the result is from the queried station, the less
Palo Alto, CA likely it is that it will be considered relevant, so the
relevance rating should be lowered.
A transit stop is a location typically designated by a bench or covered waiting area, a posted sign, or
street markings. Transit stations, on the other hand, are typically larger areas associated with major
structures including, but not limited to, platforms, ticketing offices, enclosed waiting/seating areas, or
terminal buildings/structures encompassing the transit area. The term “station” is primarily used to
refer to transit locations that are larger and typically a terminal housing multiple routes. All stations
are stops, but not all stops are stations.
Since all stations are stops, but not all stops are stations, returning a station for a stop query is ok, but
returning a stop when the query is station should result in a rating of Bad with the User Intent
checkbox selected. Try to identify these corresponding terms in the test locale and understand the
relationship between them.
For the category [bus stops], relevance should be based mainly on distance from the user location
or fresh viewport and the physical size of the bus stop. If the result is a small bus stop in a rural area
and the bus stop is among the closest ones to the user’s location intent, it should be rated Excellent.
On the other hand, if the result is a large bus hub that is a bit farther away from the user, it should still
receive an Excellent because of its size, regardless of the fact that there are closer, smaller bus
stops. Results close to the user should not be demoted because there is a larger bus stop farther
away, instead, the large bus stop should be promoted because of its importance.
59
Query Result Rating and Explanation
Relevance Excellent
Greyhound Lines
200 Folsom St This is a major bus station in San Francisco
San Francisco, CA 94105 where a user can take Greyhound buses.
Relevance Excellent
Chicago Bus Station
630 W Harrison St The query intent is for a bus stop. This result is
Chicago, IL 60607 a Greyhound station, which fully satisfies the
user's intent. This result is close to the user.
Relevance Excellent
[bus stop] W Harrison St & S The query intent is for a bus stop. This result is
Jefferson St a Greyhound station, which fully satisfies the
User and viewport in Chicago, IL 60607
Chicago, IL user's intent. This result is close to the user.
Harlem Ave & W 115th The query intent is for a bus stop. This result is a
St bus stop and matches the user's intent, but there
Worth, IL 60482 are many bus stops closer to the user in the real
world we should be returning instead. Therefore,
this result should be demoted due to distance.
60
5.17. Parking Intent
• Parking that is a mix of residential/staff/permit and visitor parking and is not in a gated
community
• Parking that can be used only when visiting a certain business (limited-use parking)
If you cannot confirm whether parking is public or private, give the result the benefit of the doubt
and consider it public parking.
Sometimes a query specifically requests a certain level of service, which may or may not be reflected
in the result. Common requests include:
When the query requests a specific level of service which is not reflected in the result, give an initial
rating of Good and demote as necessary depending on how well the result would satisfy the user
intent.
When the query requests a type of business with a generic level of service, providing a result that
offers more service than requested still satisfies user intent and should receive an initial rating of
Excellent.
When the query does not specify the type of service, any relevant result can be rated Excellent.
61
Query Result Rating and Explanation
Relevance Excellent
Walmart Neighborhood
Market The query does not specify the type of Walmart,
5500 E 22nd St, Tucson, and any Walmart can be rated Excellent. Demote
AZ 85711 further for distance.
62
Query Result Rating and Explanation
Relevance Excellent
Relevance Excellent
Citibank ATM 7-Eleven
3421 E Tropicana Ave This is an ATM located inside a 7-Eleven
Las Vegas, NV 89121 convenience store. It satisfies the primary intent of
the category.
Relevance Bad (User Intent)
A user has asked for a specific fast food restaurant
McDonald’s and the result is another fast food restaurant that
[burger king] 6875 Sand Lake Rd, offers similar food and service. Even though the
Orlando, FL 32819 service level in the two restaurants is similar, this
result does not match the user intent for the named
restaurant.
63
5.19. Rating Relevance When the Result Status is PERMANENT_CLOSURE
There are some situations where you can expect to see results with the status
PERMANENT_CLOSURE and others where such results are not expected. The following sections
will describe how to identify and rate them.
Sometimes you can expect to see results whose status is shown as PERMANENT_CLOSURE.
64
Examples of results where PERMANENT_CLOSURE status is expected
• Navigational queries:
• Queries that can only return a single result, which is permanently closed. This could be
because the POI or business name is unique or the query contains location intents like
locality or street components.
• Chain queries for closed chains:
• All chain locations within the area of location intent are permanently closed and the closest
open chain result is significantly farther away.
Rating Approach
Rate results with an expected status of PERMANENT_CLOSURE as if they were open. This means
that in most cases the rating will be either Navigational or Excellent, because even though they are
closed, these are the best or only results that could ever be returned.
65
[Link]. Expected PERMANENT_CLOSURE Status: Naviga@onal Query
66
Result Rating and Explanation
Relevance Navigational
Business/POI
99 Bottles Of Beer On The Closed/Does not Yes
Wall exist
PERMANENT_CLOSURE
This permanently closed restaurant is the only result that meets
110 Walnut Ave, Santa Cruz, CA
the user intent, which makes it expected. Choose the
Business/POI Closed/Does not exist checkbox and rate the
business as if it were open.
Relevance Bad (User Intent)
99 Cents Only Stores
260 E 10th St, Gilroy, CA The 99 Cents store does not match the user intent and is rated
Bad.
Relevance Bad (User Intent)
99 Bottles & Cocktails While also a restaurant with a name that starts with 99 Bottles,
8901 Katella Ave, this is not in Santa Cruz, does not match the user intent, and is
Anaheim, CA rated Bad.
67
[Link]. Expected PERMANENT_CLOSURE Status: All chains closed in area
Chico’s has closed all of its locations in Canada. The closest locations to the user are across the
border in the United States.
68
Result Rating and Explanation
Chico’s The open Chico’s closest to the user is just across the border.
5151 Main St, Because it is the closest open result, it is rated Excellent.
Williamsville, NY
United States
These are results whose status is shown as PERMANENT_CLOSURE, but are not expected to be
shown at all.
Results with the status PERMANENT_CLOSURE are unexpected when there are also open results in
the area of location intent that would satisfy the actual user intent fully without changing or altering the
user query.
Examples of situations where results with PERMANENT_CLOSURE status are not expected
• Category queries:
• There are always a large number of possible results for category queries like [restaurant] or
[hair salon]
• Note: In cases where there is only one match for the category query within a large area and
it is marked with the PERMANENT_CLOSURE status, consider it an exception and choose
Business/POI is closed or does not exist, then rate it as if it were open. This should be
extremely rare.
• Queries with several possible interpretations:
• These are queries could have several possible results and/or result types available, and do
not depend on PERMANENT_CLOSURE results.
• Most chain queries:
• There are often multiple locations of a chain available within the area of location intent, and
a permanently closed result does not need to be shown in these cases.
Rating Approach
Unexpected permanently closed results should be demoted by 2 for relevance which means the
highest rating starts at Acceptable.
69
[Link]. Unexpected PERMANENT_CLOSURE Status: Open Op@ons are Nearby
There are many options available near the user for this category query, so there is no reason to show
a permanently closed business.
Relevance Excellent
Meeps Vintage
2104 18th St NW, Washington, Meeps Vintage matches the user intent and is close to the user
DC within the fresh viewport.
Relevance Excellent
Miss Pixie's
1626 14th St NW, Washington, Miss Pixie’s sells vintage clothing and is among the closest
DC results for this category query.
70
Result Rating and Explanation
You’ll see this rating referred to throughout the guidelines as both “Name Accuracy” and "Name and
Category Accuracy.”
If you give a final Name and Category Accuracy rating of Partially Correct or Incorrect, you may be
presented with two checkboxes:
• Name Issue
• Category issue
If they appear, use one or both them to select the reason(s) for your rating.
The n/a rating should be used for all address type results, including residential addresses, streets,
localities, and so on.
Unlike Business/POI type results, address type results do not actually have a result name. Instead,
the first line of address type results appears as the result title. This is because this field is meant to
present the most relevant part of the address information.
71
Since address results do not have a name or category, their Name and Category Accuracy cannot be
evaluated. This is why the n/a rating should be selected.
Your final Name and Category Accuracy rating will take into consideration both the accuracy of the
Business/POI name and the category assigned to it.
A business/POI result name is accurate when it is used on the POI’s official website or on other
official resources. Even if the official website does not use the name, if it is used on other official
sources, the name is correct. Note that the name has to be used to refer to the particular POI. The
corporate name by itself is not automatically the correct name.
72
Business Name
Every name that a specific business location uses to refer to itself is considered correct. These
names can be listed in a variety of ways in different sections of the entity's official website or official
social media website(s):
If these resources are not available, other reliable sources that can be used for researching business
names include:
• Signs and storefronts seen on recent street or online imagery or crowdsourced review pages
• Recent articles in primary publications (newspapers or similar publications that do their own
reporting)
• Official restaurant menus (user photos or scanned images from restaurants)
If the name cannot be confirmed with these resources and there is nothing objectively wrong with it,
rate it Can’t Verify.
Corporate name
The corporate name (and sometimes brand or product name) is often used to refer to a particular
entity, but might be not the preferred name for a specific location. This depends on the particular
company and the specific result.
Some official websites have a local language and an international (English) version. Consider the
name given in the international version only if English is the language/script of the test locale, the
query, or the result region, or if the official company, chain, or brand name is commonly used and
understood in English in this market. If it is not, select the Result name/title is in unexpected
language or script checkbox. No further rating is required.
McDonald’s McDonald’s The chain calls all stores McDonald’s and has the
name in front of all locations as corporate
branding.
Name Accuracy Correct
The name is considered Correct, because it is
Peet’s Coffee Peet’s - Polk Street used on the sign on the storefront. The store is
officially called “Peet’s - Polk Street” on the
website, as it refers to the Polk Street location.
73
Result Name Official Business Name Rating and Explanation
Name Accuracy Correct
Businesses can include the name of the locality or the larger complex or organization they belong to
as additional information. These modifiers, even when not specifically used by the official resources,
can be considered correct. A name with missing modifier can also be considered correct as long as
the modifier isn’t crucial for understanding the particular result. If a modifier is present, it must be
spelled correctly. If it is misspelled, the name is partially correct.
See your Country Specific guidelines for cases where the location modifier is essential for
understanding the result.
Apple Apple Valley Fair The result name is missing the location modifier
(Valley Fair) given on the official website, but is still
considered Correct.
74
Result Name Official Business Name Rating and Explanation
Name Accuracy Correct
Peet’s Coffee Peet’s – Ferry Bldg SF The result name is Correct because it is used as
the name on the official website, while the specific
store has an optional location modifier.
A variation is still correct when a business uses stylized logos and letters (like the backwards “R” in
Toys ”R” Us) that are outside the regular set of letters.
Toys ‘R’ Us Toys Я Us This business uses a special character in its name,
so the name is still considered Correct.
Home Depot The Home Depot The official name of this business is “The Home
Depot,” but since it is so often referred to as “Home
Depot” the name is considered Correct.
75
6.2.2. Partially Correct Name
A partially correct name differs from the official versions but can still be recognized by the user.
Partially correct names can include minor and moderate misspellings, service level mismatches, and
missing or unnecessary name parts, including holding names/corporate structures. When the
business name on the storefront does not include the corporate status (Ltd., Inc., etc.) seen in the
result, it is partially correct.
Consider names partially correct when they contain issues that don’t prevent the user from identifying
the business:
HM H&M
Missing the “&” in H&M is a misspelling but the
name is still recognizable.
Seven Eleven 7-Eleven The name is in an unexpected form not used by the
business itself.
76
Result Name Official Business Name Rating and Explanation
Name Accuracy Partially Correct
GAMESTOP GameStop The name written in ALL CAPS is not expected for
this business and demoted.
Name Accuracy Partially Correct
Mosjaw Moosejaw The name of this outdoor store has two missing
letters but is still identifiable.
77
Result Name Official Business Name Rating and Explanation
Name Accuracy Partially Correct
Aqua Spa Aqua Spa - Ocean The query [aqua spa] was issued in the zh-
City Hant_HK (Hong Kong) test locale and the result
locale is in the US (English). Consider this Partially
Correct due to the mix of expected scripts.
University of University of California Irvine is more than a location modifier for this
California Irvine university. The city name differentiates the Irvine
location from other universities in the University of
California network.
78
Result Name Official Business Name Rating and Explanation
Name Accuracy Partially Correct
The Sears Sears Sears does not use “The” in any of their official
webpages. Adding it to the company name gives
the name a rating of Partially Correct.
Chain businesses often indicate the level of service provided at that location in their name. If the
result name does not reflect the correct type, it is considered a service-level mismatch and is
considered partially correct.
Patagonia Outlet Patagonia The result name suggests that the store is an outlet,
which it isn’t.
Best Buy Best Buy Express A Best Buy Express is a vending machine and not a
store. This is a service-level mismatch and
considered Partially Correct.
Name Accuracy Partially Correct
Best Buy The user is expecting a vending machine where
Best Buy
Express there is a store. This is a service-level mismatch
and considered Partially Correct.
Holding names or corporate structures are not considered correct if they are not explicitly used by the
individual stores. Holding names or names that include corporate structure are considered partially
79
correct or incorrect depending on how recognizable the name is in context with the particular
business.
An incorrect result name is one that can’t be recognized because of severe misspelling or ambiguous
or unnecessary/missing parts in the name.
• Severe misspellings that prevent the user from identifying the business because of:
• Change in meaning
• Misspelling that results in an entirely different word or gibberish
• Holding names that are completely different than the recognized name
• Unnecessary or missing parts in the name that prevent the user from recognizing the
business
• Slang and inappropriate language
• Using the previous name of the same entity that is not a variation of the current name and
therefore cannot be identified
Note: If a result name is incorrect, the final Name and Category Accuracy rating will always be
Incorrect, even if the category is correct.
80
Result name Official Business Name Rating and Explanation
Name Accuracy Incorrect
JAB Holding
Peet’s Coffee The holding company name is completely different
Company
than the store name.
Zatas Tacos + Zacatecas Tacos + The misspelling is severe and does not allow the
Tequila Tequila user to identify the business with certainty. The user
is likely under the impression that it is a different
restaurant.
81
Result name Official Business Name Rating and Explanation
Cheesecake The Cheesecake Factory When missing the word “factory”, the result name
“Cheesecake” is not specific enough and the chain
business cannot be identified with certainty.
Starbucks &
Marks & Spencer By switching Marks with Starbucks, the business
Spencer
can no longer be identified.
Mickey D’s McDonald’s Mickey D’s is British slang for McDonald’s brand.
However it is not an official variation of the brand
name.
Name Accuracy Incorrect
82
Result name Official Business Name Rating and Explanation
Showing a former name that is not shown on the
Bridgestone arena’s official webpage is not a good experience.
Sommet Center
Arena Even when the name might still be in use among
users, if a result shows a former name, rate it
Incorrect.
Once you have determined the correctness of a result’s name, you must evaluate the accuracy of its
category in order to determine the final Name and Category Accuracy rating. The category of a result
refers to the category of the Business/POI.
Not every result will include a category, but when one appears, you will find it below the address
details
If the category is missing or listed as N/A, make your final Name and Category Accuracy rating based
on the name alone.
When a business or POI is categorized correctly, the category accurately reflects the business,
service, or function of the entity. This includes broad or alternate categorizations that are not the
preferred choice but are not misleading.
A correct name paired with a correct category is rated Correct for Name and Category Accuracy.
• Not every result will include a category. If the category is missing or listed as N/A, do not
demote.
• Some categories may seem slightly too specific or too general. As long as the categorization
is not misleading, consider it correct.
• Categories can vary for similar POIs and vary per market. Localization of categories should
be taken into account when deciding on correctness.
83
Category Accuracy Correct
Jocko’s World Famous
Chicken and Seafood This categorization may seem a bit too specific but it is not misleading.
Seafood Restaurant Although this restaurant sells more than just seafood, categorizing it as a
seafood restaurant still properly reflects the nature of this entity.
Category Accuracy Correct
When the category is wrong, the final Name and Category Accuracy rating is always Incorrect. This
is true whether the result name is Correct, Partially Correct, or Incorrect.
• Wrong
• Misleading
• Misspelled
• Incomplete (missing parts or has uncommon/odd abbreviations)
• In an unexpected language/script. The category must match the language/script of the query,
test locale, or result region
84
Result Name and
Expected Category Final Rating and Explanation
Category
Incorrect (Category Issue)
Denver Zoo Category is wrong since the result is a zoo. This
Zoo
Active Life category does not represent the nature of the result.
Final Name Accuracy rating is Incorrect.
85
Result Name and
Expected Category Final Rating and Explanation
Category
The result name should be considered partially
Macys correct because it does not include the proper
Bar Department Store punctuation: “Macys” should be “Macy’s.” The
category of Bar for this department store is wrong.
When the name is partially correct and the category
is wrong, rate Name Accuracy Incorrect.
When, due to a lack of available data online, the business or POI name cannot be confirmed, rate
Can’t Verify. This can be because of a lack of official resources or street imagery, or can be the case
for small businesses that don’t maintain their own webpage or social media profile.
Transit stations and other transit results (like airports and shipping ports), are often named after the
locality or street where they are located and can include a transit indication such as "Station" or
“Subway.” The transit indication in the result name/title is considered optional and can be missing and
still be considered correct. The user query for [san mateo station] can therefore return the name
San Mateo Station or simply San Mateo to be Correct. The category of the result will help you
correctly interpret the result because categories for transit POIs should be a reference to transit.
Keep in mind that some transit POIs located on street intersections may have a result title that is the
name of the street intersection (e.g. “Lincoln Way & 19th Avenue”). This is also considered Correct.
If there are multiple transit systems operating out of the same station, any of the systems can be
included in the name to be Correct. If transit stations are close to each other, but users have to walk
outside to get from one building to another, consider the results for the two stations as two separate
POIs.
A parking lot may or may not have a name. Confirm this on the lot’s official webpage:
• The generic names “Parking,” “Garage,” or “Lot” (or any other words that indicate parking can
take place at the location) are considered Correct when no official name can be found.
• If an official name can be found, rate the generic names “Parking,” “Garage,” or “Lot” (or any
other words that indicate parking can take place at the location) as Partially Correct.
• If the official website provides a name that differs from the standalone brand name found in
the result, rate the brand name (e.g. “Impark”, “Qpark”, etc.) as Partially Correct.
• If the parking lot is specialized (for instance, motorcycle-only parking), and the result’s name
doesn’t reflect that specialization, the result should be rated Incorrect for name accuracy.
Parking
(Result is for the Union Research shows that the official name for this
Square Garage) parking location is Union Square Garage
87
6.7. Final Name and Category Accuracy Rating (Summary Table)
This table shows the final ratings produced by different combinations of name correctness and
category accuracy.
Remember: If you give a final Name and Category Accuracy rating of Partially Correct or Incorrect,
you may be presented with two checkboxes:
• Name Issue
• Category Issue
If they appear, use one or both to select the reason(s) for your rating.
88
7. Address Accuracy: Components and Issues
Address Accuracy is split into two main parts: Components and Issues and Result Expectation. This
section will discuss Components and Issues and the next section will discuss Result Expectations.
Address components are the elements used to form the address details
for each result. These components include street number, unit/apt,
street name, locality, region/state, postal code, and country. The
components are defined in these guidelines with a global approach in
mind. There may be variations for specific markets that are not
addressed here. See your Country Specific guidelines for more
information on the address component requirements for each type of
result.
This section covers the issues that can be associated with the address
components as well as the possible issues that can be associated with the address itself. It refers to
the checkboxes presented in the rating interface when Incorrect is selected. Checkboxes should be
selected for incorrect or missing information. Issues can occur within parts of the address or the entire
address.
Choose all identified incorrect or missing components. If the issue is not tied to individual
components but to an issue pattern, choose the appropriate issue instead.
Never select issues and components at the same time to report the same problem. That is, do not
rate Incorrect —Language/Script issue for the entire address and also Incorrect—Street Name
because street name is in an incorrect language.
When a Language/Script issue is present, make sure to check the address components for
accuracy and to select the appropriate checkbox. For instance, if you select language issue for the
entire address, you can also mark street number as incorrect, since this is an error that's not
language related.
If the result address has an incorrect or missing street number rate Address Accuracy as Incorrect –
Street Number.
89
Result Official Address Rating and Explanation
The way street numbers are assigned varies by country and area. Some patterns you may see:
Some markets use a street number extension system. Street number extensions are part of the street
number, not a further breakdown of it like building or unit numbers. If a street number extension is
incorrect or missing from a POI address it should be treated as an incorrect/missing street number.
Refer to Country Specific Guidelines for more details.
Address Range
Address ranges are used to assign numbers to a stretch of road. Given the nature of these ranges,
not all numbers will have a building assigned to them.
When an address range is given by the query or returned as a result, consider it Correct when:
90
Suggestion Official Address Rating and Explanation
Address Accuracy Correct
The Crutched Friar
39 Crutched Friars, No need to select the Incorrect – Street Number
London checkbox since the street number in the
39-41 Crutched Friars,
suggestion is within the official address range.
London EC3N 2AE,
United Kingdom Address Accuracy Incorrect – Street Number
The Crutched Friar
45 Crutched Friars, Select the Incorrect – Street Number checkbox
London because the street number in the suggestion is
outside of the official address range.
7.1.2. Unit/Apt
A street number can be divided into unit, apartment, or building numbers. Commonly seen forms
include the use of letters: A, B, C as well as the character # in front of a number: #420. Less common
are forms like ½.
A unit number should be correct and present when the official address of a business/POI contains a
unit number.
When a business does not list a unit number and the unit number cannot be confirmed, no unit
number should be given in the result. Rate Incorrect – Unit/Apt when unit number is present in the
rating tool in these cases.
If the result address has an incorrect or missing street name rate Address Accuracy as Incorrect –
Street Name.
Misspellings in the street name, including missing diacritics (e instead of é, l instead of ł) may be
rated Incorrect – Street Name. See your Country Specific guidelines for more information.
92
Result Official Address Rating and Explanation
Street directions (North (N), East (E), South (S), West (W)) as well as street types (Street (St),
Boulevard (Blvd), Avenue (Ave), etc.) are part of the street name. If they are incorrect or missing, the
street name is wrong and rated Incorrect – Street Name. Exceptions are when such elements of a
street name are used interchangeably for the same street.
118 El Camino Real 118 E El Camino Address Accuracy Incorrect – Street Name
118 El Camino Real, Real, Sunnyvale, CA This address is missing the direction. Therefore, the
Sunnyvale, CA 94087 94087 street name checkbox should be selected.
Blue Stones Address Accuracy Incorrect – Street Name
3530 El Camino
3530 E El Camino
Real, Santa Clara, This result address has additional direction, which is
Real, Santa Clara, CA
CA 95051 wrong and does not exist in real life.
95051
Some countries or areas require an additional subdivision, like sub-locality, for correct address
information. See your Country Specific guidelines for specific guidance. The general guidance is to
rate a wrong sub-locality as Incorrect – Sub-Locality. This is also true if the sub-locality is required
but missing.
93
7.1.5. Locality
Misspellings within the locality name, including missing diacritics (e instead of é, l instead of ł) may be
rated Incorrect – Locality. See your Country-Specific Guidelines for more information.
Every result requires the correct locality component within its address details. In cases of local
government reforms or other changes in naming, the result has to reflect the official name.
Exceptions are made when alternate names are accepted.
Each country has its own understanding of what is expected (correct) or unusual (incorrect) for region
or state components. See your Country Specific guidelines for more information.
94
Result Official Address Rating and Explanation
Incorrect – Region/
Address Accuracy
State
Van Gogh Museum
Museumplein 6, 1071 Region is not a mandatory component in the
Museumplein 6, 1071
DJ Amsterdam, Netherlands, but if present has to be correct. The
DJ Amsterdam, North-
Netherlands correct region for the city of Amsterdam is North-
Brabant, Netherlands
Holland, therefore the region/state checkbox will
be selected.
The postal code accompanies the locality name and provides further detail about where a feature is
located. See your Country Specific guidelines for more information on when postal codes are a
mandatory address component.
If a postal code is not mandatory but is present in the result address, rate Correct as long as the
postal code applies to at least part of the feature (street, locality, large POI without an expected
address, etc.).
For many localities, more than one postal code may apply. As long as the returned postal code is
correct for at least a part of the feature (street, locality, large POI) rate Correct. Columbus, OH, for
example, contains 45 postal codes.
Postal code standards differ between locales so be sure to consult your Country Specific guidelines
for details.
Consider any country specific conventions when it comes to the use and correctness of shortened
postal codes. For example, the US postal code does not need the four-digit extension that follows the
five digit main code. Ignore it if it appears.
7.1.7. Country
The country is a “nice to have” piece of information, but should always be included when the result is
located in a country other than the test locale. If missing, rate Incorrect and select the Country
checkbox.
95
Test
Address in Result Address in Reality Rating and Explanation
Locale
An address-type result needs to be associated with a building or with a plot of land that has been
officially assigned that address. If you find strong evidence that there is no building at the address or
that no plot of land has been officially assigned the address, rate Incorrect – Address does not exist
and leave a detailed comment including links. If there are not enough resources available to make an
informed decision, rate Can’t Verify.
Within markets that use street number extensions, if the result offers an address with a generic street
number, but the street number alone does not exist without an extension (e.g. result returns “163
Main St.”, but only “163A Main St.” and “163B Main St.” exist), rate the address as Incorrect –
Address does not exist, since the street number without the extension is not a valid, real-life address.
Note that street number extensions differ from the building numbers referred to in Unit/Apt section.
In rare cases, an existing street address can be found in a different locality. Always mark such cases
as Incorrect – Address does not exist and not as Incorrect – Locality.
Use the Incorrect – Address does not exist checkbox for any address result that doesn’t
exist, like a street or sub-locality result. This rating should not be applied to POI addresses.
The address details must be in a language and script that matches the test language (like en_US),
the user query, or the result region.
96
Use the Address Accuracy Incorrect – Language/Script Issue checkbox if you find issues of this
nature in any of the address components in the address details of any result. (For business/POI
names and address titles in unexpected languages, see Result title/name in unexpected language.)
These examples show incorrect language and script for the result “Cafe Timber, 1066 Hippy Hollow
Rd, Red Boiling Springs, TN 37150” with a user in the US using English.
Results located in a market with different scripts are hard to verify. Use the normal research steps to
confirm the address. It is not expected that you understand markets and address formats outside your
local knowledge expertise, so do the best you can without doing more research than normal.
Rate mixed languages and scripts found in any address details as Language/script Issue when
they use a different language or script than the one used in the query, test, or result location.
The variety of address formats and distinctive country specific issues is broad. In general, use the
checkbox for Country Specific Issue when there is an address problem that is not covered by the
available checkboxes. This includes things like instances when an address also requires a
municipality in addition to locality and state, but those components are either missing or incorrect.
See your Country Specific guidelines for more information.
Any additional components beyond the regular address format for a country are rated:
Issues not mentioned in these guidelines are reported using the Incorrect – Other Issue checkbox. If
you choose this option, be sure to leave a comment as well as links to the resources you used to
identify the issue. The checkbox is also used for:
When all the result address information is correct and present, but not in the format expected, mark it
as Correct with Formatting issue. Formatting issues include the order of address components and
other minor issues that are not necessarily considered wrong. They do not include misspellings which
are addressed under the relevant individual components. Some reasons to rate Correct with
formatting issue:
If optional components already discussed in this chapter appear in the address, use the guidance
provided in the section that applies to those components, not the Correct with formatting issue
rating. If your market has additional address components, consult your Country Specific guidelines
before demoting.
An address is rated Can’t Verify when it cannot be confirmed as Correct or Incorrect. This is usually
the case when there is a lack of resources or an unexpected address format is given on the official
website.
• Lack of resources:
• No official webpage found
• No official address listed
• General lack of official resources
• Lack of street imagery
• Unexpected address formats used by official resources can include:
• Intersection address (Main St and 2nd St)
• Exit address (Exit 5, Hwy 101)
• Descriptive address (Main St between 6th and 7th Streets)
Ask yourself: Is the location given by the result address at least not wrong given all information I
have found? Use the following examples to learn how reach a conclusion.
Note: If an address contains missing or incorrect components, it can be confirmed as Incorrect. Mark
the individual incorrect components. See your Country Specific guidelines for more information on
missing or incorrect components.
98
7.7.1. Can’t Verify for Street Number
The following example shows address details for a business called “Utopia.” No information online
confirms the address and only a few street numbers can be confirmed with official resources.
The following examples give different address details for a business called Aztec. The official address
is “Granite Ave & W Babcock St, Bozeman, MT” and is in a different format than the result addresses.
99