Back to Community
Home / Community / Core → Networking wordpress

Understanding WordPress Multisite: Why Your Subdomains Don't Have Physical Folders

16 threads Sep 16, 2025 Core → Networking wordpress

Content

If you've recently set up a WordPress Multisite network with subdomains, you might be searching your server's file system for the folders containing your new subsites. This is a common point of confusion, especially for users migrating from single-site installations or those familiar with creating subdomains in cPanel.

The Core Concept: Virtual Directories

A fundamental principle of WordPress Multisite is that subsites created as subdomains (e.g., store.example.com) or subdirectories are virtual. Unlike a traditional website setup where a subdomain points to a physical folder on your server (e.g., public_html/store), Multisite does not create individual directories for each subsite.

Instead, all subdomains and subdirectories are managed by the single WordPress installation in your root directory. The WordPress core and its rewriting rules in the .htaccess file handle all incoming requests and dynamically serve the correct content from the shared database based on the URL.

Why Users Expect Physical Folders

This confusion often arises for a few key reasons:

  • Traditional Hosting Experience: Most control panels, like cPanel or DirectAdmin, automatically create a physical directory (e.g., public_html/subdomain) when you add a subdomain through their interface. This is not required for Multisite and can actually cause conflicts.
  • File Uploads: While the subsites themselves are virtual, their uploaded media files are stored physically. These files are located in wp-content/uploads/sites/[site-id]/. Finding this folder can mistakenly lead users to believe the entire subsite should be there.
  • DNS Configuration: Some hosting providers require a specific DNS record (like a CNAME or A record) to point a subdomain to the main site's root directory. Users accustomed to pointing subdomains to their own folders may find this process unfamiliar.

Common Problems and Solutions

Problem 1: "I need to modify the .htaccess file for a specific subsite."

Solution: This is not possible in the way you might be used to. There is only one .htaccess file for the entire Multisite network, located in the root WordPress directory. All rewrite rules and server configurations for every subsite must be managed from this single file. You cannot have individual .htaccess files for each subdomain.

Problem 2: "My host created a folder for the subdomain, and now it's not working with Multisite."

Solution: For a Multisite subdomain setup to function correctly, the subdomain must point to the same root directory as your primary domain. If your hosting panel (cPanel, DirectAdmin, etc.) created a separate folder, you need to modify the subdomain's settings.

  • Locate your subdomain management tool in your hosting control panel.
  • Find the "document root" or "web root" setting for the subdomain.
  • Change this path so it points to the exact same directory as your main domain (e.g., public_html or /home/user/public_html).

Problem 3: "I can't access my subdomain; I get a 404 or other error."

Solution: This is often a DNS or server configuration issue, not a file location problem. The most critical step is setting up a wildcard subdomain.

  1. Wildcard DNS: In your domain's DNS settings (often at your domain registrar), you need to create a wildcard record that points *.yourdomain.com to your server's IP address.
  2. Wildcard Virtual Host (Server): Your server must be configured to accept wildcard subdomains. Many hosts have an option for this in their control panel. If not, you may need to contact their support and request that they enable it for you. This step ensures that every possible subdomain you create in your Multisite network is automatically routed to your main WordPress installation.

Key Takeaways

  • WordPress Multisite subdomains are virtual and do not have their own physical root folders on the server.
  • All subsites run from the same set of core files in the main WordPress directory and a shared database.
  • The single .htaccess file in the root directory governs the entire network.
  • For subdomains to work, they must point their document root to the main site's directory, and a wildcard subdomain should be configured.

Understanding this virtual nature of Multisite is the first step to successfully managing your network. If you encounter issues, always double-check your subdomain's document root path and your wildcard DNS configuration before looking for missing files.

Related Support Threads Support