Translate first the pages foreign visitors actually open, with TranslatePress

Already connected?

If SAR is already in your AI app, this is enough:

What happens

1. The AI app reads how many of the strings TranslatePress has seen are untranslated, machine translated or reviewed, site-wide.
2. It runs a Google Analytics report of the most visited pages in your second language.
3. It opens each chosen page once in that language, as a visitor would, so TranslatePress learns its strings; visitors see no change.
4. It lists each page's strings with their status and shows you the translations next to the originals.
5. Once you approve them in SAR, up to 100 translations at a time show on the site at once, marked reviewed; they can be undone for 30 days.

Approvals involved

Worked out from the tools this recipe uses.

• wordpress_untranslated_reportUntranslated stringsNone
• ga4_run_reportRun a reportNone
• wordpress_prime_page_translationsPrepare a page for TranslatePressNone
• wordpress_list_page_stringsA page's strings in TranslatePressNone
• wordpress_translate_page_stringsTranslate page stringsApproval

What you get

Your translation effort spent where visitors actually are, and a site-wide count to track progress. Pages that get few foreign visits can wait for a later round.