{"id":98,"date":"2026-09-23T11:24:42","date_gmt":"2026-09-23T11:24:42","guid":{"rendered":"https:\/\/docs.latw.ai\/uncategorized\/automatic-translation-2\/"},"modified":"2026-09-23T11:24:42","modified_gmt":"2026-09-23T11:24:42","slug":"automatic-translation-2","status":"publish","type":"post","link":"https:\/\/docs.latw.ai\/pl\/latw-for-polylang\/automatic-translation-2\/","title":{"rendered":"Automatic Translation"},"content":{"rendered":"

Available in LATW AI Translation for Polylang PRO<\/strong>.<\/em><\/p>\n

What it does<\/h2>\n

Normally you translate content by opening the plugin’s Translations<\/strong> screen and pressing a
\nbutton. Automatic translation removes that step: as soon as a new post, page or product is
\npublished, the plugin sends it to the AI on its own and the finished translation is linked to it in
\nPolylang a short while later.<\/p>\n

It was built for sites where content does not arrive by hand \u2014 a product feed from a supplier, a CSV
\nimporter, an app that posts articles through the API. You publish, and the translations appear.<\/p>\n

Important:<\/strong> every automatic translation is billed by your AI provider, exactly like a manual one.
\nThe settings include daily limits so an importer that misbehaves cannot run up a bill overnight \u2014
\nsee Daily limits<\/a>.<\/p>\n

How it works, step by step<\/h2>\n
    \n
  1. Someone (or something) publishes a new post.<\/li>\n
  2. The plugin notes the post and starts a short countdown \u2014 60 seconds by default.<\/li>\n
  3. If the post is saved again during the countdown, the countdown restarts. This is deliberate:
    \nimporters usually write the same product several times in a row (first the text, then the
    \nprice, then the stock level, then the images), and we want to translate it once, after it has
    \nsettled \u2014 not four times.<\/li>\n
  4. Once the countdown runs out, the plugin’s regular every-minute background task picks the post up
    \nand sends it to the AI, in the same way as if you had pressed Translate yourself.<\/li>\n
  5. The translation is saved and linked to the original in Polylang.<\/li>\n<\/ol>\n

    What does not<\/em> start a translation<\/h3>\n
      \n
    • Editing content that is already published.<\/strong> Only content entering<\/em> one of the selected
      \nstatuses counts \u2014 a brand-new post being published, or a draft going live. Re-saving a published
      \npost does nothing at all. A stock or price sync that touches every product every few hours will
      \ntherefore not trigger anything.<\/li>\n
    • Content that is already translated.<\/strong> If a post already has a translation in every target
      \nlanguage, it is skipped.<\/li>\n
    • Translations themselves.<\/strong> A translated post is never treated as new content to translate, so
      \nthere is no loop.<\/li>\n
    • Drafts in progress, trashed posts and media attachments.<\/strong><\/li>\n<\/ul>\n

      Keeping existing translations up to date when the original changes remains a manual decision on
      \nthe Translations<\/strong> screen.<\/p>\n

      One case worth knowing: if a post is published that already has some<\/em> of its target languages, the
      \nmissing ones are translated and the ones it has are brought up to date in the mode chosen under
      \nOutdated Translations<\/strong> \u2014 for free when nothing changed, but at full price if that setting is
      \nRe-translate the whole post from scratch<\/strong>. See Updating Outdated Translations<\/em>.<\/p>\n

      \n

      The settings<\/h2>\n

      All options live in AI Translation \u2192 Settings \u2192 Automation<\/strong>. Without an active licence the tab
      \nshows a notice instead, and nothing is watched.<\/p>\n

      Automatic translation \u2014 “Translate new content automatically”<\/h3>\n

      The master switch. While it is off, nothing below has any effect and the plugin behaves exactly as
      \nbefore. Tick it and save, and the plugin starts watching for new content.<\/p>\n

      While posts are waiting for their countdown, the switch shows how many: N item(s) are currently
      \nwaiting to be translated.<\/em><\/p>\n

      Content types<\/h3>\n

      Which kinds of content are watched: Posts, Pages, Products, or any custom type your theme or plugins
      \nregister \u2014 as long as Polylang is set to translate it.<\/p>\n

      Nothing happens until at least one type is ticked.<\/strong> This is the usual reason automatic
      \ntranslation appears to “not work”.<\/p>\n

      Triggering statuses<\/h3>\n

      The status a post has to enter<\/em> for a translation to start. Published<\/strong> is the default and is
      \nwhat most sites want.<\/p>\n\n\n\n\n\n\n\n\n
      Option<\/th>\nTranslation starts when\u2026<\/th>\n<\/tr>\n<\/thead>\n
      Published<\/strong><\/td>\na post goes live (new post published, or a draft published)<\/td>\n<\/tr>\n
      Pending review<\/strong><\/td>\na contributor submits a post for review<\/td>\n<\/tr>\n
      Draft<\/strong><\/td>\na post is first saved as a draft \u2014 useful if you want translations ready before publishing<\/td>\n<\/tr>\n
      Private<\/strong><\/td>\na post is published privately<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      You can tick more than one. Remember that only the move into<\/em> that status counts \u2014 a post that is
      \nalready published and gets edited is not re-translated.<\/p>\n

      The status the translation<\/em> gets is a separate setting: Settings \u2192 Translation \u2192 Status of new
      \ntranslations<\/strong> (Draft by default).<\/p>\n

      Wait before translating<\/h3>\n

      How many seconds to wait before sending the content to the AI. Default 60<\/strong>, minimum 30<\/strong>.<\/p>\n

      Every further save of that post restarts the countdown. So the delay is not “translate 60 seconds
      \nlater” so much as “translate 60 seconds after the last time anything touched this post” \u2014 which is
      \nwhat stops half-built imported products from being translated mid-import.<\/p>\n

        \n
      • Content written by people in the editor: the default 60 seconds is fine.<\/li>\n
      • Content coming from an importer that writes in several passes: raise it to 300 seconds (5 min) or
        \nmore, so the importer is definitely finished.<\/li>\n<\/ul>\n

        Target languages<\/h3>\n

        Which languages new content is translated into.<\/p>\n

        Leave all boxes unticked<\/strong> to reuse the Target Languages you already picked on the
        \nTranslation<\/strong> tab. Tick specific languages here only if automatic translation should cover a
        \nnarrower set than your manual translations \u2014 for example, translate everything into German by hand
        \nbut let only French run automatically.<\/p>\n

        Daily limits<\/h3>\n

        Two limits, both counting automatic translations only<\/strong> \u2014 anything you start by hand is never
        \nblocked and never counted. 0 means no limit.<\/strong><\/p>\n

        Translations per day.<\/strong> One post translated into three languages counts as three<\/strong>.<\/p>\n

        This is the safety net. If a feed misfires and recreates 5,000 products, the limit stops the run
        \nonce it is reached. Nothing is lost \u2014 the remaining posts keep waiting and go out automatically once
        \nthe limit resets the next day, or as soon as you raise it. While a limit is holding content back, a
        \nwarning appears on the plugin’s own screens telling you how many items are waiting.<\/p>\n

        USD per day.<\/strong> The maximum amount to spend on automatic translations per day.<\/p>\n

        One caveat worth understanding: the exact cost of a translation is only known once it comes back
        \nfrom the provider, so this limit reacts with a delay and can be overshot \u2014 by a lot in Batch<\/strong>
        \nprocessing, where results arrive hours later. If you want a hard, immediate stop, set translations
        \nper day<\/strong> as well.<\/p>\n

        The day is counted in UTC, so it rolls over at the same moment regardless of your site’s timezone.<\/p>\n

        Settings this feature reuses<\/h3>\n

        Automatic translation is not a separate translation engine \u2014 it uses everything already configured
        \nelsewhere in the plugin:<\/p>\n

          \n
        • Engine, model, processing and reasoning effort<\/strong> (Settings \u2192 General).<\/li>\n
        • Prompt, glossary and what to translate<\/strong> (Settings \u2192 Translation, Glossary).<\/li>\n
        • Outdated Translations<\/strong>, for a post that turns out to be partly translated already.<\/li>\n<\/ul>\n
          \n

          Where to check on it<\/h2>\n
            \n
          • Settings \u2192 Automation<\/strong> shows how many posts are waiting for their countdown.<\/li>\n
          • AI Translation \u2192 Translations<\/strong> and History<\/strong> show the jobs themselves, as for any other
            \ntranslation.<\/li>\n
          • AI Translation \u2192 Logs<\/strong> records the work, with lines starting auto-translate:<\/code> \u2014 which posts
            \nwere dispatched, when a daily limit started holding posts, and any dispatch that failed. Why an
            \nindividual post was skipped is recorded too, once Settings \u2192 Advanced \u2192 Debug Mode<\/strong> is on.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"

            Available in LATW AI Translation for Polylang PRO. What it does Normally you translate content by opening the plugin’s Translations screen and pressing a button. Automatic\u2026<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_latwm_translated_slug":"","footnotes":""},"categories":[17],"tags":[],"class_list":["post-98","post","type-post","status-publish","format-standard","hentry","category-latw-for-polylang"],"_links":{"self":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/98","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/comments?post=98"}],"version-history":[{"count":0,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/98\/revisions"}],"wp:attachment":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/media?parent=98"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/categories?post=98"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/tags?post=98"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}