3 ms·
Hi Matt, Looks like the subdomain you referenced did have a hack, but the main site didn't. I had done a Google fetchbot request to check before hand. Regardle
by melvinram 14y ago
Hi Matt,
Looks like the subdomain you referenced did have a hack, but the main site didn't. I had done a Google fetchbot request to check before hand. Regardless, I can see how having hacked subdomains might trigger the warning.
Based on your comment, should we understand that split testing, where it actually redirects to a few different separate pages, is an okay form of testing that won't trigger the "this site was compromised" warning?
- Matt_Cutts 14y agomelvinram, that's correct. Split testing is a perfectly fine form of testing and doesn't have anything to do with the "this site was compromised" warning. That's the high-order bit. If you want low-level/detailed info, we discuss this topic on our support page at http://support.google.com/websiteoptimizer/bin/answer.py?hl=en&answer=72507 http://support.google.com/websiteoptimizer/bin/answer.py?hl=... . Hope that helps.
- melvinram 14y agoThanks for the clarification.
- Matt_Cutts 14y agoP.S. Looks like the robots.txt now blocks /wp-includes/ . If you remove that block, we should be able to crawl the relevant files and verify that they're clean (or more accurately, 404) now, which would let the system auto-revoke the hacked label.
- melvinram 14y agoUpdated it. PS: Thanks again for your help on this.