Welcome to the Q&A Forum

The majority of the configuration needs to happen on the server hosting the main website, Alex. Because essentailly, the visitor isn't even going to be aware of the existence of/URL for the other infrastructure. They're going to go to example.com/blog, and example.com's server configuration is going to deliver them the content from someotherserver.com which hosts the WordPress install. In addition to the proxy configurations, you may need to deal with cookies, SSL configurations and potentially other server header information that needs to be maintained between the requests passing back and forth between the different servers as well. This is a pretty common requirement in enterprise configurations though - to keep the software running the blog from potentially interfering with or compromising the security of the main site infrastructure. So like I said - eminently do-able, but not trivial to implement. Does that answer your question? Paul

Thanks Jeff! Your response was very helpful. It is true that the old domain contained a competitive keyterm which was lost in the migration. The competition is also higher for that space so this explains why we took a hit in PageRank. I will be working on regaining that competitive edge in the coming months. Thanks again! Sheena