4 ms·

Hi Pierre - Thanks for the details on this! We dug into our Wordpress and realized that W3 Total Cache was configured to block anything that had the word 'bot'

by jeresig 15y ago

Hi Pierre - Thanks for the details on this! We dug into our Wordpress and realized that W3 Total Cache was configured to block anything that had the word 'bot' as part of its user agent string (sigh). That's now fixed and live. As to the redirect - that's actually a bit of devious magic on our end. Since jquery.it is hotlinking to our JavaScript and CSS we just added a bit of JavaScript to automatically redirect them to the right jQuery.com page: if ( /jquery\.it/.test( window.location.hostname ) ) { window.location = window.location.href.replace('y.it', 'y.com'); } Thanks again for your pointers - looks like the jQuery 1.6.2 blog post is already showing up in the search results and jQuery.it is not in the first page of results (although "jquery 1.6.1" hasn't updated yet and jQuery.it is still there - I assume that it'll be remedied as the Google spider makes more progress). Thanks again!

yuhong 15y ago
Of course, the best solution is to get the jquery.it domain name transferred to the genuine owner of jQuery, but that will take time.
- jeresig 15y ago
  Naturally, we're talking with our legal representation about that - we'll have to see what we can actually do. I think we're "ok" for now though as users are getting to the right place in the end.
pierrefar 15y ago
>configured to block anything that had the word 'bot' as part of its user agent string Yep, that'll do it :) Glad you found it and fixed it quickly! One follow-up thought for you and anyone in this situation: Set up a Google Webmaster Tools account ( http://www.google.com/webmasters/tools/ http://www.google.com/webmasters/tools/ ) and make reviewing it part of the webmasters' daily routine. In this particular case, the Crawl Errors page in the Diagnostics section would have flagged this problem very quickly. A couple of pro tips for Webmaster Tools: 1. Be sure to look at the "date detected" column because it is accurate and somehow people miss it. 2. Set up email forwarding for messages Webmaster Tools sends to you: http://www.google.com/support/webmasters/bin/answer.py?answer=140528 http://www.google.com/support/webmasters/bin/answer.py?answe...
- danheberden 15y ago
  Odd, but the Crawl Errors actually displayed "No known errors" - which is odd, since it was definitely having issues fetching as googlebot. Thanks for the suggestions and finds, though - we'll be looking at it more often for sure! :)
  - pierrefar 15y ago
    That's usually the case if you've just verified the site for the first time. It takes a few days for the first data to be collected. Because of this we always recommend webmasters verify early (before things break) and monitor constantly.

by jeresig 15y ago

yuhong 15y ago

Of course, the best solution is to get the jquery.it domain name transferred to the genuine owner of jQuery, but that will take time.

jeresig 15y ago
Naturally, we're talking with our legal representation about that - we'll have to see what we can actually do. I think we're "ok" for now though as users are getting to the right place in the end.

pierrefar 15y ago

>configured to block anything that had the word 'bot' as part of its user agent string Yep, that'll do it :) Glad you found it and fixed it quickly! One follow-up thought for you and anyone in this situation: Set up a Google Webmaster Tools account ( http://www.google.com/webmasters/tools/ http://www.google.com/webmasters/tools/ ) and make reviewing it part of the webmasters' daily routine. In this particular case, the Crawl Errors page in the Diagnostics section would have flagged this problem very quickly. A couple of pro tips for Webmaster Tools: 1. Be sure to look at the "date detected" column because it is accurate and somehow people miss it. 2. Set up email forwarding for messages Webmaster Tools sends to you: http://www.google.com/support/webmasters/bin/answer.py?answer=140528 http://www.google.com/support/webmasters/bin/answer.py?answe...

danheberden 15y ago
Odd, but the Crawl Errors actually displayed "No known errors" - which is odd, since it was definitely having issues fetching as googlebot. Thanks for the suggestions and finds, though - we'll be looking at it more often for sure! :)
- pierrefar 15y ago
  That's usually the case if you've just verified the site for the first time. It takes a few days for the first data to be collected. Because of this we always recommend webmasters verify early (before things break) and monitor constantly.