|Problem with 301 redirections|
I have a little problem with my website
We will call my main domain : (maindomain.net)
For this domain I have made a 301 redirection from an old domain name that I own (that we will call 301domain.net)
My problem is that my current domain name (maindomain.net) is not ranked anymore in google for some of my keywords since yesterday and in the GWT I received yesterday a manual action message for "uninformative content"
And the weird thing is that my domain used at the start for the 301 redir (301domain.net) is ranked for almost all my keywords on google instead of my main domain (maindomain.net)
The problem has started after the expiration of 301domain.net (that is now active). <--- I don't know if it's linked
What can I do ?
Invert the redirection ?
Make a URL change in GWT ?
Thanks in advance
How can you, if the old domain has expired?
My 301domain.net isn't expired anymore, I have renew it
yes Inversion is a best option.
|yes Inversion is a best option. |
Do not invert redirection.
You need to analyse what is wrong and then decide the course of action, otherwise you can create more mess.
- How old are each of your domains?
- How long did you own each of them?
- How long was 301domain.net ranking before you implemented redirect?
- Why did you redirect? Are you moving domains or some other reason?
- If some other reason, why? And how closely is the content related? Are you redirecting page to page or everything to a home page?
- Have you ever had the redirect other way around?
- Also - the manual action is because of content not being good enough. If your maindomain.net got this penalty, but not your 301domain.net, then I presume the content is quite different. Can you put 301domain.net content on your maindomain.net or improve the maindomain.net content?
In fact :
301domain.net has no content, I only use it to redirect to my maindomain.net
301domain.net is my old main domain, but when I created maindomaint.net, 301domain.net wasn't indexed anymore on google.
Expires OnMay 23, 2014
Registered OnMay 23, 2013
Updated OnMarch 11, 2014
Expires OnJanuary 27, 2015
Registered OnJanuary 27, 2014
Updated OnFebruary 27, 2014
I have been the only one owner since they exist
|The problem has started after the expiration of 301domain.net (that is now active). <--- I don't know if it's linked |
Expires OnMay 23, 2014
From the information you have posted, it is very difficult to follow the problem you describe. The domain has not ever expired, so how could your problem start after it expired?
When you visit your old domain that is empty except for a redirect to the new domain, what do you see as server response? If you type or paste in an old URL from your old domain, what happens? What is the server response? If you are not familiar with viewing headers to see server response, there are some Free Tools here at WWF, a link is at the top of the page near the logo, to help you do that.
Just trying to help you get some help. Not sure what means in regards to your post.
Sorry, in Fact the domain name never expired, it's just the Hosting that have been expired (I have to renew it every month)
When I at the URL of my old domain name, it redirects to my new one (the 301 redirection works)
The thing that I'm unable to explain is, why my old domain instead of my new one since this week end...
The reason I asked if you could check the headers for the server response is because although it is redirecting, it would make a difference if it were not redirecting with a proper 301 response.
The default redirect is a 302 (Temporary) so if you aren't sure that it does return a 301 response, you need to look there to solve your problem.
|the domain name never expired, it's just the Hosting that have been expired (I have to renew it every month) |
Urk. Does that mean there was a period when the redirect wasn't taking place? Redirects have to originate at the originally requested site. If the host locks you out, that would mean that any requests-- including from the googlebot-- got some type of error instead of the 301.
Still can't escape the nagging feeling that the actual message was itself a mistake of some kind. Or am I thinking of the other thread?