Bulk translation and the Translation Manager

The WordPress Translations screen combines editing tools, translation status controls, content exclusions, URL dictionaries, software catalogs, and a site-wide pending-string generator.

Choose the correct workflow

  • Use Translate contents to search, filter, edit, or machine-translate stored content strings for one additional language.
  • Use Other translations for registered strings, the per-language date format, and WooCommerce email text.
  • Use Translate URLs for content slugs and custom-link destinations.
  • Use Translation exclusions to remove a post, term, or menu item from selected target languages.
  • Use Software translations to work with gettext strings and export PO or MO files.
  • Use Generate pending translations to choose between a complete content rescan and translating only unresolved strings already stored.

Both generation modes are site-wide across the configured additional languages. They do not inherit the tab, language, search, status, or object filters used elsewhere in the manager. Translate pending only narrows the work by skipping source discovery, not by applying table filters.

Start safely

Before a site-wide run, finish structural content changes, confirm the enabled post types and taxonomies, review exclusions, and check every additional language. If automatic translation is enabled, the generator immediately sends unresolved strings in bounded requests from the open browser tab. If it is disabled, the tool still refreshes stored strings but skips translation.

Use a filtered set of individual rows for a small review sample. Use Process all for a complete scan whose scope you understand, or Translate pending only after the stored strings are already current.

Chapter contents

How pending translations are found
Previous
Front-end shortcodes
Next