Navigation menus and widgets are some of the most visible elements on a WordPress site, appearing on every page, yet they are stored completely separately from post and page content. A site can have every article translated and still show an English-only main menu or an untranslated sidebar widget to visitors browsing in another language. This guide covers what menus and widgets actually store, and how AI translation keeps them consistent across every language version of a site.
Why Menus and Widgets Are a Different Translation Problem
WordPress menus are built from nav_menu_item posts, each holding a label that is often independent of the page or post it links to. Widgets, especially text and custom HTML widgets, store freeform content in options tables rather than as regular post content. Neither is picked up by translation tools that only scan post_content, which is why menus and widgets are a common blind spot even on sites where every page and post has been carefully localized.
What Needs Translating in a Menu
- Menu item labels: the visible text of each link, which is frequently customized and does not always match the linked page’s title.
- Menu item link targets: each item should point to the translated version of its target page, not the source-language version, once that translation exists.
- Menu item descriptions and title attributes: optional fields some themes display as tooltips or subtext, easy to forget during translation.
- Menu structure: nesting and order should mirror the source menu unless there is a deliberate reason to diverge for a specific market.
What Needs Translating in a Widget
| Widget Type | Translation Handling |
|---|---|
| Text / Custom HTML | The widget title and body content are translated, with any embedded HTML formatting preserved. |
| Recent Posts / Categories | Dynamic by nature; the widget title is translated, while the listed items reflect whatever language the visitor is browsing in. |
| Search | The placeholder and button text are translated so the search field reads naturally in the target language. |
| Custom widgets (page builder or theme-specific) | Handled the same way as other dynamic content, field by field, based on the widget’s own settings schema. |
Keeping Menus and Widgets in Sync as the Source Site Changes
Menus and widgets are edited more frequently than most page content, since they often get quick tweaks: a new promotional link, a reordered navigation item, a swapped-out sidebar widget. A translation workflow needs to catch these small, frequent changes the same way it catches larger content updates, otherwise language versions of the site drift out of sync at the navigation level even while the page content stays aligned. This is the same incremental logic described in our guide to translating WordPress dynamic content with AI.
How GPTranslate Handles Menus and Widgets
GPTranslate treats navigation menus and widgets as first-class translation targets rather than an edge case, translating menu item labels and widget content alongside pages and posts, and re-linking menu items to the correct translated page automatically. This is part of the same AI Agent workflow covered in the complete guide to AI translation and AI Agent for WordPress.
Frequently Asked Questions
Do menu items automatically link to the translated version of a page?
When the linked page has a translated version, the menu item should point to that translated version for visitors browsing in that language, rather than sending every language to the same source-language URL.
What happens to a widget if its source content changes after translation?
An incremental translation workflow re-translates only the changed portion of the widget content rather than requiring a manual full re-translation, keeping translated widgets aligned with source edits over time.
Are widget areas that differ between languages a problem?
Not inherently. Some sites intentionally show different widgets per region, for example a different contact number or local promotion, and a translation workflow can accommodate that as long as it is a deliberate content decision rather than an oversight.
Conclusion
Menus and widgets appear on every single page of a site, which makes them disproportionately visible compared to their size. A single untranslated menu label or sidebar widget is often the first thing a visitor notices, even on a site where every article has been carefully localized. Treating navigation and widget content as part of the core translation job, not a manual afterthought, is what makes a multilingual WordPress site feel complete in every language it supports.