Trailing Slash and SEO: Should Your URLs End With One?

This guide explains how Google treats URLs with and without a trailing slash, when it creates duplicate content, and exactly how to pick one format and enforce it. The good news about trailing slash SEO is that Google has no preference; the only thing that matters is consistency.

Is a trailing slash better for SEO?

No, a trailing slash is not better or worse for SEO; Google does not favour either format. What hurts is serving the same page at both versions without a clear signal of which one you prefer.

Google covered this in its Search Central post To slash or not to slash. The traditional convention is that a trailing slash marks a directory and no slash marks a file, but Google treats each URL on its own merits and does not care which convention you follow. Choose based on your platform. WordPress uses trailing slashes by default with most permalink settings, while many static site generators and JavaScript frameworks default to no slash.

Does a trailing slash create duplicate content?

Yes, if both /page and /page/ return the same content with a 200 status, you have two URLs for one page, which Google treats as duplicates. This is not a penalty. Google’s page on URL canonicalization says some duplicate content on a site is normal and not a violation of its spam policies.

The cost is practical. Google groups the two URLs and chooses one as canonical, and it may not choose the one you wanted. Links, both internal and from other sites, get split between two addresses. Your analytics show the same page twice. And Search Console fills up with statuses like “Duplicate without user-selected canonical”, which my guide to duplicate without user-selected canonical explains.

Should I redirect URLs with a trailing slash?

Yes, you should 301 redirect whichever version you do not use to the version you do, because a permanent redirect is the strongest way to tell Google which URL is canonical. Google’s guide to specifying a canonical URL lists redirects and rel=”canonical” as strong signals and sitemap inclusion as a weak one, and says combining them increases the chance your preferred URL is chosen.

A rel=”canonical” tag on both versions is an acceptable fallback if you cannot set redirects, but a redirect is better because it also fixes the experience for visitors and consolidates links. Most platforms handle this for you:

• WordPress: the permalink structure decides the format, and WordPress redirects the other version automatically. Keep the setting stable; changing it later creates thousands of redirects.
• Apache or Nginx: one rewrite rule can add or remove the slash for all URLs except real files such as .css, .js and images.
• Next.js and other frameworks: a trailingSlash style configuration option controls the format and the redirect.
• CDNs: some apply their own slash rules, so test after any CDN change.

How do you choose and enforce one URL format?

You choose a format by checking what your platform already does and what most of your backlinks use, then enforce it in redirects, internal links, canonicals and sitemaps at the same time. Switching formats on an established site is rarely worth it unless you are migrating anyway, because the redirects and reprocessing add risk with no ranking benefit in return.

1. Test both versions. Request a few page URLs with and without the slash and note the status codes.
2. Check your backlinks. If most links point to one format, prefer it.
3. Set one redirect rule. Send the other format to your chosen one with a 301 in a single hop. Combine it with your HTTPS and www rule so a visitor never passes through two redirects.
4. Fix internal links. Menus, footers, body links and breadcrumbs should all use the chosen format so visitors do not hit redirects inside your own site.
5. Align canonicals and sitemaps. Self referencing canonicals and every sitemap URL should match the chosen format exactly.
6. Watch Search Console. After the change, the other format will show as “Page with redirect”, which is expected. My guide to the Page with redirect status explains why.

You can check your current setup in under a minute. Open a terminal and run curl -I on one page URL with the slash and once without it. One should return 200 and the other a 301 whose Location header points to the first. If both return 200, you have duplicates. If the redirect is a 302 or 307, change it to a permanent redirect. If the Location points to an http or non-www address that redirects again, you have a chain to fix at the same time. Browser extensions that show redirect paths do the same job if you prefer not to use the command line.

Does the trailing slash matter for the homepage and files?

No, the trailing slash does not matter for the bare domain, because example.com and example.com/ are the same request; the browser always asks the server for “/”. It only matters for paths after the domain, so example.com/blog and example.com/blog/ are different URLs.

For files, keep the natural format. A URL like /images/logo.png or /sitemap.xml should not have a slash added, and blanket redirect rules must exclude real files or they will break images, scripts and your sitemap. Query strings come after the slash, as in /shop/?page=2, so they follow the same choice.

What does a trailing slash cleanup look like?

Trailing slash problems usually show up during migrations, so if you are planning one, my website redesign service includes URL format decisions and a full redirect map. For an audit of your current URL setup, my technical SEO service checks slashes, redirects, canonicals and sitemaps together.

Frequently asked questions