Jquery Redirects ARE crawled by Google

[wockawocka]

Riiiiight.

So I was Pandalised, Penguinated and manually shafter by the great and the Google for my .co.uk web url.

We built a new site on the .com and on the old site put a Javascript / Jquery redirect which apparently Google can't follow.

Well they can.

Yesterday I had 17 links showing in WMT, today, 42,234

Site was created on the 22nd August.

We've now pulled the redirect and I just wanted to let you guys know they do follow it.

[aakk9999]

Hello wockawocka,

It is an interesting and important information you are sharing.

So that we could understand better the exact circumstances, I am wondering if you could clarify what exactly you have done and what you are seeing. I would be really interested if you could answer these questions:

1) How did you implement js redirect?
- is your js redirect in an external js file
- did you block this js file in robots.txt
- have you confirmed by using WMT Robots.txt testing feature that the .js file was blocked via robots.txt
- anything else you can share on your implementation (e.g. can the target URL be seen on the page even if it is not in href ?

2) Have you tried to test page that redirects using js redirect via WMT Fetch as Googlebot? If not, could you try this and report back what is the HTTP response code for this page when Fetch as Googlebot is used.


3) You say you are seeing 42234 links in WMT.
- Are you talking about external links reported in WMT?
- the new links that appeared, when you drill down, do they say "via this intermediate URL" listing your old domain being intermediate URL?
- if not, is there any other reason why you say the js redirect has been made visible to Google?

I think that answering these questions would really help us understand what is really happening and what is Googlebot crawling/finding.

[wockawocka]

aakk9999 I'll ask my web guy. I don't think a robots.txt file was implemented on this.
.

[edited by: aakk9999 at 4:30 pm (utc) on Sep 4, 2013]
[edit reason] Charter [/edit]