are cloaked redirects fooling google?

[apollo]

I have just found a second site that redirects when cache is selected from the google results page. The first site I found was a major university that seemed to have a fake page listed in the results that redirects to a general info page, even when cache was selected. Now I have just found another that redirects to a pay per click menu and a pop-up.
I always thought it was a way to see the site that googlebot saw by looking at the cache, but it seems not.

[dirkz]

I can't see any fooling here. Redirection also has nothing to do with cloaking in first place, being two separate things that can be mixed. If it's a 302 it could well be valid that the cache contains the redirecting page.

If you want to see the source of the redirecting page, you can use wget or tell your browser not to allow redirects.

[apollo]

Thanks Dirkz
The cache does not contain the redirected page. Clicking on the cache link actually redirects to the redirected page, not a cached copy of it. The redirected page does not contain the title or the text that is displayed in the google listing (which from the information available seems to be highly optimised).

[WebGuerrilla]

View the cache with JavaScript turned off. Google doesn't parse it. Your browser does.

[dirkz]

The redirected page does not contain the title or the text that is displayed in the google listing

Then this could be a different kettle of fish. I would take a closer look at how they do it. Could be harmless, though (lots of anchor text etc.). If you want, you could sticky me the URL. I will then post my results here.

[dougmcc1]

If you want to see the source of the redirecting page, you can use wget or tell your browser not to allow redirects

Also, in IE you can type this into the address bar:
view-source:http://www.domain.com/

That gives you a chance to view the source code without getting redirected first.