Website migration related SEO is new for me. I have a situation that where the ASP pages in a website are going to get covnerted to ASPX. I am not sure of the difference between this two close technologies.
So, once the pages are converted they will still reside in the same domain. But in a week, this converted pages will be migrated to an ASPX domain (a completely different domain)
This is what I am thinking of from the SEO point of view. Your suggestion on this will really help me a lot in the process. Thanks in advance.
Phase 1: ASP to ASPX (Same domain) SEO suggestion - Put a 302 redirect
Phase 2: Domain to Domain migration SEO suggestion - Remove the 302 and put a 301 redirect.
Is this the correct process?
My concerns are: 1. The current website has more than 2000 ASP pages that are indexed by Google. When I put the 302 redirect as per the Phase1, will that get any negative impact? 2. The time range between the 'content conversion' and 'domain migration' is 3 weeks. Will Google replace the ASP pages in its index with ASPX pages before the domain migration happens? In that case should I block those pages using Robots? And when I put a 301 redirect, will that again replace the ASPX pages with the new domain destination? Is that going to help me or do harm?
@Tedster Thanks for stopping by :-) The developers are converting the pages from ASP to ASPX. Once it's done, the domain along with the converted pages will be moved to a new domain; from abc.com to xyz.com.
Should I just wait till the domain migration happens and put only one redirect which is 301 in place? Then what about the pages that go through a conversion process? Should I stop them from getting live before the domain migration happens? And I failed to stop the new ASPX pages getting live, will using 302 redirect works?
And yes, I wish the developers a good luch with the IIS server :-)
Just to be sure when you say domain you do mean a different "domain name" and not just a different host?
It's domain abc.com to xyz.com and both the domains are residing in our own server.