Creates a site in a multisite installation.
- Path for the new site. Subdomain on subdomain installs, directory on subdirectory installs.
- Title of the new site. Default: prettified slug.
- Email for admin user. User will be created if none exists. Assignment to super admin if not included.
- Network to associate new site with. Defaults to current network (typically 1).
- If set, the new site will be non-public (not indexed)
- If set, only the site id will be output on success.
$ wp site create --slug=example Success: Site 3 created: http://www.example.com/example/
GLOBAL PARAMETERS GLOBAL PARAMETERS
These global parameters have the same behavior across all commands and affect how WP-CLI interacts with WordPress.
||Path to the WordPress files.|
||Pretend request came from given URL. In multisite, this argument is how the target site is specified.|
||Perform operation against a remote server over SSH (or a container using scheme of “docker”, “docker-compose”, “docker-compose-run”, “vagrant”).|
||Perform operation against a remote WordPress installation over HTTP.|
||Set the WordPress user.|
||Skip loading all plugins, or a comma-separated list of plugins. Note: mu-plugins are still loaded.|
||Skip loading all themes, or a comma-separated list of themes.|
||Skip loading all installed packages.|
||Load PHP file before running the command (may be used more than once).|
||Execute PHP code before running the command (may be used more than once).|
||Load WordPress in a given context.|
||Whether to colorize the output.|
||Show all PHP errors and add verbosity to WP-CLI output. Built-in groups include: bootstrap, commandfactory, and help.|
||Prompt the user to enter values for all command arguments, or a subset specified as comma-separated values.|
||Suppress informational messages.|
Command documentation is regenerated at every release. To add or update an example, please submit a pull request against the corresponding part of the codebase.