<?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"
	>
<channel>
	<title>Comments on: For URLs The Future is Flat</title>
	<atom:link href="http://blog.pint.com/2007/07/12/for-urls-the-future-is-flat/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.pint.com/2007/07/12/for-urls-the-future-is-flat/</link>
	<description>The company blog for Pint Inc.</description>
	<pubDate>Sat, 22 Nov 2008 00:55:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Justin</title>
		<link>http://blog.pint.com/2007/07/12/for-urls-the-future-is-flat/#comment-144</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Mon, 03 Mar 2008 19:54:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pint.com/2007/07/12/for-urls-the-future-is-flat/#comment-144</guid>
		<description>One thing to consider is that there are certain advantages, in some cases, to using less-flat URLs and using a path structure that promotes keyword exposure.  For example, if I have sell lawn gnomes through my site.  Having http://store.gnomeemporium.com/lawn-gnomes/product-name or http://gnomeemporium.com/shop/lawn-gnomes/product-name might prove beneficial from an SEO perspective since I now have "lawn-gnomes," and "store" or "shop" keywords right in my URL.

So, like many strategies, there's always a time and a place for one versus another.  However, places like Apple and other companies that have popular products would definitely benefit from http://apple.com/imac and the like.  Additionally, I think it provides an extra level of readability and location/content awareness for users.</description>
		<content:encoded><![CDATA[<p>One thing to consider is that there are certain advantages, in some cases, to using less-flat URLs and using a path structure that promotes keyword exposure.  For example, if I have sell lawn gnomes through my site.  Having <a href="http://store.gnomeemporium.com/lawn-gnomes/product-name" rel="nofollow">http://store.gnomeemporium.com/lawn-gnomes/product-name</a> or <a href="http://gnomeemporium.com/shop/lawn-gnomes/product-name" rel="nofollow">http://gnomeemporium.com/shop/lawn-gnomes/product-name</a> might prove beneficial from an SEO perspective since I now have &#8220;lawn-gnomes,&#8221; and &#8220;store&#8221; or &#8220;shop&#8221; keywords right in my URL.</p>
<p>So, like many strategies, there&#8217;s always a time and a place for one versus another.  However, places like Apple and other companies that have popular products would definitely benefit from <a href="http://apple.com/imac" rel="nofollow">http://apple.com/imac</a> and the like.  Additionally, I think it provides an extra level of readability and location/content awareness for users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://blog.pint.com/2007/07/12/for-urls-the-future-is-flat/#comment-22</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Sat, 14 Jul 2007 01:16:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pint.com/2007/07/12/for-urls-the-future-is-flat/#comment-22</guid>
		<description>Ha ha, I thought of that as well...</description>
		<content:encoded><![CDATA[<p>Ha ha, I thought of that as well&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas</title>
		<link>http://blog.pint.com/2007/07/12/for-urls-the-future-is-flat/#comment-20</link>
		<dc:creator>Thomas</dc:creator>
		<pubDate>Sat, 14 Jul 2007 00:14:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pint.com/2007/07/12/for-urls-the-future-is-flat/#comment-20</guid>
		<description>Obviously since visuals were added you might think the URL should be blog.pint.com/flaturls if you were really going to match art to theory</description>
		<content:encoded><![CDATA[<p>Obviously since visuals were added you might think the URL should be blog.pint.com/flaturls if you were really going to match art to theory</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dylan</title>
		<link>http://blog.pint.com/2007/07/12/for-urls-the-future-is-flat/#comment-16</link>
		<dc:creator>Dylan</dc:creator>
		<pubDate>Fri, 13 Jul 2007 00:28:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pint.com/2007/07/12/for-urls-the-future-is-flat/#comment-16</guid>
		<description>Interesting idea, and very sensible. How well would search engines interpret this mapping? I wonder what effect it could have with regard to indexing maps as duplicate content, split back links, Google page rank, and other indexing behaviors. 

Some scripts such as phpMyDirectory, http://phpmydirectory.com/, have caught onto this flat URL idea and are using it for things like:

http://directoryName.com/Vendor-Name.htm</description>
		<content:encoded><![CDATA[<p>Interesting idea, and very sensible. How well would search engines interpret this mapping? I wonder what effect it could have with regard to indexing maps as duplicate content, split back links, Google page rank, and other indexing behaviors. </p>
<p>Some scripts such as phpMyDirectory, <a href="http://phpmydirectory.com/" rel="nofollow">http://phpmydirectory.com/</a>, have caught onto this flat URL idea and are using it for things like:</p>
<p><a href="http://directoryName.com/Vendor-Name.htm" rel="nofollow">http://directoryName.com/Vendor-Name.htm</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
