Go to AI Translation \u2192 Translations<\/strong>. Each row is one original, with a column showing where it Pick the languages you want and click Translate<\/strong>.<\/p>\n A language that is already translated can be ticked again. Translate<\/strong> then brings it up to date \u2014 New translations are created as drafts<\/strong> by default, so nothing appears on your site until you Tick the boxes on the left and use Translate Selected<\/strong>.<\/p>\n Bulk translation is a PRO feature.<\/em> Without the add-on the checkbox column and the button are not AI Translation \u2192 Taxonomy Translation<\/strong> works the same way, one row per term.<\/p>\n The words “Categories”, “Tags” or “Ingredients” \u2014 the taxonomy’s own labels, not its terms \u2014 are Two things worth knowing:<\/p>\n AI Translation \u2192 String Translation<\/strong> covers strings registered with Polylang: theme options, Titles, content and excerpts. ACF fields. SEO titles and descriptions for Yoast, Rank Math, SEOPress Links are deliberately left alone. A URL that came back from a model rewritten into another language Posts built with Bricks, Divi, Beaver Builder, Oxygen or WPBakery<\/strong> are marked in the list and This is on purpose. Those builders keep their content in their own storage format rather than in the Posts and pages Go to AI Translation \u2192 Translations. Each row is one original, with a column showing where it already has a translation and where\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-103","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\/103","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=103"}],"version-history":[{"count":0,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/103\/revisions"}],"wp:attachment":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/media?parent=103"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/categories?post=103"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/tags?post=103"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nalready has a translation and where it does not:<\/p>\n\n
\nticked so the next Translate<\/strong> brings it up to date<\/li>\n
\ndisabled so the same job cannot be sent twice<\/li>\n<\/ul>\n
\nwith PRO only the parts that changed are sent, and corrections you made by hand are kept (see
\nUpdating Outdated Translations<\/em>). Translate Again<\/strong> replaces the whole translation instead (see
\nHow to Translate Again?<\/em>).<\/p>\n
\nhave looked at it. Change that under Settings \u2192 Translation \u2192 Status of new translations<\/strong>.<\/p>\nSeveral posts at once<\/h3>\n
\non the page at all, and translations are started one post at a time from each row.<\/p>\nCategories, tags and custom taxonomies<\/h2>\n
The names of the taxonomies themselves<\/h3>\n
\nlisted on the String Translation<\/strong> screen, where the Domain<\/strong> column and filter show them as
\nTaxonomy labels<\/strong>. They are translated there like any other string: translate them once, and your
\nvisitors see “Zutaten” where the original says “Ingredients”.<\/p>\n\n
\nname. The rest of what WordPress calls labels (“Add New Tag”, “Separate tags with commas”) is
\nadmin wording and comes from WordPress’s own translations.<\/li>\n
\nthem in your own language, exactly as Polylang does.<\/li>\n<\/ul>\nInterface strings<\/h2>\n
\nwidget titles, and anything a plugin has handed to Polylang for translation. They are translated in
\nbatches rather than one at a time, because they are short.<\/p>\nWhat actually gets translated<\/h2>\n
\nand All in One SEO. Image alt texts. Elementor text. Any meta key a plugin declares to Polylang as
\ntranslatable \u2014 plus any key you add yourself under Settings \u2192 Custom Fields<\/strong>.<\/p>\n
\nis a broken link, so link fields are never sent for translation in the first place.<\/p>\nPosts the plugin refuses<\/h2>\n
\ncannot be selected.<\/p>\n
\npost content, and translating such a post would produce either an empty page or an untranslated copy
\nof the original \u2014 both of which look like the plugin is broken. Refusing the post and saying why is
\nthe honest outcome. Elementor is fully supported<\/strong> and is not affected.<\/p>\n","protected":false},"excerpt":{"rendered":"