WordPress multisite installations are supported on our Pro and higher plans. Because multisite networks tend to need more resources and require additional support, they are not supported on our Starter plan. If you’re currently on our Starter plan and want to enable multisite, you’ll need to upgrade your plan to a Pro plan or higher.

We recommend working with an experienced developer if you wish to switch an established site from a single site to a multisite network or if you’re just getting started with multisite.

Subdirectory vs Subdomain

We support both subdirectory and subdomain setups.

Important Notes

  • If you change from a subdomain to a subdirectory multisite, open a chat with our Support team to let them know so they can add an Nginx rule for it to work properly.
  • If you need to test a subdomain multisite on the temporary URL, you can only use HTTP, and you cannot force HTTPS. The SSL certificate provided for kinsta.cloud domains (e.g. sitename.kinsta.cloud) can only cover the first level of subdomains (e.g. sitename.kinsta.cloud), so any additional subdomain level (e.g. subsite.sitename.kinsta.cloud) cannot be covered.
  • Alternatively, if you need to test the multisite over HTTPS without pointing the network’s primary domain, you’ll need to add a different custom domain with a wildcard SSL certificate to use for testing.

Wildcard Subdomain

When you add a root/apex domain (domain.com) to a site in MyKinsta, an additional wildcard subdomain (*.domain.com) is automatically added (unless you deselect the wildcard option under Advanced Options). If you’re running a subdomain multisite, you can point that wildcard subdomain to your Kinsta site the same way you point your root/apex domain, so you don’t have to add each subdomain individually in MyKinsta.