{"id":178,"date":"2026-11-14T17:45:07","date_gmt":"2026-11-14T17:45:07","guid":{"rendered":"https:\/\/docs.latw.ai\/uncategorized\/translating-elementor\/"},"modified":"2026-11-14T17:45:07","modified_gmt":"2026-11-14T17:45:07","slug":"translating-elementor","status":"publish","type":"post","link":"https:\/\/docs.latw.ai\/pl\/latw-multilingual\/translating-elementor\/","title":{"rendered":"Translating Elementor"},"content":{"rendered":"<p><em>The texts of an Elementor page are kept as segments with a translation memory (free, version 2.8.0<br \/>\nand later) &#8211; see <\/em>Translation Memory and Segments<em>. A text that appears several times is translated<br \/>\nonce, texts you corrected by hand are not replaced by a later automatic translation, and changing<br \/>\none widget in the original only makes that widget&#8217;s text need translating again. This needs<br \/>\n<strong>Elementor<\/strong> ticked under <strong>LATW Multilingual \u2192 Settings \u2192 Translation \u2192 Page builders<\/strong>.<\/em><\/p>\n<p>A page built with Elementor is translated in the Elementor editor itself. Go to <strong>LATW Multilingual<br \/>\n\u2192 Posts<\/strong>, open the <strong>Pages<\/strong> tab and click the pencil next to a language, or use the <strong>LATW<br \/>\nTranslations<\/strong> box of the page. The page opens in Elementor at its address in that language, and<br \/>\n<strong>Save translation<\/strong> stores what you edited as that language&#8217;s version &#8211; the original page is not<br \/>\ntouched.<\/p>\n<p>You can change more than the texts there. A different picture, link or colour stays in that<br \/>\nlanguage. A widget you remove, add or move, or whose text you give a structure of its own (a new<br \/>\nparagraph, bold text the original does not have), keeps what you did &#8211; and only that widget stops<br \/>\nfollowing the original; the rest of the page is still updated from it segment by segment (version<br \/>\n2.8.1 and later). Elementor tells you when a save does this, and the segment editor can restore any<br \/>\nsuch widget from the original. See <em>When you change the layout of a translation<\/em> in <em>Translation<br \/>\nMemory and Segments<\/em>.<\/p>\n<p>This page covers two things that are specific to Elementor: the address (URL slug) of a translated<br \/>\npage, and the widgets that add-ons bring.<\/p>\n<h2>The URL slug of a translation<\/h2>\n<p><em>Available in the free version (version 2.6.5 and later).<\/em><\/p>\n<p>The slug is the last part of a page&#8217;s address: <code>\/en\/services\/consulting\/<\/code> (with languages on<br \/>\nsubdomains or domains: <code>en.example.com\/services\/consulting\/<\/code>). Leave it alone and the<br \/>\ntranslation keeps the original slug; give it one and the English page lives at its own address.<\/p>\n<p><strong>In the Elementor editor.<\/strong> Click the gear icon (<strong>Settings<\/strong>) at the bottom of the panel. Under<br \/>\n<strong>Translation URL (LATW)<\/strong> type the slug into <strong>URL slug<\/strong> and click <strong>Save translation<\/strong>. The field<br \/>\nis empty until a slug has been set, and saving it empty keeps the original slug.<\/p>\n<p><strong>In any editor, including Divi, Beaver Builder, Bricks, Oxygen and WPBakery.<\/strong> Open the page&#8217;s<br \/>\nsegment editor: in the <strong>LATW Translations<\/strong> box, click the list icon next to the language. The<br \/>\n<strong>URL slug<\/strong> field is at the top of the editor. Type the slug and click <strong>Save slug<\/strong> (or press<br \/>\nEnter). It saves at once &#8211; you do not need to save the segments or the page. The field appears once<br \/>\nthe language has a translation. The block editor also has the field in the <strong>Translation URL<\/strong><br \/>\npanel of its sidebar. (Before version 2.8.0 the field was in the <strong>LATW Translations<\/strong> box itself.)<\/p>\n<p>What to know:<\/p>\n<ul>\n<li><strong>The slug is unique within a language.<\/strong> If another page already uses it in that language, a<br \/>\nnumber is added (<code>consulting-2<\/code>). The field then shows the slug that was really stored.<\/li>\n<li><strong>Existing translations keep their slug.<\/strong> Translating a page again, by hand or with AI<br \/>\n(<strong>PRO<\/strong>), never changes a slug that is already set. To change it, edit it here.<\/li>\n<li><strong>Nothing is generated for you.<\/strong> The slug is whatever you type; with <strong>PRO<\/strong>, the <strong>Localize<br \/>\nURLs (slug)<\/strong> setting can fill it in the first time a page is translated.<\/li>\n<li><strong>Old addresses are redirected.<\/strong> A visitor on the original slug of a translated page is sent<br \/>\nto the translated one with a permanent (301) redirect.<\/li>\n<li><strong>Letters and spaces.<\/strong> The slug is turned into a normal URL form when you save it: lower case,<br \/>\nhyphens instead of spaces, accented letters replaced by plain ones. Letters are spelled the way<br \/>\nthe translation&#8217;s language writes them without accents (version 2.8.2 and later): in German<br \/>\n<code>\u00fc<\/code> becomes <code>ue<\/code> and <code>\u00df<\/code> becomes <code>ss<\/code> (<code>\u00fcber<\/code> \u2192 <code>ueber<\/code>), in Danish <code>\u00f8<\/code> becomes <code>oe<\/code>; other<br \/>\nlanguages simply drop the accent (<code>\u00e9t\u00e9<\/code> \u2192 <code>ete<\/code>). Slugs saved before keep their spelling.<\/li>\n<\/ul>\n<h3>Child pages<\/h3>\n<p>The address of a child page contains the slug of every parent: <code>\/en\/services\/consulting\/<\/code>. Each<br \/>\nlevel takes its own translated slug &#8211; translate the parent&#8217;s slug and the child&#8217;s address follows<br \/>\n(version 2.6.5 and later). A level that has no translated slug keeps the original one, so you can<br \/>\ntranslate a parent without touching its children.<\/p>\n<ul>\n<li>The old, half-translated addresses are redirected to the full translated one.<\/li>\n<li>A path with a parent that does not match the page &#8211; <code>\/en\/other-parent\/consulting\/<\/code> &#8211; shows<br \/>\n&#8220;page not found&#8221; instead of the child page.<\/li>\n<li>The address in the original language is never changed.<\/li>\n<\/ul>\n<h2>Elementor 4 atomic widgets<\/h2>\n<p><em>Available in <strong>PRO<\/strong> (version 2.6.1 and later).<\/em><\/p>\n<p>The new widgets of Elementor 4 &#8211; <strong>Heading<\/strong>, <strong>Paragraph<\/strong> and <strong>Button<\/strong> from the <em>Atomic<\/em> editor<\/p>\n<ul>\n<li>are translated by AI together with the rest of the page. The Heading, Paragraph and Button of the<br \/>\nolder, classic widget set are covered as before. Other atomic widgets (tabs, accordion, image text)<br \/>\nare not translated yet, and add-ons&#8217; own atomic widgets cannot be added on the <strong>Elementor Widgets<\/strong><br \/>\nscreen.<\/li>\n<\/ul>\n<h2>Translating custom widgets<\/h2>\n<p><em>Available in <strong>PRO<\/strong> (version 2.4.0 and later).<\/em><\/p>\n<p>When AI translates an Elementor page, it does not send the whole page layout to the translation<br \/>\nengine. It sends only the texts it knows are texts: a heading&#8217;s title, a button&#8217;s label, a tab&#8217;s<br \/>\ncontent. For that it keeps a list of widgets and of the settings in each widget that hold text.<br \/>\nThe list covers the widgets of Elementor, Elementor Pro and PowerPack for Elementor.<\/p>\n<p>A widget that is not on the list is <strong>skipped<\/strong>. That is the case for widgets your theme brings<br \/>\nwith it, and for widgets from add-on packs the plugin does not know. The rest of the page is<br \/>\ntranslated, but the texts inside those widgets stay in the original language. No error is shown,<br \/>\nbecause nothing failed: the plugin simply did not know those settings were text.<\/p>\n<p>The <strong>Elementor Widgets<\/strong> screen lets you close that gap yourself, without code: scan the site,<br \/>\nsee which widgets are not translated, and tick the settings that hold text.<\/p>\n<p>This section is about widgets an add-on <strong>built from scratch<\/strong> for Elementor. A widget whose type<br \/>\nstarts with <code>wp-widget-<\/code> is a different thing &#8211; it is a classic <strong>WordPress<\/strong> widget (Search,<br \/>\nCategories, Recent Posts, Tag Cloud, or a theme&#8217;s own widget class), dragged onto the page from<br \/>\nElementor&#8217;s <strong>WordPress<\/strong> panel. Those are already covered and do not appear on this screen: the<br \/>\n<strong>Title<\/strong> you typed into one is translated together with the page, and so are the body of a<br \/>\n<strong>Text<\/strong> or <strong>Custom HTML<\/strong> widget and the alternative text and caption of an <strong>Image<\/strong> widget<br \/>\n(PRO version 2.5.1 and later). What else such a widget shows &#8211; its built-in heading, the posts or<br \/>\ncategories it lists &#8211; is explained in <em>Translating Widgets<\/em>.<\/p>\n<h3>When you need this<\/h3>\n<ul>\n<li>A section of an otherwise translated page is still in the original language, and that section<br \/>\nis a widget from your theme or from an add-on.<\/li>\n<li>You installed a new Elementor add-on and want its widgets translated too.<\/li>\n<\/ul>\n<p>If a whole Elementor page is not translated, this screen is not the cause &#8211; check the page in the<br \/>\n<strong>LATW Translations<\/strong> box first.<\/p>\n<h3>Scanning the site<\/h3>\n<p>Go to <strong>LATW Multilingual \u2192 Elementor Widgets<\/strong> and click <strong>Scan site<\/strong>. The plugin reads every<br \/>\nElementor page, post and template (including headers, footers and popups built with the Theme<br \/>\nBuilder) and lists each widget it does not know. The scan reads your content only; it does not<br \/>\nchange anything and does not contact the translation engine, so it costs nothing.<\/p>\n<p>The results are grouped:<\/p>\n<ul>\n<li><strong>Not translated yet<\/strong> &#8211; widgets that hold text and are skipped today. This is where you work.<\/li>\n<li><strong>Translated with your settings<\/strong> &#8211; widgets you already set up.<\/li>\n<li><strong>Configured in code<\/strong> &#8211; widgets your theme or a plugin already set up for translation. Nothing<br \/>\nto do here.<\/li>\n<li><strong>No text found<\/strong> &#8211; widgets with no text stored in your pages (images, spacers, icons\u2026).<\/li>\n<\/ul>\n<p>Run the scan again after you add new widgets to your pages or install a new add-on.<\/p>\n<p>Each group, and each widget card, can be folded by clicking its heading; <strong>Expand all<\/strong> and<br \/>\n<strong>Collapse all<\/strong> fold or unfold everything at once. Widgets you already set up start folded. The<br \/>\nscreen remembers what you folded, in this browser.<\/p>\n<h4>Working on one page<\/h4>\n<p>To see only the widgets used on a particular page, pick it in <strong>Show widgets on<\/strong>. The list holds<br \/>\nevery page, post and template the scan found a listed widget on, with the number of widgets on<br \/>\neach. Groups with nothing on that page are hidden, and each group&#8217;s count shows how many of its<br \/>\nwidgets are on the page. Choose <strong>All pages<\/strong> to see everything again.<\/p>\n<h3>Choosing what to translate<\/h3>\n<p>Each widget is shown as a card: its name, how many times it is used, links to a few pages that use<br \/>\nit, and a table of its settings with an example value taken from your pages.<\/p>\n<ul>\n<li><strong>Text fields are ticked for you<\/strong> when the widget is active on your site &#8211; the plugin can see<br \/>\nwhich settings the widget declares as text (single-line text, multi-line text, rich text).<\/li>\n<li><strong>Settings that are not text are greyed out<\/strong> and cannot be ticked: selects, switches, colors,<br \/>\nicons, numbers. A setting that picks a contact form, a menu or a template is one of these &#8211; it<br \/>\nstores an ID, and translating it would break the link to the form.<\/li>\n<li><strong>Link fields are offered but not ticked.<\/strong> Tick one only when the link should lead to a<br \/>\ndifferent address in each language. Links to pages on your own site are usually handled already<br \/>\nby the <strong>Internal links in content<\/strong> setting.<\/li>\n<li><strong>Settings of an inactive widget.<\/strong> If the add-on that provides the widget is switched off, the<br \/>\nplugin cannot see its settings. It then lists only the values stored in your pages that look like<br \/>\ntext, and ticks none of them.<\/li>\n<\/ul>\n<p>Always look at the example values before you save. A text field can still hold something that must<br \/>\nnot be translated &#8211; an HTML ID, a CSS class, a shortcode. Leave those unticked.<\/p>\n<p>Click <strong>Save<\/strong>. From then on, every AI translation of a page that uses this widget includes the<br \/>\nticked settings. To stop, click <strong>Stop translating<\/strong> on the card. Translations that already exist<br \/>\nstay as they are.<\/p>\n<h3>Updating pages that are already translated<\/h3>\n<p>Saving a widget&#8217;s settings does not change your pages, so pages you translated earlier still count<br \/>\nas up to date and will not be translated again on their own.<\/p>\n<p>To bring them up to date, translate them again the usual way &#8211; from the <strong>Posts<\/strong> screen or the<br \/>\n<strong>LATW Translations<\/strong> box of each page. The widget&#8217;s card lists how many pages use it, and picking a<br \/>\npage in <strong>Show widgets on<\/strong> shows which widgets it holds, so you can see which pages are affected.<\/p>\n<p>Translating a page again sends only the texts that have no translation yet &#8211; the newly ticked<br \/>\nsettings of that widget &#8211; and is billed for those only. The rest of the page keeps its translation.<\/p>\n<h3>What this does not do<\/h3>\n<ul>\n<li><strong>Texts left at the widget&#8217;s default.<\/strong> Elementor stores a setting in the page only when you<br \/>\nchange it. A button label you never touched is not in the page at all &#8211; the widget prints its<br \/>\nbuilt-in text, which comes from the theme or add-on. Translate those under<br \/>\n<strong>LATW Multilingual \u2192 Themes &amp; Plugins<\/strong>.<\/li>\n<li><strong>Content outside the widget.<\/strong> A widget that shows a contact form, a menu or a post only points<br \/>\nto it. The form, menu or post is translated on its own &#8211; for Contact Form 7 see<br \/>\n<em>Translating Contact Form 7 Forms<\/em>.<\/li>\n<li><strong>Lists inside lists.<\/strong> Repeater items (a list of tabs, slides, features) are supported. A list<br \/>\nnested inside a repeater item is not.<\/li>\n<li><strong>Elementor 4 (Atomic) widgets from other add-ons.<\/strong> They store text in a different format and<br \/>\nare not offered on this screen.<\/li>\n<li><strong>Built-in widgets.<\/strong> Elementor, Elementor Pro and PowerPack widgets, and WordPress widgets<br \/>\nplaced through Elementor (<code>wp-widget-*<\/code>), are already covered and cannot be changed here. A<br \/>\nWordPress widget from your theme with more text than a title (a button label, an intro line) is<br \/>\ntranslated only through code &#8211; see the <em>Developer reference<\/em> below.<\/li>\n<\/ul>\n<h3>Developer reference<\/h3>\n<p>The list of widgets and their text settings is in the free version (<code>includes\/segments\/elementor-text.php<\/code>);<br \/>\n<code>LATWM_Builder_Segmenters::elementor()<\/code> turns the texts it finds into the segments of<br \/>\n<code>_elementor_data<\/code>. The screen stores its choices in the <code>latwmp_elementor_widgets<\/code> option. A theme<br \/>\nor plugin can declare its widgets in code instead, through the <code>latwm_elementor_widgets_to_translate<\/code><br \/>\nfilter (with PRO, the older <code>latwmp_elementor_widgets_to_translate<\/code> works as well) &#8211; for example<br \/>\nfrom a child theme&#8217;s <code>functions.php<\/code>:<\/p>\n<pre><code class=\"language-php\">add_filter( 'latwm_elementor_widgets_to_translate', function ( $widgets ) {\n    $widgets['tj-form'] = array(\n        'match'  =&gt; array( 'widgetType' =&gt; 'tj-form' ),\n        \/\/ Each entry is a path under the widget's settings.\n        'fields' =&gt; array(\n            array( 'tj_title' ),\n            array( 'tj_subtitle' ),\n            array( 'button_link', 'url' ), \/\/ $settings['button_link']['url']\n        ),\n        \/\/ Repeaters: one group per repeater control ('items' =&gt; one group is also accepted).\n        'items_groups' =&gt; array(\n            array(\n                'items_field' =&gt; 'features',\n                'fields'      =&gt; array( array( 'feature_text' ) ),\n            ),\n        ),\n    );\n    return $widgets;\n} );<\/code><\/pre>\n<ul>\n<li>\n<p>The filter receives the built-in list merged with the choices from the <strong>Elementor Widgets<\/strong><br \/>\nscreen, so code has the last word.<\/p>\n<\/li>\n<li>\n<p>A widget declared in code is shown under <strong>Configured in code<\/strong> and cannot be edited on the<br \/>\nscreen.<\/p>\n<\/li>\n<li>\n<p>Only list settings that hold text a visitor reads. Never list a setting that stores an ID,<br \/>\nbecause the translation would replace it.<\/p>\n<\/li>\n<li>\n<p>Settings driven by an Elementor dynamic tag are handled automatically: only the tag&#8217;s<br \/>\n<em>before<\/em>, <em>after<\/em> and <em>fallback<\/em> texts are translated.<\/p>\n<\/li>\n<li>\n<p>A WordPress widget placed through Elementor (<code>wp-widget-{id_base}<\/code>) keeps its whole instance<br \/>\nunder <code>settings.wp<\/code>. Its <code>wp.title<\/code> is covered for every widget; to add another of its fields,<br \/>\ndeclare the nested path:<\/p>\n<pre><code class=\"language-php\">$widgets['wp-widget-tj-promo'] = array(\n    'match'  =&gt; array( 'widgetType' =&gt; 'wp-widget-tj-promo' ),\n    'fields' =&gt; array( array( 'wp', 'button_text' ) ), \/\/ $settings['wp']['button_text']\n);<\/code><\/pre>\n<\/li>\n<li>\n<p>A <code>match<\/code> value ending in <code>*<\/code> matches by prefix (<code>'widgetType' =&gt; 'wp-widget-*'<\/code>).<\/p>\n<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>The texts of an Elementor page are kept as segments with a translation memory (free, version 2.8.0 and later) &#8211; see Translation Memory and Segments. A\u2026<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_latwm_translated_slug":"","footnotes":""},"categories":[4],"tags":[],"class_list":["post-178","post","type-post","status-publish","format-standard","hentry","category-latw-multilingual"],"_links":{"self":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/178","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/comments?post=178"}],"version-history":[{"count":3,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/178\/revisions"}],"predecessor-version":[{"id":221,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/178\/revisions\/221"}],"wp:attachment":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/media?parent=178"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/categories?post=178"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/tags?post=178"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}