301 Redirects

Hi.


I know that for SEO purposes if you re-launch a site with a new URL you should implement 301 redirects on as many pages as possible (preferably all) to make sure that the page rankings are passed on and the search engine traffic gets filtered through.



My question is whether the redirects that you can manually set up on the URL screen for each page asset are 301s and, if not, how these can implemented in the most efficient way possible in the CMS for a fairly large number of pages.



Many thanks.

[quote]Hi.


I know that for SEO purposes if you re-launch a site with a new URL you should implement 301 redirects on as many pages as possible (preferably all) to make sure that the page rankings are passed on and the search engine traffic gets filtered through.



My question is whether the redirects that you can manually set up on the URL screen for each page asset are 301s and, if not, how these can implemented in the most efficient way possible in the CMS for a fairly large number of pages.



Many thanks.[/quote]



If you want to be really efficient put the redirects in the apache config. But you will have to remember that the old URLs will not work in Matrix if you want to use them later - you will have to remove them from the apache config

Since 3.20, you can import large lists of remaps (301 redirects) from CSV in the Remap Manager (under System Management) and remaps can have query strings in the URLs. You can also set an expiry for individual remaps.


This is now much easier to manage than Apache configuration IMHO.

We've done this before, yes they are 301 and it works fine by using CSV files to change all old pages to the new ones. PM if you'd like to see one of our case studies.

This is just what I needed. Thanks all.


Alison