Why isn't a job returning for a certain non-English search keyword?
Cloud Talent Solution relies on Google Translate to translate non-English search queries and job data. Because job searches are usually performed on short strings of keywords, some word context might be missing. This can result in an unexpected translation output. We've accounted for the lack of context in German and French to ensure quality results, but rely entirely on Google Translate for other languages. If the language in question is not English, German, or French, and you're unsatisfied with results, try entering the exact job search query into Google Translate. If the translation isn't accurate, please suggest an edit to the translation in Google Translate. If the results for English, German, or French queries aren't optimal, please contact support.
Why isn't a job returning when its requisitionId is entered as a search keyword?
Cloud Talent Solution typically detects common requisitionId regular expressions. However, it's possible that the structure of a requisitionId is similar to some other important information, such as part of a location or address. For best results:
- Ensure that your
requisitionIdfields are populated with the requisition IDs your users expect to be able to search for, since your system may be designed to have multiple versions of requisition IDs (one for your internal, technical purposes, and another for the user). - Help Cloud Talent Solution look strictly for the job with a particular requisition ID by prefixing searches for requisition IDs with
req:orrequisition:. You can add this prefix by giving users a dedicated field to search for requisition ID or by using a regular expression in your own business logic to identify requisition ID structures.
Why are jobs returning from outside of the search location and radius?
When a radius (such as 15 miles) is used in the search query, Cloud Talent Solution uses that value to add the specified additional radius to the edges of the total area of the location indicated in the search query. For example, a search is performed looking for jobs within a 15-mile radius of Mountain View, CA. This search will return results including jobs inside Mountain View city limits as well as jobs within a 15 mile radius of the city limit boundaries. If this was already your expectation, the issue may be a result of one of the following:
- A job has its
PostingRegionset toADMINISTRATIVE_AREAorNATION, meaning that it the job will return for searches within the specifiedADMINISTRATIVE_AREAorNATION, as long as the scope of the query's search is within the correspondingADMINISTRATIVE_AREAorNATION. This functionality exists to support jobs that can accommodate a job seeker from a particular region, rather than a defined city. - A job has an ambiguous
addressthat Cloud Talent Solution resolves to a location that isn't the same as the one that you or the employer intended. For best results, ensure that your jobs have full street addresses.
Why are other jobs returning for a specific job's requisitionId as a keyword?
When Cloud Talent Solution doesn't semantically understand the keywords in a job seeker's query, Cloud Talent Solution may separate keywords to attempt to derive meaning, and/or fall back to more of a keyword-based search. In this scenario, you may have more jobs that mention the searched requisition ID or parts of it (such as a zip code, if Cloud Talent Solution assumed part of the requisition ID was a zip code). You can help Cloud Talent Solution look strictly for the job with a particular requisition ID by prefixing searches for requisition IDs with req: or requisition:. You can add this prefix by giving users a dedicated field to search for requisition ID or by using a regular expression in your own business logic to identify requisition ID structures.
For a location-ranked query, if two jobs have the exact same address, how is their rank determined?
Cloud Talent Solution uses the relevance of job results to determine the order of jobs that are the same distance from a location.
Can I use my own fields if you don't have the standard fields I need?
Yes. See more information about using custom attributes.
How can I influence the order of search results?
You can use the custom ranking functionality when making search requests.
For additional troubleshooting for the below cases, see here
- A job or jobs are being returned in search results that should not contain these jobs.
- A job or jobs are not being returned in search results that should contain these jobs.
- A job or jobs are being returned too high or too low in the search results.
- Similar jobs are being returned next to each other in the search results.
- Not enough jobs are being returned in my search results.
If your issue is not addressed here, please contact support.