“A bilingual search should preserve what the person meant while making language, content parity, and results behaviour explicit.
Diagnosis
Bilingual search breaks intent when an Arabic query reaches an English-only result, a translated label maps to a different property category, or switching language resets the user’s work. It can also fail when the mobile version exposes less searchable content than desktop. Diagnose the chain from query language to result labels, detail content, filters, and enquiry handoff rather than judging translation in isolation.
Decision framework
Define which concepts must remain equivalent across languages: location, property type, price, bedrooms, availability status, and the next action. Decide whether results are language-specific, bilingual, or mixed, then label that choice visibly. Preserve query and filters when switching language, use localized alternate signals for indexable pages, and ensure the mobile experience retains the same essential content.
Explicitly hypothetical property example
Implementation and measurement
Create paired test cases for Arabic and English queries, including synonyms, transliteration, locations, and filters. Verify alternate page annotations, parity of important mobile content, preserved state, result-label clarity, and form language at handoff. Measure query-to-result relevance through task review, language-switch resets, zero-result recovery, detail opens, and enquiry completion. Track defects by concept, not only by translated string, so taxonomy fixes reach both markets.
Put it to work
- Build paired Arabic-English queries for locations, types, and filters.
- Preserve query, filters, and language state during switching.
- Audit mobile parity and test enquiry handoff in both languages.
Sources and visual credits
Illustrative photograph: Hand holding smartphone with blank white screen. It does not depict the hypothetical example. Santeri Viinamäki · CC BY-SA 4.0 · Wikimedia Commons · CC BY-SA 4.0