Trailing slashes only matter when both versions of a URL load. Pick one format, redirect the other and use it consistently.
Trailing slashes matter for SEO only when your site serves the same page at both versions of a URL. Google treats /page and /page/ as two different URLs, so if both load, you have duplicate content and split signals. Pick one format, redirect the other to it, and use it consistently.
Whether you use a trailing slash or not makes no difference to rankings in itself. Google has said it doesn’t prefer one over the other. What causes problems is inconsistency.
The fix is usually a single server or CMS rule, but trailing slash issues often go unnoticed for years because both versions of every page work fine for users.
What a trailing slash is
A trailing slash is the forward slash at the end of a URL, as in example.com/services/ rather than example.com/services. Historically, a trailing slash meant a folder and no slash meant a file. On modern websites that distinction rarely holds, because most URLs are generated by a CMS rather than mapped to real folders.
The root of a domain is the exception. example.com and example.com/ are treated as the same URL, because browsers add the slash automatically. You don’t need to redirect one to the other.
When trailing slashes cause SEO problems
Problems start when both versions of a page return a 200 status. Google then sees two URLs with identical content, and has to choose one as canonical. That causes a few issues:
- Split signals. Links pointing at both versions are divided between them until Google consolidates them.
- Wasted crawling. Google crawls both versions of every page, which matters on large sites.
- The wrong version ranking. Google may pick the version you didn’t intend, especially if your internal links are mixed.
- Messy reporting. Analytics and Search Console split data for the same page across two URLs.
Google is usually good at working out that the two versions are the same page. But relying on Google to guess is never as reliable as telling it clearly. A clear, consistent URL format also makes every other technical job easier, from redirects to canonicals to reporting.
How to check your site
Take a few important pages and load each one with and without the trailing slash. You want to see one of these results for the version you don’t use:
| What happens | Is it a problem? |
|---|---|
| 301 redirect to your preferred version | No, this is the ideal setup |
| 404 error | Acceptable, though a redirect is friendlier if anyone links to it |
| Page loads with a canonical tag to the preferred version | Workable, but weaker than a redirect |
| Page loads with no redirect and no canonical | Yes, this creates duplicate URLs |
A site crawl will show whether this happens across the whole site, and whether your internal links mix the two formats. In Search Console, the Page indexing report can also show URLs flagged as duplicates where Google chose a different canonical.
How to fix trailing slash issues
Choose one format and make every part of the site agree with it.
- Pick your format. If your site already mostly uses one style, keep it. Changing every URL on an established site creates work and risk for no ranking benefit. WordPress, for example, uses trailing slashes by default.
- Redirect the other version. Add a server-side rule (in your server config, CDN or CMS) that 301 redirects every non-preferred URL to its preferred equivalent. Our guide to SEO redirects covers how to do this without creating chains.
- Update internal links. Make sure navigation, body links and footers all use the preferred format, so users and Googlebot never hit a redirect from inside your own site.
- Set self-referencing canonicals on every page using the preferred format.
- List only preferred URLs in your XML sitemap.
- Recrawl to confirm. Check that the old format redirects in a single hop and that no internal links point at it.
Watch for conflicts. If your CMS adds a trailing slash and your server or CDN removes it, you’ll create a redirect loop. Make the change in one place only.
Trailing slashes and files
Don’t add trailing slashes to URLs that end in a file extension. example.com/sitemap.xml and example.com/image.jpg should never have a slash after them. Most redirect rules exclude files automatically, but it’s worth checking after any change, because a broken rule here can stop your sitemap or images loading.
Trailing slash consistency is one of the checks in every technical SEO audit we run. It’s rarely the cause of a big traffic drop on its own, but it often sits alongside other duplication issues that are. If you’d like us to look at yours, book a free strategy session.
Related reading: our guides to indexability and keyword cannibalisation.
Common questions
Does Google prefer URLs with or without a trailing slash?
Neither. Google has no preference. What matters is that each page resolves at one version and the other version redirects to it.
Is example.com the same as example.com/?
Yes. For the root of a domain, the two are treated as the same URL. You don’t need to redirect between them.
Should I change my URLs to add or remove trailing slashes?
Usually not. Changing the format across an established site means redirecting every URL for no ranking gain. Keep the format you have and make it consistent.
Can trailing slashes cause duplicate content?
Yes, if both versions of a page load without a redirect or canonical. Google sees two URLs with the same content and has to choose which one to index.
