| 12:47 am on Jan 25, 2007 (gmt 0)|
|Are google smart enough... |
It would not be smart of them at all -- the web standard set way back when by the W3C is that the URI is case sensitive beyond the domain. Yes, changing the case like that can lead to duplicate uri problems. I've seen it with clients and helped them fix it.
| 12:58 pm on Jan 25, 2007 (gmt 0)|
Thanks for the answer Tedster. So i should focus on one type of uris then, huh?
| 3:45 pm on Jan 25, 2007 (gmt 0)|
Absolutely. Most people will tell you to just make everything lowercase and leave it at that, but no matter what you do, keep it consistent - both internally (all the content in your site) and externally (all the people that link to your site). As it's much harder to control the latter part, leaving things lowercase by default again makes it simpler to keep things consistent.
| 5:53 pm on Jan 25, 2007 (gmt 0)|
Alright, thanks a lot for heads up! I really appreciate it.
| 12:07 pm on Jan 26, 2007 (gmt 0)|
Capitalistation issues are one of the main causes of duplicate content problems when using IIS.
Apache is immune to it.
| 11:30 am on Jan 29, 2007 (gmt 0)|
On a similar subject...
If I changed this URL:
Would it be treated as a completely new URL even though the capitalisation of one letter is the only change? (I think there would be no dupe content issues because the partner parameter is dynamic)
| 11:46 am on Jan 29, 2007 (gmt 0)|
Yes it would because everything beyond the TLD is case-sensitive dynamic or not.
| 12:27 pm on Jan 29, 2007 (gmt 0)|
If you're using IIS then yes, make sure you don't mix and match your querystrings... we experienced massive duplicate content problems due to this, and it took considerable time and effort to resolve.
| 10:01 pm on Jan 29, 2007 (gmt 0)|
If anything at all about the URL is different then it is a different URL.
Multiple URLs that return the same content are "duplicate content".