Resolve translated URL conflicts

Each stored slug must identify one route object within a locale. The Content URLs editor checks the normalized target against the complete stored slug dictionary before saving it.

Recognize the error

If another object already uses the value, POM Translate reports:

Slug "value" is already in use for locale.

The conflicting field is not updated. Other non-conflicting locale values submitted in the same form can still be processed.

Choose a distinct slug

1. Note the normalized value shown in the error.
2. Review Current content URL translations for the same locale and slug.
3. Identify whether the owner is a post or term.
4. Decide which object should keep the clearest address.
5. Enter a meaningfully distinct value for the other object.
6. Select Save slugs again.
7. Test both generated routes.

Spaces, capitalization, punctuation, and accents can normalize to the same WordPress slug. Cosmetic differences in the input are therefore not a reliable way to avoid a collision.

Consider the complete path

The storage check is intentionally conservative across stored route slugs in the same locale, even when two objects might appear below different route bases. This keeps segment-to-object lookup deterministic during generic path localization.

Also review hierarchy. Two child pages can share a final WordPress slug in some native structures, but POM Translate's localized slug dictionary still needs an unambiguous segment-to-object mapping.

Protect published URLs

If resolving a conflict changes an already public address:

1. record the former URL;
2. save and verify the replacement;
3. add an explicit permanent redirect;
4. update internal links, canonical expectations, and alternate-language checks.

The slug editor prevents current dictionary collisions; it does not create historical redirects.