<?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>Alson Kemp &#187; Pretty URLs</title>
	<atom:link href="http://www.alsonkemp.com/tag/pretty-urls/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.alsonkemp.com</link>
	<description>Hackfoofery</description>
	<lastBuildDate>Thu, 05 Jan 2012 03:53:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Pretty URLs &#8211; how-tos &amp; guides</title>
		<link>http://www.alsonkemp.com/best-practices/pretty-urls-how-tos-guides/</link>
		<comments>http://www.alsonkemp.com/best-practices/pretty-urls-how-tos-guides/#comments</comments>
		<pubDate>Wed, 10 Sep 2008 18:09:00 +0000</pubDate>
		<dc:creator>alson</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Guides]]></category>
		<category><![CDATA[How-To]]></category>
		<category><![CDATA[Pretty URLs]]></category>
		<category><![CDATA[SEO]]></category>

		<guid isPermaLink="false">http://www.alsonkemp.com/?p=8</guid>
		<description><![CDATA[Since we run a membership-fee-based service, we&#8217;ve focused on providing security for our inside-the-walled-garden URLs. It&#8217;s been important to protect the content generated by our members for our members from being scooped out by unscrupulous operators. That said, we&#8217;re probably getting to the point at which we should pretty up our URLs, if only to [...]]]></description>
			<content:encoded><![CDATA[<p>Since we run a membership-fee-based service, we&#8217;ve focused on providing security for our inside-the-walled-garden URLs.  It&#8217;s been important to protect the content generated by our members for our members from being scooped out by unscrupulous operators.  That said, we&#8217;re probably getting to the point at which we should pretty up our URLs, if only to enhance our member experience and ease with which members can find their content.</p>

<p>In searching around for guidance on how to go about switching to pretty URLs, I&#8217;ve found the following helpful:</p>

<ul>
    <li>A <a href="# http://blog.searchenginewatch.com/blog/070323-083029" target="_blank">Report</a> on one company&#8217;s experience with switching to pretty URLs</li>
    <li>An analysis of that report <a title="Analysis" href="http://www.searchenginejournal.com/no-fear-of-remapping-urls-of-your-site/4578/" target="_blank">here</a>.</li>
    <li>A bunch of solid <a href="http://www.seomoz.org/blog/11-best-practices-for-urls" target="_blank">advice</a> on how to think about pretty URLs.</li>
    <li>Nuts &amp; bolts about <a href="http://www.roscripts.com/Pretty_URLs_-_a_guide_to_URL_rewriting-168.html" target="_blank">setting up Apache</a> for URL rewriting.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.alsonkemp.com/best-practices/pretty-urls-how-tos-guides/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

