Linking to a twitter account? Best to use the /#!/ or not? or no difference?

[Thos003]

So if I am linking to someone's twitter account should I use the ajax code #! or not?

http://twitter.com**/#!/**thos003 vs http://twitter.com/thos003

Bonus Question:

I have also seen in the past that google splits a domain that has as a secure protocol.

https://twitter.com vs http://twitter.com

Does does that split link juice?

[caseyhen]

Hi Thomas,

Check out this article talking about how Google looks at Twitter's use of the hashbang.

http://searchengineland.com/how-twitters-technical-infrastructure-issues-are-impacting-google-search-results-86229

I always link to the non-ajax version.

Casey

[AdoptionHelp]

Good question, but unfortunately I don't know. I imagine it would lose a small fraction of the link juice similar to the way 301's do. On the other hand, I think results in twitter are probably based on internal twitter metrics (followers, followed) rather than page authority.

[Thos003]

Apart from the easier to remember, the link used without the AJAX is being redirected to the AJAX url. So would it theoretically have less juice if it's hitting a redirect?

[AdoptionHelp]

I wouldn't use the AJAX # part because its easier to remember/say and there is less chance that a non-human user (like googlebot) will screw it up.

Using SSL shouldn't split the link juice, because they both refer to the same subdomain, they just use different protocols to transfer the data. Similar to the way you can FTP to mydomain.com or pull it up in a browser using HTTP. They just define the way the URI is sent to the client, they don't represent different resources.