TranslateSense uses XML mapping rules to decide which content fields are extracted for translation. The rules are different for Gutenberg blocks, Elementor widgets, and Classic Editor or custom fields. A rule identifies a block, widget, or field and the values TranslateSense should process; it does not mean that every value on a page will be translated automatically.
Choose the guide for your task
- Understand XML Configuration to learn how the configuration is organized.
- Understand Content Field Mapping to identify the field path that contains the text.
- Generate Elementor XML Rules when a widget needs a mapping rule.
- Update Elementor XML Rules when an existing mapping needs to change.
- Troubleshoot missing Elementor fields if content is not extracted as expected.
Where to review mapping rules
Open Languages → TranslateSense when Polylang is active. If Polylang is not active, open Settings → TranslateSense. Choose the relevant editor tab, such as Elementor, and use the available Generate or Edit Config controls. The dashboard exposes separate configuration for Gutenberg, Elementor, and Classic Editor fields.
Check a rule before relying on it
- Confirm that the source content uses the expected block, widget, or field.
- Check the exact block or widget name and the field path. Nested Elementor fields can use paths such as
link>url. - Review whether the field is intended to contain translatable text rather than styling or layout data.
- Test the mapping on a representative page and inspect the translated result before using it in a larger batch.
Valid XML syntax is necessary, but it does not guarantee that a rule points to the correct field. Change only the relevant mapping and retest when content is missing or an unexpected value is translated.
Screenshot to add: [TranslateSense XML Mapping and Content Rules dashboard overview]