Most questions about trailing slash in URL SEO come down to one worry: does Google prefer /blog/ or /blog? It does not. What it does care about is that they are two separate addresses, and a site that answers on both has quietly doubled some of its URLs.
That makes this a housekeeping issue rather than a ranking lever. You will not gain anything by switching from one form to the other. You can lose crawl efficiency and muddle your signals by leaving both live.
What Google has said about trailing slashes
The clearest statement came from Google’s John Mueller, reported by Barry Schwartz at Search Engine Roundtable in December 2017 in a piece on trailing slashes in URLs. Mueller drew a line between two places a slash can appear.
After the hostname, it does not matter: “the slash after a hostname or domain name is irrelevant, you can use it or not when referring to the URL, it ends up being the same thing.” Everywhere else, it does: “a slash anywhere else is a significant part of the URL and will change the URL if it’s there or not.”
His example made the point concrete. google.com/humans.txt works. Add a trailing slash and the same request returns a 404, because to the server it is a different resource that does not exist.
Trailing slash in URL SEO: which URLs are the same
Put side by side, the distinction is simple. Only the root of the domain is slash-neutral.
| URL pair | Same URL? | Why |
|---|---|---|
| example.com and example.com/ | Yes | The slash after a hostname is “irrelevant” |
| example.com/blog and example.com/blog/ | No | A slash anywhere else “will change the URL” |
| example.com/guides/soil-testing and example.com/guides/soil-testing/ | No | Two addresses that may serve the same page |
| google.com/humans.txt and google.com/humans.txt/ | No | Mueller’s example: the slashed version returns a 404 |
The example.com paths are illustrations. The humans.txt pair is the one Mueller cited.
Why both versions cause problems
Whether /blog and /blog/ behave differently is decided by your server, not by Google. Some servers redirect one to the other automatically. Some return a 404 for the form they do not expect. And some serve the same page on both, with a 200 status, which is the case that creates SEO problems.
When both versions return the same content, you have two URLs for one page. Search engines have to work out which is the main one, links can be split between them, and crawlers spend fetches on addresses that add nothing. It is a small instance of the problem our guide to duplicate content covers in full. Google usually picks one version to show, but you are leaving the choice to it rather than making it yourself.
The opposite failure is quieter. If your server only answers on one form and your internal links, sitemap or old backlinks use the other, those links lead to 404s. That is how a site can end up with a crop of broken internal links after a platform change, all caused by one character. Migrations are the usual trigger: the old system used one form, the new one defaults to the other, and nobody maps the difference because the URLs look identical at a glance.
Should you use a trailing slash or not?
Either. There is no ranking difference between the two, and nothing in Mueller’s comments suggests one. Follow whatever your platform does by default. WordPress sites commonly use the trailing slash; many other frameworks and static hosts do not. Fighting the platform’s default creates more redirect rules and more room for error.
A convention some sites follow is a slash for folder-like pages and none for files, so /blog/ but /sitemap.xml. That mirrors how URLs have traditionally mapped to directories and files, and it explains why Mueller’s humans.txt example breaks with a slash. It is a sensible habit, not a requirement.
Trailing slash URL best practice
The fix is consistency, applied in four places.
Redirect the other form. Pick the version you use and send the other to it with a permanent redirect. A request for the unslashed URL should get a response like this:
A 301 rather than a 302 tells search engines the change is permanent; our comparison of 301 and 302 redirects explains why that matters. Make sure it lands in one hop, not as the second step after an http-to-https redirect.
Use a self-referencing canonical. Each page’s canonical tag should name the chosen form, as a backstop if a duplicate ever gets served:
Link consistently. Internal links, navigation and breadcrumbs should all use the chosen form, so crawlers and visitors never hit the redirect in the first place. List consistently. Your XML sitemap should contain only the chosen form, too.
How to audit an existing site
Request a handful of pages in both forms and note the status codes. You want a 200 on the chosen version and a single 301 to it from the other. Two 200s mean duplicates; a 404 on the other form is acceptable for search engines but wasteful for visitors following old links, so a redirect is better.
Test more than the homepage. Category pages, posts, files and pages with query strings are often handled by different rules, and the inconsistency tends to hide in whichever template nobody checked. Search Console’s page indexing report is also worth a look: pairs of slashed and unslashed URLs appearing as alternates or duplicates are a sign both forms are being crawled.
Then crawl the site and filter internal links for the form you are not using. Every one of those is a link that passes through a redirect, or worse, hits a 404. Fix them at the source in templates and menus rather than relying on the redirect forever. Check the sitemap and canonical tags in the same pass. If you are planning wider changes, our guide to URL structure for SEO covers what else is worth changing and what to leave alone.
One limitation is worth stating. The guidance here rests on a statement made in 2017, and Google rarely says how much a duplicate URL actually costs a given site. On a small site, the effect of serving both forms may be negligible. The reason to fix it anyway is that the fix is cheap, permanent and removes a source of confusion you would otherwise have to diagnose later.
Frequently asked questions
Does a trailing slash affect SEO?
Not as a ranking factor. But outside the domain root, /page and /page/ are different URLs, so serving both creates duplicates.
Is example.com the same as example.com/?
Yes. John Mueller said the slash after a hostname or domain name is irrelevant and ends up being the same thing.
Should URLs end with a slash?
Either form is fine. Use your platform’s default, redirect the other form with a 301, and link to the chosen form everywhere.
Should I change all my URLs to add or remove the slash?
No. There is no ranking gain in switching. Keep your current form and make sure the alternative redirects to it.
The takeaway Pick one form, 301 the other to it, and use the chosen form in links, canonicals and sitemaps. The choice itself does not matter; consistency does.
