WordPress.com Gave Every Paid Plan a Shell. Your First Hour With WP-CLI

Editorial card reading SSH and WP-CLI on a Cheap Plan, Hosting pillar, imivantan.com

Written by

in

On 13 November 2026, WordPress.com moved SSH, SFTP, WP-CLI, Git commands and GitHub deployments out of its top-tier plans and onto every paid plan. If you pay for Personal or Premium, you now have a shell on the server that serves your site. The practical effect is narrower and more useful than the announcement sounds: when a plugin breaks your site, you can turn it off in about ten seconds instead of filing a ticket and waiting for someone else to do it.

Here is the order I use on a fresh shell: what to check before typing anything, the read-only commands that give you a baseline, and the three that can erase weeks of work. Only one of those three asks for confirmation.

The short version

  • SSH, WP-CLI, Git and GitHub deployments are now included on Personal, Premium, Business and Commerce plans; free sites are still excluded.
  • You enable it in the hosting dashboard under Settings → SFTP/SSH, then toggle SSH access on.
  • Use an SSH key rather than the generated password, and put two-factor on the account before you open the port.
  • Start with read-only commands: wp core version, wp plugin list, wp theme list, wp option get home.
  • Never run a database search-replace without --dry-run, and never run a reset on a live site.

What actually changed

The WordPress.com changelog published on 13 November covers 30 October to 12 November. The line that matters: the developer tools are “no longer just for Business plans and above”. On any paid plan you can connect over SSH or SFTP, run WP-CLI and Git commands, and deploy from GitHub.

The support docs add details worth knowing:

  • It applies to plugin-enabled sites on Personal, Premium, Business and Commerce. Free-plan sites have to upgrade.
  • One set of credentials works for both SFTP and SSH. You create it once; “Reset password” issues a new one, with a one-minute wait between resets.
  • You can attach up to ten SSH keys to the account instead of using a password.
  • The dashboard prints the exact connection command. Copy it from there rather than assembling it from a blog post, including this one.

One caution: the pricing page still lists these tools only on Business and Commerce while the changelog says every paid plan. If you are switching plans for the shell, ask support which page is current before you pay.

Two settings before the first connection

Two-factor on the account. Your account now controls a login that can edit files directly. Do this first; it takes two minutes and separates an inconvenience from a cleanup.

An SSH key. Generate a key pair on your machine, paste the public key into the account, and keep the private key off the server. Keys can be revoked one at a time, which a shared password cannot.

The baseline: five read-only commands

Before you change anything, record the state of the site. All of these only read.

wp core version
wp plugin list --fields=name,status,version,update
wp theme list --fields=name,status,version,update
wp option get home
wp option get siteurl

The plugin list is the important one. Save it outside the server:

wp plugin list --fields=name,status,version,update > plugins-before.txt
scp user@host:plugins-before.txt ./plugins-before.txt

Use the hosting file manager if SCP is awkward. That file is your before picture: which plugins were active, at which versions, and which had updates waiting. When something breaks next month, compare against it instead of trying to remember.

The two option commands look trivial until you need them: home and siteurl are what a bad migration breaks, and having them written down has saved me more than once.

The rescue move: a plugin that white-screens the site

This is the reason the change matters. A plugin update throws a fatal error, the front end shows a blank page or a 500, and the dashboard may not load either. From the shell:

wp plugin list --status=active --fields=name,version
wp plugin deactivate plugin-slug

Reload the site. If it comes back, that plugin was the cause — update it or leave it off.

One wrinkle: if the broken plugin loads before WP-CLI starts, WP-CLI dies too. Skip it explicitly:

wp --skip-plugins=plugin-slug plugin deactivate plugin-slug

That flag stops WP-CLI loading the plugin for this one command, which is usually enough to get the deactivate through. Update or replace the plugin before you re-enable anything.

Three commands that can take the site down

Most WP-CLI commands are safe. A few are not, and they do not all stop to ask.

1. Database resets. wp db reset and wp site empty drop tables or content. With --yes they skip the confirmation. There is no undo and no recycle bin. On a live site these are not maintenance commands; they are a decision to start over.

2. Search-replace without a dry run. Changing a domain or moving from HTTP to HTTPS means running a search-replace across the database. Done wrong, it corrupts serialized data and leaves you with a site that loads but will not let you log in. The order is always: export the database, run it once with --dry-run, read the table counts, then run it for real.

wp search-replace 'http://old.example' 'https://new.example' --dry-run
wp search-replace 'http://old.example' 'https://new.example'
wp cache flush

3. Core updates you did not schedule. wp core update from the shell bypasses your host’s staging or backup routine. Fine when you are watching with a backup; bad at 11pm before a launch.

Some managed hosts lock down database commands. If wp db export is unavailable, use the host’s backup tool and treat the shell as a place for plugin and core work only.

The other half of the same changelog

The same changelog expanded what a connected AI assistant can do: list your SSH keys, deploy GitHub repositories, change PHP and WordPress versions, read server logs, and delete or reset a site.

Put that next to a cheap plan with a shell and the risk is obvious: an agent with file access and permission to reset a site is one bad instruction from an afternoon of restore work. Start on a staging copy, grant only what the task needs, and read the MCP settings instead of accepting defaults. I covered the narrower version in what an AI agent should be allowed to touch on a WordPress site.

WP-CLI makes this easier and harder: commands are deterministic, but an agent can run twenty before you look. Keep what you run in a notes file or script.

If your host is not WordPress.com

The commands are the same everywhere; the access is not. Three things worth checking with your own host:

  • Is SSH included? Many shared plans include it but do not advertise it. Ask support directly rather than reading the plan table.
  • Is there a terminal in the panel? cPanel and Plesk often ship one. That is enough to run WP-CLI without a separate SSH account.
  • Can you install WP-CLI yourself? It is a single PHP file. Download the phar, run php wp-cli.phar --info, and alias it. No plugin required.

What I would not do is install a plugin that puts a WP-CLI console in the browser on a live site. That adds an attack surface to avoid learning one command.

The first-hour checklist

Step Why it matters
Two-factor on the account A shell login is worth stealing.
Add an SSH key Revocable one at a time; no shared password.
Save the plugin list to a file Your before picture for the next outage.
Export the database, download it The shell cannot save you from a dropped table.
Test a deactivate on staging The command you need at 2am should not be its first run.
Write down home and siteurl Two values a bad migration breaks.

Do the boring part today

If your plan just gained a shell, the most valuable thing this week is not a clever command. It is the baseline: save the plugin list off the server, and export the database once so you know it works before you need it. Ten minutes now turns a future outage into a one-line fix.

If you are on a plan without SSH, see what to back up and how to test a restore, and how to update core without opening an attack window.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *