How language works inside Citadex. The UI switcher (9 locales) and the AI output language for generated content and prompt tracking are two independent settings — here's how to use both.

Two languages, two purposes

Citadex has two independent language settings, and most "why is my content in the wrong language" tickets come from confusing them:

UI Language — the language of the Citadex interface itself (menus, buttons, settings labels). Set via the language switcher in the TopBar.
AI Output Language — the language Citadex uses when generating articles, running prompt scans, or analyzing competitors for your project. Set per project, derived from your Market.

You can use Citadex in Japanese while tracking an English-speaking US market, or use the English UI while generating Spanish content for a Latin American market. The two are decoupled on purpose.

Supported UI languages

The TopBar language switcher covers 9 locales:

Code	Language
`en`	English
`zh`	中文 (Chinese, Simplified)
`ja`	日本語 (Japanese)
`ko`	한국어 (Korean)
`es`	Español (Spanish)
`fr`	Français (French)
`de`	Deutsch (German)
`pt`	Português (Portuguese)
`ar`	العربية (Arabic) — RTL layout

Your selection is saved as a cookie and applied across every page including the public blog and help center. Arabic flips the layout to right-to-left automatically.

How AI Output Language is decided

For any AI-generated artifact (Content Studio articles, prompt scans, competitor analysis, hero-image queries), Citadex picks the output language from your active Market — not from your UI language.

Markets carry a target language plus a region. A Market like "US — English" will produce English prompts and English articles regardless of whether your TopBar is set to Japanese.

If your project has no Market configured, Citadex defaults to English. To change the AI output language for an existing project, go to Project Settings → Markets and add or switch the active Market.

When the two are likely to clash

You set the UI to Japanese to read Citadex more comfortably, but you generate articles for a US audience. Correct setup: UI = ja, Market = "US — English". Output stays English.
You're a Spanish-native operator running a single Latin American brand. UI = es, Market = "MX — Spanish". Both align — content and interface match.
You're tracking the same brand in three regions (US, JP, MX). Use three Markets (see Markets — Multi-Market Brand Tracking). The UI language stays whatever you prefer; the AI output flips when you switch active Market.

Per-content language overrides

A few features take a one-off language override:

Content Studio has a language dropdown in the brief form. Default matches the active Market, but you can override per article (useful when writing a translation).
Prompt Library lets you add prompts in any language manually. Auto-generated prompts follow the Market.
Help Center and the public-facing Blog are language-routed via the URL prefix (or no prefix for English).

Frequently Asked Questions

Q: I switched the UI to Spanish and now my prompt scans came back in Spanish — was that wrong?

That's only possible if your project's Market is set to a Spanish-language one. The UI switcher itself doesn't touch scan output. Open Project Settings → Markets and check which Market is active.

Q: Can I run one project in two languages at the same time?

Not in the same project. Add a second Market for the second language — visibility, prompts, and scans are tracked per Market. See Multi-Market Brand Tracking.

Q: Does changing the UI language re-translate my saved articles?

No. Saved Content Studio drafts and published posts stay in the language they were generated in. The UI switcher only translates Citadex's own chrome.

Q: My Arabic UI looks broken on one page.

RTL layout is applied site-wide, but if a specific page renders incorrectly, send a screenshot to support@citadex.io with the URL and we'll patch it.