Forum Moderators: Robert Charlton & goodroi
[edited by: Robert_Charlton at 7:38 am (utc) on Mar 3, 2017]
I will still keep the 104 blocked domain long disavow file just to see where it leads- don't give up, but please don't block by domain.
Displayed pages are live (so no copying/scrapping), that is if I change anything on my site and refresh the hacked one, I see all changes immediately.
cat my-site.com_access_log |grep Googlebot |grep -v '66.249' |wc -l if I change something in one particular page on my site, I see those changes on hacked sites right after the refresh (I did that to check if my pages are scrapped or it's a Proxy Hijack, which at this point I'm 100% confident it is).Good! I think we're saying the same thing. If the changes appear in more or less real time, we are both thinking it's a proxy hijack.
Found and disavowed 104 different domain names already.
You can block that with x-header rules or a script that only allows parent (your site) to display your content.
<script type="text/javascript">
if (parent.frames.length > 0) {
parent.location.href = location.href;
}
</script> and the header tag in htaccess: Header append X-FRAME-OPTIONS "deny" they're getting output of the page and I don't have any control over thisThis stops the *browser* from displaying the remote content in an iframe. Your logs may still show the attempts, but none of the major browsers will display your content *if* this is actually what they are doing :)