Fighting the 302 issue

OK, So I read somewhere about how to try and combat the terrible issues that G is having in terms of handling 302 redirects...

Essentially, as far as I am aware, you need to basically cloak a 302 redirect back to the offending url.

So, in the case of my blog, the offending URL is [size=-1]www.blogger.com/r?http://www.seo-dev.co.uk...

(A google owned domain is the one screwing me up - sods law)...

So, if I were to cloak a 302 back to the blogger URL (But only for Google), can anyone see me getting in loads of sh1t?

As it is, the domain already has a whole bunch of pages missing from the index and google crawls are nearly non existant (1 every day or two as opposed to 100 or so crawls a day)...

So guys, what do you think?

Worth a go?

All I am cloaking here is a 302 redirect...
[/size]

 

Anyone?????

 

Sounds like a plan to me.

As long as you know how to redirect for G only then I see no harm.

Will you do it by IP? User Agent?

Just checked that redirect and yes, very sad but true, it's a 302. How f*cking stupid are they?

 

are you sure this is still an issue ?

my site had/ has 302 messing it up but I am back to better positions than before after being MIA since December for a full 7 weeks

 

I have no idea whether this is the actual issue or not...
But I'm sure as hell going to try to get it sorted...

Not sure how I'll cloak it to be honest... User agent would be the easiest I suppose...

I'm just concerned that I'll get even more screwed if I try to do this...

 

Give them their shit back. It sounds like you don't have much to loose. Apart from a ban extention perhaps if there is such a thing.

I wouldn't be surprised though if they had another anonymous bot floatng about checking on cloaking. Let us know how you go.

(PS 1 more post and I've caught up with you )

 

I just realised that site is hosted on iis...

Damn... Any suggestions people?

Not quite.

 

We'll be playing tag team all day; +1 for me now...

 

Even Stevens