SEO Egghead Consulting Group

Archived; click post to view.
Excerpt: What really stops anyone from using a CSS-based layout, throwing up some spammy content, then using CSS with all sorts of positioning to hide it? Spiders can read CSS now, and you'll get busted, right? Perhaps. But what if one were to place the CSS in a file and exclude that file via robots.txt? To make it look even less like subtrefuge, simply place the CSS file in your images folder or something. Assuming Google actually honors the robots exclusion protocol, wouldn't that permit one to spam with immunity? Again, I'm not a black hat, but isn't that…

Archived; click post to view.
Excerpt: I was reading SEO Black Hat during my lunch break, and it pointed me to RSnake's article on using GreaseMonkey to sniff out XSS attack vulnerabilities.  Since I'm a white hat SEO, I'll pretend I'm only interested in this stuff to the extent of attack prevention, so I added a few things to his proof of concept to make it more usable for that purpose (or any purpose, really).First, we create a script that utilizes the last code-snippet I posted here that parses out the response codes from a HTTP document (LinkChecker.php), located here. <?   include('LinkChecker.php');              $header_result = LinkChecker::getHeader($_REQUEST['text']);…