Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsYes. You can run separate WordPress installations at paths such as https://example.com/site1 and https://example.com/site2 on the same domain and server. Each installation needs its own WordPress files, wp-config.php, database connection and correctly scoped rewrite rules.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
WordPress Multisite can also create sites at those paths, but its subdirectory mode is a different architecture: one WordPress core and database serve virtual sites. It does not put an independent WordPress codebase inside every URL folder.
As an Amazon Associate I earn from qualifying purchases.
What “multiple WordPress installs in subfolders” can mean
There are two ways to get URLs such as /site1 and /site2. The first uses genuinely separate installations. The second uses one Multisite network configured for subdirectories. The URLs may look identical to visitors, but the files, databases, administration and upgrade responsibilities are different.
Separate installations in physical directories
With independent installs, the server has a directory for each site—for example, one containing the files for /site1 and another containing the files for /site2. Every copy has its own wp-config.php and can use a separate database. You may also place both sites in one database if every installation uses a unique table prefix.
#1 Best Overall
This model gives each site its own core version, plugins, themes, settings and upgrade schedule. It is the closest match to “two WordPress installations on one domain.”
Multisite subdirectory mode
A Multisite network uses one WordPress core and one database. In subdirectory mode, the network creates path-based sites such as https://example.com/subsite, but those paths are virtual. WordPress states that “a sub-directory install creates a path-based network, even though it does not use file system directories.”
Network sites have separate database tables and upload paths within the shared installation. You do not upload a complete second WordPress copy into a physical subsite folder.
Architecture comparison
| Option | Files and database | URL pattern | Best fit | Main caution |
|---|---|---|---|---|
| Separate installs in physical subfolders | Independent code directories; separate databases or one shared database with unique table prefixes | /site1, /site2 |
Strong isolation, independent upgrades and different plugin stacks | More updates, backups and administration |
| Multisite subdirectory network | One core and database; sites use separate database tables and upload paths | /site1, /site2 |
Centralized administration and shared infrastructure | Plugin compatibility, network-wide theme management and migration complexity |
| Multisite subdomain network | One core and database; DNS and server mapping are required | site1.example.com, site2.example.com |
Sites that need domain-based identity | Wildcard DNS/server setup and root-of-webfolder requirements |
How to install independent WordPress sites in subfolders
Use this approach when the sites must be upgraded, secured or customized independently—for example, when one gaming project needs plugins or themes that should never affect another.
1. Choose the paths and database arrangement
Decide the physical directories first, such as /site1 and /site2. Then choose either a separate database for each installation or one shared database with a different table prefix for every site.
- Separate databases: provide the clearest data boundary and make it easier to move one site without sorting its tables from another site’s tables.
- One database with unique prefixes: is supported, but every installation must use a distinct
$table_prefix. Reusing a prefix can make one install read or alter another install’s tables.
Regardless of the database choice, each installation needs its own database credentials in its own wp-config.php.
Rank #2
2. Create each directory and upload WordPress
Create the directory that corresponds to each public path and place a complete WordPress file set in it. The files for /site1 must not be mixed with those for /site2. A directory layout might look like this:
document-root/site1/ (first WordPress installation)
document-root/site2/ (second WordPress installation)The important point is that the web server can map each URL prefix to the intended files before a catch-all rule from the root installation handles the request.
3. Configure each wp-config.php
Open the configuration file in each directory and enter the database name, user, password and server details for that installation. If the databases are shared, set a unique $table_prefix in every file. Do not copy a working configuration unchanged if it would cause both sites to use the same prefix.
Keep the configuration files associated with their own directories. A mistake here can produce a site that appears to load correctly while reading the other site’s content or settings.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match4. Run the installer separately
Visit the first subfolder URL and complete the WordPress installer, then repeat the process at the second URL. Each installer writes its own site options and administrator account to the database selected in that directory’s configuration.
After installation, test the front end and the dashboard for both paths. Confirm that links, media uploads and administrative URLs retain the correct prefix instead of jumping to the root site or the other subfolder.
5. Configure rewrites at the correct level
Pretty URLs depend on rewrite rules. Apache needs appropriate .htaccess rules in the relevant locations; other web servers need equivalent configuration. The parent server configuration must not send every unknown path to the root installation before the child directory’s rules are evaluated.
This ordering is a common reason that /site1 displays the main site’s homepage or redirects to the root. Check the document-root mapping and make sure the child installation’s existing-file and front-controller rules are being used for requests under that prefix.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Why rewrite rules decide whether subfolder URLs work
WordPress normally receives many requests through a front controller rather than a physical file with the same name. The web server therefore has to distinguish requests for existing files and directories from requests that should be passed to WordPress.
For an Apache installation, the appropriate rules must be present in .htaccess. The official Multisite example includes handling for /wp-admin, existing files and directories, WordPress PHP paths and the final front-controller rewrite. Independent installations require the same principle, scoped to their own directory.
On another server platform, use that platform’s equivalent rewrite configuration. The exact syntax changes, but the requirement does not: requests for /site1 must reach the first install, requests for /site2 must reach the second, and neither child path should be swallowed by the root site’s fallback rule.
Symptoms of a routing conflict
/site1shows the root site’s homepage.- A child site’s dashboard URL redirects to the main site’s dashboard.
- Permalinks work on the homepage but fail on posts or pages.
- One installation’s media or login links point to the other path.
When these symptoms appear, inspect the parent and child rewrite configuration before changing WordPress content. Confirm that the child directory exists where the server expects it, that its configuration file points to the intended database, and that the parent catch-all rule is not evaluated first.
Rank #4
Setting up a Multisite network with subdirectory URLs
Choose Multisite when one administrative team benefits from managing a shared WordPress core and shared infrastructure. It is not a way to obtain completely independent codebases.
Prerequisites and the one-month limitation
Before enabling a network, back up the database, wp-config.php and .htaccess. Confirm that the existing installation uses pretty permalinks.
WordPress documents a specific restriction for subdirectory networks: “You cannot choose Sub-directory Install (for a path-based network) if your existing WordPress installation has been set up for more than a month, due to issues with existing permalinks.” In practice, an installation older than one month may not offer the subdirectory choice. This is a Multisite conversion constraint, not a restriction on creating separate physical installations.
The main site in a subdirectory network normally uses a /blog/ post path. Account for that path when planning page slugs and links so that network URLs do not collide with the main site’s content.
1. Enable the network feature
In the existing installation’s wp-config.php, enable WP_ALLOW_MULTISITE. Keep a backup of the file before editing it so you can restore the previous configuration if the network setup is interrupted.
2. Open Network Setup
Sign in to the WordPress dashboard and open the Network Setup screen. Confirm that pretty permalinks are active, select the subdirectory option when it is available, and provide the requested network details.
3. Apply the generated configuration
WordPress displays additional lines for wp-config.php and rewrite directives for .htaccess. Copy those generated rules exactly into the indicated files. The network will not route path-based sites correctly if only the PHP configuration is added while the rewrite rules are omitted.
4. Create and administer network sites
Use the Network Admin area to create sites whose paths become URLs such as /site1 and /site2. These are virtual sites in the network; creating a matching physical directory is neither required nor what makes the site work.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →How Multisite changes themes, plugins and upgrades
Centralization is Multisite’s main operational advantage, but it changes who controls extensions.
- Network administrators install themes for the whole network. Individual site administrators do not manage theme files as if each site were a separate WordPress codebase.
- Plugins can be activated for one site or network-activated, depending on the plugin and the desired scope.
- Some plugins do not support Multisite. Check compatibility before moving a site whose functionality depends on specialized plugins.
- A shared core reduces repeated update work, but one core or plugin change can affect several sites at once.
With separate installations, each site can use a different plugin stack and can remain on its own upgrade schedule. That independence also means every installation needs its own maintenance, security updates and backup process.
When a subdomain network is a better fit
Multisite can also use subdomains such as site1.example.com. This remains one shared core and database, but DNS and server mapping must direct the subdomains to the network. Wildcard DNS/server setup and the root-of-webfolder requirement make this a hosting concern as well as a WordPress setting.
Use subdomains when the site’s identity should be domain-based. If the required public addresses are paths under one domain, choose between physical independent installs and a subdirectory network instead.
Free tools Windows power users keep installed
One-click scans. No signup required.
Separate installs or Multisite: a practical decision framework
Choose separate installs when isolation is the priority
- Each site needs different plugins, themes or PHP-level customization.
- Sites must be upgraded or secured independently.
- One site may be migrated without moving the others.
- You want a separate database boundary for each project.
- You can handle separate backups, updates and administrator accounts.
Choose Multisite when centralized administration is the priority
- A single team should manage one WordPress core.
- The sites can use themes and plugins known to support Multisite.
- Shared infrastructure and network-wide administration outweigh independent release schedules.
- You accept that moving one site out of the network can be more complex than moving an independent installation.
Do not choose based only on the URL
Both architectures can produce /site1 and /site2. The deciding factors are isolation, database separation, plugin and theme independence, rewrite complexity, backup workload and migration plans. A path-shaped URL does not tell you whether the site is a physical install or a virtual Multisite site.
Backup and maintenance checklist
For independent installations
- Back up each database and its corresponding WordPress files.
- Keep the correct
wp-config.phpwith the correct directory and database. - Record each site’s table prefix when a database is shared.
- Test restoration of one site without overwriting another site’s files or tables.
- Review parent and child rewrite rules after server changes.
For Multisite
- Back up the shared database,
wp-config.phpand.htaccessbefore network changes. - Check plugin compatibility with Multisite before network activation.
- Plan updates at network scope because a shared core can affect every site.
- Document each site’s path, upload location and administrator responsibilities.
- Plan migration carefully if an individual site may later need to become independent.
Bottom line
Multiple WordPress sites can run under one domain in subfolders. Use separate physical installations when you need genuine independence, and use a Multisite subdirectory network when you want virtual sites managed from one shared core. In either case, correctly scoped rewrite rules are what keep /site1 and /site2 from being redirected to the main site.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
