Welcome to WebmasterWorld Guest from 18.104.22.168
Forum Moderators: goodroi
Check that the redirect works for both www and non-www at the old domain, and that both redirect you to www at the new domain.
Verify that the originally requested filepath is preserved in the redirect. That is, ensure that a "page" request at the old domain is NOT simply redirected to the root of the new domain.
Verify that non-www on the new domain redirects to www on the new domain, and preserves the originally requested path.
Check that for any starting point that is redirected, that the final target URL is reached in only one hop. That is, make sure that stuff like this does NOT happen:
exampleolddomain.com/somepage --> example.com/somepage --> www.example.com/somepage
Make sure that start to finish, the user sees just one redirect, and does NOT see a chain.
You cannot possibly know that just by looking at the page showing in your browser. You really do have to look at the HTTP response codes returned by the server.
The only way to do that is to use Live HTTP Headers for Firefox, or a similar product.
Open it in a new tab.
Go back to the original tab. Type in a URL and hit Enter.
Wait for the page to load.
Go to the Headers tab, and you will see the "conversation" between your browser and the server.
You need to look at the Status Codes returned for each request and verify they are all correct and what you want: 200, 301, 404, etc.
In particular, a chain, or a 302, is usually bad news. Likewise 500 and unexpected 4xx or 5xx errors will need to be investigated.
Everything is perfect, no?
Now I look at Live HTTP Headers and see:
Response: www.example.com/folder/index.html -- 302 -->
example.com/folder -- 301 -->
example.com/folder/ -- 302 -->
www.example.com/folder/ -- 302 -->
examplenewsite.com/newfolder -- 301 -->
examplenewsite.com/newfolder/ -- 302 -->
www.examplenewsite.com/newfolder/ --> 200 OK.
That's an Extremely Mis-Configured Server, and the "Redirection Chain From Hell".
You would want to know about that. Right Away. If Not Sooner.
Don't change anything about the redirect. If you do, then the "delay clock" starts all over again.
Be aware that actual PageRank is a logarithmic, not linear value, and that it likely includes many, many decimal places -- unlike the linear, single-digit PR shown on the toolbar. Also, that toolbar PR (TBPR) is not updated very often (perhaps four times per year), whereas actual PR is re-calculated constantly.
Therefore, is quite doubtful that your actual page PR is 0.000000000000, and so yes, it will pass *some* PR.
While you are waiting for Google to recognize your 301 redirects, it sounds like spending some time seeking on-topic, relevant links from related-subject sites would be a very good investment of your time.