Websites and banners, made understandableImages · Code · WordPress
Home / Guides
WordPress

WordPress language: site, profile and theme translations

Public-page language, a user’s dashboard language and theme translations can be configured separately. One setting does not automatically translate the whole website.

Before you begin

Identify where the wrong language appears: dashboard menus, theme controls, dates or article text. These strings come from different sources.

WordPress language: site, profile and theme translations. Site → Profile → Theme and plugins
Site → Profile → Theme and plugins
Text explanation of the diagram

Site → Profile → Theme and plugins. A Russian editor dashboard does not translate an English article. The lang attribute should describe the document’s actual language.

The procedure

  1. Review the main site language in general settings and the current user’s profile language. Different administrators may use different dashboard languages.
  2. For untranslated theme or plugin buttons, check language packs and translation updates. Text entered directly into templates or page builders may need separate editing.
  3. View the public page while logged out and inspect navigation, forms, dates and error messages. Multilingual sites also need actual content versions and language links.

A worked example

A Russian editor dashboard does not translate an English article. The lang attribute should describe the document’s actual language.

Check the result

Settings do not unexpectedly change colleagues’ preferences; public controls are readable; translated pages have their own URLs and correct language attributes.

A common mistake

Do not edit core files for one string. An update can overwrite the change and make maintenance harder.

Sources and next steps

Diagram and examples: Web Article editorial team. The diagram explains a principle; it is not an interface capture or a software test result.

Keep making