Hi Tycho, Thanks for the explanation - it sounds like a big topic - like there may be additional considerations. :) I would be happy to simply shut off the "force to lowercase" setting altogether, but as you noted, it may cause issues with Analytics, even if Google generally realizes that two variants of the URL are the same page for Search Results. I did do a test and noted that, with the "all-lowercase" option shut off, mixed case URLs still reach the intended page that was defined with an all-lowercase URL; I was afraid it would just be a 404 or go to the previous level page as DNN does.
- What would seem to me to be really slick is if there was a way to allow mixed case to be allowed in the portion of the URL past the actual page path, so that query string parameters could be mixed, but force lowercase for the rest. The option now by building a regex expression for "
- I found an article by Bruce Chapman telling about a base page property for CanonicalLinkUrl - https://www.dnnsoftware.com/community-blog/cid/155321/create-a-canonical-url-link-in-dnn-by-using-the-canonicallinkurl-property - but it only seems to be available to set programmatically through a DNN module. If I could set it in SQL based on the page URL minus any query string parameters, that might be a way to go. Or it might create even bigger problems! :)
- I've also seen it mentioned that setting the site alias mode to "Canonical" instead of "Redirect" should add a link to every page - but that it would just mirror whatever URL got to the page at that moment.
- I may just add the tracking code regex (for hubspot tracking codes in the Keep in QueryString setting, I used: "|(/hsa_[^/]+/[^/]+)+". to prevent any URL with hubspot tracking codes in it to preserve mixed case. I'm thinking that may have about the same effect as shutting off the global option, though.
Thanks again for the input! Still trying to wrap my head around what the best option is here.
PS - Here's a sample URL: https://unitedtraining.com/course-o...id=Test123