Google reads yoursite.com/repairs and yoursite.com/repairs/ as two separate addresses. That sounds bad, and it almost never is. If one of them already bounces to the other, or your pages already name a preferred one, the slash is costing you nothing.
Two addresses, not one
Google said this plainly a long time ago and has not taken it back. In a post titled “To slash or not to slash” on the Google Search Central Blog, dated Wednesday, April 21, 2010, Maile Ohye, a Developer Programs Tech Lead there, wrote that Google “treats each URL above separately (and equally) regardless of whether it’s a file or a directory, or it contains a trailing slash or it doesn’t contain a trailing slash.”
That page carries no update date. It is sixteen years old. Worth knowing before you treat it as fresh news.
The rule underneath it is older. RFC 3986, “Uniform Resource Identifier (URI): Generic Syntax,” by Berners-Lee, Fielding and Masinter, January 2005, is the standard that defines what a web address is. Google names that same standard in its own URL documentation, where it says Google Search “supports URLs as defined by IETF STD 66.” The RFC makes the scheme and the host name case-insensitive, then says “the other generic syntax components are assumed to be case-sensitive unless specifically defined otherwise by the scheme.” The part after your domain name is one of those other parts. Two paths that differ by one character are two paths. A slash is a character.
There is one exception, and it is the handy one. RFC 3986 lists four forms of a bare home page address as equivalent, and the first two on that list are http://example.com and http://example.com/. The 2010 Google post says the same thing in plainer words: for your root address, the version without the slash “is equivalent to” the version with it, and it “can’t be redirected.” So this question never applies to your home page. Only to pages below it.
Check your own site in two minutes
Open your contact page. Look at the address bar. If it ends in a slash, take the slash off and press enter. If it does not end in one, add it.
Three things can happen.
- The address snaps back to the version you started with. Your site redirects. Nothing to do.
- The page loads and the address stays the way you typed it. Both versions work. Read the next section.
- You get a “not found” page. Your site serves one version only. That is fine too, though a redirect is friendlier to anyone who typed it by hand.
Two of those three patterns are live on well known sites right now, the redirect in both directions and the case where both versions load. Check each one yourself:
- wordpress.org/news returns a 301 redirect and adds the slash.
- www.energystar.gov/products/ returns a 301 redirect and takes the slash off.
- The 2010 Google post loads with a 200 response at both addresses, with the slash and without it.
Two large sites, two opposite choices, and neither is in trouble. That is the real answer to “which one should I use.” Either. Pick one and stay with it.
What to do if both versions load
Google’s 2010 post gives two ways out, and it puts them in order.
The first is a 301 redirect from the version you do not want to the one you do. The post tells you to choose a preferred version, use that version in your internal links, put that version in your sitemap file, and leave the other one redirecting.
The second is the fallback. If a redirect is not possible, the post calls the canonical tag “a strong option.” That is a single line in a page’s code naming the address you want counted. Google runs its own blog this way. Both versions of that 2010 post return a 200 response, and both carry the same canonical line pointing at the version without the slash. If Google is happy to run its own documentation like that, your site will survive it.
You may need neither. Google’s documentation page on how to specify a canonical address, last updated July 10, 2026, says that while Google encourages these methods, “none of them are required; your site will likely do just fine without specifying a canonical preference.”
If you do add a redirect, add one, not a stack of them. A redirect pointing at another redirect is a separate small mess of its own. Leave the redirect in place once it is there, since how long you keep a redirect is a separate question with a separate answer.
The same rule bites harder on capital letters
The slash rarely bites. Capital letters do, and it is the same character by character rule doing it.
Google’s “URL structure best practices for Google Search”, last updated December 10, 2025, puts Google in the same camp as the standard: “Like any other HTTP client following IETF STD 66, Google Search’s URL handling is case sensitive (for example, Google treats both /APPLE and /apple as distinct URLs with their own content).” The same page adds that if your server treats upper and lower case text the same, you should convert it all to one case, so Google can tell that the two addresses are one page.
You can prove this on Google’s own site in ten seconds. Their documentation sits under developers.google.com/search/docs with a lowercase s. Change that s to a capital S and the address returns a 404. Same words, same server, one different letter, no page.
For a trade business this shows up on paper. Somebody prints YourSite.com/Emergency-Service on a card, a yard sign or a truck wrap, and the site only ever served the lowercase version. That address is dead, and it stays dead for the life of the sign, since print cannot be redirected. Type any address into a browser before it goes on a vehicle.
What fixing this will not do
It will not lift your rankings, and nobody can promise you it would. A slash is not the sort of thing that moves a local trade business up or down a results page.
It will not explain a drop in calls. If your traffic fell off after a new site went live, the slash sits near the bottom of the list of suspects. Start with why traffic drops after a new site launches instead.
It is also not worth paying for on its own. If someone quotes you for a URL audit and the trailing slash is the headline finding, you are being sold a chore that takes a competent developer a few minutes on a site that was built properly. Ask what else they found. If the answer is thin, keep your money.
One more limit, said out loud. The clearest official word on this is a blog post from 2010 with no update date, and Google’s current URL page does not mention trailing slashes at all. So the honest position is narrow: Google has treated these as separate addresses for a long time and has never said it stopped. That is all the evidence supports.
What to do next
- Open your contact page. Try the address both ways, with the slash and without it.
- If one version bounces to the other, you are finished. Close the tab.
- If both versions load, find which one is in your sitemap file and your menu links. Ask whoever runs your site to redirect the other one to it, or to add a canonical line naming it.
- Type your three busiest page addresses with a capital letter in them. If any return a “not found” page, fix the ones printed on signs, cards and trucks first.
- Leave your home page alone. The slash there is not a choice anyone gets to make.
None of this is a rebuild, and none of it is urgent. If your site is old enough that nobody can tell you which version it serves, that says something about the site rather than about the slash. A site built this decade picks one form and holds it everywhere, in the menu, the sitemap and every internal link, from the first day it goes live.