I would talk in great detail about the URL you want to pave. And put it above the default route.
routes.MapRoute( "HomeActions", "AboutUs", new { controller = "Home", action= "AboutUs" } ); routes.MapRoute( "Default", "{controller}/{action}/{id}", new { controller = "Home", action = "Index", id = UrlParameter.Optional } );
Being less specific with a route like the one you suggested may have undesirable consequences. Especially if the default route is listed below.
routes.MapRoute( "HomeActions", "{action}", new { controller = "Home", action= "AboutUs" } );
For example, if the above route is added after the default, then the URL http://www.example.com/AboutUs will most likely match the route {controller = "AboutUs", action = "Index", id = UrlParamter.Optional }. If you added a route above the default, then look for the URL http://www.example.com/Users , which you might want to be an index action in the Users controller will now look for the Users action on the Home controller.
So, I would advise to be specific about such routes.
source share