Understand translated term archive URLs

POM Translate assembles a public term archive from several independent pieces. Knowing which piece is wrong avoids repeatedly editing the term name when the problem belongs to routing.

URL composition

A localized path can contain:

1. the language prefix, when that locale uses one;
2. the taxonomy rewrite base;
3. every ancestor term slug for a hierarchical taxonomy;
4. the selected term's own localized slug.

For a child category, the shape may be:

/es/category/parent-slug/child-slug/

A flat tag does not add parent segments. Taxonomy bases can have their own localized value; they are not derived from the translated term name.

Fallback order

For each term in the hierarchy, POM Translate first looks for the target-locale slug, then the base-locale slug, and finally the current WordPress term slug. This can keep an archive functional while one portion of its URL remains in the source language.

Generated term links preserve an existing query string or fragment while replacing the archive path.

Verify an archive

1. Open the source term's normal WordPress archive.
2. Switch to the target locale using a POM Translate selector.
3. Copy the generated target URL.
4. Compare the language prefix, taxonomy base, ancestry, and final segment separately.
5. Confirm the route resolves to the original term ID.
6. Check its canonical and alternate-language links.
7. Follow links from a post, breadcrumb, menu, and taxonomy widget.

Do not create a duplicate term to obtain a translated route. POM Translate resolves localized segments back to the canonical WordPress term and verifies the complete hierarchy.

If a previously published slug changes, arrange an external redirect when needed; saving a replacement slug does not create a redirect automatically. Broader URL configuration is covered in URLs and routing.