Your Cart
WPML widget translation

How to Translate WordPress Widgets with WPML Across Classic and Block-Based Widget Areas

Translating WordPress widgets with WPML is not one universal procedure. The correct workflow depends on the way the widget is stored and displayed: it may belong to a block-based widget area, be a legacy non-block widget, appear through a Legacy Widget block, or come from a custom plugin, theme or page builder. These distinctions matter because WPML places the relevant translation controls in different areas of the WordPress administration panel.

Before changing anything, identify the widget environment used by the site and confirm that the required WPML components are active. This guide explains how to translate block-based widgets, handle legacy widget strings that are not immediately visible, display different widgets for selected languages and approach custom widgets without assuming automatic compatibility.

What Counts as a WordPress Widget in a Multilingual Site?

In a multilingual WordPress site, a widget can refer to more than one type of content. Block-based widgets are built from blocks and are placed in widget areas managed by the block-based Widgets Editor. Legacy widgets are older, non-block widgets that may still be available in a site’s widget configuration. A legacy widget can also appear inside a block-based widget area through the Legacy Widget block, which allows existing non-block or third-party widgets to be managed in that environment.

Custom widgets are supplied by a plugin, theme or page builder and may not follow the same translation path as standard widgets. Their text can depend on how the particular product stores and outputs it, so their behavior should be checked on the specific site setup.

The active theme is also important. Classic themes that support widget areas may expose the traditional Appearance → Widgets screen. Block themes use the Site Editor instead, and the traditional widget menu may not be available. Do not select a WPML workflow until you know which editor and widget areas are actually present.

Before Translating Widgets with WPML

Start by checking the translation setup rather than editing individual widgets immediately. WPML requires the WPML core plugin and WPML String Translation to translate widget text and related interface strings. If String Translation is not active, widget titles or content may not be available in the relevant translation workflow.

Next, establish how the target widget is managed:

  • Check whether the site uses classic widget areas with block-based widgets.
  • Identify whether the target is an older non-block widget or a Legacy Widget block.
  • Check whether a block theme uses the Site Editor instead of the traditional Widgets screen.
  • For a custom widget, note which plugin, theme or page builder supplies it.

Before changing widget assignments or language visibility on a production site, create a backup or test the changes on staging where possible. This is a practical precaution that makes it easier to review the front-end result without treating every configuration change as final.

How to Translate Block-Based Widgets

For classic, block-based widgets placed in widget areas, the main WPML workflow starts in the translation dashboard. Open WPML → Translations → Dashboard, then expand the Block section. Select the relevant widget area containing the blocks you want to translate and choose an available translation method.

The important point is to select the widget area, not simply search for a widget title in the wrong translation category. First inspect the WordPress widget editor and determine where the target block is placed. Then choose that same area in the Block section of the WPML dashboard. Complete the translation using the method available for the site’s WPML configuration.

This procedure applies when the site has a theme with widget areas and the target content is managed as a block-based widget area. It should not be treated as proof that every block or third-party widget is automatically compatible with WPML. If the widget is actually a legacy widget displayed through a block, use the legacy-widget workflow instead.

Identifying the Correct Block-Based Widget Area

Widget areas can contain several blocks, and the same type of block may appear in more than one location. Before translating, check the area that contains the target content and compare it with the areas listed under the Block section in the WPML Translations dashboard. This reduces the risk of translating a different sidebar, footer or other widget area than the one visible on the relevant page.

Also distinguish a true block-based widget from a non-block widget placed inside the Legacy Widget block. The visual editor alone may not be enough to determine the translation route, so identify how the widget is represented in the configuration before selecting the WPML workflow.

How to Translate Legacy WordPress Widgets

Legacy widgets that are not block-based use a different translation path. Open WPML → Translations and look for the relevant widget text in Other texts (Strings). Select the strings associated with the widget and choose an available translation method from the dashboard.

This workflow is intended for older widget content such as text that is stored as a string rather than as a block-based widget area. Keep it separate from the Block workflow: selecting the wrong category can make it appear that the widget text is unavailable even when WPML can expose it through String Translation.

After translating the relevant strings, review the front end in the appropriate language. Confirm that the widget appears in the expected area and that the translated title or content is connected to the correct widget instance. If the text is still missing from the dashboard, use the additional procedure below rather than assuming that the widget cannot be translated.

When Legacy Widget Text Is Not Visible

Some legacy widget titles or content may not initially appear in the string list. In that situation, open WPML → Translations → Strings and use Admin Texts Translation from the utilities area. Locate the relevant widget texts, select them and add them to String Translation.

Once the texts have been made available, return to the string translation workflow and translate them from the WPML dashboard. This is a targeted troubleshooting step for missing strings. It does not mean that every setting from every widget will be exposed in exactly the same way, because the available text depends on the widget and the way it stores its content.

How to Display Different Widgets for Each Language

Translating one widget does not always meet the site’s needs. Sometimes each language should show a different widget instance or different content. When the relevant screen is available, open Appearance → Widgets, select the widget and open the Display on language panel in the widget settings sidebar.

Choose the language in which that widget should appear. You can use this control to assign visibility to selected languages, allowing different widget instances or content to be shown rather than displaying one translated instance everywhere.

The exact location and availability of these controls depend on the site’s widget editor and theme setup. Block themes may use the Site Editor instead of the traditional Widgets screen, so do not assume that every installation exposes the same menu. After changing language visibility, test the front end in each relevant language and check that the intended widget is displayed.

Custom Widgets: Registration and Compatibility Checks

Custom widgets require an additional step: they must be registered in WPML before their text can be translated. After registration, the translatable text is handled through Other texts (Strings) in the WPML Translations dashboard.

This requirement is especially important for widgets supplied by third-party plugins, themes or page builders. A custom widget should not be assumed to behave like a built-in widget simply because it appears in the same editor. Default widgets covered by a supported integration may follow a documented workflow, while an add-on or independently supplied widget may require separate verification.

For a site owner, the practical approach is to identify the product that supplies the widget, confirm that the widget has been registered in WPML and then check whether its visible text appears in Other texts (Strings). Test the result with the specific plugin, theme or page builder used on the site. WPML documentation does not establish automatic support for every custom widget, and compatibility can depend on how the widget stores and outputs its text.

Troubleshooting Missing or Untranslated Widget Text

When widget translation does not appear as expected, work through the setup in a fixed order. First verify that the WPML core plugin and WPML String Translation are active. Without String Translation, text stored as strings may not be available for translation.

Next, identify the widget type again. A block-based widget area belongs in the Block section of WPML → Translations → Dashboard. A legacy or string-based widget belongs in Other texts (Strings). A custom widget must be registered before its text can follow that path.

If a legacy widget title, content or related text is not listed, open WPML → Translations → Strings and use Admin Texts Translation to find and add the relevant text to String Translation. Then return to the translation workflow.

  • Confirm that you selected the widget area containing the target block.
  • Check whether a non-block widget is being displayed through the Legacy Widget block.
  • Verify that the widget is rendered in the intended area on the front end.
  • Check language visibility settings when different widget instances are used.
  • Retest the front end after changing a translation or display condition.
  • Review the specific plugin, theme or page builder when a custom widget remains untranslated.

Exact labels and screen availability can vary with the active theme, installed WPML components and product version. A missing menu or different label is therefore not, by itself, evidence that the widget is incompatible. At the same time, avoid a universal compatibility assumption when a particular third-party widget does not translate as expected.

The reliable decision path is to identify the site’s widget environment first, then choose the matching WPML workflow. Use the Block section for block-based widget areas, Other texts (Strings) for legacy widgets, Admin Texts Translation when relevant strings are missing, and language display conditions when different widgets are needed for different languages. Register custom widgets before translating them and verify third-party behavior on the specific site setup. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.

One comment

Comments are closed.

Free Worldwide shipping

You can download the products right away at wpbetterplugins.com

Immediate delivery

After the payment is credited, the product is ready for download

International Warranty

Offered in the country of usage

100% Secure Checkout

Stripe / Apple Pay / Google Pay / MasterCard / Visa

Zadzwoń