This video breaks down exactly how the Polylang AI Translation add-on handles ACF integration. The key insight is that not every field should be translated automatically – some data like product IDs, dates, or technical specifications need to stay consistent across all languages, while others like descriptions and titles should be fully independent.
The Five Translation Options Explained
As of Polylang Pro 3.7, you get five distinct ways to handle ACF field translations:
- Synchronize – Keeps fields identical across all languages (perfect for SKUs, dates, or technical specs)
- Translate – Makes each language completely independent (ideal for descriptions, titles, and localized content)
- Translate Once – Copies/translates the field when first created, then becomes independent (great for initial setup that may need tweaking per language)
- Copy Once – Duplicates the original value once, then no further updates (useful for media or structural data)
- Ignore – Leaves the field blank in translations (for language-specific fields that shouldn’t carry over)
How Our Plugin Respects Your Polylang Pro / ACF Settings
The smart thing about the Polylang AI Translation add-on is that it only processes fields you’ve explicitly set to “Translate”. (when you have Polylang Pro enabled) This prevents accidentally translating fields that should remain synchronized or ignored, giving you complete control over your multilingual workflow.
In the video above, I walk through exactly how this logic works and show you the customization options available through filter hooks. Whether you’re just getting started with multilingual sites or looking to streamline your existing workflow, understanding these translation behaviors will save you time and prevent headaches down the road.