Control translatable custom fields
POM Translate uses two gates for post metadata: the post type must have Meta enabled, and the exact metadata key must be registered as translatable. This allowlist prevents technical post data from appearing indiscriminately in the translation editor.
Built-in keys
The plugin includes these defaults:
| Post type | Metadata keys |
|---|---|
| Posts and pages | _yoast_wpseo_title, _yoast_wpseo_metadesc |
| All enabled post types with Meta enabled | rank_math_title, rank_math_description, rank_math_facebook_title, rank_math_facebook_description, rank_math_twitter_title, rank_math_twitter_description, rank_math_breadcrumb_title, rank_math_focus_keyword |
| Attachments | _wp_attachment_image_alt |
Themes and plugins can extend the list for one post type or all types. Registration is a developer responsibility; the Content types screen does not provide a text box for arbitrary keys.
Rank Math fields are included automatically for products and custom post types as well as posts and pages. See Translate SEO titles and meta descriptions for field coverage, template variables, and social fallbacks.
Prepare a custom field
Before requesting registration, establish:
- the exact post-type slug;
- the exact metadata key;
- whether the stored value is visitor-facing text;
- whether the value is a single scalar string;
- where the translated value is rendered;
- one source object suitable for verification.
Do not register passwords, tokens, IDs, serialized layouts, prices, dates used for computation, or other operational values merely because they are stored as post metadata.
Make a registered key available
- Ask the theme or plugin that owns the field to register its key with POM Translate.
- Open Settings → POM Translate → Content types.
- Enable the owning post type.
- Enable Meta for that type.
- Save the settings.
- Add a non-empty source value to the custom field and save the object.
- Open Translations → Translate contents and locate the metadata row.
- Translate it, save, and verify the frontend component that reads the field.
POM Translate reads the single stored value for each approved key. Empty values do not create rows. If a field stores an array or complex structure, it needs a purpose-built integration rather than ordinary metadata registration.
Troubleshoot a missing field
If the row is absent, check both gates first. Then confirm the key is spelled exactly, the source value is not empty, and the object was saved after registration. A field can look populated in an editor while its visible text is actually stored under another key.
Developers can use the supported registration guidance in Register custom fields. Editors can continue with Translate custom fields.