Multiple WordPress sites on one hosting account

You can run multiple WordPress sites on a single hosting account — separate domains, subdirectories, or subdomains. Each is fully independent (own database, own admin, own plugins).

How to install multiple sites

Use the install wizard once per site:

Go to Services → click hosting → WordPress tab → Install.
Pick the destination (different domain, subdomain, or subdirectory each time).
Run the wizard.

Repeat for each WordPress site you want.

The WordPress tab shows all installed sites in a card grid — easy to manage from one place.

Where each site lives

Each WordPress install gets its own directory:

Primary domain: /public_html/ → yourdomain.com.
Addon domain: /public_html/another-site.com/ → another-site.com.
Subdomain: /public_html/blog/ → blog.yourdomain.com.
Subdirectory: /public_html/shop/ → yourdomain.com/shop.

Each has its own:

WordPress files.
Database (separate from other sites).
wp-config.php, .htaccess, etc.
Admin users.
Plugins and themes.

Resource sharing

Multiple sites on one hosting account share:

Disk space — total usage = sum of all sites.
Database server — same MariaDB instance, different databases.
Bandwidth — total monthly transfer = sum of all sites.
CPU and memory — your plan's resources are shared across all sites.

For a small site or two, this is fine. For multiple high-traffic sites, you might bottleneck — consider upgrading or moving heavy sites to their own service.

Multiple sites vs WordPress Multisite

Two different concepts:

Multiple sites (this article)

Independent WordPress installs on the same hosting:

Each install is fully separate.
Different versions, different plugins, different themes.
Easy to migrate one off without affecting others.

WordPress Multisite

A network of sites running on one WordPress install:

Single core, single set of files, multiple "sites" sharing them.
Centralized admin (network admin) over all sites.
Plugins/themes shared (but can be activated per-site).
Used when sites are highly related — same brand, same maintenance team.

Multisite is more efficient for many similar sites. Multiple separate installs is more flexible — you can use different WordPress versions, different stacks per site, etc.

For most users, "multiple separate installs" is the right pattern. Multisite is specifically for SaaS-style WordPress deployments.

Managing multiple sites

The portal's WordPress tab makes it easy:

Card grid showing every install on the hosting.
Status at a glance — running, needs update, has error.
Auto-login — one click to admin for any site.
Bulk operations — update plugins across all sites in one go (depending on portal version).

Plus per-site management pages with tabs for plugins, themes, tools, backups.

Common patterns

Main site + blog

yourdomain.com → Main marketing site (sometimes a static landing page, sometimes WordPress).
yourdomain.com/blog/ → WordPress for content marketing.

Marketing site + e-commerce

yourdomain.com → WordPress for content/marketing.
shop.yourdomain.com → WordPress with WooCommerce for the store.

Or run them as one WordPress install with WooCommerce — depends on whether you want shared admin and theme.

Multiple brands

Several distinct businesses, each with its own domain:

brand1.com → WordPress
brand2.com → WordPress
brand3.com → WordPress

All on one hosting account if traffic is modest. Split to separate hosting if any one site needs dedicated resources.

Limits

How many WordPress installs you can have on one hosting account:

Most plans: limited only by total disk space and number of databases (typically 5–25 databases per shared plan, unlimited on VPS).
Each WordPress install needs: ~50MB minimum for WordPress core, plus database, plus your content.

Practical limit on a typical shared plan: 5–15 WordPress sites depending on size.

Power-user note

For lots of small WordPress sites, consider running WordPress Multisite — one core install handling many "sites." Saves on disk space, simplifies updates (update once, applies to all), and centralizes admin. Setup is more involved than separate installs, but pays back at scale.

For very-many sites (50+) at scale, look at managed WordPress hosting platforms or build out a custom solution. Shared hosting with 50 WordPress installs becomes a maintenance burden.