Installing the necessary plugins<\/h2>\n\n\n\n
To translate sites built with Toolset, make sure you have a Multilingual CMS<\/strong> or Multilingual Agency<\/strong> account and install both the WPML Multilingual CMS<\/strong> and WPML String Translation<\/strong> plugins.<\/p>\n\n\n\n From your WPML Account\u2019s download page<\/a>, you\u2019ll find the OTGS Installer<\/strong>\u2014a lightweight plugin that helps you download and install all the required WPML components. <\/p>\n\n\n\n After installing WPML, a quick setup wizard will guide you through selecting your site\u2019s languages, choosing who will handle translations, and other basic settings.Check out WPML\u2019s getting started guide<\/a> for more information.<\/p>\n\n\n\n To be able to translate your Toolset site, you need to make all the relevant custom content translatable. You can do this from the WPML \u2192 Settings<\/strong> page:<\/p>\n\n\n\n Make Custom Post Types Translatable<\/strong><\/p>\n<\/div>\n\n\n\n Make Custom Fields Translatable<\/strong><\/p>\n<\/div>\n\n\n\n Make Custom Taxonomies Translatable<\/strong><\/p>\n<\/div>\n\n\n\n In the Post Types Translation<\/strong> section, select all the custom post types you want to translate and set them to Translatable \u2013 only show translated items.<\/strong><\/p>\n<\/div>\n\n\n\n In the Custom Fields Translation<\/strong> section, look for custom fields with the wpcf-<\/strong> prefix. Then, choose one of the four translation options<\/a> for each field.<\/p>\n<\/div>\n\n\n\n In the Taxonomies Translation<\/strong> section, select the translation options you want to use for your custom taxonomies.<\/p>\n<\/div>\n\n\n\n Once your custom content is set as translatable, you can translate it from WPML \u2192 Translation Management<\/strong>. You\u2019ll learn more about translating content in the course about translating content in WordPress<\/a>, but here\u2019s a quick overview:<\/p>\n\n\n\n From the Translation Management Dashboard, select the custom posts you want to translate and send them for translation.<\/p>\n\n\n\n There\u2019s no need to translate custom fields separately. When you send a post or page that uses custom fields for translation, WPML will include the attached fields.<\/p>\n\n\n\n Custom taxonomies are translated along with the custom post type they belong to. Just send the main content for translation from the Translation Management<\/strong> Dashboard.<\/p>\n\n\n\n After making your custom post type translatable (see previous section<\/a>), you can translate its slug. WPML allows you to translate the whole URL structure, including the slugs of your custom post types. For example, a real estate site might feature a custom post type called \u201cHouses\u201d. The slug <\/strong>of a post type is its singular name or \u201chouse\u201d in this example. This means that the URL structure for this post type will be the following:<\/p>\n\n\n\n In the Spanish version of our site, we can translate this so that the URL structure for this post type viewed in Spanish will be:<\/p>\n\n\n\n After making your custom post type translatable (see previous section), you can translate its slug<\/strong>. To do this, follow the instructions provided on the WPML page about translating page slugs<\/a>.<\/p>\n\n\nMaking your custom content translatable<\/h2>\n\n\n\n
![\"\"](\"https:\/\/toolset.com\/wp-content\/uploads\/2025\/03\/Setting-Recipe-custom-post-type-as-Translatable-1024x536.png\"){kind=spacer}
<\/a><\/figure>\n<\/div>\n\n\n\n![\"\"](\"https:\/\/toolset.com\/wp-content\/uploads\/2025\/03\/wpml-custom-field-translation-preferences-1024x331.png\"){kind=spacer}
<\/a><\/figure>\n<\/div>\n\n\n\n![\"\"](\"https:\/\/toolset.com\/wp-content\/uploads\/2025\/03\/wpml-settings-taxonomy-translation-1024x691.png\"){kind=spacer}
<\/a><\/figure>\n<\/div>\n<\/div>\n\n\n\nTranslating your custom content<\/h2>\n\n\n\n
\n
\n
\n
Translating slugs of custom post types<\/h2>\n\n\n\n
<\/p>\n\n\n\n\n
\n
![\"\"](\"https:\/\/toolset.com\/wp-content\/uploads\/2020\/08\/translating-custom-post-type-slugs-500x199.png\"){kind=spacer}
<\/a>