Exclude specific content on specific from automatic translation

This thread is resolved. Here is a description of the problem and solution.

Problem:
You are working on a site and want to exclude certain paragraphs or headings on specific pages from automatic translation using WPML. You have encountered issues where you cannot clear a translation field and save it empty in the ATE, and editing through the WP editor causes the translation to disappear.
Solution:
Excluding specific paragraphs or headings from automatic translation within the same page using WPML's automatic translation system is not directly possible. To achieve different content on specific translated pages, you can switch from using ATE to the WP editor for those specific pages. This allows you to fully customize the translated versions, including removing content altogether. For detailed steps on how to switch editors and customize translations, please visit Using Different Translation Editors for Different Pages.

Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If this does not resolve your issue, please open a new support ticket at WPML support forum.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: Documentation request

This topic contains 5 replies, has 0 voices.

Last updated by Boris 2 weeks, 5 days ago.

Assisted by: Bruno Kos.

Author	Posts
April 7, 2025 at 2:26 pm #16904954
Boris	Background of the issue: I am working on a site under development and want to exclude certain paragraphs or headings on specific pages from automatic translation using WPML. This is because some products are not offered in all countries, and therefore texts differ. I have tried editing automatic translations through the ATE and WP editor. Symptoms: When I edit an automatic translation through the ATE, I cannot clear a translation field and save it empty. It is not accepted. Additionally, if I edit an automatic translation through the WP editor, the translation disappears, presumably because automatic translation is not available for editing through the WP editor? Questions: How can I exclude certain paragraphs or headings or other content on specific pages from automatic translation?
April 8, 2025 at 11:39 am #16908892
Bruno Kos WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+02:00)	Hi, What you're looking to do isn't directly possible with WPML's automatic translation system. You can’t exclude specific paragraphs or headings from automatic translation within the same page. The ATE doesn’t allow saving empty fields, and editing via the WordPress editor can break the translation sync, as you've noticed. The only way to achieve different content on specific translated pages (like showing or hiding certain text) would be to use the method described here: https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/#how-to-get-different-designs-for-different-translations This lets you switch from using ATE to the WP editor for just those specific pages, so you can fully customize the translated version—including removing content altogether.
April 8, 2025 at 11:44 am #16908900
Boris	Hi Bruno, that's exactly what I thought. Thank you for confirming that. That leads me to the following questions: 1. does that mean I cannot make use of automatic translation for those pages? Once I switch a page to the WP editor, automatic translation is no longer an option, am I right? 2. I'm sure this is not the only site around that requires differences in content between languages. Is there a plan to add a bit more flexibility to the ATE/automatic translation system in this regard, so specific content can be excluded? I realize that is a complex thing. Actually, I suppose it would be better, more flexible and more sturdy, to add the possibility of automatic translation using the WP editor. Is anything like that on the roadmap?
April 8, 2025 at 12:39 pm #16909368
Bruno Kos WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+02:00)	Once a page is switched to the WP editor, automatic translation via ATE is no longer available. At the moment, there's no built-in way to selectively exclude content from automatic translation. The only related item currently on the roadmap is the ability to exclude certain HTML markers from needing to match across translations — which would help in some cases, but it's not yet available. The closest workaround for now is segment joining, which might offer some flexibility by allowing you to group certain content together. However, it’s limited — not all segments can be joined, depending on the content structure.
April 8, 2025 at 12:41 pm #16909404
Boris	Hi Bruno, thanks, yes, I'm aware of that. It may help in some cases, but not all. We'll find the best way to deal with each page. So no way of automatic translation combined with the old school WP editor is anywhere on the roadmap?
April 8, 2025 at 1:12 pm #16909576
Bruno Kos WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+02:00)	At the moment, automatic translation combined with the classic WordPress editor isn’t on our roadmap. This is mainly because ATE (Advanced Translation Editor) is an external system and not integrated directly into WordPress. As a result, changes made in one environment aren’t visible or synced with the other. There’s also a technical limitation around segmentation. If you make more substantial changes directly in WordPress, ATE may not be able to properly match those segments with the original content. Because of these constraints, a hybrid or back-and-forth workflow between ATE and the classic editor isn’t something we plan to support at this time.
April 8, 2025 at 1:14 pm #16909595
Boris	Hi Bruno, okay. Too bad, but I understand that it is a very complex situation. Good to know exactly what to expect though. Thanks!!