In this post, you will learn how to set up a word press site in a separate subdomain instead of using multiple sites. Note: this document uses the wpmu dev hosting function and is aimed at wpmu dev members. If you are not a member, please consider joining the risk-free trial. Web proxy (for example: https:\/\/webagency.site ）, we assume that you want to strictly use the main website for promotional or marketing purposes, but you want to run a completely independent word press installation in a sub domain of the same brand. Your primary site (that is, using the same domain). The
For example: https:\/\/lms.webagency.site Learning management system (LMS) part of, e-commerce store (e.g.: https:\/\/store.webagency.site ）, https:\/\/event.webagency.site Activities and ticket sales in https:\/\/event.webagency.site Or, simply show the customer the pre release site that is being built as part of the white label service (for example: https:\/\/client1.webagency.site ） To do this, you usually need to set up the WordPress multi site installation, refer to the sub domain (not the sub directory) in the setting, and then add the new WordPress site to the multi site network. The
However, what should I do if I set up and run a completely independent word press site in a sub domain without going through a multi site environment? As this article shows, you can easily accomplish this task by creating additional wpmu dev hosting sites. This guide includes: Advantages and disadvantages of installing WordPress in a sub domain without multiple sites install and set up WordPress sub domain sites outside the primary site. Under the advantages and disadvantages of installing WordPress in a sub domain without multiple sites, set up and maintain a single sub domain using more detailed instructions. Let’s start with the benefits of timing. The
This is easier than installing, setting up, and maintaining an entire multi site installation. Use hubs effectively, just like a network site with a multi site setup. You can set up, develop, and start a word press subdomain site without affecting the original primary site. There is no need to change the default managed package size, just create a new managed package. In addition, since the site is hosted on a separate server account, the hosting can be modified without touching the hosting of the primary site (for example, charging an upgrade or downgrade). All plug-ins associated with sub domain sites (such as LMS, events, and \/ or woocommerce, etc.) will be maintained separately from the primary site to reduce the burden on the server. If the primary site must be more static (that is, only the company information page) and the sub domain site must be dynamic (for example, e-commerce site), hosting two sites in a separate account can keep the primary site relatively stable. For plug-in updates, this may also affect the caching of static and dynamic sites (i.e., experiencing longer \/ better caching at the primary site). Since only the required are installed at each site, there is little chance that the plug-in will crash. Only HTTP authentication can be used for password protection. If there is a server problem, there is little chance that both sites will fail at the same time. You can perform separate backups for each site. Every server can use dumps, so it’s much easier to adjust. Now, let’s take a look at this, and let’s look at some of the disadvantages of installing WordPress in a subdomain instead of using multiple sites. The
Theme changes do not automatically remain \
This site only synchronizes the theme version. (Note: most themes allow you to manually import \/ export settings. For example, a site built with elementor allows you to export site kit, which can contain theme settings for the entire site.) You must maintain the plug-ins corresponding to the two sites (but the center allows you to update multiple sites at the same time and use the auto service to update automatically, so it is easy.) Multisite allows you to synchronize all site settings (in other words, it’s easy to use a central configuration). There may be some additional costs compared to setting up a site in a single multi site installation, depending on the required packages and components. For example, some themes and plug-ins may require two licenses. \
The configuration shown below only works when both sites are hosted by wpmu Dev and the DNS manager of the hub manages DNS for the top-level domain, as described in the how to install and set up WordPress subdomains guide. Let’s look at the steps. First, add the new site to the hub. Note: primary site replication can be a good starting point for creating child domain sites. Therefore, this guide will replicate and start the default site. Copy the default site and add a new sub domain site. If you are not creating a new site from scratch, select the site you want to copy. The
Male select the default site as the replication source. Then select the hosting plan for the new site. After selecting a schedule, you will be prompted to create a temporary URL for the new site. When you are finished, click continue. Male enter the temporary URL of the subdomain site. Select the server location for the new site, and then click the button. The new site will be created in a few minutes. Create a new website in a few minutes. Now that the site has been created, let’s set up a subdomain. In this case, store. Webagency Set up a separate WordPress site under the site sub domain. The
The core of this operation is to add the a record of the child domain to the DNS record of the primary site. This guide section details how to use a subdomain and how to use a subdomain as the default domain. The following is a summary of the steps: First, navigate to the hub, select the managed part of the site where you want to add a subdomain, click the domain and copy the IP address of the site. Male select the IP address of the sub domain site. Then, add the new DNS record to the DNS section of the default domain. Enter the following information and click the Add button: The
Recording type – select \
