Skip to main content
Cernel supports multi-language content generation. Enable the languages your store needs, give each one a generation prompt and a translation prompt that guide how content is written and translated in it, and generate enriched content across all your active languages in a single enrichment run.

How it works

Your organization has a primary language and can enable additional languages. When you run enrichment, Cernel generates content in each enabled language. Each language can carry its own translation prompt: instructions Cernel applies whenever it translates content into that language, like grammar rules, cultural preferences, or terminology that should be used. Content generated directly in a language follows the language’s generation prompt instead: the instruction Cernel adds to your agents whenever they write content in that language. Languages are managed under Tools > Languages & markets:
  • The languages list is where you enable or disable languages and add new ones.
  • Each language has its own detail page - open it to edit that language’s generation prompt and translation prompt, and choose whether content for it is always written in that language.
Beyond these organization-wide settings, you can refine how content reads in a given language for a single agent, and decide which languages a single attribute is written in. See Fine-tuning language output.

Every language is also a market

Every language you add is also a market. Cernel writes your product content in the language, and Search demand reads what shoppers search for in that market. Choose the code that matches where you sell, and include the country when it matters: en_GB and en_US are the same language but two markets, each with its own search demand.

Why you would use this

Reach customers in their language

Generate product descriptions, meta titles, and structured data in every language your store supports - without hiring translators.

Language-appropriate content

A per-language translation prompt makes translated content follow the grammar, tone, and conventions of each target language, not just a word-for-word translation.

Setting up languages

1

Enable languages

Go to Tools > Languages & markets. You’ll see a table of your languages, each shown with its flag, name, and language code in the Language & market column and a switch in the Enabled column. Toggle languages on or off using the switch in each row.Your primary language is marked with a badge and cannot be disabled.
The Languages & markets page with an Add language & market button and a table of languages, each row showing the language name and code in the Language & market column and a toggle in the Enabled column, with the primary language marked Primary
2

Add a new language

Click Add language & market to enable a language that isn’t in your list yet. Type the language code you want, for example en for English, da for Danish, or a region-specific code like sv_FI for Swedish (Finland), and click Add language & market. Once added, the language appears in your table, and it is also a market that Search demand can read.
The Add language & market dialog explaining that every language you add is also a market, with a Language field (placeholder e.g. en, da, sv_FI) and the hint that en_GB and en_US are the same language but different markets
Language codes follow the IETF / ISO 639 conventions Cernel uses across the platform. Use a two-letter code (en, da, de) for a generic language, or combine a language and region with an underscore (sv_FI, pt_BR, en_GB) when you need region-specific content. The platform validates the code on submit, so if a code isn’t recognised you’ll see an error and can try again.
3

Set a language's generation prompt

From Tools > Languages & markets, click a language in the table to open its detail page. The page has two tabs: Generate and Translate, and opens on Generate.The Generate tab holds the Always output in [language] toggle and, below it, the Generation prompt. While the toggle is on, which it is by default, Cernel adds the generation prompt to your agents’ instructions whenever they write content in this language. The box shows the prompt in effect right now: Cernel’s standard instruction to write every word in this language, or your own wording if you’ve changed it. Edit it to match how you want content written in this language, for example to ask for formal address or a regional spelling, then click Save.
  • Clear the box and click Save to go back to Cernel’s standard prompt.
  • Turn Always output in [language] off to add no language instruction at all, and control the output language entirely through your own agent prompts. The generation prompt can’t be edited while the toggle is off.
  • The toggle is saved together with the prompt, so click Save after switching it.
The Danish language detail page with the Generate tab selected, showing the Always output in Danish toggle switched on with its helper text, the Generation prompt box holding Cernel's standard instruction to output in Danish with a 'Type / to reference data' hint, and a Save button

A language's Generate tab, with its generation prompt

Saving the prompt box as it is, without editing it, stores Cernel’s current standard wording as your own. Your language then keeps that wording even if Cernel later improves the standard prompt. To keep following the standard prompt, leave the box unchanged and don’t save it, or clear it and save.
4

Configure a language's translation prompt

Open the Translate tab to write a translation prompt for that language, instructions that guide how the AI translates content into it. Use it for:
  • Grammar and style rules specific to the language
  • Cultural conventions and preferences
  • Terminology that should (or shouldn’t) be used
Type / in the prompt editor to pull in a Data Source for reference, then click Save.Cernel applies the translation prompt whenever it translates a Text or HTML value into this language, for example when the language is set to Translate in an enrichment run. When the language is set to Generate, the agent writes the value from its own prompt plus the language’s generation prompt, and the translation prompt isn’t used. To give an agent language-specific rules for generated content, use its Languages tab.
The Danish language detail page with the Translate tab selected, showing the Translation Prompt section with its helper text, an empty prompt editor with a 'Type / to reference data' hint, and a Save button, and the Generate and Translate tabs above

A language's Translate tab, with its translation prompt

Your languages are configured. When you run enrichment, Cernel writes content in each enabled language, following each language’s generation prompt when it writes and its translation prompt when it translates.

Fine-tuning language output

A language’s generation and translation prompts set how content is written and translated in that language across your whole organization. Two further controls let you refine language behavior more precisely: per agent, and per attribute.

Give an agent its own language instructions

Text and HTML agents can carry their own instructions for each language, on top of the organization-wide settings. Open a Text or HTML agent in the Agent Sandbox, go to the Languages tab, and you’ll find one box per enabled language. Whatever you write in a box is applied when the agent writes a value in that language, and when a value is translated into it. Leave a box empty to add nothing for that language. Type / in a box to reference a Data Source. Use this when a single agent needs a language rule the others don’t, for example a size-guide agent that must use metric phrasing in German, without changing how any other agent writes German.
The Languages tab of a Text agent in the Agent Sandbox, with the Use the organization's language instructions toggle switched on and a per-language instruction box for each enabled language, the primary language marked Primary
The Use the organization’s language instructions toggle above the boxes is on by default. While it’s on, the agent also gets the language’s generation prompt when it writes, and its translation prompt when it translates, in addition to anything you type in the boxes. Turn it off to make the agent’s own boxes the only language instructions it gets, replacing the organization’s wording instead of adding to it. The Languages tab appears only on Text and HTML agents, the ones whose values a model writes and translates. Single Select, Multi Select, Media, External Data, and Picker agents don’t have it: their values come from option labels or source data rather than model-written text, so the organization’s language instructions and model translation don’t apply to them.

Choose which languages an attribute is written in

By default, each enrichment run decides which languages an attribute is written in, one plan for the whole run. You can instead fix that choice for a single attribute. Open the attribute’s agent settings, expand Enrichment Settings, and turn on Override language settings. A per-language plan appears where each enabled language is set to Generate, Translate, or Skip, the same editor you use when starting a manual enrichment. Once it’s on, that plan replaces whatever a run asks for, but only for this attribute. A new plan starts the way a run does: the attribute is written in your primary language and translated into the rest. Because the plan is a fixed list rather than a rule, a language you enable later sits outside it and is skipped for this attribute until you add it. Cernel notes under the editor which languages are currently left out, so the gap is easy to spot.
You edit these settings at the category where the attribute’s agent is set. Viewed from a subcategory that receives the attribute from a parent category, they show as read-only with a link to the category that owns them. They are also read-only until an agent is attached.

Advanced configuration

Besides per-language translation prompts, you can set Global Prompts per attribute type (Text, HTML, Single Select, Multi Select). These are configured in Settings > Global Prompts. Each one is added to every agent of that type that has Include default system instructions switched on, so keep it to rules that must apply to every value of the type.For example, a system prompt for HTML might say “Always use semantic HTML headings” while one for Single Select might say “When uncertain, choose the closest match rather than leaving empty.”
For Single Select and Multi Select attributes, the predefined values can be translated into each enabled language. When configuring an attribute, the Values section shows translation status for each value. You can auto-translate or enter translations manually.Auto-translate handles each language on its own. If one language can’t be translated, its values stay as they were and the other languages still update, so you can retry or fill in just the language that’s missing.
Disabling a language hides it from language selections but preserves all existing translations. You can re-enable it later without losing any data.

Frequently asked questions

No. The same agents work across all languages. Cernel handles the language through your language settings, including each language’s translation prompt when content is translated. Your agents focus on what to generate, not which language to use.
The enrichment modal shows your enabled languages. Content is generated for all enabled languages by default. If you need content in just one language, you can manage this through your language settings.
The same one that wrote it. When a language is set to Translate, each Text or HTML value is translated by the AI provider of the agent that produced it, so values from an agent on Anthropic are translated on Anthropic and values from an agent on OpenAI are translated on OpenAI. There is no separate translation setting: to change which provider translates an agent’s values, change the agent’s AI Provider on its Advanced Settings tab. See AI provider and model behavior.
A translation prompt is set per language and applies automatically whenever content is translated into that language - it handles language-wide rules for translations. Agent prompts define what content to generate and how. They work together: the agent prompt says “write a 150-word product description”, and when that description is translated into Danish, the Danish translation prompt adds “use formal Danish grammar.” Content generated directly in a language follows the agent prompt plus the language’s generation prompt; to add language-specific rules for one agent only, use the agent’s Languages tab.
Yes. Open the language under Tools > Languages & markets and edit the Generation prompt on its Generate tab. It starts as Cernel’s standard instruction to write every word in that language, and whatever you save there is added to every agent’s instructions whenever it writes content in that language. Clear the box and save to go back to the standard prompt, or turn Always output in [language] off to add no language instruction at all. To change the wording for a single agent instead, use that agent’s Languages tab.
They stack. A language’s generation prompt and translation prompt, set under Tools > Languages & markets, apply whenever any agent writes content in that language or its content is translated into it. An agent’s Languages tab adds instructions for that one agent only. With the agent’s Use the organization’s language instructions toggle on, the agent gets both. Turn it off and the agent’s own boxes replace the organization’s wording for that agent. See Give an agent its own language instructions.
Use the agent’s per-language instruction boxes and point each one at a different Data Source. A Data Source entry is a single block of text you insert whole, so there’s no way to filter one shared entry down to a market’s slice. Instead, create one entry per market (for example seo/keywords-es, seo/keywords-fr), then open the agent, go to its Languages tab, and in each language’s box type / to reference only that market’s entry: the Spanish entry in the Spanish box, the French entry in the French box, and so on. A run in a given language then only pulls in the content from that language’s box, so each market sees only its own keywords. You don’t need separate agents to do this. See Give an agent its own language instructions.
Yes. When a language is set to Translate (rather than Generate), Cernel translates the value produced in the source language instead of writing it again from scratch. The translation reuses the prompt that generated the original value as read-only guidance, so the translation is asked to follow the same length, tone, and format rules as its source. For example, a value written to a 150-word limit is translated with the instruction to stay within it. This is guidance for the AI, not an exact count, so a translation can still run somewhat longer, as some languages need more words. To check translated values, add a review step: translated values are reviewed against the agent’s review steps too. Each translated value also passes the same quality check Cernel applies to generated content, so corrupted output is caught and retried automatically.

What’s next

AI Agents

Create agents that generate content across all your enabled languages.

Enriching Products

Run multi-language enrichment across your product catalog.

Search demand

See what shoppers search for in each of your markets, and how much of it your product data answers.