Your site has one menu structure, shared by every language. The plugin does not build a second
\nmenu per language – it translates the labels of the menu you already have, and rewrites each link
\nso it points at the page in the active language. Add an item to the menu once and it appears in
\nall languages.<\/p>\n
Turn it on under LATW Multilingual \u2192 Settings \u2192 Translation \u2192 Other objects<\/strong>, with Translating menu labels by hand is part of the free version. Translating them automatically with Where a label is translated depends on where WordPress keeps it, and that is not the same for This is the ordinary case: you dragged Contact<\/strong> out of the Pages box in Nothing to do.<\/strong> Translate the page, and its menu label follows automatically. It is the same These items are deliberately not<\/strong> listed on the Strings page. If you cannot find a menu item An item pointing at a page that has no<\/strong> translation yet keeps the original title – there is A Custom Link<\/strong> is a label and a URL you typed yourself, so there is no page behind it to take Go to LATW Multilingual \u2192 Strings<\/strong> and set the Type<\/strong> filter to Menus<\/strong>. Each menu item is Leave a field empty and the original is used for that language.<\/p>\n Translating the label does not change the URL. A custom link to a page on your own site If the target is an ordinary page on your site, prefer a real Page<\/strong> item over a custom link. The third case is the one that surprises people. If you added the page About<\/strong> to the menu and That item now behaves like a custom link: the page’s translated title is ignored, and the label So if one menu label refuses to change language while every other one does, open This is the most common support question about Elementor, and it is really a question about where The title is not part of the Elementor canvas.<\/strong> It is the WordPress post title, the same field When you open a translation with the Edit<\/strong> button in the LATW Translations<\/strong> box (or from the The panel opens on General Settings<\/strong>, and Title<\/strong> is the first field. Change it there, save, The field is filled with the translation you already have, so if you translated the page before If you changed Title<\/strong> in Page Settings, saved, and the big heading on the page is still in the A quick way to tell them apart: open the page for editing in Elementor and click the heading. If Elementor’s Hide Title<\/strong> switch, in the same Page Settings panel, only stops the theme from The title in the browser tab and in Google is produced by your SEO plugin, not by Elementor. It Your site has one menu structure, shared by every language. The plugin does not build a second menu per language – it translates the labels of\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-74","post","type-post","status-publish","format-standard","hentry","category-latw-multilingual"],"_links":{"self":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/74","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=74"}],"version-history":[{"count":2,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/74\/revisions"}],"predecessor-version":[{"id":119,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/74\/revisions\/119"}],"wp:attachment":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/media?parent=74"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/categories?post=74"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/tags?post=74"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nNavigation menu labels (custom links & label overrides)<\/strong>.<\/p>\n
\nAI – one item, or every item in every language at once – requires PRO<\/strong>.<\/em><\/p>\n
\nevery item. There are three cases.<\/p>\nItems that follow a page or post title<\/h2>\n
\nAppearance \u2192 Menus<\/strong> and left the label alone. WordPress stores no label of its own for that
\nitem – it just shows the title of the page it points to.<\/p>\n
\ntext, so it cannot drift. The same applies to items pointing at a category, tag or product
\ncategory: translate the term and the menu follows.<\/p>\n
\nthere, this is almost always why – and it means the item is already handled.<\/p>\n
\nnothing to show instead. Its link still carries the language prefix, and what the visitor gets
\nthere is decided by the Missing translation<\/strong> setting under
\nLATW Multilingual \u2192 Settings \u2192 Languages<\/strong> (show the default-language content, redirect to the
\ndefault language, or return a 404).<\/p>\nCustom links<\/h2>\n
\nthe text from. The label is stored on the menu item and has to be translated.<\/p>\n
\none row, with the menu it belongs to shown underneath it. Click the item’s name to open it, or
\nclick the pencil next to a single language in the Languages<\/strong> column to go straight to that
\nlanguage. You get three fields:<\/p>\n\n
The URL of a custom link<\/h3>\n
\n(https:\/\/example.com\/contact\/<\/code>) is rewritten to the active language by the
\nInternal links in content<\/strong> setting under LATW Multilingual \u2192 Settings \u2192 Languages<\/strong> –
\n“Rewrite hard-coded links inside content to the active language”. With that setting off, a custom
\nlink keeps sending visitors to the default-language page even while the rest of the menu is
\ntranslated.<\/p>\n
\nIts label and its URL are then both handled for you, and neither can be forgotten.<\/p>\nOverridden navigation labels<\/h2>\n
\nthen typed About Me<\/strong> over the label in Appearance \u2192 Menus<\/strong>, WordPress stops following the
\npage title and stores About Me<\/em> on the menu item instead.<\/p>\n
\nhas to be translated on its own. It appears on the Strings<\/strong> page under type Menus<\/strong>, with the
\nmenu name next to it, and is translated exactly like a custom link above.<\/p>\n
\nAppearance \u2192 Menus<\/strong> and look at that item: its Navigation Label<\/strong> almost certainly differs
\nfrom the title of the page it points to. Either translate the item on the Strings page, or clear
\nthe override so the item follows the page title again.<\/p>\nWhat this does not do<\/h2>\n
\n
\nin one language. Menu translation covers the text, not the structure.<\/li>\n
\nlabel and is not shown to visitors.<\/li>\n
\na menu plugin are that plugin’s own data and are not covered here.<\/li>\n
\nAppearance \u2192 Menus<\/strong>. A block theme’s Navigation block<\/strong> is a different mechanism: its labels
\nare block attributes stored in the template, not menu items, so they do not pass through this
\nlayer. They can only be translated under Strings \u2192 Blocks<\/strong>, and only when the theme or plugin
\nthat registered the block declares those attributes as translatable in its wpml-config.xml<\/code>.
\nIf your theme uses the Navigation block and no labels show up there, that declaration is
\nmissing.<\/li>\n<\/ul>\nThe page title an Elementor page shows<\/h2>\n
\nthe title lives.<\/p>\n
\nthe menu reads, and inside Elementor it sits in the settings panel – not in the layout you are
\ndragging widgets around in.<\/p>\n
\nPosts<\/strong> page), an Elementor page opens in Elementor itself, in that language – provided
\nElementor<\/strong> is ticked under LATW Multilingual \u2192 Settings \u2192 Translation \u2192 Page builders<\/strong>. To
\nreach the title:<\/p>\n\n
\nPage Settings<\/strong> (or Post Settings<\/strong>, Product Settings<\/strong> – it is named after the content
\ntype). In older Elementor versions without the top bar, it is the gear icon<\/strong> at the bottom
\nleft of the panel.<\/li>\n
\nand the page title, the menu label, the breadcrumb and the browser tab all change with it.<\/p>\n
\nopening Elementor you will see the translated title waiting for you – not the original.<\/p>\nWhen the title on screen still does not change<\/h3>\n
\noriginal language, then that heading is not the page title. Two things look identical to a
\nvisitor:<\/p>\n\n
\ninto a Heading widget at the top of the page, with the real page title hidden. That text is part
\nof the layout, so you translate it in the canvas<\/strong>, by clicking the widget in the translation
\nsession and editing it like any other text – not in Page Settings.<\/li>\n
\nPro’s Theme Builder) draws the heading with a Post Title<\/strong> widget, it does read the page title,
\nso Page Settings is<\/em> the right place – give the save a moment and clear any caching plugin.<\/li>\n<\/ul>\n
\nthe panel that opens says Heading<\/strong>, it is layout text. If it says Post Title<\/strong>, it comes from
\nPage Settings.<\/p>\nHide Title<\/h3>\n
\nprinting the title – it does not change it. It is per page, not per language, so it applies to
\nevery language at once.<\/p>\nThe browser tab and search results<\/h3>\n
\nfollows the page title unless you wrote a custom SEO title. That custom string is a separate field
\nand is only translated when Custom fields declared by themes and plugins (e.g. SEO titles and
\ndescriptions)<\/strong> is enabled under LATW Multilingual \u2192 Settings \u2192 Translation \u2192 Other objects<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"