What is WordPress Multisite?

WordPress Multisite is a powerful feature that allows you to create and manage a network of multiple websites from a single WordPress installation. All sites in the network share the same themes and plugins, simplifying updates and management under a central Super Admin.

Subdirectory, Subdomain, or Domain-Based?

If you’ve decided that Multisite is the right fit for your project (unsure? consider the pros and cons first), one of the most crucial initial decisions is choosing the URL structure for the sites within your network. This choice impacts:

• Branding: How users perceive the relationship between the sites.
• Technical Setup: The complexity involved in configuring your network and DNS.
• SEO: How search engines view and rank the individual sites within your network.
• User Experience: How easily users can navigate and understand the site structure.

WordPress Multisite offers three primary structures: Subdirectories, Subdomains, and Custom Domain Mapping. Let’s explore each option to help you decide which is best for your needs.

Option 1: Subdirectory Structure (example.com/site1/)

• Description: In this structure, each new site in your network is created as a virtual “directory” or “folder” under your main network domain.
• Example: If your main site is example.com, new sites would look like example.com/subsite1, example.com/subsite2, etc.

Technical Considerations:

• Simpler Setup: Generally the easiest structure to configure, as it typically doesn’t require special DNS settings like wildcard records.
• Availability: Supported on all Pressable hosting plans.
• URL Path: Uses the URL path after the main domain name.

Characteristics & Implications:

• SEO: Search engines often interpret subdirectory sites as being part of the main domain. This can potentially consolidate SEO authority, benefiting the main domain’s ranking power.
• Close Relationship: Best suited when the subsites are closely related thematically to the main site or represent distinct sections of a larger entity.

Use Cases (Good Fits):

• Universities/Schools: Different departments, faculty blogs, course sites (e.g., university.edu/biology, university.edu/professors-blog).
• Digital Publications: Sections managed by different teams (e.g., magazine.com/news, magazine.com/sports).
• Businesses with Locations/Branches: If a strong tie to the main brand is desired (e.g., maincompany.com/branch-location1).
• Internal Networks: Corporate intranets with departmental sites.
• Multilingual Sites (Path-Based): Using paths for language variations (e.g., mysite.com/en/, mysite.com/es/).

Option 2: Subdomain Structure (site1.example.com)

• Description: With this structure, each new site in the network gets its own unique subdomain attached to the main network domain.
• Example: If your main site is example.com, new sites would look like subsite1.example.com, subsite2.example.com, etc.

Technical Considerations:

• DNS Configuration Required: You need to configure DNS records to point each potential subdomain to your Pressable site. The easiest way to manage this is typically by setting up a wildcard DNS record (*.example.com) for your domain. This record acts as a catch-all for any subdomain. Alternatively, you could create individual DNS records (like A or CNAME) for each specific subdomain, but this requires more manual management.
• Increased Complexity: Setting up and managing DNS for subdomains adds technical complexity compared to subdirectories, especially if not using a wildcard.
• Plan Requirement: Subdomain Multisite networks are only available on Pressable plans supporting 5 sites or more. (See Pressable Pricing for details).
• Hosting Support: Pressable fully supports subdomain Multisite setups on eligible plans.

Characteristics & Implications:

• SEO: Search engines typically treat subdomains as distinct websites separate from the main domain. Each site generally needs its own independent SEO strategy.
• Distinct Identities: Offers more separation and potentially a more “professional” look for sites that need their own identity while still being part of the network.
• Flexibility: Provides more flexibility for site names compared to the path constraints of subdirectories.

Use Cases (Good Fits):

• Blogging Networks: Hosting multiple blogs under one umbrella (e.g., tech.blognetwork.com, food.blognetwork.com).
• User-Created Sites: Platforms allowing users to create their own sites (like WordPress.com or school networks where students get studentname.school.edu).
• Campaign Sites: Distinct websites for specific marketing campaigns or events (e.g., summersale.company.com).

Option 3: Custom Domain Mapping (newdomain.com)

• Description: Domain mapping allows a site within your Multisite network (initially created as a subdirectory or subdomain) to use a completely different, “mapped” domain name. The original network URL structure is hidden from visitors.
• Example: A site created as subsite1.example.com or example.com/subsite1 could be mapped to appear as completelynewdomain.com.

Technical Considerations:

• DNS Pointing: You need to point the custom domains’ DNS records (usually an A record or CNAME record) to your Pressable server/site IP address. (Refer to How to Point Your Domain to Pressable).
• Increased Complexity: Managing DNS for multiple custom domains adds significant technical overhead.
• Plan Requirement: Using custom domain mapping for sites within a Multisite network is only available on Pressable plans supporting 5 sites or more. (See Pressable Pricing for details).
• Hosting Support: Pressable fully supports domain mapping on eligible plans.

Characteristics & Implications:

• SEO: Search engines treat mapped domains as entirely separate websites. This is often the best structure if each site needs maximum independent ranking potential.
• Complete Branding Separation: Allows each site to have a unique brand identity with its own domain name, completely masking its connection to the underlying Multisite network from a visitor’s perspective.

Use Cases (Good Fits):

• Distinct Brands: Managing multiple websites with unique brand names and domains (e.g., brandA.com, brandB.org) from one dashboard. (Note: If sites are completely unrelated with no shared users/content needs, separate installs will be much simpler).
• Multilingual/Regional Sites: Using country-code TLDs or distinct regional domains (e.g., company.fr, company.de, company.co.uk).
• Franchises/Enterprises: Allowing regional branches or franchises to have their own domains (e.g., franchisecity.com) while maintaining central control.
• Client Sites (Full Domain): Hosting client sites on their own custom domains within your network (subject to the complexities of shared resources).

WordPress Multisite Structure Support on Pressable

Pressable’s platform is optimized for WordPress performance and security, making it an excellent choice for hosting demanding Multisite networks.

• Full Support: We fully support WordPress Multisite installations using all three URL structures. (Remember that subdomain and domain mapping options require plans with 5 or more sites.)
• Performance & Security: Our managed hosting environment provides the robust infrastructure needed for complex Multisite setups.
• Expert Support: While Pressable provides expert support for platform-level issues (hosting, server configuration, DNS assistance related to pointing domains), please be aware that troubleshooting specific Multisite application behavior, plugin/theme conflicts within the network, or complex custom code falls outside our standard Scope of Support. Setting up and managing the complexities of subdomain and domain-mapped networks requires careful planning and execution.

Making the Final Decision

Choosing the right URL structure is fundamental to a successful Multisite implementation. Consider these key factors:

1. Relationship Between Sites: Are they closely related sections (Subdirectory) or more distinct entities (Subdomain/Custom Domain)?
2. Branding Needs: Do sites need to share the main brand identity (Subdirectory), have some distinction (Subdomain), or be completely separate (Custom Domain)?
3. SEO Goals: Do you want to consolidate authority (Subdirectory) or have sites rank independently (Subdomain/Custom Domain)?
4. Technical Complexity & Resources: Are you comfortable managing DNS (required for Subdomain/Custom Domain)? Does your Pressable plan support your desired structure? Subdirectories are the simplest to manage and available on all plans.
5. User Experience: Which structure will be clearest and most intuitive for your target audience?

Weigh the pros and cons of each structure carefully based on your specific project goals. If you have questions about the hosting requirements for your chosen structure or need assistance pointing your domains to Pressable, please don’t hesitate to contact our support team.