Is this even possible? also www.mynewbook.com has page rank5 but without the www mynewbook.com has PR0 My portfolio site www.mysite.com and mysite.com both are PR6
Does it matter that the redirect is a 302 redirect?
To answer the immediate question, first, evidence suggests that the 302 will "eventually" merge your PR, though perhaps not as quickly or surely as would a 301. In my earlier post, I linked to a list of well known PR 10 sites
, most of which use a redirect to force all users to their www equivalent domain. Go to apple.com, for example, and you'll be redirect to www.apple.com. The return status on most of these redirects is a 302, not the expected 301, and yet virtually every one I've checked has merged PR/backlinks in Google's database.
The real question is whether G merged the PR and backlinks because it saw the 302 return code or because it eventually
recognized duplicate content in combination with a www subdomain? All of the PR 10 sites, after all, have been around a while. I strongly suspect that even without the 302 redirect, Google would merge the PR/backlinks. It just takes longer than it would with a 301.
So, the immediate answer is, "Give it more time." Your 302 should merge the PR/backlinks eventually. If you're in a hurry, changing it to a 301 would almost certainly reach the goal more quickly.
The not-so-immediate answer, however, isn't quite so clear-cut.
You indicate you have a redirect
from both mynewbook.com and www.mynewbook.com to me.com/subdirectory/? Remember, a redirect is not the same as an alias. What you're saying is that if I type mynewbook.com into my browser, I will be redirected to me.com/subdirectory and my location bar in the my URL will change
to me.com/subdirectory. If the location bar changes, it's a redirect. If the location bar doesn't change, if it stay at mynewbook.com, then it is an alias.
It's an important distinction, because if mynewbook.com and www.mynewbook.com are redirects returning a 302 status, they will potentially be dropped from the Google index when the algorithm eventually detects duplicate content on me.com/subdirectory. I doubt that's what you want to see?
Here's what I would suggest:
1. The contents of me.com/subdirectory have to be removed from Google's index, using a robot.txt in the root.
2. www. mynewbook.com should be configured as an alias to me.com/subdirectory and should return a 200 status code. This means if I type www.mynewbook.com into my browser, I will go to me.com/subdirectory, but my location bar will still indicate I'm at www.mynewbook.com.
3. mynewbook.com should be configured with a redirect to www.mynewbook.com and return a 301 status code. If I try to go to mynewbook.com directly, the URL in my location bar should immediately change to www.mynewbook.com. You can return a 302 status code instead, but the merger will take longer because G has to algorithmically detect the duplicate content.