Why an Elementor popup opens in the wrong language
Illustrative scenario: a Dubai manufacturer has an Arabic product page with an Arabic brochure button. The page looks complete in WPML. The button is translated. The visitor clicks it and gets an English brochure-request popup.

It is a small break in the journey, but it lands at the worst point: when somebody has decided to ask for something. They have done the reading, accepted the offer, and then the site quietly sends them back to English.
This is usually a translation ownership problem rather than a mysterious Elementor fault. The page, its trigger, the popup template and the form inside the popup may all be separate things to translate and connect. If the issue needs a wider inspection of templates, forms or front-end behaviour, it belongs in a focused WordPress website repair review, rather than a round of hopeful edits in the translation editor.
Start by identifying what is actually in the wrong language
Do not assume the whole popup is wrong. Open the affected language page as a visitor would, then note the first part that switches language.
- If the entire popup is English, the wrong popup template may be attached to the translated page or trigger.
- If the heading and text are Arabic but the fields are English, the popup translation is probably working and the embedded form needs its own check.
- If the popup and form are Arabic but the success message is English, follow the form submission route rather than rebuilding the popup.
- If one language works while the other opens nothing, inspect the translated page’s button action before changing display conditions.
The boring detail that catches people out is the button itself. In Elementor, a button can look identical across languages while its Popup action still points at a default-language template. Copying a page layout or translating its visible text does not prove that action followed along.
What WPML and Elementor are meant to do
WPML documents Elementor popups as translatable templates. In the supported workflow, a button using a Popup action on a translated page should open the translated popup rather than the original-language version. See WPML’s guidance on translating Elementor popups for the documented behaviour.
When an Elementor popup opens in the wrong language, check the popup translation and the page trigger independently. Confirm that the translated popup exists, compare the template selected by each language version of the page, then test the live button while logged out. The first layer that displays the wrong language is the layer to fix.
That last bit matters. A logged-in administrator may have different cookies, cached assets or access to drafts that ordinary visitors do not. Test in a private browser window, on a mobile device if the button is prominent there, and in both directions: Arabic page to Arabic popup, then English page to English popup.
Trace the popup route without changing five settings at once
- Open the translated page. Confirm the page content and call-to-action label are correct on the public URL.
- Inspect the button or link action. Check whether it is set to open a popup and which popup template is selected on that language version.
- Find the popup in Elementor templates. Confirm there is a completed translation connected to the original popup, rather than an unrelated Arabic copy with similar content.
- Open the translated popup directly in the editor. Check its heading, body copy, close control and any reusable widgets.
- Inspect the embedded form separately. Form labels, validation messages, consent wording and success messages can be owned by the form plugin or widget, not by the popup template.
- Retest from the front end. Use the actual button, submit a safe test entry if appropriate, and record what appears after submission.
This is less glamorous than clearing every cache and hoping for the best, but it is faster. You are establishing the chain of ownership rather than treating every visible English word as the same problem.
The form inside the popup may be a separate translation job
A translated popup heading does not guarantee translated form labels. Elementor Forms, embedded shortcode forms and third-party form widgets can each have their own language configuration. A popup may simply be the container holding the wrong component.
For example, an Arabic brochure popup might correctly show its Arabic heading and privacy note, but the email field, dropdown placeholder and submission confirmation remain in English. In that case, editing the popup template again is unlikely to help. Check how the form is inserted, whether it has a translated version, and where its confirmation message is configured.
Also confirm delivery before calling the route finished. A visible success message only shows that the front end displayed one. Check the recipient inbox, spam folder or CRM record used for the test. Plenty of sites manage to translate the button perfectly while sending the enquiry nowhere useful.
Keep a popup issue separate from a URL language issue
If the correct language page loads and only the popup changes language after a click, keep the diagnosis narrow. That is not automatically a hreflang problem. If alternate language URLs themselves point to the wrong equivalents, that needs a separate WordPress hreflang audit for incorrect language URLs.
Likewise, do not reach for an old compatibility snippet because a forum thread says it fixed something three years ago. Check the installed versions of WPML, Elementor and Elementor Pro first, then use the supported translation route where it applies.
Test beyond the popup opening
Language QA follows the visitor’s action all the way to the popup and its submission confirmation. For an Arabic brochure request, the useful route is not merely Arabic page to Arabic popup. It is Arabic page, Arabic trigger, Arabic popup, Arabic form, submitted test entry, Arabic confirmation, and confirmation that the request reaches the intended team.
Use the full Arabic WordPress launch route test when you need to extend that check through the rest of the enquiry journey. It is a better launch check than declaring the page complete because WPML shows a green translation status.
FAQ: What if the popup heading is Arabic but form labels are English?
That normally means the popup template is translated but the embedded form is not. Identify whether the form is an Elementor form, a shortcode from another plugin, or a reusable widget. Then check its labels, validation text, consent fields and success message in the form’s own translation and settings route. Retest the submitted form, not just the popup display.
Include the popup and its form in your Arabic launch review.