<?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>John Shehata - Marketing Strategist &#187; SEO Mistakes</title>
	<atom:link href="http://www.john-shehata.com/seo-sem/seo-mistakes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.john-shehata.com</link>
	<description>Search Engine Marketing &#038; Optimization: Tips, Tactics and Strategies</description>
	<lastBuildDate>Wed, 24 Mar 2010 03:18:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Twitter https: Ignoring SEO 101 Basics</title>
		<link>http://www.john-shehata.com/twitter-https-seo-101-basic/</link>
		<comments>http://www.john-shehata.com/twitter-https-seo-101-basic/#comments</comments>
		<pubDate>Mon, 15 Mar 2010 05:12:13 +0000</pubDate>
		<dc:creator>john shehata</dc:creator>
				<category><![CDATA[SEO Mistakes]]></category>
		<category><![CDATA[https]]></category>
		<category><![CDATA[seo audit]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[twitter seo]]></category>

		<guid isPermaLink="false">http://www.john-shehata.com/?p=171</guid>
		<description><![CDATA[if you are a frequent user of twitter you might came across this page before &#8230;


it is obvious that there are some SSL issues here, but what does this have to do with SEO? Doing some simple investigative work you will find the following:
1. twitter uses relative links on https pages, so all the http [...]]]></description>
		<wfw:commentRss>http://www.john-shehata.com/twitter-https-seo-101-basic/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>SEO Over-Optimization Penalty (OOP)</title>
		<link>http://www.john-shehata.com/seo-over-optimization/</link>
		<comments>http://www.john-shehata.com/seo-over-optimization/#comments</comments>
		<pubDate>Thu, 20 Sep 2007 03:25:32 +0000</pubDate>
		<dc:creator>john shehata</dc:creator>
				<category><![CDATA[Advanced SEO]]></category>
		<category><![CDATA[SEO Mistakes]]></category>
		<category><![CDATA[oop]]></category>
		<category><![CDATA[over optimization]]></category>
		<category><![CDATA[penalty]]></category>

		<guid isPermaLink="false">http://www.john-shehata.com/seo-over-optimization/</guid>
		<description><![CDATA[While many SEOs claim this is a myth, a lot of us see it happening everyday. I am discussing &#8220;white-hat&#8221; tactics that may cause over-optimization penalties. Hitting the over-optimization filters in Google is also called &#8220;-950 penalty&#8221; because site rankings get demoted 950 positions.
Matt Cutts (Google&#8217;s anti-spam engineer) mentioned over-optimization as a reason for ranking [...]]]></description>
		<wfw:commentRss>http://www.john-shehata.com/seo-over-optimization/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>SEO Mistakes</title>
		<link>http://www.john-shehata.com/seo-mistakes/</link>
		<comments>http://www.john-shehata.com/seo-mistakes/#comments</comments>
		<pubDate>Sun, 11 Mar 2007 20:36:16 +0000</pubDate>
		<dc:creator>john shehata</dc:creator>
				<category><![CDATA[SEO Mistakes]]></category>

		<guid isPermaLink="false">http://www.john-shehata.com/seo-mistakes/</guid>
		<description><![CDATA[There are some fatal SEO mistakes that can hurt your site, here is a list that will be updated on a regular basis
Duplicate title among multiple pages; each page should have its unique title meta tag
Duplicate description; each page should have its unique description meta tag
]]></description>
		<wfw:commentRss>http://www.john-shehata.com/seo-mistakes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
