Trailing Slashes in URLs

To search engines, /about and /about/ are different URLs. Inconsistent use can create duplicate content issues and dilute ranking signals.

"For the root URL, it doesn't matter—but for all other URLs, a trailing slash is significant. Whatever you choose, pick one and stick with it."

The Duplicate Content Problem

This seemingly minor detail creates real SEO problems. When both URL versions are accessible and contain identical content, you effectively have two pages competing against each other in search results. Backlinks might point to either version, splitting the authority that should be consolidated on a single URL.

# Google sees these as different pages:
https://example.com/about
https://example.com/about/

# If both are accessible, you might have:
- Split backlinks between versions
- Diluted ranking signals
- Wasted crawl budget
- Inconsistent analytics data

Each of these problems compounds over time. A site with 1,000 pages could have 2,000 indexable URLs if trailing slashes are not handled consistently. That's twice the crawl budget wasted on duplicate content.

Before deciding which format to use, let's understand the conventions that have emerged across different platforms and frameworks.

Common Conventions

Different platforms have established different conventions for trailing slashes. Your choice often depends on your tech stack, but you can override defaults with proper configuration. The table below shows common patterns.

Now that you understand the conventions, let's implement automatic enforcement so your site always uses your chosen format.

Enforcing Consistency

The best solution is automatic enforcement at the server level. When a user or bot requests the wrong format, your server should respond with a 301 redirect to the correct format. This ensures consistency regardless of how external sites link to you.

// Next.js config (next.config.js)
module.exports = {
  trailingSlash: false, // or true for trailing slashes
};

// Nginx redirect (remove trailing slash)
location ~ ^(.+)/$ {
  return 301 $1;
}

// Nginx redirect (add trailing slash)
location ~ ^([^.]*[^/])$ {
  return 301 $1/;
}

// Express.js middleware
app.use((req, res, next) => {
  if (req.path !== '/' && req.path.endsWith('/')) {
    return res.redirect(301, req.path.slice(0, -1));
  }
  next();
});

Each of these examples shows the same pattern: detect the wrong format and redirect with a 301 status code. The Next.js config is the simplest as it handles both the redirect and internal link generation automatically.

There's one important exception to trailing slash rules that you must understand: static files.

Static Files Exception

Static files like images, PDFs, and other downloads should never have trailing slashes. A trailing slash on a file URL can cause download failures and confuses browsers about the file type. This rule applies regardless of your site's general trailing slash preference.

# Files should NEVER have trailing slashes
✅ /images/logo.png
❌ /images/logo.png/

✅ /docs/guide.pdf
❌ /docs/guide.pdf/

# If your server adds slashes to file URLs, that's a bug

If you notice trailing slashes appearing on file URLs, check your server configuration. Some redirect rules accidentally match file extensions and need to exclude them with a pattern like [^.] to match only paths without dots.