It’s important that you get it right the first time.<\/p>\n
In this post, I’ll\u00a0help you with that, by explaining the differences between WordPress Multisite subdomain and subdirectory installation. I’ll also look at some scenarios in which you might need\u00a0Multisite, and identify which of subdomains and subdirectories might be better for each. I’ll also identify those scenarios where you have no choice.<\/p>\n
So let’s start!<\/p>\n
- \n
- Subdomain vs. Subdirectory \u2013 What\u2019s the Difference?<\/a><\/li>\n
- New vs. Established WordPress Installations<\/a><\/li>\n
- Personal Networks vs. Public Ones<\/a><\/li>\n
- Domain Redirection<\/a><\/li>\n
- Hosting Challenges with WordPress Multisite Subdomain<\/a><\/li>\n
- Networks Stored in a Subdirectory<\/a><\/li>\n
- Local vs. Remote Networks<\/a><\/li>\n
- Your Site, Your Choice<\/a><\/li>\n
- Choosing Between Subdomains and Subdirectories Needn\u2019t Be Difficult<\/a><\/li>\n<\/ul>\n
Subdomain vs. Subdirectory\u00a0\u2013\u00a0What’s the Difference?<\/h2>\n
WordPress Subdomains and Subdirectories relate to the structure of the URLs used for each of the sites in your Multisite network. They don’t correspond to where your server stores\u00a0the sites, but to the way WordPress creates URLs for them.<\/p>\n
![\"wordpress](\"https:\/\/wpmudev.com\/blog\/wp-content\/uploads\/2017\/07\/site-on-subdirectory.png\")
This demo site on my personal network uses a subdirectory structure.<\/figcaption><\/figure>\n Let’s say you’ve got a network called mynetwork.com<\/em>. If you set it up to run on subdomains, a site called myblog<\/em> will have an address of myblog.mynetwork.com<\/em>. But if you set it up to run on subdirectories, then that blog’s URL will be mynetwork.com\/myblog<\/em>.<\/p>\n
A page called ‘About Me’ on your myblog<\/em> site will have a URL of myblog.mynetwork.com\/about-me<\/em> on subdomains, while on subdirectories it will be mynetwork.com\/myblog\/about-me<\/em>.<\/p>\n
It uses the same structure for every single site in your network\u00a0\u2013\u00a0you can’t pick and mix. So once you’ve chosen, they’ll all be the same.<\/p>\n
Which you choose will depend on a few things:<\/p>\n
- \n
- Whether your network is on a new WordPress installation or an established one.<\/li>\n
- Whether your network is for your personal sites, or sites you will let other people set up or buy.<\/li>\n
- Whether you’re using domain redirection.<\/li>\n
- Your hosting\u00a0\u2013\u00a0can you set up subdomains?<\/li>\n
- Your site’s location\u00a0\u2013\u00a0on a local or remote server, or in a subdirectory.<\/li>\n
- And finally, it will depend in part on your preference.<\/li>\n<\/ul>\n
Let’s look at each of these scenarios.<\/p>\n
New vs. Established WordPress Installations<\/h2>\n
If you’re activating Multisite on a new WordPress installation, then it’s up to you to decide between subdomains and subdirectories. But if you have an\u00a0established site, you must\u00a0force\u00a0the use subdomains. So, if your site is over a month old, you’ll have no choice.<\/p>\n
This is because there could be a clash between the subdirectory addresses for sites created on your new network, and content you’ve already added to the site. Imagine you’ve created a site at mygreatsite.com<\/em> and added a page called “WordPress is Awesome,” with the URL mygreatsite.com\/wordpress-is-awesome<\/em>. You then create a Multisite network and let users set up their own sites on subdirectories. Someone comes along and creates a site called “WordPress is Awesome,” which would have a URL of\u00a0mygreatsite.com\/wordpress-is-awesome<\/em> (forget about any copyright issues for now). You can see how this would be a problem.<\/p>\n
So instead, you’re forced to use subdomains, and the new site singing WordPress’s praises would be at wordpress-is-awesome.mygreatsite.com<\/em>. No clash now.<\/p>\n
Once you’ve finished activating Multisite though, you can switch between subdomain and subdirectory installations<\/a>.<\/p>\n
Personal Networks vs. Public Ones<\/h2>\n
I run three Multisite networks. Two of them are for client sites and one is for personal use. One of them runs on subdomains, which is the one that allows clients to create their own sites. Two run on subdirectories\u00a0\u2013\u00a0one that uses domain redirection (more of which shortly) and the other that’s my personal site.<\/p>\n
The reason I use subdomains for sites created by clients and subdirectories for my sites is twofold. First, subdomains give a more professional feel to the service I offer my clients. Most of them use domain redirection to redirect to my IP address, but I know that if they don’t, they’ll have a domain name that starts with their brand, not mine. Second, subdirectories are easier to work with, so that’s what I use for my site where it’s less of an issue.<\/p>\n
![\"Edublogs](\"https:\/\/wpmudev.com\/blog\/wp-content\/uploads\/2017\/07\/site-on-subdomain.png\")
Edublogs makes it possible for users to create their own sites, so it uses subdomains<\/figcaption><\/figure>\n Using subdirectories means you don’t have to worry about creating new domains or allowing wildcard domains via your hosting provider, and it just makes things simpler. For me, it also means that the sites in my personal network have URls that mirror the URL in\u00a0their opposite numbers on my local copy of the network. Again, more on that later.<\/p>\n
Domain Redirection<\/h2>\n
If all the sites on your network use our invaluable\u00a0Domain Mapping<\/a>\u00a0guide\u00a0to\u00a0redirect their own unique domains to each site, then as far as your visitors go, it doesn’t matter if you use subdomains or subdirectories. This is because no one\u00a0will ever see the “real”\u00a0URL for the sites in your network.<\/p>\n
![\"An](\"https:\/\/wpmudev.com\/blog\/wp-content\/uploads\/2015\/09\/A-WordPress-Multisite-Network.png\")
<\/p>\nSo if you’re creating a network (like one of mine) with sites that will all have domains redirected to them, then use whichever of subdomains or subdirectories you prefer – or whichever you’re forced to if that’s the case.<\/p>\n
Personally, I use subdirectories on my network with redirected domains,\u00a0I already outlined.<\/p>\n
Hosting Challenges with WordPress Multisite Subdomain<\/h2>\n
Some hosting providers will make it difficult for you to work with subdomains.<\/p>\n
They might charge you extra to set up subdomains on your account, they might not give you access to cPanel where you can set up your own subdomains, or they might not allow wildcard subdomain creation.<\/p>\n
A wildcard subdomain is when you create a subdomain called *\/mynetwork.com<\/em>, instead of setting up each subdomain individually. If you’re using subdomains and offering site creation to your users, then you’ll need a wildcard subdomain.<\/p>\n
![\"cPanel](\"https:\/\/wpmudev.com\/blog\/wp-content\/uploads\/2017\/07\/CPanel-domain-editing.png\")
If you want to use subdomains, you must\u00a0be able to\u00a0edit them in cPanel or a similar system.<\/figcaption><\/figure>\n So if you want to use subdomains, then check first that your hosting provider allows it. If they don’t, you’ll either have to use subdirectories – or switch to a better hosting provider (hint: WPMU DEV Hosting<\/a> supports wildcard subdomains and all of our premium plugins are Multisite compatible too).<\/p>\n
Networks Stored in a Subdirectory<\/h2>\n
Most Multisite networks are installed in the root directory of your site. This means that if you’ve bought a hosting plan using mygreatsite.com<\/em>, then that will be the URL for your base site on the network.<\/p>\n
But if you’ve installed WordPress Multisite in a subdirectory, then you can’t\u00a0use subdomains. So, if you already have a single site installation at\u00a0mygreatsite.com<\/em>,\u00a0and you add another WordPress installation in a subdirectory running Multisite, then its address will be\u00a0mygreatsite.com\/mynetwork<\/em>.<\/p>\n
If this is the case, you MUST use subdirectories, meaning that a site you create on your new network will be at\u00a0mygreatsite.com\/mynetwork\/my-new-site<\/em>. Creating a subdirectory would be impossible here, as it would have to be at an address like mygreatsite.com\/my-new-site.mynetwork<\/em>. Which just doesn’t work.<\/p>\n
Local vs. Remote Networks<\/h2>\n
If you’re setting up a local Multisite network on your machine, as in the above example, you MUST use subdirectories. This is because a local installation of WordPress will always be in a subdirectory itself – it will never be in the root directory of your machine.<\/p>\n
This is one reason I prefer to use subdirectories remotely. It means that my URLs are as consistent as possible between local and remote versions of my networks, making things easier if I have to migrate the database.<\/p>\n
Your Site, Your Choice<\/h2>\n
I’ve already stated my preference, which is for subdirectories. But that’s not to say there aren’t times when I use subdomains. Networks that allow users to create their own sites will always appear more professional with a subdomain structure. It’s what we use at Edublogs<\/a>.<\/p>\n
![\"edublogs](\"https:\/\/wpmudev.com\/blog\/wp-content\/uploads\/2017\/07\/edublogs.png\")
At Edublogs we use subdomains as it’s better for users<\/figcaption><\/figure>\n If your network doesn’t have any restrictions on it, and you’re not forced to use one or other of the two options, then you can go with your preference. But if you will\u00a0host client sites on your network, it also makes sense to consider what their preferences might be, too.<\/p>\n
- New vs. Established WordPress Installations<\/a><\/li>\n