The WP-CLI Commands Every Developer Should Know

This article may contain affiliate links. See our affiliate disclosure.

A reader emailed us last month asking how we handle this. Here's the long answer.

What you need before starting

Access to the WordPress admin (or your host's file manager)
A working backup. Here's the backup approach we recommend if you don't have one.
About 20 minutes of uninterrupted time.

Step-by-step

Step 1 — Audit what you actually have

Open the relevant section of your WordPress dashboard and just look. Most people skip this. Don't. You'll find at least one thing that's already misconfigured.

Step 2 — Make the change in staging first

If your host offers one-click staging (SiteGround, Kinsta, WP Engine all do), use it. If not, LocalWP lets you pull a copy down to your laptop. The five extra minutes save an hour of panic later.

Step 3 — Apply the change

Whatever the actual change is, document it as you go. Even just notes in a text file. Future you will thank present you.

Step 4 — Test on three devices

Not just your laptop. Real phone, real tablet, real second browser. Things that work in Chrome desktop break in Safari mobile more often than you'd think.

Step 5 — Push to production

Many hosts let you push staging-to-live with one click. If yours doesn't, manually replicate the change. Take screenshots before and after — you'll want them if something breaks at 2 AM.

Step 6 — Monitor for 48 hours

Check Google Search Console for crawl errors. Check Wordfence (or your security plugin) for unusual activity. Most issues show up within 48 hours, not immediately.

Common mistakes

Skipping the staging step. You've made this exact change ten times before. That's exactly the kind of confidence that breaks production.
Not waiting for caches to clear. Cloudflare, your host's cache, your browser cache, the CDN — there are at least four layers. Give it 10 minutes before deciding something didn't work.
Forgetting to flush permalinks. When in doubt: Settings > Permalinks > Save Changes. Fixes more weird issues than it should.

What if something goes wrong?

Restore the backup. That's why you took one. Don't waste 30 minutes debugging something at midnight when a 90-second restore gets you back to a known-good state.

If you find yourself doing this kind of work often, a managed host with built-in staging pays for itself within a quarter.

— The RevealTheme Team