Trailing slash

A trailing slash is the forward slash character (/) placed at the end of a URL, as in example.com/page/ versus example.com/page. Although the two addresses look almost identical to a human, a web server can treat them as two distinct URLs pointing to potentially different resources, which has practical consequences for consistency and search visibility.

Why the trailing slash matters

Historically, a trailing slash signalled a directory, while its absence suggested a file. Modern applications route URLs however they choose, so the distinction is now a matter of configuration rather than a hard rule. The important point is consistency: if both versions of an address return the same content without one redirecting to the other, you effectively have two URLs for one page. That can split link signals, waste crawl budget and create duplicate-content confusion for search engines during indexing.

Handling trailing slashes correctly

The recommended practice is to pick one canonical form — with or without the trailing slash — and configure the server to redirect the other version to it with a permanent redirect. This ensures every visitor and crawler lands on a single, consistent URL, consolidating SEO value and avoiding duplicates. Consistency also helps caching: a cache keyed on the exact URL will store two separate copies if both forms are used, reducing hit rates. The choice between the two styles is less important than applying it uniformly across the whole site and reflecting it in internal links and sitemaps. Because URLs ultimately resolve to servers via DNS, the trailing slash operates purely at the application layer, but getting it right is a small detail that keeps a site's addressing clean and its ranking signals undivided.