Let me guess. You’re cruising around the internet looking for a place to host your multisite setup on WordPress, or maybe you’re just thinking of going down the multisite path but haven’t even gotten started yet. Have no fear, Pagely® is here.
For those of you who haven’t gotten started yet, here’s the scoop on what WordPress multisite is…
With the release of WordPress 3.0 back in 2010, what used to be called WordPress Multiuser (WPMU or WordPress MU) was renamed WordPress Multisite (WPMS or WordPress MS). The details are long and boring, and you can find them here. Anyways, just know that when you’re reading about multisite that there are a number of ways it can be referred to, and some are still using the old nomenclature. I personally think the rename made sense and that it’s more descriptive, but you know how people hate change.
Regardless of what you want to call it (i’ll use WPMS for purposes of this article), WordPress can be converted to multisite mode by changing a few lines of code. If you signup for a Professional plan with us here, we actually do this part for you, so you can just login and begin building your multisite network empire. Enough of the self-promotion, let’s get on with it.
Once in multisite mode, using the WP admin you can create “subsites” that reside within the one install of WPMS. Each can have its own domain name utilizing what’s called a “domain mapping” plugin. You can have as many of these subsites as you practically want, assuming you have the proper hosting resources to support them. If you’re going to be creating a ton of sites that serve a similar purpose and you’re okay with each one selecting from the same set of plugins/themes you designate, then multisite is a very efficient option both from a hosting resources standpoint (since many hosts cap the number of WP installs, and you’re technically only running one), as well as an admin management standpoint.
If you’re creating say 100 sites and each is totally unique, then you might be better off having a separate WP install for each which gives you more flexibility. With WPMS, you are creating what we’ll call a “pool” of X plugins and Y themes to use, and then the subsites get to pick and choose from that pool. If a subsite wants a plugin or theme that’s not available in the “pool” the master admin (you!) has setup, then they are SOL.
Examples where WPMS might make sense:
- Creating a network of informational sites that seek to generate revenue via AdSense.
- Creating sites for small businesses of a similar genre (think accountants) and charging them in a SaaS format.
- Creating a bunch of blogs for your university, with one for each university department.
Let’s say you build 100 subsites and are charging each accountant $20/mo. Assuming the sites are all fairly similar and get little traffic like most small business sites do, you’re bringing in $2000/mo in revenue and your hosting costs would be nowhere near that. If you had used a separate WordPress install for each client site, you’d be looking at multiple hosting plans, because you’d want to avoid most of the providers that allow “unlimited” installs and the ones that allow multiple installs per plan often have a cap on the # allowed.
In order to scale using WPMS, you have a couple options. Let’s say you’ve got a professional plan with us here at Pagely® and are hitting the upper limits of your bandwidth and storage. You can…
- A) Move to a VPS or dedicated server. If you run a plan with a dedicated database, then you can utilize “sharding” which basically means you use a special plugin to allow each subsite to have its own database which makes the overall network extremely scalable.
- B) Create a second multisite network on a separate hosting plan (this time say for attorney websites) and scale it up as well.
How scalable does WPMS utilizing “sharding” get? Here are a few examples…
- WordPress.com has tens of millions of subsites running, while serving an incredible amount of pageviews each day.
- Edublogs has 2+ million subsites currently running.
Finally, here are some links to other helpful articles about WPMS: