{"id":157,"date":"2026-11-09T17:56:04","date_gmt":"2026-11-09T17:56:04","guid":{"rendered":"https:\/\/docs.latw.ai\/uncategorized\/translating-custom-post-types\/"},"modified":"2026-11-09T17:56:04","modified_gmt":"2026-11-09T17:56:04","slug":"translating-custom-post-types","status":"publish","type":"post","link":"https:\/\/docs.latw.ai\/pl\/latw-multilingual\/translating-custom-post-types\/","title":{"rendered":"Translating Custom Post Types"},"content":{"rendered":"<p>A custom post type is any content type your theme or a plugin adds next to Posts and Pages:<br \/>\n<strong>Projects<\/strong> in a portfolio theme, <strong>Events<\/strong> in an events plugin, <strong>Team members<\/strong>, <strong>Services<\/strong>,<br \/>\n<strong>Testimonials<\/strong>. The plugin translates them the same way it translates posts and pages &#8211; there<br \/>\nis no separate mode to learn.<\/p>\n<p><em>Translating custom post types by hand is part of the free version. Translating them<br \/>\nautomatically with AI &#8211; one item, a selection, or everything on save &#8211; requires <strong>PRO<\/strong>.<\/em><\/p>\n<h2>One item, every language<\/h2>\n<p>The plugin does not create a copy of a project for each language. There is one project, and its<br \/>\ntranslations are stored alongside it and shown in its place under the language prefix<br \/>\n(<code>\/en\/\u2026<\/code>). That has a few consequences worth knowing. (If you run languages on subdomains or separate<br \/>\ndomains instead &#8211; see <em>Languages on Subdomains and Separate Domains<\/em> &#8211; read <code>\/en\/\u2026<\/code> as the same path<br \/>\non the English host, for example <code>en.example.com\/\u2026<\/code>.)<\/p>\n<ul>\n<li><strong>Everything that is not text is shared.<\/strong> The featured image, the gallery, the date, the<br \/>\ncategories it belongs to, the order, custom settings such as a &#8220;featured&#8221; switch &#8211; all of it is<br \/>\nset once, on the original, and every language shows the same thing. The exception is a custom<br \/>\nfield you name under <strong>Extra meta keys<\/strong> (see below): that one gets its own value per language,<br \/>\neven when it is an image or a number.<\/li>\n<li><strong>Publishing is shared too.<\/strong> A draft project is a draft in every language; publish the<br \/>\noriginal and the translations go live with it.<\/li>\n<li><strong>Deleting the original deletes its translations.<\/strong> There is nothing left to translate.<\/li>\n<\/ul>\n<h2>Turning it on<\/h2>\n<p>Go to <strong>LATW Multilingual \u2192 Settings \u2192 Translation<\/strong> and look at <strong>Content Types<\/strong>. Every public<br \/>\ncontent type on the site is listed there, the custom ones included, and a ticked type gets a<br \/>\n<strong>LATW Translations<\/strong> box on its edit screen and its own tab on the <strong>Posts<\/strong> page.<\/p>\n<p>All of them are ticked on a fresh install. If you install a theme or plugin later, come back here<br \/>\nand check that its content type is ticked &#8211; a type that is not ticked has no <strong>LATW Translations<\/strong><br \/>\nbox and no tab on the <strong>Posts<\/strong> page, so its items cannot be translated.<\/p>\n<p>The list shows <em>public<\/em> types only &#8211; the ones that have their own pages on the front end. A type<br \/>\na plugin uses only internally (form entries, logs, settings) has nothing a visitor reads, and is<br \/>\nnot offered.<\/p>\n<h2>What gets translated<\/h2>\n<p>Open a project and use the <strong>LATW Translations<\/strong> box, or go to <strong>LATW Multilingual \u2192 Posts<\/strong>, pick<br \/>\nthe content type&#8217;s tab and click the pencil next to a language. The translation opens in the same<br \/>\neditor you use for the original &#8211; the block editor, or your page builder if the project is built<br \/>\nwith one (see the <strong>Page builders<\/strong> setting under <strong>Settings \u2192 Translation<\/strong>).<\/p>\n<p>You translate:<\/p>\n<ul>\n<li><strong>Title, content and excerpt.<\/strong><\/li>\n<li><strong>The URL slug<\/strong> &#8211; the last part of the address, <code>\/en\/projects\/my-project\/<\/code>. In the block<br \/>\neditor it is the <strong>URL slug<\/strong> field in the <strong>Translation URL<\/strong> panel of the sidebar; in any<br \/>\neditor it is also at the top of the segment editor (see <em>Translating Elementor<\/em>). Leave it empty<br \/>\nand the original slug is used.<\/li>\n<li><strong>Custom fields that hold text<\/strong> &#8211; ACF text fields, fields declared by the theme or plugin in<br \/>\nits <code>wpml-config.xml<\/code> (SEO titles and descriptions among them), and any meta key you name under<br \/>\n<strong>Extra meta keys<\/strong> on <strong>Settings \u2192 Translation<\/strong>. A field that is not covered stays in the<br \/>\noriginal language &#8211; if one detail of a project refuses to change language, this is usually why.<\/li>\n<\/ul>\n<p>The categories and tags of a custom post type (a &#8220;Project category&#8221;, say) are translated<br \/>\nseparately, on the <strong>Taxonomies<\/strong> page &#8211; their name, description and slug. Translate a category<br \/>\nonce and every project in it shows the translated name.<\/p>\n<h2>Labels of the content type itself<\/h2>\n<p>The theme also shows text that belongs to the content type rather than to any one project: the<br \/>\nheading of the archive page (&#8220;Projects&#8221;), the singular name (&#8220;Project&#8221;) some themes print in<br \/>\nbreadcrumbs or above a single item, &#8220;No projects found&#8221;. WordPress keeps these in the content<br \/>\ntype&#8217;s registration, not in a post, so they are translated on their own.<\/p>\n<p>Go to <strong>LATW Multilingual \u2192 Strings<\/strong> and set the <strong>Type<\/strong> filter to <strong>Post types<\/strong>. Each custom<br \/>\npost type is one row; open it to translate its names and labels. The list appears when<br \/>\n<strong>Custom post type labels<\/strong> is enabled under<br \/>\n<strong>LATW Multilingual \u2192 Settings \u2192 Translation \u2192 Other objects<\/strong>.<\/p>\n<h2>Addresses: a different URL base per language<\/h2>\n<p><em>Available in the free version (version 2.6.3 and later).<\/em><\/p>\n<p>The address of a project has two parts after the language prefix: the <strong>base<\/strong> the theme gives<br \/>\nthe content type, and the project&#8217;s own slug.<\/p>\n<pre><code>https:\/\/example.com\/progetti\/nome-progetto\/        (Italian, the default language)\nhttps:\/\/example.com\/en\/progetti\/project-name\/      (English, base not translated)\nhttps:\/\/example.com\/en\/projects\/project-name\/      (English, base translated)<\/code><\/pre>\n<p>On a site with languages on subdomains or domains the same addresses read<br \/>\n<code>en.example.com\/projects\/project-name\/<\/code>. A base that belongs to another language, requested on the<br \/>\nwrong host, is redirected (301) to the base that host&#8217;s language uses.<\/p>\n<p>The project&#8217;s slug is translated with the project (see above). The base &#8211; <code>progetti<\/code> &#8211; is set by<br \/>\nthe theme or the plugin that registered the type, often in the theme options, and it is the same<br \/>\nfor every language until you translate it.<\/p>\n<p>To translate it, go to <strong>LATW Multilingual \u2192 Strings<\/strong>, set the <strong>Type<\/strong> filter to <strong>Post types<\/strong><br \/>\nand open the content type. Under its labels there is a <strong>URL base<\/strong> row: the original base on the<br \/>\nleft, one field per language. Type <code>projects<\/code> in the English column and save.<\/p>\n<ul>\n<li><strong>Leave a field empty<\/strong> to keep the original base in that language.<\/li>\n<li><strong>The archive follows the base.<\/strong> When the content type has an archive at its base, it moves<br \/>\ntoo: <code>\/en\/projects\/<\/code>, with its pages (<code>\/en\/projects\/page\/2\/<\/code>) and feeds.<\/li>\n<li><strong>Old addresses keep working.<\/strong> A visitor or a search engine arriving at<br \/>\n<code>\/en\/progetti\/nome-progetto\/<\/code> is sent to <code>\/en\/projects\/project-name\/<\/code> with a permanent (301)<br \/>\nredirect, so existing links and rankings are not lost.<\/li>\n<li><strong>Links follow automatically.<\/strong> Menus, the language switcher, <code>hreflang<\/code> tags, the sitemap and<br \/>\nlinks typed into your content all point at the translated address.<\/li>\n<li><strong>The default language keeps the theme&#8217;s own base.<\/strong> Change the base in your theme options and<br \/>\nthe default language follows it. The translated bases stay as you set them, so check them after<br \/>\nsuch a change.<\/li>\n<li>You can use a path with several parts, such as <code>our-work\/projects<\/code>. Spaces and capital letters<br \/>\nare turned into a normal URL form when you save.<\/li>\n<\/ul>\n<h3>What the URL base will not do<\/h3>\n<ul>\n<li><strong>It is entered by hand only.<\/strong> AI translation (<strong>PRO<\/strong>) never fills or changes the URL base.<br \/>\nThe base is part of the address of every item of the type, and a different wording on the next<br \/>\ntranslation would move all of them at once. Translate it once, deliberately.<\/li>\n<li><strong>No two types can share a base.<\/strong> If another content type already uses <code>projects<\/code> in that<br \/>\nlanguage &#8211; as its own base or as its translated one &#8211; the value is refused with a message, and<br \/>\nthe previous one is kept.<\/li>\n<li><strong>Choosing a base that is also the slug of a page<\/strong> makes the two compete for the same address.<br \/>\nWhen the content type has an archive, the archive wins and the page becomes unreachable in that<br \/>\nlanguage. Pick a different base, or rename the page.<\/li>\n<li><strong>Bases of categories and tags are not translated.<\/strong> <code>\/en\/project-category\/web\/<\/code> keeps the<br \/>\noriginal <code>project-category<\/code>, although the category&#8217;s own slug (<code>web<\/code>) can be translated on the<br \/>\n<strong>Taxonomies<\/strong> page.<\/li>\n<li><strong>An archive at a different address than the base<\/strong> &#8211; a content type registered with an<br \/>\narchive at, say, <code>\/all-projects\/<\/code> while its items live under <code>\/projects\/<\/code> &#8211; is not moved; only<br \/>\nthe items are.<\/li>\n<\/ul>\n<h2>Untranslated items<\/h2>\n<p>A project that has no translation in a language is handled by two settings under<br \/>\n<strong>LATW Multilingual \u2192 Settings \u2192 Languages<\/strong>:<\/p>\n<ul>\n<li><strong>Missing translation<\/strong> decides what a visitor gets on the project&#8217;s own page in that language:<br \/>\nthe original content, a redirect to the default language, or a 404.<\/li>\n<li><strong>Untranslated posts in listings<\/strong> decides whether the project appears on the content type&#8217;s<br \/>\narchive and in other lists of projects (including a page builder&#8217;s posts widget) in that<br \/>\nlanguage. With <strong>Show only posts translated into the active language<\/strong>, an untranslated project<br \/>\nsimply is not listed.<\/li>\n<\/ul>\n<h2>Translating with AI (PRO)<\/h2>\n<p>With <strong>PRO<\/strong>, custom post types are translated exactly like posts:<\/p>\n<ul>\n<li>From the <strong>Posts<\/strong> page, the content type&#8217;s tab: translate one item, or tick several and use<br \/>\n<strong>Translate Selected<\/strong>.<\/li>\n<li>Automatically, with <strong>Automatically send a post for translation when it is saved or published<\/strong><br \/>\nunder <strong>LATW Multilingual \u2192 Settings \u2192 Translation prompt<\/strong>.<\/li>\n<li>The translated slug of each item can be generated for you from the translated title &#8211; turn on<br \/>\n<strong>Localize URLs (slug)<\/strong> on the same screen. A slug is only generated when the translation does<br \/>\nnot have one yet, so an address never changes behind your back.<\/li>\n<\/ul>\n<p>The labels of the content type on <strong>Strings \u2192 Post types<\/strong> can be translated with AI too. The<br \/>\n<strong>URL base<\/strong> is the exception, for the reason given above.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A custom post type is any content type your theme or a plugin adds next to Posts and Pages: Projects in a portfolio theme, Events in\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":[4],"tags":[],"class_list":["post-157","post","type-post","status-publish","format-standard","hentry","category-latw-multilingual"],"_links":{"self":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/157","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=157"}],"version-history":[{"count":2,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/157\/revisions"}],"predecessor-version":[{"id":190,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/157\/revisions\/190"}],"wp:attachment":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/media?parent=157"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/categories?post=157"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/tags?post=157"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}