<?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: Book Source Code</title>
	<atom:link href="http://www.seowarrior.net/book-source-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.seowarrior.net/book-source-code/</link>
	<description>Companion Blog to SEO Warrior Book</description>
	<lastBuildDate>Fri, 28 Oct 2011 00:23:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: John</title>
		<link>http://www.seowarrior.net/book-source-code/comment-page-1/#comment-37</link>
		<dc:creator>John</dc:creator>
		<pubDate>Fri, 15 Jan 2010 07:58:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.seowarrior.net/?p=217#comment-37</guid>
		<description>I haven&#039;t tried all of the scripts on Linux, but it should be straight forward though. I would probably try usinh XAMPP for Linux first. If there is enough interest I might port everything to Linux. For now I would suggest to copy everything under htdocs to your Linux box under your Apache web folder (if not htdocs). Let me know if you get any problems. I might actually try this on my Mac as it is a Linux variant.</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t tried all of the scripts on Linux, but it should be straight forward though. I would probably try usinh XAMPP for Linux first. If there is enough interest I might port everything to Linux. For now I would suggest to copy everything under htdocs to your Linux box under your Apache web folder (if not htdocs). Let me know if you get any problems. I might actually try this on my Mac as it is a Linux variant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith</title>
		<link>http://www.seowarrior.net/book-source-code/comment-page-1/#comment-36</link>
		<dc:creator>Keith</dc:creator>
		<pubDate>Fri, 15 Jan 2010 06:43:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.seowarrior.net/?p=217#comment-36</guid>
		<description>I guess it will be pretty simple to set up on LINUX (Fedora, for example). Are you planning a summary for this, please?</description>
		<content:encoded><![CDATA[<p>I guess it will be pretty simple to set up on LINUX (Fedora, for example). Are you planning a summary for this, please?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.seowarrior.net/book-source-code/comment-page-1/#comment-35</link>
		<dc:creator>John</dc:creator>
		<pubDate>Fri, 15 Jan 2010 04:10:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.seowarrior.net/?p=217#comment-35</guid>
		<description>Thanks for the compliments! Comments like these makes it worthwhile to spend 2 years of time to write a book.  

Also, thanks for the &quot;perlold&quot; tip. Yes, it can be deleted. Yes, I am aware of WP 2.1 release --I am just doing the backup first :) 

Regards,
John</description>
		<content:encoded><![CDATA[<p>Thanks for the compliments! Comments like these makes it worthwhile to spend 2 years of time to write a book.  </p>
<p>Also, thanks for the &#8220;perlold&#8221; tip. Yes, it can be deleted. Yes, I am aware of WP 2.1 release &#8211;I am just doing the backup first <img src='http://www.seowarrior.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  </p>
<p>Regards,<br />
John</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith</title>
		<link>http://www.seowarrior.net/book-source-code/comment-page-1/#comment-34</link>
		<dc:creator>Keith</dc:creator>
		<pubDate>Fri, 15 Jan 2010 04:04:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.seowarrior.net/?p=217#comment-34</guid>
		<description>Fabulous book, by far the best (if not the only) in the &quot;quantitative market research on the web&quot; field; thanks for all the work you put into it. 

OT comments: 
Maybe the &quot;perlold&quot; directory in xampp.zip can be deleted?  
(WP 2.9.1 is out, according to the dashboard of your web site.)</description>
		<content:encoded><![CDATA[<p>Fabulous book, by far the best (if not the only) in the &#8220;quantitative market research on the web&#8221; field; thanks for all the work you put into it. </p>
<p>OT comments:<br />
Maybe the &#8220;perlold&#8221; directory in xampp.zip can be deleted?<br />
(WP 2.9.1 is out, according to the dashboard of your web site.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.seowarrior.net/book-source-code/comment-page-1/#comment-6</link>
		<dc:creator>John</dc:creator>
		<pubDate>Fri, 11 Dec 2009 02:29:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.seowarrior.net/?p=217#comment-6</guid>
		<description>Rad,

Thanks for the comments. Let me answer your questions. 

1) The purpose of the stopwords.txt is to list any common words that search engines would typically ignore. For more details, you can refer to the explanation offered at the following links: 
  a&gt; &lt;a href=&quot;http://searchenginewatch.com/2156061&quot; rel=&quot;nofollow&quot;&gt;http://searchenginewatch.com/2156061&lt;/a&gt;
  b&gt; &lt;a href=&quot;http://en.wikipedia.org/wiki/Stop_words&quot; rel=&quot;nofollow&quot;&gt;http://en.wikipedia.org/wiki/Stop_words&lt;/a&gt; 

2) The spider viewer script is meant as an illustration (only) of how search engines would view each URL. Each search engine would do this in any way they like. In regards to the space between HTML elements, I have used no space just to make a point about the way search engines will read a particular URL (html) in the serial fashion -- after stripping out (semantically irrelevant) HTML tags. 

Thanks,
John</description>
		<content:encoded><![CDATA[<p>Rad,</p>
<p>Thanks for the comments. Let me answer your questions. </p>
<p>1) The purpose of the stopwords.txt is to list any common words that search engines would typically ignore. For more details, you can refer to the explanation offered at the following links:<br />
  a> <a href="http://searchenginewatch.com/2156061" rel="nofollow">http://searchenginewatch.com/2156061</a><br />
  b> <a href="http://en.wikipedia.org/wiki/Stop_words" rel="nofollow">http://en.wikipedia.org/wiki/Stop_words</a> </p>
<p>2) The spider viewer script is meant as an illustration (only) of how search engines would view each URL. Each search engine would do this in any way they like. In regards to the space between HTML elements, I have used no space just to make a point about the way search engines will read a particular URL (html) in the serial fashion &#8212; after stripping out (semantically irrelevant) HTML tags. </p>
<p>Thanks,<br />
John</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: radimkoudela</title>
		<link>http://www.seowarrior.net/book-source-code/comment-page-1/#comment-5</link>
		<dc:creator>radimkoudela</dc:creator>
		<pubDate>Thu, 10 Dec 2009 17:16:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.seowarrior.net/?p=217#comment-5</guid>
		<description>Hi John

first of all let me say that you&#039;ve done a great job on your book.

I&#039;m recently going through the chapters and the codes. I have two simple questions regarding chapter II.

1. stopwords.txt - What is the exact purpose of loading spotwords.txt? I&#039;m asking if it&#039;s there to  opt out some keywords  (SEO-wise) or just simply HTML codes.

2. It appears like there is no space in spider view output between HTML elements. Is only the code or is the search engines parse the text out?

Thanks
Rad</description>
		<content:encoded><![CDATA[<p>Hi John</p>
<p>first of all let me say that you&#8217;ve done a great job on your book.</p>
<p>I&#8217;m recently going through the chapters and the codes. I have two simple questions regarding chapter II.</p>
<p>1. stopwords.txt &#8211; What is the exact purpose of loading spotwords.txt? I&#8217;m asking if it&#8217;s there to  opt out some keywords  (SEO-wise) or just simply HTML codes.</p>
<p>2. It appears like there is no space in spider view output between HTML elements. Is only the code or is the search engines parse the text out?</p>
<p>Thanks<br />
Rad</p>
]]></content:encoded>
	</item>
</channel>
</rss>

