Understand Content Field Mapping

Field mapping tells TranslateSense which value inside a block, widget, or custom field contains the content to process. Correct mapping matters when a page contains nested settings or several fields with different purposes.

Examples of mapped fields

• Gutenberg: the default configuration maps content for core/paragraph, and maps alt and caption for core/image.
• Elementor: the default button mapping includes text and the nested path link>url.
• Classic Editor and custom fields: rules identify the exact custom-field name and its configured action.

Find the correct field path

1. Identify the block or widget that contains the missing text.
2. Inspect its content structure and find the exact setting that stores the text.
3. Compare that field name or nested path with the active XML configuration.
4. Check the field’s mapping type and editor type, where provided, so the text is handled appropriately.
5. Test the rule on a page with that field and inspect the resulting translation.

If a field is still missing

For Elementor, TranslateSense can discover candidate text fields that are not covered by existing rules while parsing widget settings. Persisting discovered rules depends on the current user’s permission to manage site options or an applicable filter. Styling and layout attributes are excluded from this discovery process. If a text field remains missing, verify the widget name, nested path, active rules, and user’s permissions before changing unrelated mappings.

For more help, see Understand XML Configuration and Why are Elementor fields missing from the translated page?.

Screenshot to add: [Example Elementor widget field path in the XML mapping editor]