Do trailing slashes matter for SEO? Google’s answer has been stable for fifteen years: /page and /page/ are two different URLs, treated separately and weighted equally. Neither version ranks better. The slash only becomes an SEO problem when both versions of the same page resolve and nothing tells Google which one is canonical. Then it is not a slash problem, it is a duplicate URL problem wearing a slash.
While writing this I audited my own site for it and found something worth being honest about, which I will get to.
Is a trailing slash better for SEO?
No, and Google has said so directly since its 2010 “To slash or not to slash” post, which the current documentation still reflects. The two forms are separate, equal URLs. The one place the slash is not optional is the bare hostname: https://example.com and https://example.com/ are literally the same URL, because the root slash is implied. Everywhere deeper in the path, the two forms are distinct, and either can be your standard. Convention says directories take the slash and files do not, but Google does not care which convention you pick. It cares that you pick one.
What happens when both versions return 200?
This is the actual question behind the keyword. Three configurations exist, and Google’s guidance covers each:
One version redirects to the other. The good state. Duplicate content cannot arise, and search results show the URL that returns 200, whether the redirect was a 301 or a 302. Which permanent status code you use matters even less than people think, something I measured on this site in 301 vs 308 redirect.
Both return 200 with the same content, with canonical tags. Google’s documented consolidation path: rel="canonical" works similarly to a 301 for indexing purposes. Google crawls both URLs but indexes and shows the one the tag names.
Both return 200 with the same content, with nothing. Google picks a canonical itself, and usually picks fine. The 2010 post is surprisingly relaxed about this state, calling it legitimate while recommending you fix it for crawl efficiency. The cost is real but modest: every page crawled twice, and any links people point at the non-canonical form consolidating a step later. On large sites that doubling is exactly the kind of waste that shows up in crawl stats.
What I found on my own site
The honest part. This site serves both forms with a 200. https://www.shahidali.co/blog and https://www.shahidali.co/blog/ both return the page, no redirect between them, and the same is true of every post URL. I verified it today with direct HTTP requests.
What makes that configuration safe rather than sloppy is the second layer: both forms serve an identical canonical tag pointing at the trailing-slash version. Fetch either variant of any page here and the HTML says rel="canonical" href="https://www.shahidali.co/blog/", with the slash. Every internal link on the site uses the slash form, and the sitemap lists only slash URLs. So all three of Google’s consistency levers, canonical tag, internal links and sitemap, agree on one version.
Would a redirect be stricter? Yes, and Google’s steps for serving one version list the 301 first and the canonical tag as the strong second option when a redirect is not possible. On this static host the canonical-tag route was the configuration the framework gave me, and Search Console agrees it works: the Page indexing report shows no duplicate statuses for slash variants on this property, and inspected URLs report the slash form as both my declared canonical and Google’s selected one. If those two ever disagree, that is the situation I unpacked in duplicate without user-selected canonical.
How do I check my own site?
Four requests tell you everything. Fetch a deep page in both forms and record the status codes, then look at the canonical tag in whichever forms return 200:
- One form redirects to the other: done, you are in the good state.
- Both return 200, canonicals agree on one form: fine, but make internal links and the sitemap match it.
- Both return 200, each names itself canonical: this is the state that fragments signals, because now the duplicate pair carries contradicting declarations. Fix the template so one form wins.
- The pair returns different content: rare, legitimate per Google, and almost always an accident when I find it in an audit.
Then confirm in Search Console rather than assuming: inspect one URL in each form and compare the declared and selected canonicals. When they match your intent, the slash question is closed for your site. If instead you are seeing the related status where Google acknowledges your tag but picks differently, start with alternate page with proper canonical tag, because that status is usually the system agreeing with you, not overriding you.
Sources
- Google Search Central blog, To slash or not to slash, on separate equal URLs, redirect behavior and the steps for serving one version, checked 30 August 2026
- Google Search Central, consolidate duplicate URLs, on rel canonical as a strong consolidation signal
- My own HTTP and canonical tag measurements on shahidali.co, 30 August 2026