To Slash or Not to Slash. That’s A Server Header Question.

Slash or not to slashUh, not that kind of slashing!

Let’s say you are setting up your keyword rich links to point to a subdirectory. Should the link point to: or to with a “/” at the end?

Most new SEOs won’t know the difference, thinking that if it gets the visitor there, it works, right?

There is a problem with this thinking. Let me introduce you to checking server headers. To do this, I’ll use my favorite server header tool over at . You just pop a URL in the field and you’ll get a page back telling you how it did. Here are some of the possible results:

200 OK – This means everything’s cool.

301 Moved Permanently – The URL you typed in is properly being redirected to a new location.

302 Found – This means your URL has temporarily been moved and found at the new location.

There are several other status indicators, but for the purpose of this article, we’ll concentrate on these three. Actually, your server header status can come back as a combination of these. For instance, if you have a good 301 redirect in place, you’ll first see a 301 Moved Permanently message and then a 200 OK message below it.

Sample server header check

With a non-redirected page, you just want to see a 200 OK message when you enter any URL. As an example, if you do a server header check for or you’ll get a 200 OK for either.

But, that’s not always the case. Sometimes, particularly on Microsoft IIS web servers, what you will get back will be totally different when you check server headers with the “/” or without it. On such servers, what you can get is a 302 Object Moved message and then the 200 OK message when you check for the subdirectory URL without the “/” included. This means that the web server automatically 302 redirects the non-slashed URL to the slashed version.

This is not good and not particularly SEO friendly. Although there are good reasons to use a 302 redirect at times, it is meant to be used as a temporary redirect, not permanent. Web sites have been known to get into trouble with the search gods for using 302 redirects instead of the 301 permanent redirect and link juice is said to be passed almost totally with a 301 redirect. Such is not the case with a 302 redirect. Again, it is supposed to be temporary.

What can you do? First, check your URLs to see if you have this issue. If not, don’t sweat it, though I recommend that you stick with a standard way of writing your URLs – preferably with the “/” at the end – Pointing to exactly the same URL every time is always a good thing in SEO, not unlike the canonical issue with using www or not in a URL. It’s best to choose one and always use it. Don’t mix and match.

If you do find that your non-slashed subdirectory URLs are being 302 redirected, make a point of always, always, always, using the slash at the end. Do a link audit on your site and check for this type of link and change them so that they include the ending slash.

In the long run, you and your site’s SEO will be better off. Your links will be better focused without unwanted (and unexpected) 302 redirects in the way.


One thought on “To Slash or Not to Slash. That’s A Server Header Question.

  1. Damn right. It’s absolutely critical to have consistency with your link addresses. Aside from the 302/301s, some servers will even serve the content as 200 from both request URLs – leaving you open to duplicate content penalisation. Nightmare!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s