Last, but not least. Someone said case difference may mean different pages and that case Google would index them separately. I’m not sure if this is true but the best practice is to have one version of the page (I’d recommend it be the lowercase). Follow these steps to generate lowercase URLs:Create a new class that overrides Sitecore.Links.LinkProvider class

Share this:

8 responses

Nice material here. One issue with the space to dash replacement is that once you make that change, you can no longer use dashes in the item names and must stick with spaces. Sometimes clients like to name items with colons and since colons are not allowed, they use a dash in the place of a colon (for the item name). With this approach, they can’t use the dash either. Just something to note.

Thank you for reiterating that Mark. I forgot to say I usually add dash into InvalidItemNameChars value=”\/:?"<>|[]-” as well to prevent the issue. However, when you install some Sitecore modules that contain item with dash, you might have to temporarily remove dash from the setting.

All super useful information! I was looking for an article like this a month or 2 ago. I’ve since found most of the solutions described here scattered through the web. But it’s great to see them all in one space.

Mark’s comment is very important, if you use:

then you really have to add the ‘-‘ to the InvalidItemNameChars to protect your content creators from breaking the pages they create.

You are so awesome! I do not suppose I’ve read anything like that before.

So wonderful to discover someone with original thoughts on this issue.
Seriously.. many thanks for starting this up. This web site is
something that is needed on the internet, someone with some
originality!

Thanks for the post! I added the configuration and it does work with replace space in url with dash but sadly the links replaced are all broken it says cannot find the item. Am I missing something? Thanks!