Place taxonomy archives below a page

A public POM taxonomy can use a published page’s complete permalink as its archive base. This creates one coherent branch in which the page introduces the subject and each term provides a filtered archive.

/documentation/
/documentation/pom/
/documentation/pom/installation/

The first route remains a normal WordPress page. The other routes are taxonomy archives.

Confirm the structure is eligible

Before configuring the base:

1. Open Settings → POM Theme → Content model → Taxonomies.
2. Confirm the taxonomy is connected to the intended post types.
3. Leave Disable archive for this taxonomy inactive.
4. Enable Enable hierarchical URLs if child-term routes should include their ancestors.
5. Publish the page that should introduce the archive branch.

The selected page cannot be the static front page, the posts page, or a descendant of either. It remains independently editable and keeps its normal page template.

Select the page base

1. Open Settings → Permalinks.
2. Find Taxonomy archive page bases.
3. Use the taxonomy selector to choose the published page.
4. Save the permalink settings.
5. Open the page, a parent-term archive, and a child-term archive.

Keep the current taxonomy base (default) leaves the taxonomy’s ordinary custom base unchanged.

Understand the shared URL branch

The page and taxonomy terms share a namespace below the selected path. To keep routes unambiguous:

• One page path can belong to only one taxonomy archive branch.
• Two selected bases cannot be the same path or sit above or below one another.
• A selected taxonomy branch cannot overlap a page-backed custom post type single or general archive branch.
• A colliding page or term slug receives WordPress’s numeric suffix, beginning with -2.
• Existing colliding term paths are normalized when the structure is enabled.
• Child pages beneath the selected page remain routable.

Pagination and feeds continue below the archive route. Saving the base page or one of its ancestors refreshes the affected page-backed paths.

Canonical, translated, and inherited URLs

The page-backed term URL becomes the canonical URL returned through WordPress term links and used by WordPress sitemaps. POM Theme also aligns Rank Math and Yoast canonical output with that URL. Requests to the previous taxonomy base permanently redirect to the new canonical route and retain unrelated query parameters.

POM Translate can localize the page hierarchy, taxonomy path, and term slugs independently:

/es/documentacion/pom/instalacion/
/en/documentation/pom/installation/

When Polylang uses language directories, save Settings → Permalinks after enabling the integration, changing its URL mode, or assigning this base.

If the related post type uses taxonomy-based post permalinks, its entries inherit the same page-backed branch:

/documentation/pom/installation/install-the-theme/

POM Theme and Rank Math breadcrumbs follow the page ancestors and then the term hierarchy. Developers can adjust the page portion with pom_taxonomy_page_base_breadcrumb_pages; return published WP_Post page objects in root-to-base order.

For page-backed single entries and general post type archives that do not use a taxonomy, see Configure custom post type URLs.

Change or remove the page base

Choose a different published page to move the branch, or select Keep the current taxonomy base (default) to restore the taxonomy base. Then save Settings → Permalinks.

Before changing a live structure, inventory term links and entries that inherit it. The previous supported taxonomy route redirects, but menus, external references, and cached output should still be reviewed.

If a term route returns a page or gains a numeric suffix, inspect the complete child-page and term hierarchy for a path collision.