The process for adding a site to the Multisite network varies depending on the type of Multisite.
Adding a new subsite to a non-wildcard ssl subdomain multisite network is a two step process (three steps if you want to enable SSL but we’ll cover that in a separate document).
This sets up the NGINX server to recognize the new subsite.
Now you just need to add the site to WordPress itself (if you haven’t already done so). Once that is complete the site has been added and is ready for use. And you can proceed to provisioning an SSL certificate for it if you so desire (see the next document for how to do this).
All you need to do is setup the site inside WordPress using the normal Add Site screen. If you have a wildcard DNS entry ( “*” ) configured at Cloudflare then all requests for a subdomain will be routed to your Multisite automatically.
There are no special steps here – just setup the site inside WordPress using the normal Add Site screen.
Keep in mind that you cannot use mapped domains with Multisites based on subdirectories.
If you are using something like WPUltimo, you can set up mapped top-level domains that route to an existing subdomain. That is, you can setup a domain such as myexternaldomain.com to route to subsite01.mymultisitedomain.com. The user will just see myexternaldomain.com in their browser – they will not know (nor do they need to know) that they are being routed to a subsite on a Multisite network.
To set this up, the process is similar to that for a new subsite under a Non-wildcard Subdomain Multisite:
This sets up the NGINX server to recognize the new mapped domain and route it to the WordPress mapping handler (usually WPUltimo).