<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Why storing URLs with truncated trailing slashes is an utterly idiocy</title>
	<link>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/</link>
	<description>If you've read my articles somewhere on the Internet, expect something different here.</description>
	<pubDate>Wed, 23 May 2012 06:41:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: Bozho&#39;s tech blog &#187; Pretty URLs and the trailing slash</title>
		<link>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-2899</link>
		<dc:creator>Bozho&#39;s tech blog &#187; Pretty URLs and the trailing slash</dc:creator>
		<pubDate>Tue, 21 Jun 2011 08:48:34 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-2899</guid>
		<description>[...] This article explains the matter in more details. Note however that it advocates retaining the trailing slash, but it doesn&#8217;t focus on pretty urls in particular. Yes, you should retain the trailing slash for your index page and for any directories, but that&#8217;s it. The rest are resources and so they should not have the slash. The main point is that you must be consistent. From the practical point of view it is not that wrong to retain the slash (although it contradicts the directory structure logic), but have it for every resource, and have all your links conform to that choice. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] This article explains the matter in more details. Note however that it advocates retaining the trailing slash, but it doesn&#8217;t focus on pretty urls in particular. Yes, you should retain the trailing slash for your index page and for any directories, but that&#8217;s it. The rest are resources and so they should not have the slash. The main point is that you must be consistent. From the practical point of view it is not that wrong to retain the slash (although it contradicts the directory structure logic), but have it for every resource, and have all your links conform to that choice. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BlueBoden</title>
		<link>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-2790</link>
		<dc:creator>BlueBoden</dc:creator>
		<pubDate>Sun, 16 Jan 2011 22:01:06 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-2790</guid>
		<description>Sebastian you are indeed wrong, if the "/" slash is missing, it will be automatically assumed. The path can NOT be empty, I've read the specifications.

It will not generate any duplicate content.</description>
		<content:encoded><![CDATA[<p>Sebastian you are indeed wrong, if the &#8220;/&#8221; slash is missing, it will be automatically assumed. The path can NOT be empty, I&#8217;ve read the specifications.</p>
<p>It will not generate any duplicate content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BlueBoden</title>
		<link>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-2762</link>
		<dc:creator>BlueBoden</dc:creator>
		<pubDate>Sun, 12 Dec 2010 11:29:32 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-2762</guid>
		<description>I think you are wrong with the http://example.com/ redirect, because the requested path will always be "/", it makes no sense to redirect http://example.com to http://example.com/

The HTTP specification states, that a empty path, is the same as "/", in other words the root directory.

[Link removed, page doesn't load in Chrome. For search engines and other services indexing Web resources by URI http://example.com and http://example.com/ are (usually) different URIs, giving two records for a resource. That's crap. Sebastian]</description>
		<content:encoded><![CDATA[<p>I think you are wrong with the <a href="http://example.com/">http://example.com/</a> redirect, because the requested path will always be &#8220;/&#8221;, it makes no sense to redirect <a href="http://example.com">http://example.com</a> to <a href="http://example.com/">http://example.com/</a></p>
<p>The HTTP specification states, that a empty path, is the same as &#8220;/&#8221;, in other words the root directory.</p>
<p>[Link removed, page doesn&#8217;t load in Chrome. For search engines and other services indexing Web resources by URI <a href="http://example.com">http://example.com</a> and <a href="http://example.com/">http://example.com/</a> are (usually) different URIs, giving two records for a resource. That&#8217;s crap. Sebastian]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sebastian</title>
		<link>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-2398</link>
		<dc:creator>Sebastian</dc:creator>
		<pubDate>Tue, 18 May 2010 13:19:14 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-2398</guid>
		<description>Don't miss out on this &lt;a href="http://maileohye.com/search-engines-urls-trailing-slash/"&gt;status report from Google's very hot Maile Ohye&lt;/a&gt;!</description>
		<content:encoded><![CDATA[<p>Don&#8217;t miss out on this <a href="http://maileohye.com/search-engines-urls-trailing-slash/">status report from Google&#8217;s very hot Maile Ohye</a>!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: g1smd</title>
		<link>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-2355</link>
		<dc:creator>g1smd</dc:creator>
		<pubDate>Tue, 23 Mar 2010 13:33:33 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-2355</guid>
		<description>Yes, this is exactly the point. Quoting  example.com  in a printed newspaper advert, or on radio and TV, allows people to access the site by typing the least amount of characters, the site redirecting the user to www.example.com/ before showing the content. There are no searchengine related effects.

On the other hand, where there is another website linking out to a non-canonical URL such as example.com or example.com/index.html this may mean that the linked-to site does not get a full credit for that link when it is the URL www.example.com/ that will serve the content after the redirect.

The redirect is necessary. It removes the possibility of Duplicate Content issues, but there might still be some drawbacks when non-canonical URLs are used in links.</description>
		<content:encoded><![CDATA[<p>Yes, this is exactly the point. Quoting  example.com  in a printed newspaper advert, or on radio and TV, allows people to access the site by typing the least amount of characters, the site redirecting the user to <a href="http://www.example.com/">www.example.com/</a> before showing the content. There are no searchengine related effects.</p>
<p>On the other hand, where there is another website linking out to a non-canonical URL such as example.com or example.com/index.html this may mean that the linked-to site does not get a full credit for that link when it is the URL <a href="http://www.example.com/">www.example.com/</a> that will serve the content after the redirect.</p>
<p>The redirect is necessary. It removes the possibility of Duplicate Content issues, but there might still be some drawbacks when non-canonical URLs are used in links.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-2261</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Thu, 11 Feb 2010 07:01:46 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-2261</guid>
		<description>Giuseppe said:
 It doesn’t matter what’s cool and what’s not, fashion of the day changes, well, everyday.

What’s important (and you haven’t addressed it) is the fact that people can link to your URL with or without the trailing slash.
And since Google doesn’t give you full recognition for a link that points to a 301 you want to make sure your site returns 200 for URL with AND without slash.

That is exactly what happen to my site, being dropped off the Google index because of an automatically added slash (and all of my links don’t have slashes)
=======================


Is this true??</description>
		<content:encoded><![CDATA[<p>Giuseppe said:<br />
 It doesn’t matter what’s cool and what’s not, fashion of the day changes, well, everyday.</p>
<p>What’s important (and you haven’t addressed it) is the fact that people can link to your URL with or without the trailing slash.<br />
And since Google doesn’t give you full recognition for a link that points to a 301 you want to make sure your site returns 200 for URL with AND without slash.</p>
<p>That is exactly what happen to my site, being dropped off the Google index because of an automatically added slash (and all of my links don’t have slashes)<br />
=======================</p>
<p>Is this true??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen</title>
		<link>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-2260</link>
		<dc:creator>Stephen</dc:creator>
		<pubDate>Wed, 10 Feb 2010 17:48:18 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-2260</guid>
		<description>Hello Sebastian.

I never thought I would come across an article so pertinent to my long-held secret: I've always had a problem with "trailing" slashes. Im not an expert but I always understood that our root index page should be expressed as: http://wwww.example.com/ for instance. And that made sense, and I have tried to use that. Over the years though, I have found that many site submission companies would not accept this format. To make a long story short, I began designing various iterations of my site by using the following base href: http://www.example.com (i.e. no trailing slash). So as a result of that, I have always written links to internal directories in what I now assume is an incorrect format, as so: /MedwordStore/index.html. I preface internal links with the forward slash since the base reference doesn't include one. I suppose I could change the base href in each directory to minimize the size of actual written links under each directory. I also work on our virtual server sometimes and, I may be wrong, but I thought the rule was that those directories are to be finished without a trailing slash?

Do I have any chance of redemption? Can I change my wrong-thinking and still make bad web designs? :-)

[301 is your friend]</description>
		<content:encoded><![CDATA[<p>Hello Sebastian.</p>
<p>I never thought I would come across an article so pertinent to my long-held secret: I&#8217;ve always had a problem with &#8220;trailing&#8221; slashes. Im not an expert but I always understood that our root index page should be expressed as: <a href="http://wwww.example.com/">http://wwww.example.com/</a> for instance. And that made sense, and I have tried to use that. Over the years though, I have found that many site submission companies would not accept this format. To make a long story short, I began designing various iterations of my site by using the following base href: <a href="http://www.example.com">http://www.example.com</a> (i.e. no trailing slash). So as a result of that, I have always written links to internal directories in what I now assume is an incorrect format, as so: /MedwordStore/index.html. I preface internal links with the forward slash since the base reference doesn&#8217;t include one. I suppose I could change the base href in each directory to minimize the size of actual written links under each directory. I also work on our virtual server sometimes and, I may be wrong, but I thought the rule was that those directories are to be finished without a trailing slash?</p>
<p>Do I have any chance of redemption? Can I change my wrong-thinking and still make bad web designs? <img src='http://sebastians-pamphlets.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>[301 is your friend]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Links: Por Que uma Barra Faz Diferença? - Linka - SEO, links patrocinados e SEM</title>
		<link>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-1779</link>
		<dc:creator>Links: Por Que uma Barra Faz Diferença? - Linka - SEO, links patrocinados e SEM</dc:creator>
		<pubDate>Fri, 11 Sep 2009 08:57:00 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-1779</guid>
		<description>[...] parar no lugar errado, ou em lugar nenhum. Façamos a analogia dos números de telefone, como fez Sebastian: pense na URL como um número de telefone. Se você discar 3165-2020 terá a pizzaria que [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] parar no lugar errado, ou em lugar nenhum. Façamos a analogia dos números de telefone, como fez Sebastian: pense na URL como um número de telefone. Se você discar 3165-2020 terá a pizzaria que [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Could You Be Damaging Your Own Link Building Strategies? - Scotland SEO Blog</title>
		<link>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-1777</link>
		<dc:creator>&#187; Could You Be Damaging Your Own Link Building Strategies? - Scotland SEO Blog</dc:creator>
		<pubDate>Thu, 10 Sep 2009 07:01:27 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-1777</guid>
		<description>[...] is an old post on Sebastian’s Pamphlets that has been picked up by Ann Smarty on Search Engine Journal. The question of using exact URLs is [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] is an old post on Sebastian’s Pamphlets that has been picked up by Ann Smarty on Search Engine Journal. The question of using exact URLs is [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Linking Issues: Why a Trailing Slash in the URL Does Matter &#124; Search Engine Journal</title>
		<link>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-1772</link>
		<dc:creator>Linking Issues: Why a Trailing Slash in the URL Does Matter &#124; Search Engine Journal</dc:creator>
		<pubDate>Tue, 08 Sep 2009 07:19:35 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/thou-must-not-steal-the-trailing-slash-from-my-urls/#comment-1772</guid>
		<description>[...] Well, to begin with, if you get such a reply from a web developer, start looking for another one because this answer is profoundly incorrect, to say at least. When it comes to an URL, every single character matters, I like it how Sebastien put it in his totally cool post on stealing the trailing slash from the URL: [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Well, to begin with, if you get such a reply from a web developer, start looking for another one because this answer is profoundly incorrect, to say at least. When it comes to an URL, every single character matters, I like it how Sebastien put it in his totally cool post on stealing the trailing slash from the URL: [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

