[Update: This post was written before Community Server 2.1 SP2 was released. With SP2 and later versions of Community Server, the URLs are automatically formatted all lowercase with no punctuation characters.]
One of my co-workers, Alex Lowe, recently pointed our team to a post on SEOmoz about best practices for URLs. If you haven't checked it out, I would highly recommend it. Since Alex recommended this post, I have been more aware of URL formats while I browse the web and work with various applications.
So, using Windows Live Writer to post to my blog (which is powered by Community Server) I wanted to see if there was a way to have more control over the URL that was generated for a post. As you may know, Community Server already does a pretty good job converting a post title into a URL. However, if you use certain characters in your title, especially puctuation, it will be encoded to a not so friendly URL... which is expected.
Let's use the example of a post entitled "Pleats are sexy!".
By default, Community Server would create the following URL:
- /_2200_Pleats-are-sexy_21002200_.aspx
Now, minus the punctuation, this seems pretty good. However, if you are creative and are using Windows Live Writer, you can get the following URL instead:
Here's how: simply name your post pleats are sexy and publish it as a draft (notice it is all lowercase and no punctuation). Then, change the title to whatever you like. A different URL will not be created on subsequent publishings of the same post because Windows Live Writer will only send updates for the title, body, and categories to Community Server.
Look at it as a feature or a bug ... whatever you like ... but I must say, I really like this feature.