Plan a large-site run
Process all discovers the complete enabled content set before translating it. On a large site, use Translate pending only when stored strings are already current and the source discovery pass is unnecessary.
Prepare the translation surface
Before starting:
- confirm only the required post types and taxonomies are enabled for translation;
- finish large imports or structural edits;
- configure genuine language exclusions;
- test representative strings individually;
- review automatic-translation quotas and availability;
- choose a quiet editorial window.
Do not use global exclusions as temporary batching controls. Global exclusion removes stored strings and skeletons for the selected object.
Run one site at a time
On multisite, open the Translations screen for the intended site and complete that site's run before moving to another. Keeping the generation tab open accelerates the saved server-side job, while WordPress cron can continue bounded steps after the tab closes.
In Process all, posts and terms are fetched in pages, then processed in bounded groups. Both modes use a cursor-paginated pending sweep and translation requests bounded by string and word limits.
Check progress in stages
After completion:
- filter Translate contents by Pending to find unresolved work;
- filter by Machine to review newly generated text;
- inspect Other translations for registered defaults;
- check the queue panel separately for strings scheduled by normal background extraction;
- validate a sample of public pages, terms, menus, and localized routes.
If the browser run is interrupted, select the same mode again to resume its saved checkpoint. Resolved values remain stored.