Skip to main content

How to translate product metafields

Metafields hold extra data on your products, collections, and other resources — things like a subtitle, a care guide, or content added by another app. Lokalize can translate the metafields that contain customer-facing text, while leaving the ones that power app or theme logic untouched.

Translate metafields in a bulk job​

  1. Open Lokalize → Bulk Translate.
  2. Tick the Metafields row, then click Configure.
  3. Choose an owner type — Products, Collections, Blogs, Articles, or Pages.
  4. Add one or more namespace.key entries, for example judgeme.badge or mycustom.subtitle.
  5. Save the modal, then click Translate.

The job walks every owner of the chosen type, finds metafields matching your entries, and translates only those.

Screenshot pending

Metafields configuration modal with namespace.key entries

Why you have to list namespace.key entries​

Many apps and themes attach metafields to your resources for internal logic, layout configuration, or programmatic identifiers. Translating those would break functionality.

Requiring you to list the exact namespace.key combinations you want translated is a safety gate: it guarantees only the metafields you intend — typically display content like review widgets or product descriptions — ever reach the translation engine.

JSON metafields are skipped​

If a metafield's value is JSON, it's skipped during bulk translation. Running a raw JSON blob through a text engine almost always corrupts its structure, which would break the app or theme that reads it.

If you need to translate values inside a JSON metafield:

  • Use the dedicated flow for that data — for example, Judge.me reviews for review-widget JSON, or
  • Edit individual values from the Translations page.