Does "seomoz.org" lose LJ when someone use "seomoz.COM" as the link site?

[AlanMosley]

Philip is correct, they will lose link juice thought a 301 from com to org
but it goes further then that as you used uppercase letters. I am not sure about the actual domain name as it seems to give a 200 OK status for seomoz.ORG but resolves to seomoz.org
But try changing the path “to does-seomoz-ORG-lose-…”
You will see that you still get the 200 OK status but does not resolve to ”does-seomoz-org-lose-…”
search engines will see this as 2 different URL’s, really it should 301 to lower case
http://perthseocompany.com.au/seo/reports/violation/the-page-contains-multiple-canonical-formats
Something else I noticed was the /q/ in the path, if you change that to /Q/ you get a 404, this would be because of some code they have comparing the q as binary and not text I suggest

[RyanKent]

I agree with Phillip as well.

A 301 redirect is designed to redirect the user from the old URL to the new one. When the redirect occurs, an estimated 1 - 10% of link juice is lost. This loss is by design and will always occur on any form of redirect. The loss is amplified when multiple redirects occur. A good short video on this topic: http://www.youtube.com/watch?v=r1lVPrYoBkA

I believe Anthony only capitalized the .COM for emphasis. It is true the folder and file portions of a URL are case sensitive, the domain name is not. You can visit any URL on the internet via any form of capitalization of it's domain name. www.seomoz.org = wWw.SeOmoz.ORG.

[AlanMosley]

Well depends on what you mean by case sensitive, the url will work, but it will be seen as 2 separate Url’s to search engines if you use upper case or not(disregarding domain name) , to me case sensitive means it will 404. That is why I pointed out that the “/q/ “ is truly case sensitive, if you change it to /Q/ it will 404
Case sensitive in programming languages means how you compare, Binary or Text

In text Q= q

In binary Q<>q

as they have different binary numbers, the q in the path of this post is probably used in a binary compare and is case sensitive, the rest of the path is not case sensitive.

[RyanKent]

I believe you are confused or mistaken Alan.

To the best of my knowledge, it makes absolutely no difference to anything related to Google whether any letters are capitalized in a domain name. In 100% of cases, Google will show the domain name of an organic search result in lower case.

Some support on this statement: http://www.searchenginejournal.com/url-capitalization-and-seo/12667/

I have personally used websites where internal links always used camel-case, but Google still displayed the URL as lower-case. If I am mistaken, please feel free to correct me. I would love to learn a bit and update my knowledge.

[AlanMosley]

I said "(disregarding domain name), " meaning the path
Read first post
“I am not sure about the actual domain name as it seems to give a 200 OK status for seomoz.ORG but resolves to seomoz.org”

Meaning that’s fine, because it resolved
“But try changing the path “to does-seomoz-ORG-lose-…””
You will see that you still get the 200 OK status but does not resolve to ”does-seomoz-org-lose-…”
search engines will see this as 2 different URL’s, really it should 301 to lower case
http://perthseocompany.com.au/seo... “

Meaning it is not ok
Domain seems to not be a problem, but path is.

The link you posted is confirms what I said, at least with windows servers (As I have always worked with Microsoft technologies)
With lynx the problem is worse because it 404’s , this is something I did not know. This would explain the /q/ in the path 404ing if you capitalize it. The rest of the path acts like a windows server (does not 404), I assume this is because of some URL-rewriting.
But the point is UPERCASE in the path will cause a canonical issue. The same conclusion as Ann Smarty

I say it SEEMS to be ok for domain name, because I believe it is ok I don’t really know how it resolves, I also notice that Ann Smarty also is ambiguous as for domain name.

[AlanMosley]

As for the camelCase example, no it would not resolve unless you 301 it, it would lead to canonical issues (assuming you are talking of path not domain)

IIS servers have a built in url-rewrite template you can use to correct this.
http://perthseocompany.com.au/seo/tutorials/how-to-fix-canonical-issues-involving-the-upper-and-lower-case

[RyanKent]

My original reply was going to be....we will have to agree to disagree. I should have stuck to that reply. This issue is not related to the original Q&A anyway. My apologies for allowing the convo to move in this direction.

As for the camelCase example, no it would not resolve unless you 301 it, it would lead to canonical issues (assuming you are talking of path not domain)

The original Q&A only asked about the domain name. I am not sure why you ever brought up the deeper URL path as it seems completely unrelated to the question. My responses were applicable to the domain name itself as I indicated.

Camel case in the domain name is perfectly acceptable and does not case any issues.

[AlanMosley]

Well in this case there is not much to disagree on.
we can test it
Lynux server
https://www.linux.com/learn/docs 200 OK
https://www.linux.com/learn/DOCS 404 Page doe not exist , does not resolve to lower case
Windows server
http://www.bing.com/toolbox/webmaster/ 200 OK
http://www.bing.com/toolbox/WEBMASER/ 200 OK does not resolve to lower case

Windows server with 301 redirect (my server I have 301 to lowercase)
http://perthseocompany.com.au/seo/tutorials/how-to-fix-canonical-issues-involving-the-upper-and-lower-case 200 OK
http://perthseocompany.com.au/SEO/tutorials/how-to-fix-canonical-issues-involving-the-upper-and-lower-case 301 permanent redirect , resolves only because of a 301 redirect

[RyanKent]

Alan, I am at a loss here. I don't know what words or combination of words I can type to help you.

The original Q&A asked about a domain URL specifically. For an unknown reason you chose to bring up the folder path portion of the URL which I agree uses a different set of case sensitive rules. All of my comments are directed at the base domain URL which I have expressly and repeatedly shared.

At this point I have done all I can here and I will let this topic go. If you disagree with any portion, that is perfectly ok.

Best Regards

[AlanMosley]

I stated, the path with upper case was a canonical isssues, not the domain name, you suggested i was confused or mistaken.

i was not canfused or mistaken, I think it is pretty plain you were