Language Defaults and AI Translation
The default plugin language supplies the “plugin default” choice used by AI translation and metadata generation. It does not automatically translate every interface string or page.
The default plugin language is an authoring preference used when a supported AI tool offers “Use default plugin language.” It tells metadata generation or translation which target language to request. It does not translate the WordPress admin, the compiled widget interface, existing assistant text, source pages, or visitor messages automatically.
Begin by choose english, dutch, german, spanish, french, croatian, or italian in general. The work pays off when you save the owning form and test the visitor/security behavior; that final observation is more meaningful than a saved notice because it shows what an administrator or visitor actually receives.
What this feature does and when to use it
Section titled “What this feature does and when to use it”Use the default for a consistent authoring target, then invoke translation only on screens that provide Translate with AI.
Use this feature in the following situations:
- Most administrator-authored content should target one of the seven supported languages.
- You want translation and metadata dialogs to share a default language choice.
- You are reviewing whether translated instructions preserved Markdown, placeholders, URLs, and policy meaning.
Where to find it
Section titled “Where to find it”Before you begin
Section titled “Before you begin”- SmartSite Assistant is installed and activated.
- You are signed in with an account that can manage WordPress options.
Set it up step by step
Section titled “Set it up step by step”- Choose English, Dutch, German, Spanish, French, Croatian, or Italian in General.
- Save the setting.
- Open a supported assistant, chat-content, or security text field with Translate with AI.
- Choose Use default plugin language or a specific language.
- Add optional translation guidance.
- Translate, review, and Apply.
- Save the owning form and test the visitor/security behavior.
Fields, controls, and important values
Section titled “Fields, controls, and important values”Language settings keep administrator-generated content and visitor-facing text consistent. Translation can make instructions and messages easier for the intended audience to understand, but it does not translate or improve the underlying knowledge automatically. Review important terminology with a fluent speaker, because a polished mistranslation can guide both the visitor and the AI in the wrong direction.
| Field, control, or status | What SmartSite Assistant does with it | How to use it and why it matters |
|---|---|---|
| Default plugin language | English by default; supported keys are English, Dutch, German, Spanish, French, Croatian, and Italian. | Changing “Default plugin language” can alter capability, wording, speed, cost, or language, but it cannot fill gaps in the knowledge base. Compare the same realistic prompts before deciding that a model or translation choice is an improvement. |
| Use default plugin language | Resolves at request time to the saved General setting. | “Use default plugin language” affects newly generated output rather than rewriting content that is already saved. Choose a supported value, test representative questions, and have a qualified reviewer check language, terminology, latency, and cost where those differences matter. |
| Translation model | gpt-4.1-mini, temperature 0.1, store=false. | Administrative translation uses this fixed model and controlled generation settings. Review fresh output—especially instructions and policy-sensitive wording—because fluent language can still shift meaning, terminology, or the behavior expected from the assistant. |
| Translation limits | Source up to 25,000 characters and optional guidance up to 240. | Keep source text and optional translation guidance inside these fixed request boundaries. If content is longer, translate it in reviewed sections; do not assume truncation will preserve the most important instructions or visitor wording. |
| Apply | Replaces the current field value after review; the owning form still must be saved. | “Apply” commits the values or advances the workflow; it is not the final proof that everything works. Follow it with the page’s success check, especially when OpenAI, Meta, email, knowledge indexing, or frontend caching is involved. |
How to confirm it is working
Section titled “How to confirm it is working”For Language Defaults and AI Translation, a saved notice is only the beginning. Confirm the outcome from a fresh session and compare it with the success description above so cached pages or earlier conversation context do not create a false positive.
Practical example
Section titled “Practical example”Translate a welcome message into Croatian, preserve the product name, then have a fluent reviewer approve it.
Recommended practice
Section titled “Recommended practice”- Change one part of Language Defaults and AI Translation at a time and keep a short record of the previous value and test result.
- Check the public widget with keyboard, touch, light, dark, desktop, and mobile conditions relevant to the site.
Important warnings
Section titled “Important warnings”Common problems and focused checks
Section titled “Common problems and focused checks”| Problem | What to check and what to do next |
|---|---|
| Language Defaults and AI Translation is missing or does not match this guide. | Confirm the plugin is active and the account can manage WordPress options. Compare the saved public widget with the preview and account for caching, theme CSS, and viewport width. |
| A change on Language Defaults and AI Translation does not produce the expected result. | Keep the exact notice and test case, then review the browser console and WordPress/PHP log. Compare the saved public widget with the preview and account for caching, theme CSS, and viewport width. |
Screen reference
Section titled “Screen reference”- Capture
- Show Settings → General with Croatian selected and a separate translation toolbox using “Use default plugin language,” with no real policy text.
- Show
- Default plugin language, Save, translation language and guidance
- Viewport
- Desktop, 1440 × 900
- Annotate
- Use numbered callouts only for controls referenced in the procedure.
- Redact
- OpenAI keys, tokens, secrets, personal information, private URLs, IP addresses, and conversation text