Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Plugin how-tos · Guide

How to Translate Footer with Polylang (Step by Step)

How to Translate Footer with Polylang (Step by Step)

Short answer

Give each language its own footer content. Set a language on each footer widget, translate widget titles and theme text in Languages > Translations, assign a footer menu per language, and use one footer template per language in block themes or page builders.

Key takeaways

  • Footers mix widgets, menus, theme text and templates, and each is translated in a different place.
  • Set a language on every footer widget so only the right version shows.
  • Translate shared strings in Languages > Translations.
  • Create one footer menu per language and assign it in Manage Locations.
  • Block theme and page builder footers need one template per language or Polylang Pro support.
  • Clear all caches before deciding a translation is not working.

You translate a footer with Polylang by giving each language its own footer content: set widget languages, translate strings in Languages > Translations, assign a footer menu per language, and use language-specific templates for block themes or page builders.

Polylang does not translate text automatically. It lets you create a separate version of each piece of content, then shows the right version based on the visitor's language.

A footer is tricky because it is not one thing. It can be made of widgets, a menu, a copyright line in the theme, a template part in a block theme, or a page builder template. Each one is translated in a different place.

This guide walks through every type in turn. If Polylang is not set up yet, start with our guide on how to use the Polylang plugin and come back once you have at least two languages.

Before you translate anything, check how your footer is built, because the method depends on whether it uses widgets, menus, theme options, a block template part or a page builder template.

Here is a quick way to tell:

  • Go to Appearance > Widgets. If you see a Footer area with blocks or widgets in it, your footer uses widgets.
  • Go to Appearance > Menus and look for a footer menu location.
  • Go to Appearance > Editor. If this exists, you have a block theme and the footer is a template part.
  • If you use Elementor, Divi or a similar builder, check its theme builder for a footer template.
  • Check Appearance > Customize for a copyright or footer text field.

Many sites mix several of these. A common setup is a widget area for links, a footer menu, and a copyright line from the theme. Note each part down so you do not miss one.

Footer partWhere to translate it in Polylang
Classic widgetsLanguage setting on each widget
Widget titles and site textLanguages > Translations
Footer menuOne menu per language in Appearance > Menus
Theme copyright textLanguages > Translations, or a code snippet
Block theme template partPolylang Pro full site editing support, or blocks per language
Page builder footerOne footer template per language

For footer widgets, add one widget per language to the footer area and use Polylang's language setting on each widget so it only shows for that language.

Polylang adds a language option to widgets. By default a widget shows for all languages. You can limit it to one language instead.

The steps look like this:

  1. Go to Appearance > Widgets and open the footer widget area.
  2. Add or open the widget for your first language, for example English.
  3. Find the Polylang language option on the widget and choose English.
  4. Add a second copy of the widget, write the content in your second language, and set its language to that language.
  5. Save and repeat for each language and each widget.

Your footer area will look busy in the admin because it holds every language version. On the front end, visitors only see the widgets for their current language.

Where the language option appears depends on your WordPress setup. With the classic widgets screen, it shows as a dropdown inside each widget. With the block-based widget editor, Polylang's option may be in the block settings, and older Polylang versions handled block widgets less well. If you cannot find it, check the Polylang plugin page for your version's notes, or install the Classic Widgets plugin.

For general help with widget areas, see our guide on adding a footer widget in WordPress.

Shared text such as widget titles, the site title, the tagline and some theme strings is translated in Languages > Translations, where Polylang lists every registered string with a box for each language.

This screen used to be called Strings translations. It holds short pieces of text that are not posts or pages.

To use it:

  1. Go to Languages > Translations.
  2. Use the group filter or search box to find your footer strings, such as a widget title.
  3. Type the translation in the box for each language.
  4. Click Save changes.

If a widget is set to All languages, Polylang usually registers its title here. This lets you keep one widget and only translate the heading, which suits simple text that has no links.

The Polylang strings translation documentation explains which strings appear and how themes add their own.

Create a separate footer menu for each language, then assign each one to the footer menu location for that language in Appearance > Menus > Manage Locations.

Polylang duplicates every menu location once per language. If your theme has a location called Footer Menu, you will see Footer Menu English and Footer Menu French, or similar.

Follow these steps:

  1. Build your footer menu in the main language and save it, for example as Footer EN.
  2. Create a new menu called Footer FR and add the translated pages and links.
  3. Open Manage Locations.
  4. Assign each menu to the matching language location.
  5. Save.

Link to the translated pages, not the originals. If you add the English About page to the French menu, French visitors will jump back to English.

In block themes, the footer often uses a Navigation block instead of a menu location. In that case, the menu is part of the template part, so see the block theme section below.

If the copyright line comes from theme options or the Customizer, check Languages > Translations first; if it is not listed there, you need a theme that supports Polylang or a short code change.

Some themes register their footer text with Polylang so it appears in the strings list. Popular themes such as Astra publish their own instructions, for example Astra's guide to translating widgets with Polylang.

If your theme does not, there are three common options:

  • Disable the theme's copyright field and put the text in a footer widget instead, then translate it as a widget.
  • Use a footer builder or block that supports languages.
  • Register the text yourself with a small code snippet.

For developers, Polylang provides functions such as pll_register_string() to add a string to the Translations screen and pll__() or pll_e() to output the translated value. In a child theme, the footer text could look like this:

// In functions.php of a child theme
add_action( 'init', function () {
    if ( function_exists( 'pll_register_string' ) ) {
        pll_register_string( 'footer-copyright', 'All rights reserved.', 'Footer' );
    }
} );

// In footer.php
<?php if ( function_exists( 'pll_e' ) ) { pll_e( 'All rights reserved.' ); } ?>

After adding the code, the string appears in Languages > Translations under the Footer group. Full details are in the Polylang function reference.

Always make code changes in a child theme so a theme update does not wipe them. Take a backup before you edit theme files.

In a block theme, the footer is a template part edited in Appearance > Editor; Polylang Pro adds full site editing support for translating template parts, while free users often rely on language-aware blocks or patterns.

Block themes such as Twenty Twenty-Four store the footer as a template part. That template part is shared by every language unless something tells WordPress otherwise.

Your options:

  • Polylang Pro: recent Pro versions add support for site editor content, including template parts. Check the Polylang Pro documentation for how your version handles it.
  • Language-specific blocks: some blocks and plugins can show content only for a given language.
  • Patterns: keep a synced pattern for each language and insert it in a way that only one shows per language.

Because this area of Polylang has changed across versions, read the current documentation before you build a workaround. What needed custom code a few versions ago may now be built in.

You can read about how template parts work in the Site Editor documentation on WordPress.org.

With a page builder, create one footer template per language, then set display conditions or language settings so each language loads its own footer.

Page builders store footers as templates, which are a kind of post. If Polylang can treat those templates as translatable, you can link the language versions together like any other post.

The usual workflow:

  1. Design the footer in your main language.
  2. Duplicate it and translate the text and links.
  3. Mark each template with its language, or use the builder's conditions so each template only loads for one language.
  4. Check the front end in each language.

Elementor support depends on your setup, since some features need an extra connector plugin. Our article on whether Polylang works with Elementor covers this in more detail.

Our guide to editing the footer in Elementor shows where the footer template lives.

A footer in the wrong language usually means a widget is still set to All languages, the menu location for that language is empty, the text is hard-coded in the theme, or a cache is serving an old page.

Work through these checks:

  • Widget language: open each footer widget and confirm its language is set. A widget left on All languages shows everywhere.
  • Menu location: confirm every language has a menu assigned in Manage Locations.
  • Missing string: if the text is not in Languages > Translations, the theme does not register it.
  • Hard-coded text: some themes print footer text directly in PHP, which Polylang cannot see.
  • Cache: clear your caching plugin, server cache and CDN cache, then reload in a private window.
  • Language detection: make sure you are really viewing the translated URL, such as /fr/, and not the default language.

If the language switcher itself misbehaves, our guide to fixing the Polylang language switcher covers the common causes.

What are good habits for multilingual footers?

Keep the footer simple, link only to translated pages, and recheck every language after theme, plugin or menu changes.

A few habits save time later:

  • Fewer parts: a footer built from one or two widgets is much easier to maintain than one with five sources of text.
  • Naming: name menus and widgets with the language code, such as Footer EN, so you can spot gaps.
  • Legal pages: make sure privacy policy and terms links point to the correct language version.
  • Checklist: after updates, load the home page in each language and scan the footer.

If you later want to move the language switcher into the footer, the steps are similar to those in our guide on adding the Polylang language switcher to the header, just using a footer widget area instead.

Frequently asked questions

Does Polylang translate the footer automatically?

No. Polylang does not create translations by itself. You write the translated content and Polylang shows the right version for each language. Automatic machine translation needs Polylang Pro with a translation service or a separate plugin.

Why does my footer widget show in every language?

The widget is probably set to show for all languages, which is the default. Open the widget in Appearance > Widgets, choose a single language in the Polylang language option, save, and add a separate widget for each other language.

Where is Strings translations in Polylang?

In current versions the screen is under Languages > Translations. It lists the site title, tagline, widget titles and any text that themes or plugins register. Use the search box or group filter to find footer strings quickly.

Can I translate the copyright text in my theme footer?

Yes, if the theme registers it with Polylang, it will appear in Languages > Translations. If not, move the text into a footer widget, use a theme that supports Polylang, or register the string with pll_register_string in a child theme.

How do I translate a footer in a block theme with Polylang?

Block theme footers are template parts. Recent Polylang Pro versions add support for site editor content, so check its documentation first. With the free version, use blocks or patterns that can be limited to one language as a workaround.

Sources

  1. Polylang WordPress.org
  2. Strings translation Polylang
  3. Function reference Polylang
  4. Widget translation with Polylang Astra
  5. Site Editor WordPress.org

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.