If a WPML preview opens the wrong language or domain, first check which record you are editing and which address the Preview action generated. Keep the draft unpublished. Changing the site's public URL or deleting a translation is not a safe first response to a preview mismatch.
Check the relevant WPML release, then reproduce your symptom
The WPML 5.2.0 changelog lists corrections for previews on separate language domains and language context when several block-editor tabs are open. These are related troubleshooting leads, not proof that every wrong-language page has the same cause. Record WPML and add-on versions, the editor being used, and the language URL format before testing a supported update.
Use a protected staging copy with harmless draft text and disabled outbound integrations. Preserve the configured language-domain arrangement where your staging environment supports it. A staging site using language directories cannot fully reproduce a failure that depends on separate domains. Document that limitation rather than calling the domain-specific test passed.
Build a four-part preview record
Choose one source post and its intended translation. Record their IDs from the administration interface, not from a guess based on their titles. Add a unique, non-sensitive phrase to the test draft so that you can recognize the returned content. Keep the marker out of public content when the test is finished.
| Checkpoint |
Record |
What a mismatch suggests |
| Editor |
Post ID and selected language |
Wrong record or language context |
| Preview action |
Generated host and path |
Preview URL generation or configuration |
| Navigation |
Redirect statuses and final host |
Redirect, authentication or host routing |
| Rendered page |
Test phrase and language |
Wrong translation, stale output or template |
For example, a French test record might generate a preview under an English host. That differs from a correct French URL that redirects to the English host, and from a French host displaying English text without a redirect. The first useful repair depends on where the mismatch begins.
Compare the selected record, generated preview URL, final host and rendered language. A correct hostname does not prove that the correct translation was loaded. Explanatory diagram.
Separate a preview session problem from public routing
Open the preview through the editor as an authorized user. Preserve the network log while following the action, then inspect the navigation chain. Do not paste complete preview URLs into public tickets: query parameters may contain temporary authorization material, record identifiers or unpublished paths. Share the host, sanitized path shape, response statuses and relevant timestamps instead.
If the preview stops at a login screen on the second domain, record that as an authentication/session problem. It is not evidence that the translation itself disappeared. Do not make a private draft public, disable authentication, or broadly widen cookie scope to make the test convenient. Ask the site owner or host to review the supported cross-domain configuration.
Compare one already-approved translated page as a signed-out visitor. If that public URL is wrong too, investigate the language switcher and redirect rules separately. If only the preview fails, keep the investigation focused on the preview path. The WPML translated-URL ownership guide covers a different case: a draft or pending record interfering with an established published translation.
Test several editor tabs without losing work
Save or otherwise preserve work before closing any editor tabs. Start with a single disposable post and confirm its language and preview. Next, open a second test record in another language in a separate tab. Return to the first tab and repeat the preview, checking the post ID before saving anything.
Repeat the same sequence after the supported update on staging. A test that works with one tab but fails after switching languages between tabs deserves a clear reproduction sequence. Avoid changing browser language, WPML settings and redirect rules all at once: that makes it difficult to identify which condition mattered.
Do not overwrite a real translation merely to test whether the language selector is stale. Use disposable records and harmless text. If translated content is still in a job queue rather than saved to the expected record, use the WPML automatic-translation state diagnostic.
What counts as a completed fix?
The correct editor record should produce the intended preview host and content, remain in its original publication state, and still work after the multi-tab sequence. Verify a public source page and its approved translation without exposing the test draft. Check that switching languages does not introduce a redirect loop.
Keep a sanitized before-and-after record with installed versions, post IDs, language configuration and navigation results. Remove temporary diagnostic content through the normal editorial workflow. HandL WP can trace a multilingual preview failure when editor context, domains and authentication disagree. A matching address alone is not enough: the content and access state must also be correct.
Sources reviewed November 3, 2026. Examples and diagrams are diagnostic aids, not customer test results.