handbook/commands/site/get.md

wp site get

Gets details about a site in a multisite installation.

OPTIONS

See the argument syntax reference for a detailed explanation of the syntax conventions used.

<site>

Site ID or URL of the site to get. For subdirectory sites, use the full URL (e.g., http://example.com/subdir/).

[--field=<field>]

Instead of returning the whole site, returns the value of a single field.

[--fields=<fields>]

Limit the output to specific fields. Defaults to all fields.

[--format=<format>]

Render output in a particular format. --- default: table options:

• table
• csv
• json
• yaml ---

AVAILABLE FIELDS

These fields will be displayed by default for the site:

• blog_id
• url
• last_updated
• registered

These fields are optionally available:

• site_id
• domain
• path
• public
• archived
• mature
• spam
• deleted
• lang_id

EXAMPLES

# Get site by ID
$ wp site get 1
+---------+-------------------------+---------------------+---------------------+
| blog_id | url                     | last_updated        | registered          |
+---------+-------------------------+---------------------+---------------------+
| 1       | http://example.com/     | 2025-01-01 12:00:00 | 2025-01-01 12:00:00 |
+---------+-------------------------+---------------------+---------------------+

# Get site URL by site ID
$ wp site get 1 --field=url
http://example.com/

# Get site ID by URL
$ wp site get http://example.com/subdir/ --field=blog_id
2

# Delete a site by URL
$ wp site delete $(wp site get http://example.com/subdir/ --field=blog_id) --yes
Success: The site at 'http://example.com/subdir/' was deleted.

GLOBAL PARAMETERS

These global parameters have the same behavior across all commands and affect how WP-CLI interacts with WordPress.

Argument	Description
--path=<path>	Path to the WordPress files.
--url=<url>	Pretend request came from given URL. In multisite, this argument is how the target site is specified.
--ssh=[<scheme>:][<user>@]<host|container>[:<port>][<path>]	Perform operation against a remote server over SSH (or a container using scheme of "docker", "docker-compose", "docker-compose-run", "vagrant").
--ssh-args=<args>	Pass additional arguments to SSH (or other tools specified by --ssh scheme).
--http=<http>	Perform operation against a remote WordPress installation over HTTP.
--user=<id|login|email>	Set the WordPress user.
--skip-plugins[=<plugins>]	Skip loading all plugins, or a comma-separated list of plugins. Note: mu-plugins are still loaded.
--skip-themes[=<themes>]	Skip loading all themes, or a comma-separated list of themes.
--skip-packages	Skip loading all installed packages.
--require=<path>	Load PHP file before running the command (may be used more than once).
--exec=<php-code>	Execute PHP code before running the command (may be used more than once).
--context=<context>	Load WordPress in a given context.
--[no-]color	Whether to colorize the output.
--debug[=<group>]	Show all PHP errors and add verbosity to WP-CLI output. Built-in groups include: bootstrap, commandfactory, and help.
--prompt[=<assoc>]	Prompt the user to enter values for all command arguments, or a subset specified as comma-separated values.
--quiet	Suppress informational messages.
--alias=<name>	Name of the alias to use. Aliases can reference local WordPress installations or remote SSH connections. Aliases are defined in the wp-cli.yml file.
--assume-https	Set $_SERVER['HTTPS'] to make WordPress treat the site as HTTPS. Use when WordPress is behind an HTTPS proxy or load balancer.