Skip to content

Translating Elementor

On this page

The texts of an Elementor page are kept as segments with a translation memory (free, version 2.8.0
and later) – see
Translation Memory and Segments. A text that appears several times is translated
once, texts you corrected by hand are not replaced by a later automatic translation, and changing
one widget in the original only makes that widget’s text need translating again. This needs
Elementor ticked under LATW Multilingual → Settings → Translation → Page builders.

A page built with Elementor is translated in the Elementor editor itself. Go to LATW Multilingual
→ Posts
, open the Pages tab and click the pencil next to a language, or use the LATW
Translations
box of the page. The page opens in Elementor at its address in that language, and
Save translation stores what you edited as that language’s version – the original page is not
touched.

You can change more than the texts there. A different picture, link or colour stays in that
language. A widget you remove, add or move, or whose text you give a structure of its own (a new
paragraph, bold text the original does not have), keeps what you did – and only that widget stops
following the original; the rest of the page is still updated from it segment by segment (version
2.8.1 and later). Elementor tells you when a save does this, and the segment editor can restore any
such widget from the original. See When you change the layout of a translation in Translation
Memory and Segments
.

This page covers two things that are specific to Elementor: the address (URL slug) of a translated
page, and the widgets that add-ons bring.

#The URL slug of a translation

Available in the free version (version 2.6.5 and later).

The slug is the last part of a page’s address: /en/services/consulting/ (with languages on
subdomains or domains: en.example.com/services/consulting/). Leave it alone and the
translation keeps the original slug; give it one and the English page lives at its own address.

In the Elementor editor. Click the gear icon (Settings) at the bottom of the panel. Under
Translation URL (LATW) type the slug into URL slug and click Save translation. The field
is empty until a slug has been set, and saving it empty keeps the original slug.

In any editor, including Divi, Beaver Builder, Bricks, Oxygen and WPBakery. Open the page’s
segment editor: in the LATW Translations box, click the list icon next to the language. The
URL slug field is at the top of the editor. Type the slug and click Save slug (or press
Enter). It saves at once – you do not need to save the segments or the page. The field appears once
the language has a translation. The block editor also has the field in the Translation URL
panel of its sidebar. (Before version 2.8.0 the field was in the LATW Translations box itself.)

What to know:

  • The slug is unique within a language. If another page already uses it in that language, a
    number is added (consulting-2). The field then shows the slug that was really stored.
  • Existing translations keep their slug. Translating a page again, by hand or with AI
    (PRO), never changes a slug that is already set. To change it, edit it here.
  • Nothing is generated for you. The slug is whatever you type; with PRO, the Localize
    URLs (slug)
    setting can fill it in the first time a page is translated.
  • Old addresses are redirected. A visitor on the original slug of a translated page is sent
    to the translated one with a permanent (301) redirect.
  • Letters and spaces. The slug is turned into a normal URL form when you save it: lower case,
    hyphens instead of spaces, accented letters replaced by plain ones. Letters are spelled the way
    the translation’s language writes them without accents (version 2.8.2 and later): in German
    ü becomes ue and ß becomes ss (über → ueber), in Danish ø becomes oe; other
    languages simply drop the accent (été → ete). Slugs saved before keep their spelling.

#Child pages

The address of a child page contains the slug of every parent: /en/services/consulting/. Each
level takes its own translated slug – translate the parent’s slug and the child’s address follows
(version 2.6.5 and later). A level that has no translated slug keeps the original one, so you can
translate a parent without touching its children.

  • The old, half-translated addresses are redirected to the full translated one.
  • A path with a parent that does not match the page – /en/other-parent/consulting/ – shows
    “page not found” instead of the child page.
  • The address in the original language is never changed.

#Elementor 4 atomic widgets

Available in PRO (version 2.6.1 and later).

The new widgets of Elementor 4 – Heading, Paragraph and Button from the Atomic editor

  • are translated by AI together with the rest of the page. The Heading, Paragraph and Button of the
    older, classic widget set are covered as before. Other atomic widgets (tabs, accordion, image text)
    are not translated yet, and add-ons’ own atomic widgets cannot be added on the Elementor Widgets
    screen.

#Translating custom widgets

Available in PRO (version 2.4.0 and later).

When AI translates an Elementor page, it does not send the whole page layout to the translation
engine. It sends only the texts it knows are texts: a heading’s title, a button’s label, a tab’s
content. For that it keeps a list of widgets and of the settings in each widget that hold text.
The list covers the widgets of Elementor, Elementor Pro and PowerPack for Elementor.

A widget that is not on the list is skipped. That is the case for widgets your theme brings
with it, and for widgets from add-on packs the plugin does not know. The rest of the page is
translated, but the texts inside those widgets stay in the original language. No error is shown,
because nothing failed: the plugin simply did not know those settings were text.

The Elementor Widgets screen lets you close that gap yourself, without code: scan the site,
see which widgets are not translated, and tick the settings that hold text.

This section is about widgets an add-on built from scratch for Elementor. A widget whose type
starts with wp-widget- is a different thing – it is a classic WordPress widget (Search,
Categories, Recent Posts, Tag Cloud, or a theme’s own widget class), dragged onto the page from
Elementor’s WordPress panel. Those are already covered and do not appear on this screen: the
Title you typed into one is translated together with the page, and so are the body of a
Text or Custom HTML widget and the alternative text and caption of an Image widget
(PRO version 2.5.1 and later). What else such a widget shows – its built-in heading, the posts or
categories it lists – is explained in Translating Widgets.

#When you need this

  • A section of an otherwise translated page is still in the original language, and that section
    is a widget from your theme or from an add-on.
  • You installed a new Elementor add-on and want its widgets translated too.

If a whole Elementor page is not translated, this screen is not the cause – check the page in the
LATW Translations box first.

#Scanning the site

Go to LATW Multilingual → Elementor Widgets and click Scan site. The plugin reads every
Elementor page, post and template (including headers, footers and popups built with the Theme
Builder) and lists each widget it does not know. The scan reads your content only; it does not
change anything and does not contact the translation engine, so it costs nothing.

The results are grouped:

  • Not translated yet – widgets that hold text and are skipped today. This is where you work.
  • Translated with your settings – widgets you already set up.
  • Configured in code – widgets your theme or a plugin already set up for translation. Nothing
    to do here.
  • No text found – widgets with no text stored in your pages (images, spacers, icons…).

Run the scan again after you add new widgets to your pages or install a new add-on.

Each group, and each widget card, can be folded by clicking its heading; Expand all and
Collapse all fold or unfold everything at once. Widgets you already set up start folded. The
screen remembers what you folded, in this browser.

Working on one page

To see only the widgets used on a particular page, pick it in Show widgets on. The list holds
every page, post and template the scan found a listed widget on, with the number of widgets on
each. Groups with nothing on that page are hidden, and each group’s count shows how many of its
widgets are on the page. Choose All pages to see everything again.

#Choosing what to translate

Each widget is shown as a card: its name, how many times it is used, links to a few pages that use
it, and a table of its settings with an example value taken from your pages.

  • Text fields are ticked for you when the widget is active on your site – the plugin can see
    which settings the widget declares as text (single-line text, multi-line text, rich text).
  • Settings that are not text are greyed out and cannot be ticked: selects, switches, colors,
    icons, numbers. A setting that picks a contact form, a menu or a template is one of these – it
    stores an ID, and translating it would break the link to the form.
  • Link fields are offered but not ticked. Tick one only when the link should lead to a
    different address in each language. Links to pages on your own site are usually handled already
    by the Internal links in content setting.
  • Settings of an inactive widget. If the add-on that provides the widget is switched off, the
    plugin cannot see its settings. It then lists only the values stored in your pages that look like
    text, and ticks none of them.

Always look at the example values before you save. A text field can still hold something that must
not be translated – an HTML ID, a CSS class, a shortcode. Leave those unticked.

Click Save. From then on, every AI translation of a page that uses this widget includes the
ticked settings. To stop, click Stop translating on the card. Translations that already exist
stay as they are.

#Updating pages that are already translated

Saving a widget’s settings does not change your pages, so pages you translated earlier still count
as up to date and will not be translated again on their own.

To bring them up to date, translate them again the usual way – from the Posts screen or the
LATW Translations box of each page. The widget’s card lists how many pages use it, and picking a
page in Show widgets on shows which widgets it holds, so you can see which pages are affected.

Translating a page again sends only the texts that have no translation yet – the newly ticked
settings of that widget – and is billed for those only. The rest of the page keeps its translation.

#What this does not do

  • Texts left at the widget’s default. Elementor stores a setting in the page only when you
    change it. A button label you never touched is not in the page at all – the widget prints its
    built-in text, which comes from the theme or add-on. Translate those under
    LATW Multilingual → Themes & Plugins.
  • Content outside the widget. A widget that shows a contact form, a menu or a post only points
    to it. The form, menu or post is translated on its own – for Contact Form 7 see
    Translating Contact Form 7 Forms.
  • Lists inside lists. Repeater items (a list of tabs, slides, features) are supported. A list
    nested inside a repeater item is not.
  • Elementor 4 (Atomic) widgets from other add-ons. They store text in a different format and
    are not offered on this screen.
  • Built-in widgets. Elementor, Elementor Pro and PowerPack widgets, and WordPress widgets
    placed through Elementor (wp-widget-*), are already covered and cannot be changed here. A
    WordPress widget from your theme with more text than a title (a button label, an intro line) is
    translated only through code – see the Developer reference below.

#Developer reference

The list of widgets and their text settings is in the free version (includes/segments/elementor-text.php);
LATWM_Builder_Segmenters::elementor() turns the texts it finds into the segments of
_elementor_data. The screen stores its choices in the latwmp_elementor_widgets option. A theme
or plugin can declare its widgets in code instead, through the latwm_elementor_widgets_to_translate
filter (with PRO, the older latwmp_elementor_widgets_to_translate works as well) – for example
from a child theme’s functions.php:

add_filter( 'latwm_elementor_widgets_to_translate', function ( $widgets ) {
    $widgets['tj-form'] = array(
        'match'  => array( 'widgetType' => 'tj-form' ),
        // Each entry is a path under the widget's settings.
        'fields' => array(
            array( 'tj_title' ),
            array( 'tj_subtitle' ),
            array( 'button_link', 'url' ), // $settings['button_link']['url']
        ),
        // Repeaters: one group per repeater control ('items' => one group is also accepted).
        'items_groups' => array(
            array(
                'items_field' => 'features',
                'fields'      => array( array( 'feature_text' ) ),
            ),
        ),
    );
    return $widgets;
} );
  • The filter receives the built-in list merged with the choices from the Elementor Widgets
    screen, so code has the last word.

  • A widget declared in code is shown under Configured in code and cannot be edited on the
    screen.

  • Only list settings that hold text a visitor reads. Never list a setting that stores an ID,
    because the translation would replace it.

  • Settings driven by an Elementor dynamic tag are handled automatically: only the tag’s
    before, after and fallback texts are translated.

  • A WordPress widget placed through Elementor (wp-widget-{id_base}) keeps its whole instance
    under settings.wp. Its wp.title is covered for every widget; to add another of its fields,
    declare the nested path:

    $widgets['wp-widget-tj-promo'] = array(
        'match'  => array( 'widgetType' => 'wp-widget-tj-promo' ),
        'fields' => array( array( 'wp', 'button_text' ) ), // $settings['wp']['button_text']
    );
  • A match value ending in * matches by prefix ('widgetType' => 'wp-widget-*').