Repair a translated URL that returns 404

Start from the base-language object. Confirm its normal permalink works before diagnosing localization.

Check the route

1. Verify the requested locale is enabled.
2. Confirm the configured locale prefix is unique.
3. Open the object's stored localized slug.
4. For hierarchical posts or terms, verify every ancestor slug.
5. Confirm the object is published and not excluded for that locale.
6. Save Settings → Permalinks to refresh WordPress rewrite rules.
7. Clear page, object, server, and CDN caches.

Do not manually add a prefix to an already localized URL. Generate the route through POM Translate or its selector.

Narrow conflicts

Check whether another plugin or server rule claims the same first path segment. Test post, term, archive, pagination, and WooCommerce endpoint routes separately. A single custom rewrite conflict should not be “fixed” by changing every translated slug.

If the old slug worked before an edit, confirm whether a redirect exists and purge stale cached redirects. POM Translate canonical handling does not replace a deliberate long-term redirect strategy for externally linked retired paths.

The route is repaired when the direct logged-out request resolves once to the intended WordPress object, returns the correct locale, and does not loop or fall back to an unrelated base page.