Set up machine translations

purple hub summary to configure machine translations within purple hub, you need to set up polylang pro and machine translations via the deepl api this article will guide you through the setup process precondition have a 'super admin' role in the purple hub if you don't have a super admin role, contact us and we can set it up for you we are happy to help! have a polylang pro license key generated learn more https //polylang pro/doc/managing license keys/# text=you%20receive%20your%20license%20key,%3e%20settings%20%3e%20license%20keys%20module have a deepl api key for translations generated learn more https //support deepl com/hc/en us/articles/360020695820 api key for deepl s api# text=the%20right%20%e2%80%8cplan ,creating%20new%20api%20keys,keys%20depends%20on%20your%20subscription enabling polylang pro in purple hub, in the left side menu, navigate to ' plugins ' > ' polylang pro ' plugins page (1) activate the polylang pro plugin by clicking on this button important make sure to activate the 'polylang pro ' plugin, not 'polylang' depending on your user role, you might not be able to access the plugins page in purple hub if this is the case, please talk to us, we are happy to help configuring polylang pro to work with machine translation in purple hub, in the left side menu, navigate to ' languages ' —> ' settings ' below license keys , next to polylang pro , the license key coming from your polylang subscription is stored save changes activates the connection to your polylang pro account license keys setup configuration of deepl machine translation in purple hub, in the left side menu, navigate to ' languages ' > ' settings ' for setting up the deepl translations, scroll to machine translation machine translation setup (1) settings opens the setup options (2) deactivate machine translation in your purple hub in case the setting machine translations isn't visible on the settings page, polylang pro wasn't set up correctly and you should verify the setup machine translation setup (1) data used as soon as the api key for deepl is successfully enabled (see 2), this bar appears, indicating the percentage of usage of available characters for translation, according to your plan in deepl (2) the deepl api key is stored in this entry field you can get a new api key, with a subscription to the deepl api ( here https //www deepl com/en/pro#developer ) and afterwards following the instructions on the helpcenter of the provider https //support deepl com/hc/en us/articles/360020695820 api key for deepl s api# text=the%20right%20%e2%80%8cplan ,creating%20new%20api%20keys,keys%20depends%20on%20your%20subscription (3) check connection to deepl indicates, whether the api key you created is working if the bar has turned green, after clicking on the button, you can continue with the setup if the bar has turned red, you api key is invalid, and you have to re create it in order to proceed with the setup (4) formality defines whether the translated text should have a formal or informal style choose from ' default '; ' prefer formal '; ' prefer informal ' if your choice is not available for the target language, the default formality will be used (5) cancel configuration (6) save changes to make your configuration take effect in your purple hub internal link handling for machine translation when your content gets machine translated automatically, existing links will be preserved this can lead to situations where translated content of one language links to pages of different languages to prevent this, there is an option to automatically remove any internal links during machine translation external links to other web pages will still be kept with this option enabled