After creating some Umbraco sites and using packages such as Teacommerce. These use umbracoRedirect to redirect the top/landing node to another, for example en language or just because there is a "Site Settings" node above home for setting global properties.
I have noticed that umbracoRedirect uses a 302 redirect and understand this is not great for SEO purposes. I have started using the permanentRedirect package which results in a 301 redirect instead.
Is there a better way of doing this? I.e. so no redirect is required at all? I notice many of the case study sites on Umbraco also have this 302 redirect.
I must admit I can't remember why Umbraco is using a 302 but I think it's actually one of the minor bugs reported on the issue tracker, which should be fairly easy to fix for a person with the proper skills to do it so it makes a 301 instead.
In your case it sounds like you have made the right decision using an external package.
Why does Umbraco use 302 Redirect/home node
After creating some Umbraco sites and using packages such as Teacommerce. These use umbracoRedirect to redirect the top/landing node to another, for example en language or just because there is a "Site Settings" node above home for setting global properties.
I have noticed that umbracoRedirect uses a 302 redirect and understand this is not great for SEO purposes. I have started using the permanentRedirect package which results in a 301 redirect instead.
Is there a better way of doing this? I.e. so no redirect is required at all? I notice many of the case study sites on Umbraco also have this 302 redirect.
Hi Matt
I must admit I can't remember why Umbraco is using a 302 but I think it's actually one of the minor bugs reported on the issue tracker, which should be fairly easy to fix for a person with the proper skills to do it so it makes a 301 instead.
In your case it sounds like you have made the right decision using an external package.
/Jan
is working on a reply...