57

Is there anything built into SharePoint 2010 that will handle this? If not, can anyone suggest where to start to implement something that will allow me to rewrite URLs so they are more SEO and user friendly?

For example I have the following URL:

http://mySite.com/igs/isapps/Documentation/Forms/AllItems.aspx?RootFolder=%2Figs%2Fisapps%2FDocumentation%2FDept%20of%20Social%20Services%20ISA%20Processes&FolderCTID=0x0120005714AE5SFBAA334D4EA0BC44CD9F3308CD&View={23BE8E1-563C-4B98-97E9-DC4FF53C38B8}

And I would like to rewrite it to be something like this:

http://mySite.com/InformationServices/SocialServicesProcesses

5 Answers 5

41

There is no built-in SharePoint mechanism to do this. It is frequently requested, particularly for public-facing sites, usually for purposes of SEO and for vanity domains. In both cases the re-writing is usually unnecessary and should be resisted. Apart from anything else, URL rewriting is not supported. It can also affect performance significantly if you have complex rules, and you risk breaking something in SharePoint.

Having said that, we live in the real world ;-)

Microsoft have an add-on for IIS7 called URL Rewrite that does the job. There is also a third-party module called urlrewriter.net. Both of these work; neither are supported. You will need to disable them or possibly remove them to get support from Microsoft. But I would still avoid using rewrites unless it was really necessary.

A better approach may be to redirect rather than rewrite. This means sending a 301 (permanent) or 302 (temporary) redirect to the browser. It involves an additional round-trip to the browser, and the actual URL will appear in the browser address bar, but depending on circumstances this may be acceptable. This method is supported because you are not interfering with the actual SharePoint URL. Rewriters are usually also capable of doing redirects, or you may be able to use a SharePoint redirect page depending on the required URL.

6
  • 2
    We are planning on doing this in order to cover some document changes as the web site gets an upgrade to SharePoint 2010. In order to cover known book marked sites and public documents we are using the URL Rewrite and its working pretty well in Test.
    – MichaelF
    Commented May 15, 2011 at 18:11
  • 1
    Yes, sometimes business necessitates going unsupported and if you are forced down that route you carry an extra burden of risk; so now you have to test thoroughly. I would add that if it is just a change of URL (and you don't need to hide that fact) then the 301 redirect is the best solution.
    – SPDoctor
    Commented May 16, 2011 at 9:31
  • Actually that's good to know, it is what we ended up with. In testing it's what seemed to work better for navigation and page controls. Thanks for confirming it!
    – MichaelF
    Commented May 16, 2011 at 11:51
  • Thanks for your explanation. Do you have a public source from Microsoft for your statement that URL rewriting is not supported in SharePoint 2010? Commented May 24, 2012 at 12:12
  • I am not aware of a specific online Microsoft resource that specifically states that rewriting is unsupported. However, it is common knowledge in the SharePoint community, and has been stated by Microsoft consultants and PFEs. I have also seen cases of SharePoint functionality breaking as a result of URL rewrites.
    – SPDoctor
    Commented May 24, 2012 at 13:27
21

No: you should not use URL rewriting with SharePoint. There is no built-in stuff or anything like that. SharePoint is a very URL focused product and many things can go wrong when rewriting URLs.

Yes: you could create some 302 redirect to have more friendly URL's.

It depends: the are some scenarios (mostly for public facing websites) where URL redirection might be considered. But consider it very carefully. Things might not work as expected...

5
  • 3
    ...many things can go wrong when rewriting URLs. Any chance you can point me to some more info on this? Commented May 14, 2011 at 5:15
  • 5
    One thing is that the SPContext is extremely dependant on the URL. Commented May 14, 2011 at 5:36
  • That's a big one. Do you know if there are any links out there that go over the potential pitfalls? Commented May 14, 2011 at 17:24
  • 1
    @Abe - here's a recent example that hurt me: sharepoint.stackexchange.com/q/12082/2932
    – Kobi
    Commented May 15, 2011 at 4:50
  • and i should mention about blank pages. everything is ok but the contents of the page(for example webparts) won't show up. Commented Jun 12, 2012 at 8:05
13

If you have TMG in place, you may be able to write some rules to do a redirect of your friendly URL to the less friendly SharePoint URL, but you'd have to define each one. There's no way that I know of for a rewrite to take place that will be smart enough to navigate into a folder and pull out the right URL parameters automatically to take the user there.

Just saw this over on Joel Olsen's blog also: http://www.sharepointjoel.com/Lists/Posts/Post.aspx?ID=439

11

Official Microsoft support for URL rewriting are now published as a Microsoft Knowledgebase article:

http://support.microsoft.com/kb/2818415

1
  • ...but only for symmetrical rewrites, e.g. changing one domain for another. Changing the URL tail is unsupported, .../site/SitePages/Some%20Long%20Name --> .../knowledgebase/Some_Long_Name is not allowed. Commented Sep 5, 2013 at 16:16
5

There are third party Add-Ons(like this: sharepoint short url),which can remap(302 redirect) sharepoint url.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.