Stable RFC 3986 Section 6.2.3 Architecture

Trailing Slash Consistency

Last updated: 2025-12-01

01 The Rule

Choose one convention — trailing slash or no trailing slash — and enforce it universally. Every URL that deviates from the chosen convention must 301 redirect to the canonical form.

02 Rationale

/page and /page/ are technically different URLs. If both resolve to content, search engines see duplicates. Inconsistency across a large site creates thousands of duplicate pairs, each competing for crawl budget and splitting link signals.

03 Implementation

  • Pick one convention and document it in your URL specification
  • Configure server or CDN to 301 redirect the non-canonical variant
  • Ensure all internal links use the canonical form
  • Set canonical tags to the chosen convention
  • Update sitemaps to use only the canonical form

04 Common Violations & Consequences

Violation

Both /page and /page/ return 200

Consequence

Duplicate content — Google must guess which is canonical, often choosing incorrectly

Violation

Internal links mix both conventions

Consequence

Crawl budget wasted following both variants; link equity split

Violation

Canonical tag points to one form but links use the other

Consequence

Conflicting signals — search engines may ignore the canonical hint

05 The Fix

Implement a middleware or CDN rule that enforces your chosen convention. Audit all internal links and sitemap entries. Use the Canonical Audit Tool to verify consistency.