{"id":150,"date":"2026-10-23T10:58:42","date_gmt":"2026-10-23T10:58:42","guid":{"rendered":"https:\/\/docs.latw.ai\/uncategorized\/site-settings\/"},"modified":"2026-10-23T10:58:42","modified_gmt":"2026-10-23T10:58:42","slug":"site-settings","status":"publish","type":"post","link":"https:\/\/docs.latw.ai\/pl\/latw-cloud\/site-settings\/","title":{"rendered":"Site Settings"},"content":{"rendered":"

Everything about how a connected site is translated is set in the panel, per site: open Sites<\/strong>,
\npick the site and go to the Settings<\/strong> tab. While the site is connected, the plugin in WordPress
\nlocks its own fields for these settings and links here instead.<\/p>\n

Each card is outlined when it has unsaved changes. Press Save changes<\/strong> at the bottom to keep
\nthem.<\/p>\n

Translation defaults<\/h2>\n

These are the defaults for every job on the site. A job started in the panel can change them for
\nthat one job; a job started in WordPress always uses them.<\/p>\n

AI source<\/strong> \u2014 who pays for the translation:<\/p>\n

    \n
  • LATW Credits<\/strong> \u2014 taken from your Credits balance, shown on the card. See LATW Credits and
    \nPricing<\/em>.<\/li>\n
  • Your key<\/strong> \u2014 billed by the AI provider to your own API key. Available from the Solo<\/strong> plan.
    \nChoose which of your keys this site uses in the field below. See Using Your Own API Key<\/em>.<\/li>\n<\/ul>\n

    Quality<\/strong> \u2014 three presets, each a specific model:<\/p>\n\n\n\n\n\n\n\n
    Quality<\/th>\nModel<\/th>\nBest for<\/th>\n<\/tr>\n<\/thead>\n
    Economy<\/strong><\/td>\nGPT-6 Luna<\/td>\nFast and affordable. Blogs, product catalogs and most websites.<\/td>\n<\/tr>\n
    Standard<\/strong><\/td>\nGPT-6.1 Sol<\/td>\nNatural, fluent translations for marketing and customer pages.<\/td>\n<\/tr>\n
    Premium<\/strong><\/td>\nGPT-6 Astra<\/td>\nHighest quality for legal, technical and brand-critical content.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    With LATW Credits, each option shows its price per 1,000 words on your plan. Change model<\/strong> opens
    \nthe full list. Claude and Gemini are listed as coming soon and cannot be chosen yet.<\/p>\n

    New sites start on Economy<\/strong>.<\/p>\n

    Mode<\/strong> \u2014 how new jobs are run:<\/p>\n

      \n
    • Start now<\/strong> \u2014 each item is written to your site as soon as it is translated.<\/li>\n
    • Batch mode<\/strong> \u2014 the job goes to the AI provider’s batch service: 50% cheaper<\/strong>, with results
      \nwithin 24 hours. Available from the Solo<\/strong> plan.<\/li>\n<\/ul>\n

      New sites start on Start now<\/strong>.<\/p>\n

      Target languages<\/strong> \u2014 the languages this site is translated into. You pick from the languages the
      \nsite reported when it connected; if none are listed, press Test connection<\/strong> to fetch them again.
      \nThe plugin takes this list over and locks its own setting.<\/p>\n

      Glossary & prompt<\/h2>\n
        \n
      • Glossary<\/strong> \u2014 which of your glossaries this site uses, or None<\/strong>.<\/li>\n
      • Prompt<\/strong> \u2014 which of your prompts this site uses. A job started in the panel can use another one for that job only. LATW Prompt<\/strong> is the built-in one.<\/li>\n
      • Website description<\/strong> \u2014 what the site is about, who reads it and in what tone. It is sent with
        \nevery translation (it fills {{website_context}}<\/code> in the prompt), up to 2,000 characters. When the
        \nsite connects, it is copied from the plugin’s own Website Description; after that, the one set
        \nhere is used.<\/li>\n<\/ul>\n

        Glossaries and prompts are created under Glossary & prompts<\/strong> and can be shared by any number of
        \nsites. See Glossary and Prompts<\/em>.<\/p>\n

        Plugin<\/h2>\n

        Shown only for plugins that have settings of their own here. They change how the plugin itself
        \nbehaves in WordPress, and while the site is connected they are set only here.<\/p>\n

        LATW AI Translation for WPML<\/strong><\/p>\n

          \n
        • Translation editor<\/strong> \u2014 where a translation is opened in WordPress: Classic Translation Editor
          \n(WPML)<\/strong>, WPML’s side-by-side editor with the AI translation filled in, or Native WordPress
          \neditor<\/strong>, where the translated post is edited in the standard post editor.<\/li>\n
        • Outdated translations<\/strong> \u2014 what happens when WPML marks a translation as outdated because the
          \noriginal changed (see below).<\/li>\n<\/ul>\n

          LATW AI Translation for Polylang<\/strong><\/p>\n

            \n
          • Outdated translations<\/strong> \u2014 what happens when a translation is older than the last change of the
            \npost it was translated from:<\/li>\n<\/ul>\n\n\n\n\n\n\n\n
            Option<\/th>\nWhat is sent<\/th>\n<\/tr>\n<\/thead>\n
            Translate only changed strings<\/strong> (recommended)<\/td>\nOnly the parts of the post that changed.<\/td>\n<\/tr>\n
            Translate only changed strings, with the whole page as context<\/strong><\/td>\nThe changed parts, with the whole page for context. Best quality, higher cost.<\/td>\n<\/tr>\n
            Re-translate the whole post from scratch<\/strong><\/td>\nThe whole post, as for a first translation.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

            Translating only what changed needs LATW Pro<\/strong> on the site. Without it the whole post is
            \ntranslated again, and costs what a first translation costs.<\/p>\n

            Webflow<\/h2>\n

            A Webflow site has no plugin; this card, named Webflow<\/strong>, sets how LATW Cloud writes the
            \ntranslations there:<\/p>\n

              \n
            • Publishing<\/strong> \u2014 whether translations wait for your Publish in Webflow (the default), CMS items
              \ngo live at once, or the whole site is published after each job.<\/li>\n
            • Slugs<\/strong> \u2014 whether slugs not translated yet are made from the translated name.<\/li>\n<\/ul>\n

              Connecting Webflow<\/em> explains each option.<\/p>\n

              Budget limit<\/h2>\n

              A Daily<\/strong> and a Monthly<\/strong> limit, in USD, for this site. Leave a field empty for no limit.<\/p>\n

              When a limit is reached, the site’s jobs pause. They do not start again on their own: raise the
              \nlimit, or wait for the next day or month (counted in UTC), then press Resume<\/strong> on the job. The
              \nlimit is checked between portions of a job, so a job can go slightly over it before it pauses.<\/p>\n

              There is also a limit for the whole account, under Settings \u2192 Preferences \u2192 Account budget
              \nlimit<\/strong>, which applies to all sites together.<\/p>\n

              Connection<\/h2>\n
                \n
              • Test connection<\/strong> checks that LATW Cloud can reach the site and shows how long it took. If it
                \nfails, the card lists the usual causes \u2014 see Site Unreachable<\/em>.<\/li>\n
              • Rotate secret<\/strong> replaces the secret that signs the requests between LATW Cloud and the site.
                \nSee Connecting a Site<\/em>.<\/li>\n
              • Replace token<\/strong> (Webflow, instead of Rotate secret<\/strong>) \u2014 shows the last four characters of the
                \nsite token in use and takes a new one, for example when Webflow deleted the old one. See
                \nConnecting Webflow<\/em>.<\/li>\n<\/ul>\n

                Danger zone<\/h2>\n

                Disconnect site<\/strong> switches the plugin back to the engine it used before. It is not possible
                \nwhile the site has active jobs. See Connecting a Site<\/em>. For a Webflow site, LATW Cloud stops using
                \nthe site token; delete it in Webflow afterwards.<\/p>\n","protected":false},"excerpt":{"rendered":"

                Everything about how a connected site is translated is set in the panel, per site: open Sites, pick the site and go to the Settings tab.\u2026<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_latwm_translated_slug":"","footnotes":""},"categories":[18],"tags":[],"class_list":["post-150","post","type-post","status-publish","format-standard","hentry","category-latw-cloud"],"_links":{"self":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/150","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=150"}],"version-history":[{"count":2,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/150\/revisions"}],"predecessor-version":[{"id":172,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/150\/revisions\/172"}],"wp:attachment":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/media?parent=150"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/categories?post=150"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/tags?post=150"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}