Remedies, Cure, and Precautions for 302 redirect Hijacking.

[adqas]

Hi Moz Guys,

I hope all of you are good out there. I am here to discuss remedies, cure, and precautions for 302 redirect hijacking. Although it is quite old and whenever I searched in Google, it looks like a long gone glitch of Google serps but it just happened to one of my customers' site. The site in question is www(dot)solidswiss(dot)cd. If you check the cache(cache:site) then you can see a hijacked site in the urls of the cached page. As a result all my customer's listing in the serps are replaced with this site. This hacked site then is redirecting to a competitor's site. I did many things to cop with the problem, site came back in the serps but hackers are doing this on lots of domains so when it recovered from one site then another site catches it.

I am doing lots of reporting on submit spam site.

I am doing lots of feedback on the serps page.

I have switched to https .

But seems like nothing is working. This community is full of experts and technical people. I am wondering that what are your views and suggestions to handle the problem permanently?

[Dr-Pete]

Sorry, I'm not seeing the bad URL(s) in the cache. Could you provide a sample Google query that's showing the hijacking URL?

Are you trying to prevent future hijacking or undo the SEO damage done by the previous hijacking? Sorry, I'm not completely clear on what happened or where you're at in the recovery process.