<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Top 10 URL Design Failures of Famous Websites</title>
	<link>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites</link>
	<description></description>
	<pubDate>Thu, 20 Nov 2008 22:28:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>

	<item>
		<title>By: kudzu fire</title>
		<link>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-67403</link>
		<author>kudzu fire</author>
		<pubDate>Tue, 11 Nov 2008 16:39:59 +0000</pubDate>
		<guid>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-67403</guid>
		<description>there are those that say your should always hide the urls so it can't be manipulated or critiqued</description>
		<content:encoded><![CDATA[<p>there are those that say your should always hide the urls so it can&#8217;t be manipulated or critiqued</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ramenos - Le Top 10 des sites US avec de mauvaises URL - Référencement</title>
		<link>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-45773</link>
		<author>Ramenos - Le Top 10 des sites US avec de mauvaises URL - Référencement</author>
		<pubDate>Fri, 08 Aug 2008 12:18:47 +0000</pubDate>
		<guid>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-45773</guid>
		<description>[...] url illisible pour un moteur ralentit (voire bloque) l&#8217;indexation d&#8217;un site internet. SEO Blog a listé un top 10 des sites anglophones dont la structure d&#8217;url est catastrophique. Je vous [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] url illisible pour un moteur ralentit (voire bloque) l&#8217;indexation d&#8217;un site internet. SEO Blog a listé un top 10 des sites anglophones dont la structure d&#8217;url est catastrophique. Je vous [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Website Design Perth</title>
		<link>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-43120</link>
		<author>Website Design Perth</author>
		<pubDate>Wed, 23 Jul 2008 08:49:53 +0000</pubDate>
		<guid>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-43120</guid>
		<description>Glad and sad about this post. Glad you wrote it and sad 'cos I've now got a small mountain of work to fix my - and a few clients' - urls :)</description>
		<content:encoded><![CDATA[<p>Glad and sad about this post. Glad you wrote it and sad &#8216;cos I&#8217;ve now got a small mountain of work to fix my - and a few clients&#8217; - urls :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: onreact</title>
		<link>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-42290</link>
		<author>onreact</author>
		<pubDate>Wed, 16 Jul 2008 13:01:16 +0000</pubDate>
		<guid>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-42290</guid>
		<description>Yeah Paul, exactly. That's why I don't read these posts at all after seeing the date. Otherwise I would read it first and then due to the date take the news with a grain of salt. &lt;em&gt;I would read it though!&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>Yeah Paul, exactly. That&#8217;s why I don&#8217;t read these posts at all after seeing the date. Otherwise I would read it first and then due to the date take the news with a grain of salt. <em>I would read it though!</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Burani, Clicksharp Marketing</title>
		<link>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-42287</link>
		<author>Paul Burani, Clicksharp Marketing</author>
		<pubDate>Wed, 16 Jul 2008 12:28:33 +0000</pubDate>
		<guid>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-42287</guid>
		<description>Re: #9 -- true, the date might not be the most sought after nugget of info.  But in appreciation for the ever present battle between human eyeballs and the robots... yes, sometimes that date is useful.  When reading an article about SEO, for instance, I often remind myself about how fast things change in the industry, and read the date before I read anything else.  That way, if I see that the post is from 2006, I know to read it with a certain discerning eye.

So in that case, perhaps it's a design failure from a robots point of view -- but overall I think Wordpress is doing its human readers a favor.</description>
		<content:encoded><![CDATA[<p>Re: #9 &#8212; true, the date might not be the most sought after nugget of info.  But in appreciation for the ever present battle between human eyeballs and the robots&#8230; yes, sometimes that date is useful.  When reading an article about SEO, for instance, I often remind myself about how fast things change in the industry, and read the date before I read anything else.  That way, if I see that the post is from 2006, I know to read it with a certain discerning eye.</p>
<p>So in that case, perhaps it&#8217;s a design failure from a robots point of view &#8212; but overall I think Wordpress is doing its human readers a favor.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: URL Design - auch große Seiten bauen Mist &#124; tekka.de</title>
		<link>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-40860</link>
		<author>URL Design - auch große Seiten bauen Mist &#124; tekka.de</author>
		<pubDate>Wed, 09 Jul 2008 20:29:05 +0000</pubDate>
		<guid>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-40860</guid>
		<description>[...] Design aus SEO-Sicht nicht perfekt. Dies wird in einem Post im SEO 2.0 Blog mit dem Titel &#8220;Top 10 URL Design Failures of Famous Websites&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Design aus SEO-Sicht nicht perfekt. Dies wird in einem Post im SEO 2.0 Blog mit dem Titel &#8220;Top 10 URL Design Failures of Famous Websites&#8221; [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil</title>
		<link>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-40724</link>
		<author>Phil</author>
		<pubDate>Tue, 08 Jul 2008 17:45:58 +0000</pubDate>
		<guid>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-40724</guid>
		<description>Fox news is just too cheap to upgrade from their ancient Vignette StoryServer 5.0. Those are old Vignette URL tags.  

0,2933,308077,00.html

0 = cached page (1 is not cached)
2933 = template id #
308077 = database record number
00 = No browser variations (FF has browser variations)

Wanna have some fun - advance the third number to see fox stories directly - even ones that are "pre-launch" on occasion.  Fox is proxied, but some other sites (like iVillage) will still bypass the cache if you change the first number, and give different layouts if you change the template id, etc  

Of course, you have to be REALLY bored . . .</description>
		<content:encoded><![CDATA[<p>Fox news is just too cheap to upgrade from their ancient Vignette StoryServer 5.0. Those are old Vignette URL tags.  </p>
<p>0,2933,308077,00.html</p>
<p>0 = cached page (1 is not cached)<br />
2933 = template id #<br />
308077 = database record number<br />
00 = No browser variations (FF has browser variations)</p>
<p>Wanna have some fun - advance the third number to see fox stories directly - even ones that are &#8220;pre-launch&#8221; on occasion.  Fox is proxied, but some other sites (like iVillage) will still bypass the cache if you change the first number, and give different layouts if you change the template id, etc  </p>
<p>Of course, you have to be REALLY bored . . .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: onreact</title>
		<link>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-40681</link>
		<author>onreact</author>
		<pubDate>Tue, 08 Jul 2008 10:05:13 +0000</pubDate>
		<guid>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-40681</guid>
		<description>&lt;p&gt;Alex: You are complaining. I am showing webmasters how they can avoid pitfalls of URL design. Are you the webmaster of Bloomberg? Therefore the grudge? I noticed that Bloomberg has partly removed the issues already.&lt;br /&gt;
On a side note, I'm a non-native speaker of English, it's my third language of 5 so I sometimes make mistakes especially in a hurry while blogging. What about your Polish, German, Spanish and French? Thanks for the tip in any case.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Alex: You are complaining. I am showing webmasters how they can avoid pitfalls of URL design. Are you the webmaster of Bloomberg? Therefore the grudge? I noticed that Bloomberg has partly removed the issues already.<br />
On a side note, I&#8217;m a non-native speaker of English, it&#8217;s my third language of 5 so I sometimes make mistakes especially in a hurry while blogging. What about your Polish, German, Spanish and French? Thanks for the tip in any case.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-40677</link>
		<author>Alex</author>
		<pubDate>Tue, 08 Jul 2008 09:38:44 +0000</pubDate>
		<guid>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-40677</guid>
		<description>Complaining about unreadable/unintelligible URLs might be justifiable if you'd bothered to proofread your post.  Bloomberg is, I suspect, a renowned news outlet - you want an adjective, not a noun.</description>
		<content:encoded><![CDATA[<p>Complaining about unreadable/unintelligible URLs might be justifiable if you&#8217;d bothered to proofread your post.  Bloomberg is, I suspect, a renowned news outlet - you want an adjective, not a noun.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: onreact</title>
		<link>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-40597</link>
		<author>onreact</author>
		<pubDate>Mon, 07 Jul 2008 17:27:42 +0000</pubDate>
		<guid>http://seo2.0.onreact.com/top-10-url-design-failures-of-famous-websites#comment-40597</guid>
		<description>Dan: Think about when you are looking at the URL at all. Do you see it when following a link? Or in your RSS reader? No, when they are current you don't see them. You see them in the Google results though, or when you arrive from Google. Then you bounce because the "news" is too old. The date might provide context, but is almost never the single most important part of the content. You don't make the date the h1 headline either, do you? Why do you force the readers then to read the date first in the URL?</description>
		<content:encoded><![CDATA[<p>Dan: Think about when you are looking at the URL at all. Do you see it when following a link? Or in your RSS reader? No, when they are current you don&#8217;t see them. You see them in the Google results though, or when you arrive from Google. Then you bounce because the &#8220;news&#8221; is too old. The date might provide context, but is almost never the single most important part of the content. You don&#8217;t make the date the h1 headline either, do you? Why do you force the readers then to read the date first in the URL?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
