Languages — Interface Language, Translate All and the Language AI Is Asked In
The nine interface languages and how they are detected and changed, email language, how Translate all puts prompts and answers into a language you read, and the separate rules for the language prompts are scanned in and articles are written in.
Interface language
Citadex is available in nine interface languages: English, Chinese, Japanese, Korean, Spanish, French, German, Portuguese and Arabic (right to left). The first visit follows your browser language; your choice is saved in the browser and on your account.
Where to change it: the language picker in the sidebar user menu, or Settings → Preferences. Alert emails, digests, team invitations and other emails are sent in this language too. The help center shows Chinese, Japanese or English articles to match the interface.
Translate all
When you track several countries, prompts and AI answers are often in languages you don't read. The Dashboard, Prompt Library, Prompt Tracking, Citation Sources, Competitors, Content and other pages have Translate all:
- Click the translate button in the toolbar (the 文A icon, "Translate all" on hover); it translates into the language you picked last (the interface language the first time).
- Prompts, page titles, answers and so on are translated in one go; a progress dialog shows how many are done. The button then reads "文A Chinese ▾".
- Click it for its menu: change the language, switch Show originals (on by default, the original under each translation) or Turn off translation to restore the page.
Once translation is on, every other page (including pages opened in the AI assistant's side panel) is translated into the same language too, even after a reload, until you choose Turn off translation in the menu.
Translation only changes what you see: checks still ask in the original language, and the questions AI receives, citation counts and scan data are unaffected. AI answers in the evidence drawer can also be translated one by one, and a results report can be translated before you share it. See One-click translation.
The language prompts are scanned in
Every prompt belongs to a market and is scanned in that market's language and country. One safeguard: in a Chinese, Japanese or Korean market, a prompt with no CJK characters is scanned in English.
When Prompt Tracking detects prompts whose language doesn't match their market, it shows a banner ("n prompt(s) are in a market whose language doesn't match") with Move to matching market, which moves them to the market for the detected language and creates one if needed. The add-prompt dialog gives the same warning before saving.
The language articles are written in
Answer Assets has an article-language dropdown: auto (from the source or prompt) or one of the nine languages. Strategy articles use the target market's language. Headings, tables, FAQ and body are all written in that language; proper nouns keep their original spelling.
Publishing per market
Where an article in a non-primary market language goes (for example a German article on an English site) is set under Prompt Library → "Markets & engines" in the top bar. A market whose language differs from the primary market's has a line "German articles publish to:" → "Set":
- My site has a German section: enter its address, e.g. https://example.com/de or a separate site such as https://example.de. Below, "On your connected platforms, German articles go to" sets each platform:
- GitHub: automatically to /de/blog/, nothing to set.
- WordPress: pick a category; tick "publish as German" if the site runs Polylang Pro or WPML (free Polylang ignores the language, so use a category).
- Ghost: a tag, e.g. the internal tag #de, which routes.yaml can serve under /de/.
- Shopify: a separate German blog (Online Store → Blog posts → Manage blogs).
- Webflow: with Localization, pick the German locale (the post appears under /de/); otherwise a separate collection.
- Wix: tick "publish as German" if the site runs Wix Multilingual.
- Zapier: the webhook receives "language": "de" and the address above; your Zap decides where it goes.
- My site has no German version: articles in that language go to the market's third-party platforms only (LinkedIn, industry portals…).
Unset, or set to "no German version", publishing such an article to your own site first shows "Language mismatch", with a "Set where German articles go →" link back here. With an address set, the "Originally published at" line on third-party copies points at that section (e.g. /de), not the home page.
The one-click publish dialog lists only platforms that serve the article's language: a German article never shows note, Qiita, Zenn, Ameblo (Japanese readers) or Medium, Dev.to, Hashnode, Substack (English readers); LinkedIn, WordPress, Ghost, HubSpot and your own site work in any language.
Frequently asked questions
My interface is in English but the article is in Japanese. Articles follow the market or the article-language dropdown, not the interface. Check the prompt's market.
Does translation change scan results? No. It is for display only.
Can one project have two languages? Yes, as two markets. Scans, prompts and results are kept apart per market.
Was this article helpful?
