Advanced Custom Fields is where a lot of a WordPress site’s real content actually lives: product specifications, landing page sections, staff bios, pricing tables, and countless custom layouts built with repeaters and flexible content. Standard translation plugins that only touch post_title and post_content routinely miss all of it. This guide covers how AI translation handles the different ACF field types, where the automation breaks down, and what to check before trusting a translated field to go live.
Why ACF Content Is Easy to Miss in Translation Projects
ACF stores its values as post meta, not inside the main post_content field. A translation tool built only to parse the WordPress editor content never sees this data, so the fields stay in the source language even after the rest of the page is translated. This is one of the most common gaps in multilingual WordPress projects: a page looks fully translated in the visible editor area, but a specifications table or a repeater-based feature list built with ACF is quietly left untranslated, sometimes not caught until a native speaker reviews the live site.
How AI Translation Handles Different ACF Field Types
Not every ACF field type needs the same handling. A translation workflow has to distinguish between fields that hold translatable text and fields that hold structural or relational data that should stay untouched.
| ACF Field Type | Translation Approach |
|---|---|
| Text / Textarea | Translated directly, value by value, with the field key preserved so the field still maps correctly in the target language. |
| WYSIWYG | Translated while preserving inline HTML formatting, so bold text, links, and lists survive the translation pass. |
| Repeater | Each row is translated independently while row order and row count stay identical across languages. |
| Flexible Content | Each layout block is translated using its own field definitions, since different layouts can contain different field sets. |
| Relationship / Post Object | Left untouched; these fields reference post IDs, and the reference should point to the translated version of the related post rather than being translated as text. |
| Image / Gallery | The image reference stays the same, but caption and alt text sub-fields are translated so accessibility and SEO signals carry over. |
Repeater and Flexible Content Fields: The Hardest Part to Automate
Repeater and flexible content fields are where naive translation tools fall apart. A repeater might hold ten rows today and eight next month; a translation system that hardcodes row positions instead of walking the field structure dynamically will misalign values or silently drop rows after an edit. The safer approach is to read the ACF field structure at translation time, translate each sub-field according to its own type, and write the result back into the same schema instead of treating the whole repeater as one block of text.
Keeping ACF Field Structure Intact Across Languages
- Same field keys: translated values are stored under the same ACF field keys, so the field group and any conditional logic keep working in every language.
- Values only, not structure: field labels, choices in select fields, and layout names are configuration, not content, and should not be machine-translated unless explicitly configured to be.
- No orphaned rows: repeater and flexible content rows stay in sync with the source language when the source is edited, instead of leaving stale rows behind in translated versions.
- Relational integrity: relationship and post object fields keep pointing at the correct localized post rather than the original-language one.
How GPTranslate Approaches ACF Translation
GPTranslate reads ACF field groups at the schema level rather than treating custom fields as opaque post meta. That means repeaters and flexible content layouts are translated field by field, image and gallery captions are picked up automatically, and relationship fields are re-linked to their translated counterparts instead of being blindly copied. This sits on top of the same AI Agent workflow described in our complete guide to AI translation and AI Agent for WordPress, and follows the same logic used for other dynamic WordPress content like widgets and custom post types.
SEO Considerations for Translated Custom Field Content
If ACF fields feed into a page’s visible content, search engines index them the same way they index any other on-page text, which means they need the same multilingual SEO treatment as the rest of the page. That includes making sure translated field content lines up with the page’s translated SEO titles and meta descriptions, and that the overall URL, hreflang, and metadata structure stays consistent whether the page content comes from the block editor or from ACF fields.
Frequently Asked Questions
Does AI translation understand the context of an ACF field?
Modern AI models translate each field with awareness of the field label and surrounding field group, which produces more accurate results than translating isolated strings with no context. A field labeled “Warranty Period” gives the model useful context that a bare string value would not.
What happens to repeater field order after translation?
Row order is preserved. Each row is translated independently but written back into the same position in the repeater, so the translated version matches the source layout row for row.
Can images and galleries inside ACF fields be localized too?
The image files themselves are typically shared across languages, but caption and alt text sub-fields are translated, which matters both for accessibility and for image SEO in each language.
Does translating ACF fields break Elementor or other page builder compatibility?
No, as long as the translation writes values back into the same ACF field keys. Page builders that pull data from ACF fields read whichever language version is active, the same way they read the original field.
Conclusion
ACF fields are often the most content-rich part of a WordPress page, and they are also the part most likely to be left behind by translation tools that only look at the block editor. Treating custom fields as first-class translation targets, with field-type-aware handling for repeaters, flexible content, and relationships, is what keeps a multilingual site fully translated instead of translated everywhere except the parts built with ACF. If your site relies heavily on custom fields, check every field group against the target language before considering a page done, not just the visible editor content.