Generate Elementor XML Rules

Use the TranslateSense mapping workflow when an Elementor widget contains text that is not covered by the current XML rules. The dashboard’s Generate control opens a mapping sandbox in the editor so you can prepare a representative widget for mapping.

Prepare an Elementor mapping example

1. Open Languages → TranslateSense when Polylang is active, or Settings → TranslateSense otherwise.
2. Select the Elementor tab.
3. Choose Generate ELEMENTOR Config, or use the widget’s Generate control, to open the mapping sandbox.
4. In the sandbox editor, add the widget you want to map and enter the exact placeholder text Translate This Content in the field or fields you want TranslateSense to recognize.
5. Save the sandbox content, then return to the TranslateSense configuration to inspect the available widget rule.

Review the generated mapping

Check the widget identifier and the field paths before relying on a rule. Elementor paths can include nested values, such as link>url. If a rule does not appear, confirm that the placeholder was entered exactly, that the field is part of the saved widget settings, and that the current account has the required permission to persist configuration changes.

Test before using the rule broadly

• Use a representative page containing the same widget and field structure.
• Confirm the intended text is extracted and translated.
• Check that styling, layout, URLs, or other non-text settings were not mapped unintentionally.
• If the rule needs adjustment, open Update Elementor XML Rules.

The source includes a configuration-generation endpoint that looks for the exact placeholder text and returns an XML snippet when it finds a supported mapping. If the placeholder is missing, the endpoint returns an error instead of a generated rule.

Screenshot to add: [Elementor mapping sandbox with the Translate This Content placeholder]