Title: wp post block update Published: October 6, 2026 Last modified: October 28, 2026 --- # 󠀁[wp post block update ](https://developer.wordpress.org/cli/commands/post/block/update/)󠁿 Updates a block’s attributes or content by index. ## In this article * [Options](https://developer.wordpress.org/cli/commands/post/block/update/?output_format=md#options) * [Examples](https://developer.wordpress.org/cli/commands/post/block/update/?output_format=md#examples) * [Global Parameters](https://developer.wordpress.org/cli/commands/post/block/update/?output_format=md#global-parameters) [ ⌊GitHub⌉ ](https://github.com/wp-cli/entity-command) [ View Open Issues (0) ](https://github.com/login?return_to=%2Fissues%3Fq%3Dlabel%3Acommand%3Apost-block-update+sort%3Aupdated-desc+org%3Awp-cli+is%3Aopen) [ View Closed Issues (1) ](https://github.com/login?return_to=%2Fissues%3Fq%3Dlabel%3Acommand%3Apost-block-update+sort%3Aupdated-desc+org%3Awp-cli+is%3Aclosed) [Create New Issue](https://github.com/wp-cli/entity-command/issues/new) > **Note:** This command is not part of a stable WP-CLI release yet. To use it > now, [switch to the nightly build](https://make.wordpress.org/cli/handbook/guides/installing/#updating-wp-cli) > with `wp cli update --nightly`. If you installed the command as a separate package, > updating that package may be enough. Modifies a specific block without changing its type. For blocks where attributes are reflected in HTML (like heading levels), the HTML is automatically updated to match the new attributes. ### 󠀁[Options](https://developer.wordpress.org/cli/commands/post/block/update/?output_format=md#options)󠁿 See the [argument syntax](https://make.wordpress.org/cli/handbook/references/argument-syntax/) reference for a detailed explanation of the syntax conventions used. The ID of the post. The block index to update (0-indexed). [–attrs=] Block attributes as JSON. Merges with existing attributes by default. [–content=] New innerHTML content for the block. [–replace-attrs] Replace all attributes instead of merging. [–porcelain] Output just the post ID. ### 󠀁[Examples](https://developer.wordpress.org/cli/commands/post/block/update/?output_format=md#examples)󠁿 ``` # Change a heading from h2 to h3. $ wp post block update 123 0 --attrs='{"level":3}' Success: Updated block at index 0 in post 123. # Add alignment to an existing paragraph (merges with existing attrs). $ wp post block update 123 1 --attrs='{"align":"center"}' Success: Updated block at index 1 in post 123. # Update the text content of a paragraph block. $ wp post block update 123 2 --content="<p>Updated paragraph text</p>" Success: Updated block at index 2 in post 123. # Update both attributes and content at once. $ wp post block update 123 0 --attrs='{"level":2}' --content="<h2>New Heading</h2>" Success: Updated block at index 0 in post 123. # Replace all attributes instead of merging (removes existing attrs). $ wp post block update 123 0 --attrs='{"level":4}' --replace-attrs Success: Updated block at index 0 in post 123. # Get just the post ID for scripting. $ wp post block update 123 0 --attrs='{"level":2}' --porcelain 123 # Use custom HTML sync logic via the wp_cli_post_block_update_html filter. # Use WP_CLI::add_wp_hook() in a file loaded with --require. $ wp post block update 123 0 --attrs='{"url":"https://example.com"}' --require=my-sync-filters.php Success: Updated block at index 0 in post 123. ``` ### 󠀁[Global Parameters](https://developer.wordpress.org/cli/commands/post/block/update/?output_format=md#global-parameters)󠁿 These [global parameters](https://make.wordpress.org/cli/handbook/config/) have the same behavior across all commands and affect how WP-CLI interacts with WordPress. | **Argument** | **Description** | | `--path=` | Path to the WordPress files. | | `--url=` | Pretend request came from given URL. In multisite, this argument is how the target site is specified. | | `--ssh=[:][@][:][]` | Perform operation against a remote server over SSH (or a container using scheme of “docker”, “docker-compose”, “docker-compose-run”, “vagrant”). | | `--ssh-args=` | Pass additional arguments to SSH (or other tools specified by –ssh scheme). | | `--http=` | Perform operation against a remote WordPress installation over HTTP. | | `--user=` | Set the WordPress user. | | `--skip-plugins[=]` | Skip loading all plugins, or a comma-separated list of plugins. Note: mu-plugins are still loaded. | | `--skip-themes[=]` | Skip loading all themes, or a comma-separated list of themes. | | `--skip-packages` | Skip loading all installed packages. | | `--require=` | Load PHP file before running the command (may be used more than once). | | `--exec=` | Execute PHP code before running the command (may be used more than once). | | `--context=` | Load WordPress in a given context. | | `--[no-]color` | Whether to colorize the output. | | `--debug[=]` | Show all PHP errors and add verbosity to WP-CLI output. Built-in groups include: bootstrap, commandfactory, and help. | | `--prompt[=]` | Prompt the user to enter values for all command arguments, or a subset specified as comma-separated values. | | `--quiet` | Suppress informational messages. | | `--alias=` | 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. | _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._