4 ms·
This was cloaking. Prior to link scheme fiasco they used a javascript redirect on the lyric page, effectively making the the lyric page different from what the
by mikkelewis 13y ago
This was cloaking. Prior to link scheme fiasco they used a javascript redirect on the lyric page, effectively making the the lyric page different from what the user sees and what the bot sees.
I think the 301s are actually their response to Google's ban hammer.
- Ihaveaproblem 13y agoWell I can't prove it, but I first noticed this about three weeks ago and I'm 100% positive they haven't changed anything since then. They may have used JS redirects further back in the past, I'm not sure.
- mikkelewis 13y agoOverride your user agent with Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html http://www.google.com/bot.html). You'll see that both a regular user and a google bot are getting served a 301. So I don't think it's cloaking by definition anymore. However if you go to: http://webcache.googleusercontent.com/search?q=cache:http://rapgenius.com/35640/The-notorious-big-suicidal-thoughts/I-like-black-timbs-and-black-hoodies http://webcache.googleusercontent.com/search?q=cache:http://... You'll see that you get redirected. But disable javascript in your dev tools, and you'll see that you no longer get redirected :)
- Ihaveaproblem 13y agoYa, I did the user agent testing three weeks ago and got the same results I am getting today. I'm certainly not keeping close track of them, so maybe they did change something, but everything I see is 1:1 as it was when I first saw it. Perhaps they are detecting Googlebot via IP instead of user agent. I dunno.
- donthe 13y agoI'm seeing a 302 now. http://imgur.com/yOWhanl http://imgur.com/yOWhanl