A while ago I’ve released Mavention Meta Fields: a solution that makes it easy to add meta tags to Publishing Pages in SharePoint 2010. Shortly after the release it turned out that the dependency on jQuery was causing some problems in integrating the solution with existing environments using different versions of jQuery.
A few days after we launched our new website I used my favorite search engine to do a search on one of my fellow-Mavens. I was really surprised to see that in just a few days the first result came from our brand new website! So what is it exactly that we did that gave us such great results in such a short time?
Nearly a year ago I wrote an article about why you should be using permanent redirects (301) instead of temporary redirects (302) which are SharePoint defaults. Back then I presented a custom HTTP Module as a possible solution. Since then things changed a little: we have SharePoint 2010, which still has the same challenge, and we have IIS7 which allows us to get things done without a single line of code.
Recently I’ve released the Mavention Meta Fields SharePoint 2010 solution that allows you to easily add meta tags to Publishing Pages. While the first version was a great improvement of the user experience for managing meta tags of Publishing Pages, it had a minor flaw when using multiple Content Types in a single Pages Library with different sets of meta tags fields. This issue has been fixed in this release.
Many customers who use SharePoint Server 2010 for their Internet-facing website, ask for a mechanism that would allow them to use short URLs like http://www.awt.com/edinburgh instead of http://www.awt.com/destinationguides/uk/scotland/edinburgh/. SharePoint 2010 doesn’t have such mechanism out of the box and if you know SharePoint at least a little, you know that there is always more than one way to get something done. So what are the possibilities and which one of them is the best to use?