<?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: Better Search Engine Friendly URL&#8217;s with Ruby on Rails</title>
	<atom:link href="http://www.tonyspencer.com/2007/02/04/better-search-engine-friendly-urls-with-ruby-on-rails/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tonyspencer.com/2007/02/04/better-search-engine-friendly-urls-with-ruby-on-rails/</link>
	<description>It&#039;s Just Links</description>
	<lastBuildDate>Wed, 14 Sep 2011 13:47:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Harlow</title>
		<link>http://www.tonyspencer.com/2007/02/04/better-search-engine-friendly-urls-with-ruby-on-rails/comment-page-1/#comment-8596</link>
		<dc:creator>Harlow</dc:creator>
		<pubDate>Tue, 10 Apr 2007 06:41:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.tonyspencer.com/2007/02/04/better-search-engine-friendly-urls-with-ruby-on-rails/#comment-8596</guid>
		<description>Sorry made a typo:
And in the view: link_to @client.name, client_url(:permalink =&gt; @client.permalink)</description>
		<content:encoded><![CDATA[<p>Sorry made a typo:<br />
And in the view: link_to @client.name, client_url(:permalink =&gt; @client.permalink)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harlow</title>
		<link>http://www.tonyspencer.com/2007/02/04/better-search-engine-friendly-urls-with-ruby-on-rails/comment-page-1/#comment-8595</link>
		<dc:creator>Harlow</dc:creator>
		<pubDate>Tue, 10 Apr 2007 06:40:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.tonyspencer.com/2007/02/04/better-search-engine-friendly-urls-with-ruby-on-rails/#comment-8595</guid>
		<description>I feel like the id-words-words is a bit of an ugly solution. I get that its easy and will satisfy most. 

However if you are representing clients names then the user should not have to remember the ID. I.E. if you were talking to someone and said &quot;go to mydomain.com and type /apple&quot; as opposed to &quot;go to mydomain.com and type /1233-apple&quot;

I&#039;ve found the map.something_custom in the routes.rb file to be a much nicer solution: 

map.client &#039;client/:permalink&#039;, :controller =&gt; &#039;test&#039;, :action =&gt; &#039;show&#039;, :permalink =&gt; &#039;&#039;

Then in the controller: @client = Client.find_by_permalink(params[:permalink])

And in the view: link_to @client.name, show_client(:permalink =&gt; @client.permalink)

This way you have full customization over the url paths, and still retain permalink functionality. Write a little AJAX on the input form and you can generate/and validate URLs. This is really nice because you don&#039;t always need the whole title of your post in the URL.</description>
		<content:encoded><![CDATA[<p>I feel like the id-words-words is a bit of an ugly solution. I get that its easy and will satisfy most. </p>
<p>However if you are representing clients names then the user should not have to remember the ID. I.E. if you were talking to someone and said &#8220;go to mydomain.com and type /apple&#8221; as opposed to &#8220;go to mydomain.com and type /1233-apple&#8221;</p>
<p>I&#8217;ve found the map.something_custom in the routes.rb file to be a much nicer solution: </p>
<p>map.client &#8216;client/:permalink&#8217;, :controller =&gt; &#8216;test&#8217;, :action =&gt; &#8217;show&#8217;, :permalink =&gt; &#8221;</p>
<p>Then in the controller: @client = Client.find_by_permalink(params[:permalink])</p>
<p>And in the view: link_to @client.name, show_client(:permalink =&gt; @client.permalink)</p>
<p>This way you have full customization over the url paths, and still retain permalink functionality. Write a little AJAX on the input form and you can generate/and validate URLs. This is really nice because you don&#8217;t always need the whole title of your post in the URL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack</title>
		<link>http://www.tonyspencer.com/2007/02/04/better-search-engine-friendly-urls-with-ruby-on-rails/comment-page-1/#comment-6978</link>
		<dc:creator>Jack</dc:creator>
		<pubDate>Thu, 29 Mar 2007 02:42:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.tonyspencer.com/2007/02/04/better-search-engine-friendly-urls-with-ruby-on-rails/#comment-6978</guid>
		<description>How about http://chrisfarms.googlecode.com/svn/rails/plugins/acts_as_friendly_param/README

Known as Acts_As_Friendly_Param</description>
		<content:encoded><![CDATA[<p>How about <a href="http://chrisfarms.googlecode.com/svn/rails/plugins/acts_as_friendly_param/README">http://chrisfarms.googlecode.com/svn/rails/plugins/acts_as_friendly_param/README</a></p>
<p>Known as Acts_As_Friendly_Param</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tony</title>
		<link>http://www.tonyspencer.com/2007/02/04/better-search-engine-friendly-urls-with-ruby-on-rails/comment-page-1/#comment-4023</link>
		<dc:creator>tony</dc:creator>
		<pubDate>Wed, 28 Feb 2007 01:30:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.tonyspencer.com/2007/02/04/better-search-engine-friendly-urls-with-ruby-on-rails/#comment-4023</guid>
		<description>Without a doubt chrisfarm&#039;s is the perfect solution and so easy!  Well done mate.  I just installed the plugin and was up and running in seconds.</description>
		<content:encoded><![CDATA[<p>Without a doubt chrisfarm&#8217;s is the perfect solution and so easy!  Well done mate.  I just installed the plugin and was up and running in seconds.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stancell</title>
		<link>http://www.tonyspencer.com/2007/02/04/better-search-engine-friendly-urls-with-ruby-on-rails/comment-page-1/#comment-3675</link>
		<dc:creator>Stancell</dc:creator>
		<pubDate>Fri, 23 Feb 2007 13:55:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.tonyspencer.com/2007/02/04/better-search-engine-friendly-urls-with-ruby-on-rails/#comment-3675</guid>
		<description>Chrisfarms solution is better than permalink_fu cause it allows to change url.

After renaming &quot;Apple Computer&quot; to &quot;Apple Inc.&quot;
/companies/7-apple-computer would change to /companies/7-apple-inc

/companies/7-apple-computer would return a 301 (permanent) redirect to /companies/7-apple-inc and that is the way it should be.</description>
		<content:encoded><![CDATA[<p>Chrisfarms solution is better than permalink_fu cause it allows to change url.</p>
<p>After renaming &#8220;Apple Computer&#8221; to &#8220;Apple Inc.&#8221;<br />
/companies/7-apple-computer would change to /companies/7-apple-inc</p>
<p>/companies/7-apple-computer would return a 301 (permanent) redirect to /companies/7-apple-inc and that is the way it should be.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chrisfarms</title>
		<link>http://www.tonyspencer.com/2007/02/04/better-search-engine-friendly-urls-with-ruby-on-rails/comment-page-1/#comment-3140</link>
		<dc:creator>chrisfarms</dc:creator>
		<pubDate>Thu, 15 Feb 2007 19:24:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.tonyspencer.com/2007/02/04/better-search-engine-friendly-urls-with-ruby-on-rails/#comment-3140</guid>
		<description>@tony: I took yours and Obie advice/idea into account and stoped the multiple page issue.... hope you find it useful

http://www.chrisfarms.com/2007/2/11/seo-friendly-urls-in-rails</description>
		<content:encoded><![CDATA[<p>@tony: I took yours and Obie advice/idea into account and stoped the multiple page issue&#8230;. hope you find it useful</p>
<p><a href="http://www.chrisfarms.com/2007/2/11/seo-friendly-urls-in-rails">http://www.chrisfarms.com/2007/2/11/seo-friendly-urls-in-rails</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tony</title>
		<link>http://www.tonyspencer.com/2007/02/04/better-search-engine-friendly-urls-with-ruby-on-rails/comment-page-1/#comment-2529</link>
		<dc:creator>tony</dc:creator>
		<pubDate>Sun, 04 Feb 2007 21:13:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.tonyspencer.com/2007/02/04/better-search-engine-friendly-urls-with-ruby-on-rails/#comment-2529</guid>
		<description>Hey Obie,
That would still be a bad thing for SEO as it would result in multiple, indexable pages with exactly duplicate content.</description>
		<content:encoded><![CDATA[<p>Hey Obie,<br />
That would still be a bad thing for SEO as it would result in multiple, indexable pages with exactly duplicate content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Obie Fernandez</title>
		<link>http://www.tonyspencer.com/2007/02/04/better-search-engine-friendly-urls-with-ruby-on-rails/comment-page-1/#comment-2528</link>
		<dc:creator>Obie Fernandez</dc:creator>
		<pubDate>Sun, 04 Feb 2007 20:44:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.tonyspencer.com/2007/02/04/better-search-engine-friendly-urls-with-ruby-on-rails/#comment-2528</guid>
		<description>Hey Tony, thanks for the acknowledgement, and here&#039;s one quick point that I should have emphasized -- because the significant part of the URL is the numerical id (and the textual part of the slug is ignored when pulling up a resource), then even if the name was changed in the future, the original URL would still work perfectly with old links.</description>
		<content:encoded><![CDATA[<p>Hey Tony, thanks for the acknowledgement, and here&#8217;s one quick point that I should have emphasized &#8212; because the significant part of the URL is the numerical id (and the textual part of the slug is ignored when pulling up a resource), then even if the name was changed in the future, the original URL would still work perfectly with old links.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

