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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Language filtering for external content

# Language filtering for external content {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
AI Search filters search results from external content connectors, showing only results in the user's session language, fallback language, and global fallback locale language.  
When you have the External Content Connectors application installed, AI Search applies language-based filtering to search results retrieved by your external content connectors. For an external content search result to be displayed, it must include content in one of the following languages:

* The search user's ServiceNow AI Platform® session language
* The fallback language for the search user's ServiceNow AI Platform session language (if configured)
* The language for the global fallback locale (if configured)
{#language-filtering-external-content__ul_ekw_j4b_v2c}  
As an example, if the session language is Canadian French, with French configured as the fallback language and English configured as the global fallback locale language, searches only return external content results that contain Canadian French, French, and English content. External content search results which only contain content in other languages don't appear in the search results list.  
Note:  
AI Search can detect multiple languages when indexing content from external source system documents, so a single external content search result may be tagged with multiple languages. As an example, a document in Japanese that contains a section in English might be tagged as including both Japanese and English content. This document would appear in the search results from the previous example because it contains content in English. For more information on language detection at indexing time, see [Internationalization support for AI Search](https://servicenow-prod.fluidtopics.net/Hvw2CsNhLvYl5VfpuZA5tg "AI Search supports indexing and search in all languages offered by the ServiceNow AI Platform. Search linguistic features are supported in Arabic, Brazilian Portuguese, Czech, Danish, Dutch, English, Finnish, French, French - Canada, German, Hebrew, Hungarian, Italian, Japanese, Korean, Norwegian (Bokmål), Polish, Portuguese, Russian, Simplified Chinese, Spanish, Swedish, Traditional Chinese, and Turkish.").

To learn about configuring and using connectors to make content from external source systems searchable, see [External Content Connectors](https://servicenow-prod.fluidtopics.net/_0abad_qGwYsW2_LRXJn8A "The External Content Connectors ServiceNow Store application enables AI Search applications to search content and metadata from supported external source systems, such as Atlassian Confluence Cloud and Microsoft SharePoint Online."). For details on fallback languages and the global fallback locale, see [AI Search interaction with fallback languages](https://servicenow-prod.fluidtopics.net/_WI660Bi1XhTQND5i948DA "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.") and [Enable a global fallback locale for translated content](https://servicenow-prod.fluidtopics.net/HJKEwtQFxSfngmkX_yeb1w "Configure AI Search to match translated documents in a global fallback locale's language as well as the user's session language.").