Last updated on April 15, 2026
Currently, each custom post type (CPT) such as Fragments, Chapters, and Elements uses a redirect system that points the default archive slug (e.g., /fragments/) to a custom display page (e.g., /narrative-fragments/). This ensures proper breadcrumb and canonical behavior while keeping archive pages disabled. Although this method functions correctly, it introduces redirect hops that can clutter analytics and create minor SEO noise. A future improvement would involve restructuring CPT registrations to map the archive slug directly to the intended display URL (e.g., setting ‘has_archive’ => ‘narrative-fragments’ and ‘rewrite’ => [‘slug’ => ‘narrative-fragments’]). This would remove the need for redirects, unify canonical paths, and simplify template logic by routing archive requests straight to the custom page template. The task involves evaluating whether to implement this cleaner architecture sitewide, testing breadcrumb consistency, and confirming compatibility with existing SEO and navigation systems.
