SEO - CMS-controlled URL Redirects, and automating redirects for node name changes
Hi all. I was wondering if anybody has come up with some nice solutions to redirects in Umbraco.
Currently, our process is to ditch the UrlRewriting.net stuff and use IIS URL Rewrite maps. We periodically review 404 requests for a client website, and then add in new redirects to our redirect map in source code, and then deploy to the server.
This is a time consuming process AND requires developer involvement to edit and commit files to source control, push live and then press the button to build in the deployment tool.
In an ideal world, I would like to be able to set up Umbraco to do the following:
Allow CMS users (i.e. the client) to add redirects, without developer or technical support
Automate the process of adding in new redirects when nodes get renamed or moved around in the CMS.
Point 1 - we have nothing like this in any of our Umbraco solutions. As a sort of bodge, we do allow CMS editors to use the umbracoUrlAlias feature, but obviously this is a rewrite not a redirect and it's not really what we want. It's a bodge and means we have duplicate content.
Point 2 - I don't know if any module exists or anybody does anything like this already, but I was considering writing some code that hooks into the publish event, and when a node is published it stores the node URL against the node ID in the database, and does some checks to see if there are any previous URLs for this node, and if so adds in some redirects. Whether this edits the rewritemap file on the server or we have an extra layer of redirect logic in the site, I'm not sure, I'd like to avoid the overhead of doing any of our own redirect logic. If we edit the rewrite maps, I'm not sure how to trigger IIS to reload the maps in code without resetting the app pool.
Any thoughts or suggestions for either of these issues? They are common problems and I'd be surprised if the community doesn't already have some great solutions.
I'm not sure how I didn't come across this before. It seems like it will cover off both of my requirements, but I'm not sure if it works with 6.2.x. I'll give this a try but any further suggestions or ideas are of course very welcome.
301 URL Tracker did the trick nicely, all seems to be working well on 6.2.1. Seems to be an issue with renaming nodes and then naming them back, but it's not a deal-breaker.
SEO - CMS-controlled URL Redirects, and automating redirects for node name changes
Hi all. I was wondering if anybody has come up with some nice solutions to redirects in Umbraco.
Currently, our process is to ditch the UrlRewriting.net stuff and use IIS URL Rewrite maps. We periodically review 404 requests for a client website, and then add in new redirects to our redirect map in source code, and then deploy to the server.
This is a time consuming process AND requires developer involvement to edit and commit files to source control, push live and then press the button to build in the deployment tool.
In an ideal world, I would like to be able to set up Umbraco to do the following:
Point 1 - we have nothing like this in any of our Umbraco solutions. As a sort of bodge, we do allow CMS editors to use the umbracoUrlAlias feature, but obviously this is a rewrite not a redirect and it's not really what we want. It's a bodge and means we have duplicate content.
Point 2 - I don't know if any module exists or anybody does anything like this already, but I was considering writing some code that hooks into the publish event, and when a node is published it stores the node URL against the node ID in the database, and does some checks to see if there are any previous URLs for this node, and if so adds in some redirects. Whether this edits the rewritemap file on the server or we have an extra layer of redirect logic in the site, I'm not sure, I'd like to avoid the overhead of doing any of our own redirect logic. If we edit the rewrite maps, I'm not sure how to trigger IIS to reload the maps in code without resetting the app pool.
Any thoughts or suggestions for either of these issues? They are common problems and I'd be surprised if the community doesn't already have some great solutions.
I've just noticed the package 301 URL Tracker, http://our.umbraco.org/projects/developer-tools/301-url-tracker
I'm not sure how I didn't come across this before. It seems like it will cover off both of my requirements, but I'm not sure if it works with 6.2.x. I'll give this a try but any further suggestions or ideas are of course very welcome.
301 URL Tracker did the trick nicely, all seems to be working well on 6.2.1. Seems to be an issue with renaming nodes and then naming them back, but it's not a deal-breaker.
is working on a reply...