Understanding 301 Redirects
Oct
10
Written by:
Friday, October 10, 2008 9:16 AM
I have done a guest blog entry at seablick.com about using 301 redirects to maintain search engine indexing when you change sites, urls or even website technologies.
Understanding 301 Redirects
Since writing this post, I've actually helped migrate a few more sites using 301 redirects with the Url Master product. These have included:
- Converting an old template based PHP site to a DNN install
- Migrating an older CMS to DNN
- Migrating a set of DNN Urls which were accidentally indexed for a test site to the live version
If you have decent PR for your site, then the process of eliminating old Urls and replacing them with new urls in the search indexes seems to take < 10 days or so.
2 comment(s) so far...
Using URL Master to set 301 direct from DNN site to external site
Hi,
I have a few child portals that I set up for our European office. They have now developed their own sites and would like me to have the old child portals redirect to their new sites (which are not developed in DNN). Is there a way I can use URL Master to accomplish this?
Thanks,
Dave
By Dave on
Saturday, September 04, 2010 1:44 AM
|
Re: Understanding 301 Redirects
@Dave - no, not with Url Master. You may be able to achieve this by setting up 'permanent redirect' Urls for each of the pages in the child portal. However, you may need to just implement a domain-level redirection. It also depends on whether the new sites are using the same domain names, or completely new domain names. To do the process properly each 'old' url will need to be mapped to a new Url, which will preserve the intention of the page - for example - about-us.aspx should go to an equivalent about-us page in the new site, if possible.
By Bruce Chapman on
Saturday, September 04, 2010 8:41 AM
|