Questions About Multisite Conversions
-
We are working with a company in which we have 31 separate WP installations on our servers. We use Liquid Web.
The WP maintenance is getting to be cumbersome, (we’re spending more time maintaining than marketing). We’re at a point now where we are looking at how we’re going to scale this to grow our company, so we are looking at converting to a multisite environment.
All of the sites use the same themes based on the plan they purchased. For example, Plan A gets 3 themes, Plan B gets all the themes in Plan A + 3 more, Plan C gets all the themes in Plan B + 3 more.
We use the same plugins for each installation, except Plan C gets a shopping cart.
I think multisite is something we can do (and must do), but I haven’t been able to find answers for a few things, so I’m really hoping somewhere here can help.
My main questions are these:
1. We created individual Google Webmaster Tools accounts and Google Analytics accounts for each site. How does multisite affect this regarding the Google verification for each site in a network?
2. Each site uses the client’s own domain name with DNS pointed to our server, so we’ll definitely need to use domain mapping in multisite. How does the existing DNS setup get effected (or does it?) if we move to a multi-site environment?
3. Should be use subdomains or subdirectories?
4. Are we going to mess up the existing permalink structure and SEO for each site in a multi-site environment with domain mapping?
5. In multisite, how does Robots.txt work for each site in the network?
6. Does each site in the network create its own RSS feed?
7. What about mobile? Right now, we’re using Jetpack on each site with the Jetpack mobile plugin activated.
We have white-labeled and branded their existing WP login (with our company logo), so if we convert to multi-site, it has to be totally seamless for them.
Thanks in advance!!!
The topic ‘Questions About Multisite Conversions’ is closed to new replies.