---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Searching translated content

# Searching translated content {#ariaid-title1}

* Release version: Xanadu
* 
* Updated February 4, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Understand how AI Search searches translated fields and documents.
The ServiceNow AI Platform® includes two categories of translated content:

1. Translated fields, such as translations of Catalog Item record fields.
2. Translated documents (long text and HTML values), such as translations of knowledge article records.
{#searching-translated-content-ais__ol_lgv_fzr_2rb}

The default AI Search matching behavior differs for these two types of content.

## Translated fields {#searching-translated-content-ais__section_uwc_k4q_tvb}

When you search content that includes translated fields, AI Search matches and displays field translations in your ServiceNow AI Platform session language. If a field lacks a translation in the session language, AI Search instead falls back to matching against the English-language field value. For example, if your session language is Japanese, AI Search returns Japanese field translations where present on a Catalog Item record, but returns English values for Catalog Item fields that have no Japanese translation.

To learn more about how the ServiceNow AI Platform handles translated fields, see [Translating individual UI strings](https://servicenow-prod.fluidtopics.net/ph9_UxsnphjyKQfy6c8NOw "When translating just a few UI strings, such as when you add customizations to a translated instance, use the procedure that applies to the type of text being translated.").  
If you insert or update field translation records in the Translated Text \[sys_translated_text\] table, reindex content from the relevant indexed source to make AI Search use the new translations. For details on reindexing content, see [Perform a full table index or reindex for a single AI Search indexed source](https://servicenow-prod.fluidtopics.net/ylmJp1OFiNmWvOFFxmjvuw "Make content from an internal indexed source searchable by performing a full table index. This procedure indexes existing records from the source table and any child tables configured for indexing. You can manually reindex content from an internal indexed source by repeating this procedure.") and [Perform a full table index or reindex for multiple AI Search indexed sources](https://servicenow-prod.fluidtopics.net/Z9dMtDQg0y5QT21ry1biLw "Make content from multiple internal indexed sources searchable by performing a full table index. This procedure indexes existing records from the source tables and any child tables configured for indexing. You can manually reindex content from internal indexed sources by repeating this procedure.").  
Note:  
AI Search doesn't support translated fields on the Knowledge \[kb_knowledge\] table. This behavior has the following effects.

* Search queries don't match translated versions of kb_knowledge translated fields.
* Search results don't display translated versions of kb_knowledge translated fields.
* [Search application facets](https://servicenow-prod.fluidtopics.net/DSngZomT7eAdJi9jDRHeCA "Define facets to refine your searches using categories dynamically generated from the current search results.") don't display translated versions of kb_knowledge translated fields.
{#searching-translated-content-ais__ul_imb_zk1_f5b}

## Translated documents {#searching-translated-content-ais__section_wcg_l4q_tvb}

When searching content with translated documents, by default AI Search only matches documents in the user's ServiceNow AI Platform session language. For example, a Japanese user search only matches knowledge articles in Japanese, excluding all knowledge articles in other languages.

Starting in the Utah release, you can configure a filter condition for globally searchable knowledge articles. Articles that satisfy this condition can be matched by searches in any language. For information on this setting,
see [Configure globally searchable knowledge articles](https://servicenow-prod.fluidtopics.net/p2UlsVpyooXpalMxmYGX7Q "Define an encoded query for knowledge articles that you want to make searchable in any language.").

Beginning in the Tokyo release, you can set a fallback language for each language enabled in your ServiceNow AI Platform instance. When a fallback language is configured for the user's session language, AI Search returns search results in both languages. For more details, see [AI Search interaction with fallback languages](https://servicenow-prod.fluidtopics.net/owA4NUOVSjSWEbUU6WGf6w "When a fallback language is configured for the user's session language, AI Search searches translated documents in both languages. Search uses the appropriate stop word, synonym, and typo handling dictionaries for the fallback language.").

You can configure a global fallback locale to make AI Search match documents in the instance locale's language as well as the user's session language. This configuration works best when you want to make all English-language documents globally searchable. To
learn more about configuring a global fallback locale, see [Enable a global fallback locale for translated content](https://servicenow-prod.fluidtopics.net/crjbu2ePYPvkTZUSLr1e3Q "Configure AI Search to match translated documents in a global fallback locale's language as well as the user's session language.").