Are you a Google Analytics enthusiast?
More SEO Content
Multiple Domains And Redirect 301
Posted 20 March 2005 - 04:12 PM
First I have to apologize for my long story but it's necessary for understanding the situation.
I have a few domains for my website. One of them is newer and should be the leading one. Unfortunately, when searching my site in Goggle, I receive one of the old domains as the leading one.
In order to let Google understand who is the leading domain we made a 301 permanent redirect from each of the old domains to the new one.
I tried to do it according to Microsoft instructions (I use IIS 5) but it seems that I did something wrong.
I did the next steps:
1. For each old domain I created a different website entry on my IIS (one for www.domainname.com and one for domainname.com)
2. For each of them, on the Home directory section i selected the option “a redirection to url” and than redirect the urls to [http://www.newdomain.com$V$Q]
3. Besides, on the section of “the client will be sent to” I selected the options:
3.1. The exact url entered above
3.2. A permanent redirection for this resource.
That’s what I did for each one of our old domains, but as mentioned above, it seems we made something wrong and our results in Google were tremendously deteriorated since I did it.
Could you please tell me what I did wrong?
Posted 20 March 2005 - 04:34 PM
Your deteriorating results in Google doesn't mean you did anything wrong. It would be expected that you'd have a few months before the engines gave you credit for this.
The thing to check is that when you do a server header check on your redirected domains, that it is indeed delivering a 301 on the domains that it should. If it is, and if those sites do redirect when you type them into your browser, then it sounds like you're done what you're supposed to do.
Posted 20 March 2005 - 04:40 PM
a/ you only need 2 virtual sites set up. One has a host header for the primary domain, the other has all the host headers for the others set up on it. This is the one you redirect.
b/ using the code in this thread it can be done with just one virtual host.
c/ Because you redirected to a brand new domain you will now be subject to the Google "aging delay" See here and here
Posted 25 March 2005 - 05:06 AM
Google is already recognized the 301 redirect I did and actually in its search results I find the new domain (previously I found there mainly old domains).
But, the strange (and very bad) thing is that when I search in Google for my new domain http://mynewdomain.com I got in the result a version of my homepage from september 2004 !!!
At the same time, for http://www.mynewdomain.com I get the updated version.
Thats makes me crazy !!!
This is a version with old and not well optimized content and I think that the deterioration in my rankings are due to that.
Does someone know how can I remove that old version from google cache?
Posted 25 March 2005 - 11:05 AM
Normally not having that doesn't hurt your rankings much though. Unless you have an equal quantity/quality of sites linking to each.
Posted 27 March 2005 - 04:40 PM
is exactly what I did from the beginning but it doesen't help and I already change it back to redirect 302 between the non-www version of the main domain to the www version.
Besides, I found that http://www.mynewdomain.com is also a CNAME of http://mynewdomain.com. Is it possible that this CNAME is the reeason to my problems?
Posted 27 March 2005 - 06:23 PM
Yes because it is a Canonical Name (CNAME) (Alias) it will cause duplicate issues until the SEs sort it out one way or another or you force the issue with a redirect.
Posted 27 March 2005 - 08:32 PM
As Chris said, you need to leave the 301 in place. It takes the engines some time to pick it up and do what you want them to.
Posted 04 April 2005 - 03:53 PM
Now, not just when I type in Google http://mynewdomain.com I got in the result a version of my homepage from september 2004 but also when I type http://www.mynewdomain.com I got that old version!!!
Furthermore, the Google's cache for both url's now contains
"Your search did not match any documents" !!!
Last week, I added a link from http://www.mynewdomain.com to http://mynewdomain.com. I thougt maybe it will help Google to find the new version for http://mynewdomain.com.
Coul'd it be the reason for that catastrophic ?
Coul'd it be that Google for some reasons stoppped like my website after I did the 301 redirect?
Posted 05 April 2005 - 10:02 AM
Are you truly searching Google for your domain including the "http://" part? If so it's not going to show you much. Just the main home page if you're lucky.
To do a site search to see how many pages of your site has been indexed use site:www.yourdomain.com and site:yourdomain.com[/b]. The count on that should give you an idea of how many pages are indexed both ways.
As far as the Cached date goes, that happens all the time. Could it point to a possible problem? Yes, but it's rare.
Head over to Delories Header Viewer and type in both the www and non-www address of your domain. Done correctly, one should return a 200 OK response and the other should return a 301 Moved Permanently response.
Posted 07 April 2005 - 07:15 AM
Maybe I wasn't clear enough. I searched just for my homepage and I found that Goggle indexed it with that old version.
Today, I found something interesting.
I searched for site:www.oneoftheolddomains.com (one of those I permanently redirected to www.mynewdomain.com) and find that Goggle still cached some pages of it. One of the pages was www.oneoftheolddomains.com/index.asp with that old version Goggle cached of http://mynewdomain.com. The point is that there is no http://mynewdomain.com/index.asp or http://www.mynewdomain.com/index.asp in Google.
Could it be that Goggle, after the redirect, take the content of www.oneoftheolddomains.com/index.asp and keep it also for http://mynewdomain.com and www.mynewdomain.com ?
Could it be a good idea, besides the IIS definitions of redirect 301, to add the 301 redirect line codes to these pages in www.oneoftheolddomains.com who are still indexed in google?
I have another 2 questions (hope you are still patient):
1. regards to deliria.com: I got there TAP/1.1 301 Error. Is it since I use iis5? Could it be for another reason?
2. The redirect I did was to http://www.newdomain.com$V$Q.
Could the '$VA$HQ' be a problem?
Thanks a lot,
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users