<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>web pulp 2.0 &#187; hacker</title>
	<atom:link href="http://www.webpulp.org/tag/hacker/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webpulp.org</link>
	<description>anything and everything between the cracks...</description>
	<lastBuildDate>Wed, 30 Jun 2010 19:16:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>This site was reccently hacked&#8230;.why? SEO</title>
		<link>http://www.webpulp.org/hacking/this-site-was-reccently-hackedwhy-seo/</link>
		<comments>http://www.webpulp.org/hacking/this-site-was-reccently-hackedwhy-seo/#comments</comments>
		<pubDate>Thu, 06 Nov 2008 16:15:03 +0000</pubDate>
		<dc:creator>Joe Hall</dc:creator>
				<category><![CDATA[Hacking]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[hacker]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[update]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://www.webpulp.org/?p=71</guid>
		<description><![CDATA[Believe it or not this site was hacked. And, the strange part about it is that if you were to look at it in its hacked state it would have looked completely normal, from the outside no changes were visible. However, after looking at the HTML&#8217;s source code you would have seen close to a [...]]]></description>
			<content:encoded><![CDATA[<p>Believe it or not this site was hacked. And, the strange part about it is that if you were to look at it in its hacked state it would have looked completely normal, from the outside no changes were visible. However, after looking at the HTML&#8217;s source code you would have seen close to a thousand links hidden from the public&#8217;s view using CSS.</p>
<p>I know some of you are thinking, why?? Why would anyone want to hack a site just to post hidden links? Links you can&#8217;t see, don&#8217;t get clicked, right? Yes that&#8217;s right, but these links aren&#8217;t supposed to be clicked, these links were there for the sole intent of being picked up by Search Engines like Google.</p>
<p>Why would anyone go to such an extent to post a link for Google to find? SEO, Search Engine Optimization is the method of changing a series of factors to get your web site ranked higher in search engines. One of the most important aspects of SEO are links pointing to your web site. Therefore it is easy to understand why some black hat SEOs will hack a blog to post more links that will benefit them.</p>
<p>How can we protect our sites and blogs from this type of attack? Well, if you have a WordPress blog you need to make your way over to <a href="http://www.seo-scoop.com/2008/07/01/the-ultimate-hacker-prevention-guide/">a post</a> that thet amazing <a href="https://twitter.com/DazzlinDonna">Donna Fontenot</a> wrote at SEO Scoop. Thanks to Donna for this awsome post and her constant reminder to keep our WordPress up to date!</p>


<div class="shr-bookmarks shr-bookmarks-expand shr-bookmarks-center shr-bookmarks-bg-shr">
<ul class="socials">
		<li class="shr-comfeed">
			<a href="http://www.webpulp.org/hacking/this-site-was-reccently-hackedwhy-seo/feed" rel="nofollow" class="external" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="shr-delicious">
			<a href="http://delicious.com/post?url=http://www.webpulp.org/hacking/this-site-was-reccently-hackedwhy-seo/&amp;title=This+site+was+reccently+hacked....why%3F+SEO" rel="nofollow" class="external" title="Share this on del.icio.us">Share this on del.icio.us</a>
		</li>
		<li class="shr-digg">
			<a href="http://digg.com/submit?phase=2&amp;url=http://www.webpulp.org/hacking/this-site-was-reccently-hackedwhy-seo/&amp;title=This+site+was+reccently+hacked....why%3F+SEO" rel="nofollow" class="external" title="Digg this!">Digg this!</a>
		</li>
		<li class="shr-diigo">
			<a href="http://www.diigo.com/post?url=http://www.webpulp.org/hacking/this-site-was-reccently-hackedwhy-seo/&amp;title=This+site+was+reccently+hacked....why%3F+SEO&amp;desc=Believe%20it%20or%20not%20this%20site%20was%20hacked.%20And%2C%20the%20strange%20part%20about%20it%20is%20that%20if%20you%20were%20to%20look%20at%20it%20in%20its%20hacked%20state%20it%20would%20have%20looked%20completely%20normal%2C%20from%20the%20outside%20no%20changes%20were%20visible.%20However%2C%20after%20looking%20at%20the%20HTML%27s%20source%20code%20you%20would%20have%20seen%20close%20to%20a%20thousand%20link" rel="nofollow" class="external" title="Post this on Diigo">Post this on Diigo</a>
		</li>
		<li class="shr-googlebuzz">
			<a href="http://www.google.com/buzz/post?url=http://www.webpulp.org/hacking/this-site-was-reccently-hackedwhy-seo/&amp;imageurl=" rel="nofollow" class="external" title="Post on Google Buzz">Post on Google Buzz</a>
		</li>
		<li class="shr-misterwong">
			<a href="http://www.mister-wong.com/addurl/?bm_url=http://www.webpulp.org/hacking/this-site-was-reccently-hackedwhy-seo/&amp;bm_description=This+site+was+reccently+hacked....why%3F+SEO&amp;plugin=sexybookmarks" rel="nofollow" class="external" title="Add this to Mister Wong">Add this to Mister Wong</a>
		</li>
		<li class="shr-mixx">
			<a href="http://www.mixx.com/submit?page_url=http://www.webpulp.org/hacking/this-site-was-reccently-hackedwhy-seo/&amp;title=This+site+was+reccently+hacked....why%3F+SEO" rel="nofollow" class="external" title="Share this on Mixx">Share this on Mixx</a>
		</li>
		<li class="shr-reddit">
			<a href="http://reddit.com/submit?url=http://www.webpulp.org/hacking/this-site-was-reccently-hackedwhy-seo/&amp;title=This+site+was+reccently+hacked....why%3F+SEO" rel="nofollow" class="external" title="Share this on Reddit">Share this on Reddit</a>
		</li>
		<li class="shr-stumbleupon">
			<a href="http://www.stumbleupon.com/submit?url=http://www.webpulp.org/hacking/this-site-was-reccently-hackedwhy-seo/&amp;title=This+site+was+reccently+hacked....why%3F+SEO" rel="nofollow" class="external" title="Stumble upon something good? Share it on StumbleUpon">Stumble upon something good? Share it on StumbleUpon</a>
		</li>
		<li class="shr-technorati">
			<a href="http://technorati.com/faves?add=http://www.webpulp.org/hacking/this-site-was-reccently-hackedwhy-seo/" rel="nofollow" class="external" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="shr-twitter">
			<a href="http://twitter.com/home?status=This+site+was+reccently+hacked....why%3F+SEO+-+http://b2l.me/dy5rf&amp;source=shareaholic" rel="nofollow" class="external" title="Tweet This!">Tweet This!</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>

]]></content:encoded>
			<wfw:commentRss>http://www.webpulp.org/hacking/this-site-was-reccently-hackedwhy-seo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
