<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: WordPress SEO and Dedicated IP&#8217;s</title>
	<atom:link href="http://foliovision.com/2009/07/14/wordpress-seo-dedicated-ip/feed" rel="self" type="application/rss+xml" />
	<link>http://foliovision.com/2009/07/14/wordpress-seo-dedicated-ip</link>
	<description>Making the web work for you</description>
	<lastBuildDate>Thu, 09 Feb 2012 11:42:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
<image><title>Foliovision</title><url>http://foliovision.com/site/wp-content/themes/foliovision/images/foliovision-logo-380.gif</url><link>http://foliovision.com</link><width>240</width><height>66</height><description>Making the web work for you</description></image>	<item>
		<title>By: alec</title>
		<link>http://foliovision.com/2009/07/14/wordpress-seo-dedicated-ip#comment-67674</link>
		<dc:creator>alec</dc:creator>
		<pubDate>Mon, 23 Aug 2010 07:04:47 +0000</pubDate>
		<guid isPermaLink="false">http://foliovision.com/2009/07/14/wordpress-seo-dedicated-ip/#comment-67674</guid>
		<description>The dedicated IP should only improve your situation. There is the 1/200 chance that you are getting a very dirty dedicated IP (probably not, as then the shared IP&#039;s at your host would be dirty as well and you would have had trouble rising to number one) and that you will take a dip until Google realises that a clean site is now on that former malware or porn IP. You can do a check against that IP to find out who was there via various online services:

* You can get basic info here about the current info for the IP: http://www.infosniper.net/?ip_address=96.30.44.71
* You do an historical check here: http://www.domaintools.com/hosting-history/

For the second link you have to become a member and sign up for a $15/month plan. I&#039;ve used the paid service on occasion when working on sensitive or high budget projects.</description>
		<content:encoded><![CDATA[<p>The dedicated IP should only improve your situation. There is the 1/200 chance that you are getting a very dirty dedicated IP (probably not, as then the shared IP&#8217;s at your host would be dirty as well and you would have had trouble rising to number one) and that you will take a dip until Google realises that a clean site is now on that former malware or porn IP. You can do a check against that IP to find out who was there via various online services:</p>
<p>* You can get basic info here about the current info for the IP: <a href="http://www.infosniper.net/?ip_address=96.30.44.71" rel="nofollow" class="liexternal">http://www.infosniper.net/?ip_address=96.30.44.71</a><br />
* You do an historical check here: <a href="http://www.domaintools.com/hosting-history/" rel="nofollow" class="liexternal">http://www.domaintools.com/hosting-history/</a></p>
<p>For the second link you have to become a member and sign up for a $15/month plan. I&#8217;ve used the paid service on occasion when working on sensitive or high budget projects.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: allen</title>
		<link>http://foliovision.com/2009/07/14/wordpress-seo-dedicated-ip#comment-67631</link>
		<dc:creator>allen</dc:creator>
		<pubDate>Mon, 23 Aug 2010 03:04:39 +0000</pubDate>
		<guid isPermaLink="false">http://foliovision.com/2009/07/14/wordpress-seo-dedicated-ip/#comment-67631</guid>
		<description>if i am already on a shared IP address and finally got onto the first page of google---then I upgrade to dedicated IP--will this affect my google rankings? anybody have personal experiences?</description>
		<content:encoded><![CDATA[<p>if i am already on a shared IP address and finally got onto the first page of google&#8212;then I upgrade to dedicated IP&#8211;will this affect my google rankings? anybody have personal experiences?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

