This plugin allows you to use DeepL translation API to translate posts ( and pages ) right from your WordPress Admin.
Adds a translate button to the edit post page.
Shows current and remaining API usage.
This plugin requires an active DeepL API subscription with access to the API.
Please note that DeepL User or Teams plans do NOT include API access.
You have to get a “DeepL Developer” plan (both ‘DeepL API Free’ and ‘DeepL API Pro’ work with this plugin)
Want to translate Products, meta fields, or translate in batches ?
Get the DeepL Pro API plugin
Please note : the free and the premium version works the same relative to content editors ( Elementor, Blocks, etc.). You’re free to test this plugin on your website to see if your specific configuration works well with the plugin. We cannot guarantee that all content editors work perfectly with the DeepL API so please test this plugin before buying the premium (you’ll need the premium only if you need extended features like meta translations and batch translations)
屏幕截图
To be used with an active DeepL plan WITH API access
Love it! Just not always clear how much can be translated in one go.
Would be good to have the option of splitting up the page's content into multiple pieces to translate if it's too much to do in a single time.
I have finished the Korean translation.I just want to say thank you for developing such a good plugin.And I hope it will be translated into more languages so that many WordPress users can use it conveniently.DeepL API translation plugin 한국어 번역을 모두 마쳤습니다.좋은 플러그인을 개발해 주어서 고맙다는 인사를 전하고 싶습니다.그리고 보다 많은 언어로 번역되어 많은 워드프레스 사용자들이 편리하게 사용할 수 있기를 바랍니다.
This plugin is a life saver for me. A big thank you to the developers!
It works without problems and uses DeepL to translate a post, page, CPT (Custom Post Type) to the selected language.
I've tested it both with Free and Pro API DeepL accounts.
I use it to translate a website with hundreds of posts, pages, CPTs, from Greek to English.
Any limitations is not for this plugin to blame. The translation quality is based on DeepL's quality.
In my case, after translation, I have to check the translation and apply changes. But even this way, this plugin saves so much time and money.
You have to be fluent in the translated language output to spot and perform changes. This is a DeepL's issue, but I am sure that will be improved in the future.
This plugin is a life and time saver as it helps minimize the time to translate content.
Thank you Developers!!
Hi, first this plugin saved me so much time, exactly what i was searching for.
I noticed that the <!-- wp:heading --> translation was alway partially translated in the html "text" ,
e.g.
<!-- wp:heading -->
<h2 id="h-buongiorno-a-tutti">Buongiorno a tutti</h2>
<!-- /wp:heading -->
Translated from It to eng become
<!-- wp:heading -->
<h2 id="h-buongiorno-a-tutti">good morning everyone</h2>
<!-- /wp:heading -->
How this work? in that case if not corrected the heading translation, search engine crawlers are going to see the old untraslated language?
