Skip to content

[00] Licences and sites, User guide

What counts as a site

One WordPress install is one site, however many addresses it answers on. What we collapse, what we keep separate, and which cases are free.

A site slot is one WordPress install: its own wp-admin, its own database tables and its own update check. A domain, a subdomain or an address doesn’t decide it. This page covers how we read a site’s address, which installs count separately and which don’t count at all.

One install, however it writes its address

WordPress can report its own address in several forms, and a theme or plugin can report it differently again. Before we store or compare an address, we reduce it to the part that identifies the install.

We drop:

  • The scheme. Moving to HTTPS isn’t moving site.
  • www. www.example.com and example.com are one install serving two names.
  • Capital letters in the host. Host names are case-insensitive.
  • Trailing and doubled slashes.
  • The default ports :80 and :443, under either scheme.
  • Query strings, fragments and anything before an @.

We convert an internationalised domain to its ASCII form, so bücher.example and xn--bcher-kva.example are also one site.

You might reportWe store
https://www.Example.com/example.com
HTTP://WWW.Example.COM:80/?utm=x#topexample.com
example.comexample.com
https://example.com/blog/example.com/blog
https://example.com:8080example.com:8080

The last two rows keep the path and the port. The next section explains why.

What we keep separate

A subdirectory install is a different site. example.com/blog has its own wp-admin, tables, plugin list and update check. It’s a second install, so it takes a second slot.

We chose the stricter rule on purpose. If we ignored the path, one install’s activation would satisfy another install’s update check, and two sites would share one licence. If the two are one site to you and you’re short a slot, contact us and we’ll sort it out.

A non-default port is a different site. A site on :8080 is reachable only on that port, and it’s usually a separate install on the same server.

We keep the capitalisation of the path. Paths are case-sensitive on most servers, and WordPress always reports the same value. Lowercasing paths could merge two real installs to guard against a typo that WordPress can’t make.

What doesn’t take a slot

Development and staging sites are always free. These activate without using a slot, even when every paid slot is in use: localhost, a private IP address, a .local or .test domain, a DDEV or Lando address, your host’s staging sandbox, and a staging. or dev. subdomain. Development and staging sites lists the exact rules.

A multisite network is one site. It has one install, one wp-admin and one update check, so it takes one slot however many subsites it has. See Multisite.

Activating the same site again is free. Saving the key again, reinstalling the plugin or restoring a backup updates the existing record instead of taking a second slot. If you deactivated a site and then activate it again, it takes a slot, because you gave that one back.

What a plan allows

A licence allows 1, 5 or unlimited sites, across all its plugins. Development and staging sites don’t count, so a five-site plan covers five production sites and any number of staging sites.

We check the limit when you activate, never while the site is running. If you’re out of slots, the next activation fails with a message saying so. Sites that are already activated aren’t affected.

Addresses we refuse

We reject any address that isn’t a usable http or https site: mailto:, file:, javascript: and anything that doesn’t parse as a web address. We also don’t treat a malformed address as a development site. Otherwise every broken site_url would get a free slot.