Geolocation Coding and Geosearch Overview

Geocoding a location, or geolocation coding as it's referred to in Sourcing, means assigning geographical coordinates, latitude and longitude, to that location; a city such as San Francisco is identified by those coordinates instead of its name in text. Once you have your locations geocoded, you can choose to enable Geosearch within Sourcing which provides several benefits.

Geocoding and enabling Geosearch is optional. When enabled, the following benefits are available:

• Radius Search Functionality - allows jobseekers to search for jobs within a defined perimeter around a location. For example, you may search for all jobs within a 50 mile perimeter of Paris.

• Automatic suggestions of locations when the jobseekers begin to type letters in the Location Search field.

• Radius search within the Automated Referral Campaigns (ARMs).

Note: If Geosearch is not enabled the above functions are unavailable and the Location Search field is replaced by a dropdown list of all locations associated with jobs that are currently posted.

To enable Geosearch the locations in the location tree in Recruiting must be geocoded. The latitude and longitude coordinates that we use for geolocation coding reside in a repository that requires standardized location details to retrieve the proper coordinates. The required format of the location details is country, region/state and city. The location tree in Recruiting must exactly match the repository standards of country, region and city to retrieve the correct coordinates, or geolocation. If the location hierarchy does not match the standards, or if perhaps a location name is misspelled, the geolocation coding will fail and as a result, the candidates search experience may be degraded as not all of the Geosearch capabilities will be functional. To provide the best results and experience with Geosearch, it is critical that time and effort be spent upfront ensuring that locations are geocoded correctly.

Prior to enabling Geosearch, the location tree structure and names need to be validated. If the structure is inconsistent or not standardized with the levels needed for geolocation coding; country, region/state and city, then preliminary work in Recruiting will need to be done to standardize the location tree.

Note: Standardizing the tree for geolocation coding purposes may have an impact on the organization and procedures in place for the recruitment process, so care should be taken.

The location tree must be precise and consistent for geolocation coding, and consequently Geosearch, to work properly. The locations in the location tree that are not standardized or contain spelling errors will not be geocoded. This means if you post jobs on these locations, jobseekers will not find these jobs when they search on the locations that have not been geocoded. To prevent this, you can either manually geocode the locations by entering coordinates in Sourcing or disable Geosearch.