Troubleshoot translated URLs and 404 errors

Start with one exact request. Record its status, redirect target, active locale, expected object ID, base URL, target URL, and whether the link was typed or generated.

The language root returns 404

1. Confirm the locale is still enabled.
2. Confirm that locale is configured to use a prefix.
3. Copy the prefix from a POM Translate selector rather than guessing it.
4. Open Settings → Permalinks and save the current structure once.
5. Check that the web server still passes normal WordPress routes to index.php.

If every path below the same prefix fails, investigate rewrite configuration before editing individual slugs.

One post or term returns 404

Open Translations → Translate URLs → Content URLs, load the object, and confirm its Base slug and target-locale value. Then inspect each segment:

• language prefix;
• post-type or taxonomy base;
• hierarchical ancestors;
• final object slug;
• pagination, feed, or endpoint suffix.

Use a generated permalink. A typed path may contain an obsolete or incorrectly normalized value.

The wrong object loads

Search Current content URL translations for duplicate-looking values. The editor blocks new exact conflicts, but imported or legacy data may still need review. Confirm the object type, object ID, taxonomy, and hierarchy before replacing anything.

The route redirects repeatedly

Compare the requested and final paths character by character. Check:

• duplicate or missing locale prefixes;
• a reverse proxy changing trailing slashes;
• an SEO or redirect plugin enforcing a different canonical;
• stale cached redirects;
• the base-language prefix setting;
• source and localized segments mixed in one path.

POM Translate redirects a resolvable non-canonical localized path to its current form. Another component redirecting it back creates a loop.

The page intentionally becomes a 404

For a non-base locale, a post or term excluded from that locale is forced to 404 even if WordPress can resolve the canonical object. Review translation exclusions before treating that response as a rewrite failure.

The URL works but SEO output is wrong

Inspect canonical and alternate links separately. Confirm the active SEO plugin, clear its own cache, and compare the localized route with Understand canonical URLs and Understand alternate-language links.