According to web standards, all URLs should be case sensitive. This is the case for Google and other search engines, but unfortunatelly this rule is not respected by Microsoft servers. This means your website could be serving duplicate content on hundreds or thousands of pages. Read this article to protect yourself against this issue.
google pr, case sensitive, seo, search engine optimization, duplicate content
After a little digging up, I found enough evidence to believe that…
- Google searches are never case sensitive – as we already knew.
- Google PR is case sensitive – as I suspected, according to web standards, URLs are case sensitive. Google and other search engines follow this standard.
There have been a few reported cases of the same pages being in Google’s index 2 or more times because they were linked to with different cases (ie.: /ABC.htm, /abc.htm, /Abc.htm) – see this post.
The root of the problem, as you may have guessed, is Microsoft’s ignorance towards web standards. Microsoft servers are set up in opposition to the web standard on case sensitivity in which /ABC.htm is different from /abc.htm. IIS ignores the case different and gives control of the request to wrong file.
My site is on a Windows Server, how bad is the problem?
Well, it’s not going to ‘bring down the internet’ as some lammers might suggest, but there are issues that need to be addressed. IIS’s choice to ignore case sensitivity means search engines (which are case sensitive) will index the exact same content for different URLs. It’s very unlikely a website would be penalized for this, but it can definitelly impair your website’s ability to rank well. It makes it specially difficult for the duplicated page to rank well for the terms it targets.
This is only an issue if there are two or more links point to the same URL in a different case. You can avoid this problem by always using lowercase in your link tags, but you can’t stop other websites linking into the same URL in capital letters – so something must be done on the server in order to deal with this issue.
How can I fix it?
I can almost picture you “URL Rewrite Junkies” jumping up and down with the solution on your hands, but as we all know, URL Rewrite is a feature only available to proper web-servers, nothing you’d expect to see in IIS.
A. Server Component (IIS alternative to URL Rewrite)
Not free, not easy to setup and can only be installed on your own server. The only upside is that this would work for all files/scripts/directories on the website.
An alternative for URL Rewrite in IIS – ISAPI Rewrite.
B. Script (and a little permanent redirection)
It’s free, it’s easy to setup and can be installed on any server, not just your own. The only downside is that you can only enforce case sensitiveness for requests that are handled by this script. This means static HTML pages, directories, images, etc would still be exposed to this issue. HOWEVER, if with a little help from a custom 404 error page you can do just about anything. But that’s a whole other topic…
Here’s how you’d enforce case sensitiveness using VB Script:
<% ' Force lowercase URLs
If Request.ServerVariables("URL")<>LCase(Request.ServerVariables("URL")) Then
Response.Status = 301 'Permanently Redirected
Response.AddHeader "Location", LCase(Request.ServerVariables("URL"))
It doesn’t need to be the very first thing on every page, but in order to perform a proper permanent redirect, this has to be execute before any content is written to the response’s output stream, ie.: Before any HTML or Response.Write.
Hope this helps a few up-and-coming SEO experts (and wanna-bes)