| 10:41 am on Feb 6, 2009 (gmt 0)|
Verify that your redirect returns 301, and not 302. Use Live HTTP Headers for Firefox.
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.
| 12:03 pm on Feb 6, 2009 (gmt 0)|
wat is live http header, i have it installed but not able to understand its functions
| 12:16 pm on Feb 6, 2009 (gmt 0)|
*** everythings perfect ***
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.
| 12:27 pm on Feb 6, 2009 (gmt 0)|
As an example, I type in www.example.com/folder/index.html and my browser takes me to www.examplenewsite.com/newfolder/.
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.
| 12:49 pm on Feb 6, 2009 (gmt 0)|
ok verified...no chain........only 301 permanent redirect.........also i noticed one previous inner url i had typed in the browser with the previous domain name in it and the corrosponding page opened in the browser with the new domain........only this particular inner url has been indexed........this seems the way to go for quicker indexing
| 12:52 pm on Feb 6, 2009 (gmt 0)|
Google will pick up the new URLs quicker than they drop the old ones.
Don't worry about that. Both URLs will bring traffic for a while, until the old ones are dropped.
The redirect ensures the visitor can still access the content, rather than being fed a 404 and going elsewhere.
| 1:05 pm on Feb 6, 2009 (gmt 0)|
thanx g1smd for quickly sorting this out
| 10:46 pm on Feb 8, 2009 (gmt 0)|
More in: [webmasterworld.com...]
| 3:44 am on Feb 15, 2009 (gmt 0)|
now most of my pages are indexed at the new domain, now the problem is they have lost 95% of their rankings. Is this temperary or permanent? if temperary then how long will it take to get back the rankings. Also wanted to tell you that the old domain( the redirected one) hardly has any backlinks and the new domain (the one to which the old domain has been redirected to) has PR and many good backlinks.
| 10:05 am on Feb 15, 2009 (gmt 0)|
domains don't have PR, urls do.
| 2:06 pm on Feb 15, 2009 (gmt 0)|
" the url of the 10 year old domain domain.com having url [domain.com...] has a Page Rank of 2 "
--hope this makes things clear
| 4:23 pm on Feb 15, 2009 (gmt 0)|
You will see a temporary drop in the rankings, because Google has to do back-end processing in order to pass the old URLs' PageRank to the new URLs when it finds the 301 redirects. It can take anywhere from a few days to several months for everything to return to normal, depending on the PageRank of the original URL, and depending on how often your URLs are spidered.
Don't change anything about the redirect. If you do, then the "delay clock" starts all over again.
| 6:02 pm on Feb 15, 2009 (gmt 0)|
the page rank of the original url was 0 but it used to get spidered several times a day....... a PR 0 can pass any link equity?
| 7:04 pm on Feb 15, 2009 (gmt 0)|
I'd guess you are quoting the Google Toolbar PR value.
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.
| 1:13 am on Feb 16, 2009 (gmt 0)|
thanx Jim for the info and advise