We have a two site setup of staging/edit and live - and we use courier (a third party extension) to take published content from the staging to the live site.
We have found that the 301 redirects created by umbraco on the edit site when editors make changes to the titles, are not migrated over to the live site by courier.
We are also using SEO checker to keep an eye on 404 errors and through this tool can create new 301 redirects - but don't really want to entertain this level of duplicate content admin.
Has anyone been in a similar situation an have an idea of how to automate the 301s created on edit to migrate to live?
Umbracos own 301 redirects are created automatically when necessary. If a node changes it's name (ie. by a Courier deploy), the redirect will be created.
If you rename a node on your staging environment, before it exists on your live environment, you don't need this redirect on live. Because the node has never had it's previous name on live.
Using Courier to push 301 redirects from staging to live
Hi First time post and a new person to Umbraco.
I hope you can help.
We have a two site setup of staging/edit and live - and we use courier (a third party extension) to take published content from the staging to the live site.
We have found that the 301 redirects created by umbraco on the edit site when editors make changes to the titles, are not migrated over to the live site by courier.
We are also using SEO checker to keep an eye on 404 errors and through this tool can create new 301 redirects - but don't really want to entertain this level of duplicate content admin.
Has anyone been in a similar situation an have an idea of how to automate the 301s created on edit to migrate to live?
Any help much appreciated
Jon
Hi Jon
Umbracos own 301 redirects are created automatically when necessary. If a node changes it's name (ie. by a Courier deploy), the redirect will be created.
If you rename a node on your staging environment, before it exists on your live environment, you don't need this redirect on live. Because the node has never had it's previous name on live.
is working on a reply...