Skip to main content
Signocore
// signocore multilanguage docs

AI translation

Translate posts, terms and strings with your own Anthropic, OpenAI, Gemini or Mistral key in Signocore Multilanguage Pro.

Pro: This needs a Signocore Multilanguage Pro license.

Signocore Multilanguage Pro translates posts, pages, terms and strings with your own account at Anthropic, OpenAI, Google Gemini or Mistral. New translations of posts and pages are saved as drafts for you to review.

Before you start

You need an account and an API key at one of the providers. Requests go straight from your site to the provider, and the provider bills your account for them. There are no translation credits to buy from Signocore.

The AI buttons work once your Pro license is active and a key is saved for the provider you selected. Until then they are greyed out with a lock. Hover over one to see what is missing; clicking it takes you to the AI settings or to the upgrade page. Anyone who can edit a post or term and add items of its type can translate it with AI. Translating strings with AI, like the rest of the String Translation screen, is for administrators.

Connect a provider

  1. Go to Signocore ML → AI.
  2. In the AI Translation card, choose a Provider: Anthropic (Claude) (the default), OpenAI (GPT), Google (Gemini) or Mistral AI.
  3. Under API Keys, paste your key into Anthropic API Key, OpenAI API Key, Google Gemini API Key or Mistral API Key.
  4. Click Save Changes.
  5. In the Check the Connection card, click Test connection. "Connection works." means you are ready.
Test result What to do
The API key was rejected. Check that you copied the whole key and that it is still active in your provider account.
The provider could not be reached. Your server could not connect to the provider. Try again later, or ask your host whether outgoing connections are blocked.
Unexpected answer from the provider (HTTP ...). Try again later. If it keeps happening, check your account and the service status at the provider.
No API key entered. Save a key for the selected provider first.

A saved key is not shown again: its field stays empty and is marked Saved. Leave the field empty to keep the key, or enter a new key to replace it. To delete a key, click Remove next to it under Stored keys in the Check the Connection card. Keys stay stored if your license expires, but they are not used until it is active again.

Anthropic model

Translation Model appears while Anthropic is the provider:

Model Good for
Claude Haiku 4.5 The fastest and cheapest option.
Claude Sonnet 5 The default. Balances quality and price.
Claude Opus 5.5 The most thorough, but slower and more expensive.

If you updated from a version before 2.0, Claude Haiku 4.5 stays selected, because earlier versions always translated with it. You can choose another model here at any time.

With OpenAI, Google Gemini and Mistral, Signocore Multilanguage picks the model and there is no model setting.

Anthropic workspace ID

Anthropic Workspace ID is optional. Fill it in only if your API key is not tied to a workspace, in which case Anthropic rejects requests without it. You find the ID under Settings, Workspaces in the Claude Console.

Keys shared with Signocore SEO

When Signocore SEO is active and has a key for a provider, Signocore Multilanguage uses that key as long as you have not entered one here. The empty field then says "Using the key from Signocore SEO". Enter a key here to use a different one.

While the Signocore SEO key is in use, the Anthropic Workspace ID saved in Signocore SEO is used too, unless you enter one here. The provider and the model are chosen separately in each plugin. See AI generation for the Signocore SEO settings.

Translate a post or page

  1. Open the original in the editor.
  2. In the Translations box, find the language and click Translate with AI. Confirm.
  3. The plugin copies the post as a draft in that language, translates it and opens the draft.
  4. Review the translation and publish it when it is ready.

What is translated:

  • The title, the excerpt and the content. Content is translated block by block: the text and text settings such as image alt text, captions and button labels are translated, while the HTML, block settings, URLs and shortcodes stay as they are.
  • The SEO title and meta description from Signocore SEO, Yoast SEO or Rank Math, and the breadcrumb title from Signocore SEO.
  • The slug, which is made from the translated title.

The copy also carries over the featured image and custom fields of the original, and its categories and tags are swapped for their translations where those exist. If the translation fails, the draft is deleted again and you see the error.

A post whose content is longer than 120,000 characters is refused, and so is a single paragraph or block longer than 12,000 characters. Both are checked before anything is sent, so they cost nothing. Split the text into shorter parts and try again.

Retranslate after the original changes

When the original is edited after a translation was last saved, the Translations box of the translation shows Source changed. There you can:

  • click Retranslate with AI to replace the title, content, excerpt and SEO fields with a fresh translation of the current original, or
  • click Mark as up to date when the change does not matter for this language.

Retranslating updates the existing translation in place and keeps its status. A slug you changed by hand is kept.

Important: When the translation is published, the new text goes live right away and replaces the current text, including your own edits. With revisions turned on, you can restore the earlier version under Revisions. Without revisions, the old text cannot be restored.

Translate a category, tag or other term

  1. Open the term's edit screen.
  2. In the translation panel, click Translate with AI next to the language. Confirm.

The translated term is created right away with a translated name, description and slug. Terms have no draft status. A language that already has a translation shows Edit instead; change that term by hand.

Translate strings

  1. Go to Signocore ML → String Translation.
  2. Pick a language, and a context if you only want to translate that one.
  3. Click Translate missing with AI and confirm.

Every string with the status Needs Translation is translated, 20 at a time, until none are left. The translations are saved and go live right away, also in customer emails. Strings marked Needs Update are skipped; to retranslate one with AI, empty its field first. Strings longer than 12,000 characters are skipped as well, without holding up the others. When only such strings are left, the screen says the text is too long. See String translation.

Words that must stay the same

Enter brand names, product names and other words that must not be translated in Never Translate on Signocore ML → AI, one per line. A comma also separates two entries, so an entry cannot contain one. The list goes along with every request, and the model is told to keep these names exactly as they are while translating the words around them.

Developers can change the list with signocore_ml_ai_glossary.

What is sent to the provider

Each request contains:

  • the text being translated, as listed above for posts, terms and strings,
  • the names of the source and target languages,
  • a short note on what the text is, such as a page or a category, with your site title,
  • your Never Translate list,
  • your API key, and for Anthropic the workspace ID if you entered one.

Nothing else from your site is sent: no other custom fields, user data, comments or files. How the provider stores and uses the data follows your agreement with that provider.

What it costs

The provider bills your account for every request, based on how much text goes in and comes out, so longer content and every retranslation cost more. With Anthropic, Claude Haiku 4.5 costs the least and Claude Opus 5.5 the most. Check the prices and set a spending limit in your provider account.

When a translation fails

Message What to do
AI translation is not set up. Add an API key under Signocore ML > AI. Save a key for the selected provider on Signocore ML → AI.
The provider returned an error (HTTP ...). The message from the provider follows. A 401 usually means a wrong key, and a 429 too many requests in a short time.
The AI provider took too long to answer. Try again, or translate a shorter text. Try again. For long content, split it up.
The provider returned an unexpected answer. Try again, or translate a smaller amount at a time. Try again. If it keeps happening, try another model or provider.
Claude declined to translate this text. Try again, or choose another model or provider on Signocore ML → AI.
This content is too long to translate in one go. Split the post into shorter posts, or translate it in the editor.
A part of this text is too long to translate in one go. Split the long paragraph or block into shorter ones.

Stuck on something the docs don't cover?

Questions go straight to the developer who builds the plugins. Replies usually within a day.

September Sale

€20 off Signocore SEO Pro

Pay €49 instead of €69, one time for unlimited sites. code SEP20