Why Permalinks?

Topics: Controls
Oct 18, 2011 at 1:50 PM

Here's what may seem like an odd questions... Why does blogengine have a feature called permalinks? 

I see that their is a redirection extension available, so if I need to change the page slug for a post, I can just add a redirection from the old url to the new one.  Given that, what's the point of a "permalink?"


Oct 18, 2011 at 2:39 PM
Edited Oct 24, 2011 at 8:43 PM




Java Blog

Oct 18, 2011 at 3:06 PM

Thanks Kb,  I guess I didn't ask my question well enough.  Sorry about that.

I understand the need for a unique url that can link to a blog post in isolation, i.e. not on the home page where it will scroll away.  My question isn't why do we need url's that take us to individual blog posts.  My question is why do we need the "permalinks" to be a distinct concept seprate from the blog post url?  

For example, the url to the individual blog post may look something like this /blog/post/my-cool-blog-article-title.aspx but the "permalink" on blogengine.net is a guid based link.  Here's an example from nyveldt.com; permilink: http://www.nyveldt.com/blog/post.aspx?id=49d30bcd-c70e-45e5-b9b0-81397d6fb65e does a 301 redirect to http://www.nyveldt.com/blog/post/Perfect-mockups.aspx  (real example).  Why not just have people link to the actual post? e.g. http://www.nyveldt.com/blog/post/Perfect-mockups.aspx .  Then, if the page name ever changes, use the seo redirect module to redirect requests from the old url to the new one. 

Seems like the guid based permalink doesn't add any value and causes external links to the site to use a non-intuitive url that leaks SEO juice that needn't be lost.

Am I missing something?


Oct 19, 2011 at 5:39 PM

I agree with you on that one Ron.


But, where are you seeing the "permalink" with http://www.nyveldt.com/blog/post.aspx?id=49d30bcd-c70e-45e5-b9b0-81397d6fb65e   ?


All the permalink I see in newer BE 2.0 and above just have the actual url "pagename.aspx"


Oct 19, 2011 at 5:53 PM

In BE 2.5 with the default theme, if I hover the permalink with my cursor I can see that that the link uses a guid id (or just view source in the browser to see the guid based Id).  It's true that the guid based permalink does a 301 redirection to a non guid based url.  But why even have a guid based permalink?  Why not just let people that want to link to a blog article copy the post url from the browser address bar since that's what the permalink is gonna redirect to anyway?

I think the "permalink" concept is an old outdated solution to potentially changing post urls, and a better solution exists today.  If the post url changes, we can just use the SEO Redirect module to map the old url to the new one. I think the permalink concept should go away and the SEO Redirect module should be part of the standard install.



Oct 19, 2011 at 6:31 PM

Well I am also wondering about the permalink too :)

Ben or Rtur:  Why not have link directly to the link instead of the permalink?


Why have a link like: http://www.nyveldt.com/blog/post.aspx?id=49d30bcd-c70e-45e5-b9b0-81397d6fb65e




I think the permalink concept should go away and the SEO Redirect module should be part of the standard install.


I agree 



I think BE should have some kind of a URL history tracker of the [Post/Page]s.


This way the SEO redirect is automatically.






You later on decide to change the URL name to



BE would track this change and redirect it automatically for you.

Oct 19, 2011 at 6:45 PM

Standard theme does use GUID in permalink, but it is not required. You can use "Post.RelativeLink" instead of "Post.PermaLink" and it will do exactly what you want, giving you regular post link.

Never been involved with this, but I'm guessing you right about it been old concept from time when IIS wasn't good in redirecting requests. I don't see a point in removing GUID from Post.PermaLink though, most older themes would rely on it and there may be things we are missing. For example people with established GUID-based permalinks would want to keep it, allowing duplicate posts that differ only by GUID would break etc.

But we can "modernize" standard theme, so people who use it as template for new themes won't copy "Post.PermaLink" to new designs.

Oct 19, 2011 at 6:55 PM

kb & rtur - thanks for your thoughts.

Rtur - sounds like a good approach to balancing backward compatibility with streamlining/improving the ui going forward.