Forum Moderators: open
The company I work for has two domains, #*$!xx.co.uk and yyyyy.co.uk.
yyyyy.co.uk is 12 years old, had some great rankings, has some 3000+ links in etc and is made up of .htm and .asp pages
The company decided to re-design and re-write the website and this now resides on #*$!xx.co.uk
They are hosted on a Windows server with IIS.
What is the best way to redirect yyyyy.co.uk to #*$!xx.co.uk?
I also have a couple of questions ....
1. Does setting a whole domain redirect in IIS transfer a request from yyyyy.co.uk/example.htm to #*$!xx.co.uk or to #*$!xx.co.uk/example.htm (ie - does it just replace the domain but not the page)
2. Would it be better to set a 301 redirect in IIS on a page by page basis for all pages listed the search engines and then create custom error pages which are ASP 301 redirects to redirect for any other pages that are not listed in the search engines and then remove all the pages from the old site?
Any help greatly appreciated.
Jim
But if the structure, file names or content are going to change, then you'll need page by page (or folder to folder) 301s, including 301s from old to 'nearest equivalent', plus custom, user friendly 404 page to catch anyone who got missed, and provide useful site navigation for them.
And remove all the old pages.
[edited by: Quadrille at 12:46 am (utc) on Jan. 31, 2008]