Routing, Navigation & Structural Integrity

Routing, Navigation & Structural Integrity

This document defines the non-negotiable structural rules governing URLs, pages, menus, redirects, and system routes on PenOdyssey.com.

These rules exist to preserve editorial clarity, security stability, SEO consistency, and long-term maintainability.

When in doubt, follow the canon.

I. Slug & Routing Integrity

No WordPress Page may share a slug with a Custom Post Type archive, taxonomy base, or plugin-defined endpoint. Ever.

Slug collisions create ambiguity at the routing and firewall level, often surfacing as 403 Forbidden errors, blocked redirects, or security false positives.

Pages are editorial destinations. System routes are plumbing. They must never overlap.

Approved Patterns

  • Editorial hubs: /all-books/, /press-center/
  • Namespaced taxonomies: /book-author/{term}, /book-series/{term}

Prohibited Patterns

  • Pages named books, authors, series
  • Any Page slug identical to a CPT archive, taxonomy base, or plugin endpoint

Fix collisions by renaming the Page, never the system route.

II. Menu Destination Integrity

Menus must point to intentional editorial destinations, not raw system routes.

Menus are promises to readers. Every destination must be human-intentional, stable under security and caching, and canonical.

Approved Menu Targets

  • Editorial Pages
  • Individual taxonomy terms (e.g., /book-author/john-elcik/)

Prohibited Menu Targets

  • Custom Post Type archive roots (e.g., /books/)
  • Bare taxonomy bases (e.g., /book-author/)
  • Plugin-defined utility or structural endpoints

If a destination feels automatic, it does not belong in a menu.

III. Redirect Integrity

Redirects are corrective tools, not structural dependencies.

Redirects exist to preserve legacy links and signal canonical changes. They must never be required for navigation or discovery.

Approved Uses

  • Old slug to new canonical slug
  • Retired page to curated replacement
  • Legacy URLs blocked by security (server-level redirects)

Prohibited Uses

  • Menu items pointing to redirected URLs
  • Redirects used to mask slug collisions
  • Redirect chains (A → B → C)

Enforcement test: If a redirect disappeared tomorrow and something broke, the structure—not the redirect—is wrong.

IV. Security-Aware URL Design

Pen Odyssey operates with layered security and caching. Certain URL patterns trigger protection automatically.

Avoid Slugs That Resemble

  • Enumeration paths
  • Directory roots
  • Asset containers

Examples to Avoid

  • /books/
  • /files/
  • /media/
  • /downloads/

Preferred Alternatives

  • all-xyz
  • xyz-hub
  • xyz-overview

If security blocks a URL, redesign the route—do not weaken the firewall.

V. Pre-Publish & Pre-Rename Checklist

Slug Ownership

  • Does not match a CPT archive
  • Does not match a taxonomy base
  • Does not match a plugin endpoint

Editorial Intent

  • Reader-facing destination → Page
  • System structure → CPT or taxonomy

Menu Safety

  • Menu item points to final destination
  • Destination works logged out and incognito
  • No redirect required to function

Redirect Hygiene

  • Old slugs redirected intentionally
  • Redirects are single-hop (301)
  • Redirects are not used as architecture

VI. Canonical Principle

Pen Odyssey favors clarity over cleverness, intention over automation, and editorial control over default behavior.

When uncertain:

  • Rename the Page
  • Create a hub
  • Avoid raw system paths

Silence from security tools is success.