Site settings

Automatic translation

With a Pro key, Kufi translates your pages, SEO texts and products into your site's other languages with Polylang or WPML, the way a native copywriter would write them. No API keys or setup. Each key has a monthly allowance, and top-ups add more.

Automatic translation works on sites that use Polylang or WPML, where each language has its own page. It runs on our servers, so there's nothing to set up: no API keys, no accounts with other services. You need an active Pro key on the site. See Multilingual sites for setting up the languages first.

Each Pro key translates its own product's content:

Key What it translates
Builder Pro Pages built with Kufi
Kufi SEO Pro SEO titles, descriptions and social sharing texts
Commerce Pro Product names, short descriptions and descriptions
Kufi ONE All of the above

When you publish

When you publish changes to a page that has translations, Kufi offers to carry the changes over to the other languages. Layout, styles and images follow; the translated texts and links on each translation stay as they are.

With a Pro key, the dialog also offers Translate new and changed texts automatically (on by default). The texts that are new or changed in the original are translated into each language as the changes are carried over. Only those texts are sent, so a small edit uses a few hundred characters. A translation with unpublished changes, or one that isn't published, gets the update as a draft.

Without Pro, or for any text that couldn't be translated, the new and changed texts are marked on each translation. Open the translation in the builder:

  • the elements to update have a dashed amber outline on the page;
  • the Page panel lists them under Needs translating, with the new original text, and clicking one selects the element;
  • the element's settings show the new original text at the top.

Update the text and publish, and the mark goes away. If a text needs no change, use Mark as translated. With Pro, Translate next to a text, or Translate all, puts the translation into the page for you to review before you publish.

Translate a whole page

In the builder, open the page in your main language and go to the Page panel. Under Translations, each language has Translate page; with Polylang, a language that has no translation yet has Create and translate. Kufi copies the layout, translates every text and saves the result on that language's page as a draft, so visitors don't see it until you review and publish it. Translating into an existing translation replaces its layout and texts. Use it for new pages, or to start a language again from scratch.

SEO texts and products

  • Kufi SEO: with the Kufi SEO Pro add-on and a Kufi SEO Pro or Kufi ONE key, the SEO box of a translated page or post has Translate SEO from each of its other languages, which replaces the SEO title, meta description, social title and description and breadcrumb title with a translation. Translate page in the builder does the same for the page's SEO texts. Titles and descriptions are kept within the lengths search engines show.
  • Kufi Commerce: with an Commerce Pro or Kufi ONE key, the product edit screen has a Translations box: Translate from this product replaces a language's name, short description and description with a translation, and with Polylang Create and translate creates a missing language as a draft first. Prices, attributes and other product settings are shared and aren't touched.

How translations are written

Translations are written to read naturally in each language, not word for word:

  • The tone of the original is kept: persuasive copy stays persuasive, technical text stays precise.
  • Brand names, product names, people's names, email addresses and web addresses stay as they are.
  • Formatting stays: bold, links, lists and other HTML in rich text come back in the same place.
  • Right-to-left languages such as Arabic and Hebrew get right-to-left pages, as for any translation. See Multilingual sites.
  • The same term is translated the same way across a page.

What isn't translated

  • Links and web addresses. Point links to the translated pages yourself where it matters.
  • Code: the Custom code element, custom CSS and site scripts.
  • Text inside images. Use a separate image per language if it has words in it.
  • Menus, and header and footer texts. Translate them in Polylang under Languages → Translations or in WPML under String Translation, as before.
  • Sites on TranslatePress or Weglot, which translate pages their own way.

Characters, allowance and top-ups

Translation is counted in characters of the original text sent for translation: every letter, number, space and punctuation mark, including the formatting in rich text. Only texts that are actually translated are counted.

Key Monthly allowance
1 site 150,000 characters (about 25 to 30 pages)
5 sites 600,000 characters
25 sites 2,250,000 characters
  • The allowance is shared by every site on the key and resets on the 1st of each month. Unused characters don't carry over.
  • Top-ups add 500,000 or 2,000,000 characters to one key. They're used after the month's allowance and never expire while the key exists.
  • Kufi → License shows the characters left this month and from top-ups. Buy more opens the Translation tab of Kufi Suite pricing with your key attached, so the checkout knows where the characters go. You can also buy there signed in with the account that owns the key; with more than one Pro key, you choose which one at checkout.
  • When there aren't enough characters left, Kufi says so and nothing is translated or charged. Changed texts are still highlighted for you to update by hand, as in the free version.

A refunded top-up is removed from the key. See the terms of sale.

Review your translations

Automatic translation gives you a strong first version, not a final proofread.

  1. Open each translation in the builder and read it through, especially headings, buttons and anything legal or about prices.
  2. Change any text you like and publish. Your edits stay: the next time you publish the original, only texts that changed there are translated again.
  3. For important pages, ask a native speaker to read the result.

The texts are sent to our servers only to be translated and aren't kept there; we keep only the character counts. See the privacy policy.

More in Site settings

Still need help?

Tell us what you are trying to do and what you see. We read every message.