When a translated URL suddenly shows a draft's content or the wrong page, compare post IDs and translation relationships before renaming or deleting anything. A shared slug is a clue, not proof that two records are duplicates. Preserve the established published translation while you locate the incorrect owner.
When only the preview is wrong
A wrong preview host or a language mismatch after switching editor tabs is not, by itself, evidence of a same-slug collision. Compare the selected editor record, generated preview URL, redirect chain and returned text before changing a public slug. Keep unpublished content private during the comparison.
Use the separate WPML preview language and domain diagnostic for that workflow. Continue with this ownership guide when an established public translated URL resolves to the wrong record or a same-slug draft is implicated by the record evidence.
Check the WPML 5.2 correction
WPML's 5.2 announcement describes a draft or pending page taking over a published secondary-language page. The detailed 5.2.0 changelog specifies that a same-slug draft or pending page could send the published page in another language to a 404. Wrong-content output needs separate evidence; that release note does not establish a general draft-content exposure defect. Record the installed components and test the supported coordinated update on staging.
Do not conclude that an unrelated draft caused the problem just because it has a similar name. A redirect rule, wrong language relationship, stale cache, or incorrect page template can produce a similar public result. The task is to connect the requested URL to the actual record being served.
Capture a small ownership ledger
Record the original post ID, its language, status, and public URL. Then record the intended translated post and any suspicious draft or pending record. Use the administration interface to inspect relationships and keep a backup before making edits.
| Record |
Example ID |
Intended relationship |
Status |
| Source page |
101 |
Source of the translated page |
Published |
| French translation |
202 |
Translation of 101 |
Published |
| Separate draft |
303 |
Not the translation of 101 |
Draft |
These IDs are synthetic. Replace them with your own recorded IDs, and do not run a bulk operation against example values. Include the actual post type as well as language: pages, products, and custom content can have different routing and translation configuration.
Trace the editor record, public URL, response content and translation job separately before changing a slug or post relationship. Explanatory diagram.
Compare administration, preview and public output
Open the intended translation in the editor and inspect its title and a distinctive non-sensitive text marker. View its public URL as a signed-out visitor. Separately inspect the draft through its authorized preview, without making the draft public.
Record the redirect chain and final URL for the public request. If the browser reaches a different address, investigate redirects before blaming the database relationship. If the URL stays the same but the body is old, compare the origin and supported cache diagnostics. If the editor itself opens the wrong record, preserve that ID evidence before changing slugs.
Use a test copy containing harmless text whenever unpublished material could be exposed. Do not put confidential draft content into a public troubleshooting screenshot. If private content is already publicly reachable, restrict the affected route and involve the responsible owner while the cause is investigated.
Make the correction at the responsible layer
If the supported update resolves the ownership issue on staging, repeat the same published and draft checks before production deployment. If a translation relationship remains wrong, use the vendor-supported relationship workflow or support guidance. Do not patch translation tables with a guessed SQL statement.
When a translation job is involved, retain its source, target, and job identity. A completed job must update its intended translation, not a different post that happens to share wording. A stalled job is a separate problem covered in the automatic-translation state diagnostic.
Avoid deleting the draft as the first experiment. It may contain work that must be preserved, and removal can hide the mechanism without correcting the relationship. Likewise, do not rename the established public URL merely to make the symptom disappear. That can disrupt internal links and create unnecessary redirects.
Verify ownership and discovery after the fix
Confirm that the source and translated URLs each return the intended approved content and language. Check the language switcher, canonical tags, relevant alternate-language links, and sitemap entries. The unrelated draft should remain unpublished and should not acquire the translated page's public role.
Purge only the affected cached routes using the host or cache plugin's supported controls, then repeat a signed-out visit. Keep the ledger and the before-and-after record IDs with the release note. HandL WP can investigate translated URL ownership when content relationships, routing, and cache disagree. A successful homepage load alone does not close this incident.
Sources reviewed November 1, 2026. Examples and diagrams are diagnostic aids, not customer test results.
Editorial update November 3, 2026: diagnostic distinctions and related guidance reviewed. Existing publication date and illustrative assets retained.