Mindless Philosophy






6 of the best Umbraco Properties for all websites

by Darren Street

Created on: Tuesday October 15, 2013

2 comments

As you know, Umbraco comes pretty much ready to rock n’ roll from the end of the install. If you choose to install a starter package then you will have a fully working and featured website instantly. For those individuals that like to configure and setup Umbraco from a totally clean install, then these 6 Umbraco properties are a must, to give your website enhanced functionality and flexibility. Create them from the top root document type so that these properties are cascaded down to all pages.

Six of the best

1) 302 Redirect

Assign a Content picker control and assign the alias “umbracoRedirect”. This control allows you to redirect to a page on your site. Google will see a regular temporary redirect and shouldn’t penalise you, however I wouldn’t use this on a root node for obvious reasons.

2) Invisible redirect

Assign a Content picker control and assign the alias “umbracoInternalRedirectId”. This control is a better option to a standard 302 redirect. Umbraco will load the selected page transparently with NO URL redirection. This means that you won’t lose any SEO juice.

3) Url Name Change

Assign a Textstring control and assign the alias “umbracoUrlName”. This will allow you to change the webpage url. This separates the node name form the URL which makes creating landing pages more appropriate and keyword intensive.

4) URL Alias/s

Assign a Textstring control and assign the alias “umbracoUrlAlias”. This is a really cool control. It allows to create multiple URL aliases of the same page. For instance type in “terms, tcs, termsandconditions” the following URLs will be enabled:

/terms.aspx
/tcs.aspx
/ termsandconditions.aspx

It’s really powerful but don’t get too carried away. Multiple URLs to the same content can seriously damage your SEO.

5) Hide from menu

Assign a True / False control and assign the alias “umbracoNaviHide”. A bit of a throwback really but still used in 4.x XSLT systems. Used to hide page nodes in your navigation. By default the XSLT scripts had a condition to test for this property. I think the popular opinion for the Razor folks is to create your own controls. Handly anyway and expect to see it a lot on 4.x websites.

6) Hide from sitemap

Assign a True / False control and assign the alias “umbracoSitemapHide”. Similar to the previous property (umbracoNaviHide) and included here for completeness. I wouldn’t really bother with this one for 6.x websites.

There you have it.

Six of the best, that should be part of all your websites. I tend to stick them all in a tab called “Advanced Settings” which is Windows 3.1 retro. In most of my sites I also include properties to handle bespoke page titling and social media stuff…but that's another blog.

2 comments




semperfi commented on 19 Oct 2013


I am sorry but I don't understand the difference between the first two options as they seem to do the same?

Surely Google won't mark me down for a 302 redirect will they?


Peter M commented on 16 Oct 2013


Just what I needed. Saved me a bunch of time.



Have your say


Sorry this post is no longer accepting comments.