Why Geosearch is not working for Multi language?

The Geosearch feature in RChilli's Search & Match API might not work properly with multilingual data due to several technical and configuration-related limitations. Here's a breakdown of why this could happen and what can be done:

🧭 Why Geosearch May Fail with Multi-Language Data

1. Taxonomy and Ontology Limitations

• While RChilli's taxonomy supports multiple languages, the geographical names and aliases may not be comprehensively mapped across all supported languages.

• For example, "München" (German) might not resolve the same way as "Munich" (English) unless explicitly defined in the taxonomy.

2. Standardization Challenges

• Locations may be stored in various formats due to language-specific spellings, diacritics, or regional aliases (e.g., "São Paulo" vs. "Sao Paulo").

• If the location data in the resumes or jobs is not standardized or normalized using RChilli's Taxonomy 3.0, geosearch matching can fail.

3. Search Engine Language Dependency

• RChilli’s Geosearch functionality is powered by Solr/Elasticsearch, which require properly tokenized and normalized data.

• Non-English characters or non-Latin scripts may not be indexed correctly if the tokenizer or language filter isn’t configured to support those scripts.

4. Region-Specific Indexing

• If the geolocation data is tied to a specific region or data center, and multilingual aliases aren't included during indexing, search results may be limited or inaccurate.

🔧 Recommended Solutions & Workarounds

✅ Use Taxonomy API for Normalization

• Before indexing, normalize multilingual location names using the RChilli Taxonomy API, which supports standardized values, synonyms, and aliases across languages.

✅ Enable AutoComplete Location Setting

• Make sure the autocompletelocation setting is enabled in the API configuration. This helps the parser infer missing location details based on partial information.

✅ Language Standardization in Preprocessing

• Preprocess multilingual data to convert non-English place names into their standardized English equivalents (e.g., “Köln” → “Cologne”).

✅ Ensure Region-Compatible Data Indexing

• Use the correct regional deployment server (e.g., Frankfurt for Europe, Singapore for Asia) to align with local language datasets.

✅ Request Multilingual Taxonomy Support

• If your current configuration lacks multilingual support, contact RChilli support to ensure that monthly taxonomy updates include your required language variants.

📩 Need Assistance?

For configuration help or taxonomy enhancement, contact support@rchilli.com.