<?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: A quick note about scraping</title>
	<atom:link href="http://matthewebel.com/2007/09/19/a-quick-note-about-scraping/feed/" rel="self" type="application/rss+xml" />
	<link>http://matthewebel.com/2007/09/19/a-quick-note-about-scraping/</link>
	<description>Piano Geek Rock</description>
	<lastBuildDate>Thu, 09 Feb 2012 00:44:00 -0500</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: Bryce Moore</title>
		<link>http://matthewebel.com/2007/09/19/a-quick-note-about-scraping/#comment-204</link>
		<dc:creator>Bryce Moore</dc:creator>
		<pubDate>Thu, 20 Sep 2007 02:11:39 +0000</pubDate>
		<guid isPermaLink="false">http://matthewebel.com/?p=331#comment-204</guid>
		<description>Great pointers.  Here is another redirect trick that might come in handy for Wordpress...

Since Wordpress tries to be smarter than me, I use htaccess redirects to handle those &quot;protocols&quot; that Wordpress incorrectly tries to translate in my links.  Therefore, I end up with redirects like this:

Redirect 301 /gtalk xmpp:abiteofsanity@gmail.com

Which will browser-redirect to whatever application is set to handle Google Talk.  Now, I can put a link on my site to http://abiteofsanity.com/gtalk and Wordpress will manage it appropriately.  If I try to put the &quot;xmpp&quot; address into the link, Wordpress mangles it trying to turn it back into an &quot;http&quot; link.</description>
		<content:encoded><![CDATA[<p>Great pointers.  Here is another redirect trick that might come in handy for WordPress&#8230;</p>
<p>Since WordPress tries to be smarter than me, I use htaccess redirects to handle those &#8220;protocols&#8221; that WordPress incorrectly tries to translate in my links.  Therefore, I end up with redirects like this:</p>
<p>Redirect 301 /gtalk xmpp:abiteofsanity@gmail.com</p>
<p>Which will browser-redirect to whatever application is set to handle Google Talk.  Now, I can put a link on my site to <a href="http://abiteofsanity.com/gtalk" rel="nofollow">http://abiteofsanity.com/gtalk</a> and WordPress will manage it appropriately.  If I try to put the &#8220;xmpp&#8221; address into the link, WordPress mangles it trying to turn it back into an &#8220;http&#8221; link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael van Laar</title>
		<link>http://matthewebel.com/2007/09/19/a-quick-note-about-scraping/#comment-203</link>
		<dc:creator>Michael van Laar</dc:creator>
		<pubDate>Wed, 19 Sep 2007 20:31:35 +0000</pubDate>
		<guid isPermaLink="false">http://matthewebel.com/?p=331#comment-203</guid>
		<description>Just a little note: I recently learned that there are two kinds of forwarding: a temporary one and a permanent one. The effect is the same, but the so called status code sent to the browser - or more important: the search engine spy robot -  is different. Status code 302 stands for temporary forwarding, status code 301 for permanent forwarding. Unfortunately, if you don&#039;t include a specific redicect type in your .htaccess file, the 302 status code is used. And that is said to be not so good particularly with regard to the indexing and ranking done by Google.

To put it in a nutshell, if the forwarding is intended as permanent (which it is in most cases - unless you forward a parked domain temporarily to an existing site while you work on the content, that would be one of the rare cases of a temporary forwarding) you should tell browsers and search engines so by adding the corresponding status code in your .htaccess file.

Redirect /blog http://matthewebel.com/
would simply become
Redirect 301 /blog http://matthewebel.com/
if you want to establish a permanent forwarding.</description>
		<content:encoded><![CDATA[<p>Just a little note: I recently learned that there are two kinds of forwarding: a temporary one and a permanent one. The effect is the same, but the so called status code sent to the browser &#8211; or more important: the search engine spy robot &#8211;  is different. Status code 302 stands for temporary forwarding, status code 301 for permanent forwarding. Unfortunately, if you don&#8217;t include a specific redicect type in your .htaccess file, the 302 status code is used. And that is said to be not so good particularly with regard to the indexing and ranking done by Google.</p>
<p>To put it in a nutshell, if the forwarding is intended as permanent (which it is in most cases &#8211; unless you forward a parked domain temporarily to an existing site while you work on the content, that would be one of the rare cases of a temporary forwarding) you should tell browsers and search engines so by adding the corresponding status code in your .htaccess file.</p>
<p>Redirect /blog <a href="http://matthewebel.com/" rel="nofollow">http://matthewebel.com/</a><br />
would simply become<br />
Redirect 301 /blog <a href="http://matthewebel.com/" rel="nofollow">http://matthewebel.com/</a><br />
if you want to establish a permanent forwarding.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Ebel</title>
		<link>http://matthewebel.com/2007/09/19/a-quick-note-about-scraping/#comment-202</link>
		<dc:creator>Matthew Ebel</dc:creator>
		<pubDate>Wed, 19 Sep 2007 15:19:32 +0000</pubDate>
		<guid isPermaLink="false">http://matthewebel.com/?p=331#comment-202</guid>
		<description>John-

Actually, my iTMS address only changed once, and that was shortly after they brought indie artists into the store anyway.  I did, however, sign up for an affiliate link lately, so I don&#039;t just send people to the iTMS anymore anyhow.  Rather than go back and change all my iTunes links from previous posts and blogs, I just update my redirect and they all work.

This isn&#039;t to say that the iTMS won&#039;t change URL&#039;s on us in the future, though.  Ten years from now, who knows?  They might have a major system change, but all I have to do is change one link in one file.

Pax,
Matthew</description>
		<content:encoded><![CDATA[<p>John-</p>
<p>Actually, my iTMS address only changed once, and that was shortly after they brought indie artists into the store anyway.  I did, however, sign up for an affiliate link lately, so I don&#8217;t just send people to the iTMS anymore anyhow.  Rather than go back and change all my iTunes links from previous posts and blogs, I just update my redirect and they all work.</p>
<p>This isn&#8217;t to say that the iTMS won&#8217;t change URL&#8217;s on us in the future, though.  Ten years from now, who knows?  They might have a major system change, but all I have to do is change one link in one file.</p>
<p>Pax,<br />
Matthew</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John R. Carman</title>
		<link>http://matthewebel.com/2007/09/19/a-quick-note-about-scraping/#comment-201</link>
		<dc:creator>John R. Carman</dc:creator>
		<pubDate>Wed, 19 Sep 2007 15:13:38 +0000</pubDate>
		<guid isPermaLink="false">http://matthewebel.com/?p=331#comment-201</guid>
		<description>Excellent tips, Matthew. I was unaware that an artist&#039;s iTunes music store URL changes; is there a reason, or just iTunes being unfriendly?</description>
		<content:encoded><![CDATA[<p>Excellent tips, Matthew. I was unaware that an artist&#8217;s iTunes music store URL changes; is there a reason, or just iTunes being unfriendly?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

