The command palette is one of the most borrowed ideas in modern software. VS Code has one. Figma has one. Linear has one. Notion has one. Slack has one. GitHub has one.

If you spend time in professional tools, you almost certainly already use one somewhere in your daily workflow.

In every case, the idea is the same: press a keyboard shortcut, type what you want to do, and do it. No menu hunting. No mouse-driven navigation. No remembering where a setting is buried. Just type and act.

WordPress introduced one since version 6.9– but with important limitations that most users do not know about. And a generation of third-party plugins has emerged to fill the gaps that the built-in version leaves open.

This guide explains what a command palette actually is, how it works in WordPress specifically, where the built-in version falls short, and what a dedicated command palette plugin like Commandify adds to the picture.

What is a Command Palette in WordPress Actually?

A command palette is a search-driven interface that accepts typed input and returns matching commands, content, or navigation targets. You activate it with a keyboard shortcut, usually Cmd+K on Mac or Ctrl+K on Windows. A text box appears. You start typing. Results appear as you type, filtered in real time by what you have entered.

The results are not just links. They are actions. “Publish this post.” “Clear cache.” “Open order #4521.” “Edit product: Blue Running Shoes.” Each result is something you can do, not just somewhere you can go.

The term “command palette” comes from the programming world. Visual Studio Code popularised it as the way to access every editor function without memorising every keyboard shortcut or hunting through menus.

You press Cmd+Shift+P, type a fragment of what you want, and the matching command appears. The pattern proved so effective that it spread rapidly into other tools until it is now a near-universal feature of professional software.

The underlying principle is simple: searching is faster than navigating when you know what you want. A menu assumes you will browse to discover options. A command palette assumes you already know what you are looking for and just need to get to it instantly.

The WordPress Built-In Command Palette

WordPress added a native command palette in version 6.3, released in August 2023. It is accessible anywhere in the WordPress editor via Cmd/Ctrl + K. In WordPress 6.9, the palette expanded further across more admin screens.

The built-in palette is genuinely useful for certain tasks. Inside the block editor or site editor, you can navigate between templates, insert blocks, toggle editor preferences, add custom CSS, reset template customisations, and jump between pages and posts by typing their name.

For content creators who spend most of their time in the editor, it reduces a meaningful amount of friction.

But it has significant boundaries. As the WordPress command palette limitations guide covers in depth, the core palette is editor-focused. It does not cover WooCommerce. It does not cover plugin management.

It does not cover user accounts or bulk maintenance tasks. It is not available on most standard wp-admin screens outside the editor context. And it offers no integration with the page builders, form plugins, or e-commerce tools that most WordPress sites actually depend on.

For someone whose WordPress life extends beyond writing posts, the built-in palette covers a portion of their daily work and leaves the rest unchanged.

Why WordPress Admin Navigation Is a Problem Worth Solving

To understand why a command palette matters for WordPress specifically, it helps to understand what WordPress admin navigation actually looks like for someone who manages a non-trivial site.

A typical WordPress admin menu has somewhere between 20 and 60 top-level and second-level menu items, depending on how many plugins are installed. A WooCommerce store adds its own section with Orders, Products, Customers, Reports, and Settings, each with multiple nested tabs.

Page builders like Elementor and Bricks add their own menu sections. Security plugins, SEO tools, caching plugins, form plugins- each adds to the menu.

Navigating this by clicking is slow by nature. Finding an order requires: clicking WooCommerce, clicking Orders, waiting for the page to load, entering a search term, clicking the result. That is five steps minimum.

Repeat this thirty times a day for different orders and you have spent a surprising amount of time on navigation alone, for zero productive output.

A command palette replaces that entire sequence with: Cmd+K, type order number, press Enter. Two actions. The page loads directly on the record you needed. The arithmetic of daily friction is completely different.

What a Dedicated WordPress Command Palette Plugin Adds

Third-party command palette plugins for WordPress exist precisely because the built-in palette covers the editor use case well but leaves everything else untouched.

The most capable of these is Commandify, which is available as a free plugin on WordPress.org with a Pro tier that extends deeply into WooCommerce and page builder workflows.

Here is what a full-featured WordPress command palette plugin covers that the built-in version does not.

Full Admin Navigation from Any Screen

Unlike the core palette, which is constrained to the block editor context, Commandify is available on every screen in wp-admin from a single consistent shortcut. Cmd/Ctrl + K works whether you are on the dashboard, a WooCommerce screen, a plugin settings page, or anywhere else in the admin.

The palette mirrors your complete menu structure (every plugin, every nested page, every settings section) so anything reachable by clicking is reachable by typing.

Content Search With Context

Type a post title fragment and the matching posts appear with their status, date, and author shown alongside. You can edit, view, preview, or trash the post directly from the result without opening it first.

The same applies to pages, media items, custom post types, and any other registered post type on the site. Search results include enough context to confirm you have the right record before you act on it.

User Lookup

Type a name or email address and matching user accounts appear. Open the user profile, check their order history, or manage their account from the palette result.

For membership sites, learning management systems, or any site with significant user accounts, this replaces the process of navigating to Users, searching manually, and scrolling through results. The guide on switching WordPress users and handling user issues faster covers this workflow in detail.

Maintenance Commands

Commandify Free includes maintenance actions accessible directly from the palette: clear cache, flush rewrite rules, clean transients, regenerate thumbnails, and similar housekeeping tasks.

These are actual operations, not links to settings pages. Press the shortcut, type “clear cache,” press Enter. Done. No plugin settings screen required.

WooCommerce Command Suite (Pro)

Commandify Pro’s WooCommerce integration is the feature that most distinguishes it from every other option in this space, including the WordPress core palette, Turbo Admin, and any other command palette plugin currently available.

Pattern recognition identifies what you have typed without requiring you to specify a search category. A hash-prefixed number (#4521) is recognised as an order ID. An email address triggers a customer lookup.

A known SKU format opens the matching product variation. Actions available on each record (status changes, order notes, stock adjustments) are accessible from within the palette result without opening the full admin screen for that record.

The full scope of the WooCommerce command suite is covered in the WooCommerce management guide. For store managers handling daily orders and customers, the productivity difference is significant and immediate from the first day of use.

Who Benefits Most from a WordPress Command Palette

The honest answer is: anyone who spends more than a few hours per week inside wp-admin. But the benefits scale with how much you use the admin and how complex your site is.

WooCommerce store managers who handle daily orders and customer queries see the most dramatic improvement. Every lookup that previously required five navigational steps becomes a two-keystroke action. For high-order-volume stores, this is hours recovered per week, not minutes.

Agency developers who manage multiple client sites benefit from the speed of navigating to any admin screen without remembering where each plugin puts its settings. The fuller the plugin ecosystem, the more confusing the menu structure, and the more useful the command palette becomes as an alternative to that structure.

Content editors who publish regularly benefit from the built-in WordPress palette for editor navigation, and from a plugin like Commandify for cross-site and cross-content-type navigation beyond the editor context.

Developers building client sites benefit from maintenance commands and plugin management from the palette, reducing the time spent on setup and housekeeping tasks during site builds.

If you manage a simple one-page site and visit the admin once a week to publish a post, a command palette plugin is not a high-priority addition. If WordPress admin is part of your daily professional workflow, the question is not whether a command palette is worth it- it is which one fits your workflow best.

The Learning Curve

The most common reaction from new users of command palette tools is: “Why didn’t I have this earlier?” The pattern of pressing a shortcut and typing is immediately intuitive for anyone who has used a search engine, a code editor, or Spotlight on macOS. There is no training required to understand the basic interaction.

The efficiency gains compound with use. In the first week, you are still sometimes falling back to menu clicks for things you cannot immediately recall the name of. By the second week, most common actions feel faster through the palette.

By the fourth week, using WordPress without a command palette starts to feel unnatural in the way that using a computer without copy-paste would feel unnatural.

The fuzzy search in Commandify makes this transition even smoother. You do not need to type the exact name of what you are looking for. Type “woo order” and WooCommerce order screens appear. Type “elem temp” and Elementor templates appear.

The palette matches fragments and partial strings, so you get results even before you remember the exact wording of what you need.

How to Get Started in Two Minutes

The fastest way to understand what a command palette feels like is to install one and use it.

Install Commandify free from WordPress.org. Activate it. Press Cmd/Ctrl + K from anywhere in your WordPress admin. Type the name of any admin page- “plugins,” “users,” “settings,” or the name of a post you know exists on the site.

Watch the results filter as you type. Press Enter on the result you want.

That is it. You now understand what a command palette does for WordPress. The rest is a matter of which features matter for your specific site and whether the free version covers your needs or whether the Pro version’s WooCommerce and page builder integrations are worth the upgrade.

The 14-day money-back guarantee means there is no risk in finding out.

FAQs on What is A Command Palette

Is the command palette only for power users and developers?

No. The command palette is actually more accessible than keyboard shortcuts because you do not need to memorise anything. You just type what you want in plain language. “New post,” “clear cache,” “view orders”- these all work.

Any WordPress user who can type a search query can use a command palette from day one without any learning investment.

Does WordPress have a built-in command palette?

Yes. WordPress added a built-in command palette in version 6.3 (August 2023), accessible with Cmd/Ctrl + K inside the block editor and site editor. WordPress 6.9 expanded it to more admin screens.

However, it is focused on the editor context and does not cover WooCommerce, plugin management, user lookup, maintenance tasks, or most third-party plugin functionality.

Many users install a dedicated command palette plugin like Commandify to cover the complete wp-admin surface area that the core palette does not reach. The command palette limitations article covers the specific gaps in detail.

What is the keyboard shortcut for the WordPress command palette?

For the built-in WordPress palette: Cmd + K on Mac, Ctrl + K on Windows, within the block or site editor. For Commandify: the same Cmd/Ctrl + K shortcut, available on every wp-admin screen.

The shortcut is configurable in Commandify Pro if you prefer a different key combination. Turbo Admin uses a different default shortcut but also allows customisation through your browser profile settings.

Will a command palette plugin slow down my WordPress site?

No. Commandify loads its scripts exclusively in wp-admin, for authenticated admins only. It adds nothing to the public-facing site for regular visitors. The plugin uses client-side filtering for most search results, which means no additional server requests are made per keystroke.

Longer operations like cache clearing or database maintenance display a progress indicator while they run. There is no measurable frontend performance impact.

What is the difference between a command palette and WordPress keyboard shortcuts?

Keyboard shortcuts require memorisation. You press a specific combination of keys to trigger a specific pre-assigned action. If you do not remember the shortcut, you cannot use it. A command palette requires no memorisation- you type what you want in natural language and the palette finds it for you.

The command palette is also more flexible: it surfaces dynamic content like specific posts, orders, and users based on what is actually in your site, which static keyboard shortcuts cannot do.

The two tools complement each other; a full guide to WordPress keyboard shortcuts covers the shortcuts worth memorising alongside a command palette workflow.

Here are the 9 proven ways to Speed Up WordPress Admin Dashboard with ease!

A slow WordPress admin dashboard is one of those problems that compounds quietly. One second of loading time per page does not feel serious. Across twenty admin page loads per day, it is twenty seconds.

Across a working month, it is meaningful time and more importantly, it is accumulated friction that degrades the quality of the work you do inside the admin.

The problem is also commonly misdiagnosed. Many WordPress speed guides treat admin speed as an extension of frontend speed and recommend the same fixes: get a CDN, install a caching plugin, optimise your images.

These have zero effect on wp-admin. The admin is authenticated, dynamic content that bypasses every frontend caching layer.

This guide covers what actually works. Nine specific fixes, each explained precisely, each targeted at the admin environment rather than the frontend. We also address the category of slowness that no technical fix touches: workflow speed, which is about how many steps it takes you to do things inside the admin rather than how long those steps take to load.

Before You Start: Understand Which Type of Slowness You Have

WordPress admin slowness comes in two distinct forms. Applying the wrong category of fix wastes your time and leaves the actual problem unsolved.

Technical slowness: Admin pages take a long time to fully load. You click a menu item and wait two, three, or five seconds before the page arrives. The bottleneck is server processing, database query time, or poorly written plugin code running on every page request.

Workflow slowness: Pages load quickly but reaching what you need still requires too many steps. Five clicks to check an order. Seven clicks to get to a plugin settings screen. Searching through a list of 400 posts to find the one you want to edit. The admin is technically fast; the process is the problem.

Both types are addressed below. Fix 1 targets workflow slowness directly, which is often the higher-value fix and takes two minutes. Fixes 2 through 9 address technical slowness in order of impact.

Fix 1: Install a Command Palette for Instant Workflow Speed

This is the fastest fix with the highest day-one impact and requires no server access, no plugin configuration, and no technical knowledge.

Commandify adds a command palette to wp-admin. Press Cmd/Ctrl + K from any admin screen and a search bar opens. Type the name of any admin page, post, user.

Or, with Commandify Pro– any WooCommerce order, product, or customer. The result appears instantly. Press Enter and you are there.

The free version covers full admin navigation, content search across all post types, user lookup, plugin and theme management, and maintenance commands like cache clearing and database cleanup.

Install it free from WordPress.org and try pressing Cmd/Ctrl + K within sixty seconds of activation.

For WooCommerce stores, Commandify Pro adds a full WooCommerce command suite. Type an order number, a customer email, or a product SKU and it recognises the pattern automatically and opens the correct record.

Change order statuses, add notes, and adjust product stock from within the palette itself without visiting the corresponding admin screens. The WooCommerce management guide walks through this in detail.

If you are managing WordPress sites with complex admin menus from many plugins, or running a WooCommerce store with daily orders, this single fix will have a more noticeable effect on your daily experience than any server-side optimisation.

Fix 2: Identify Slow Plugins Using Query Monitor

Before changing your hosting, upgrading your PHP version, or touching your database, do this diagnostic step. A single poorly written plugin can add two to four seconds to every admin page load, making your admin feel slow regardless of how good your hosting is. Query Monitor finds it in 30 minutes.

Query Monitor is a free WordPress plugin that exposes the full performance picture of any page load. Install it, visit the admin screen that feels slowest, and open Query Monitor from the toolbar. Navigate to “Queries by Component.” This view shows every database query made during the page load, grouped by the plugin or theme that generated each query.

A healthy admin page load involves somewhere between 30 and 80 database queries. If one plugin is generating 150, 200, or 400 queries on a single page load, it is your culprit.

Common offenders are security plugins running file scans on every admin page view, analytics plugins computing complex reports in real time, backup plugins triggering during business hours, and old or abandoned plugins with poor caching of their own queries.

Once identified: deactivate the plugin and reload the page. If the admin speed improves significantly, you have confirmed the source. Your options are to replace the plugin with a more efficient alternative, reach out to the developer, or check whether there is a setting to limit when the plugin runs its intensive operations.

Uninstall Query Monitor after your diagnostic session. It is a diagnosis tool, not a permanent installation.

Fix 3: Upgrade PHP to 8.2 or 8.3

PHP is the language WordPress runs on. Every admin page load, every plugin function call, and every database interaction goes through PHP. Newer PHP versions process all of this faster. PHP 8.2 benchmarks approximately 25-35% faster than PHP 7.4 on typical WordPress workloads. PHP 8.3 improves further. For sites still on PHP 7.x, this is likely the highest-impact server-side improvement available.

Check your current PHP version at WooCommerce → Status → Server Information, or at Tools → Site Health → Info → Server.

If you are on PHP 7.4 or below, upgrading is urgent from both a performance and a security standpoint. PHP 7.4 reached end-of-life in November 2022, meaning it no longer receives security patches.

On most quality managed hosts (Kinsta, WP Engine, SiteGround, Cloudways, Rocket.net) PHP version selection is a dropdown in your hosting dashboard.

Select PHP 8.2 or 8.3, save, and the change applies immediately. Test your site over the next 24 hours for any plugin compatibility issues. In rare cases an older plugin may not support PHP 8.x syntax, but the vast majority of actively maintained plugins have been updated for compatibility.

Fix 4: Enable Object Caching (Redis or Memcached)

Page caching saves rendered HTML pages for anonymous visitors and deliberately bypasses wp-admin. If you have only ever installed a page caching plugin, you have not done anything for admin speed from a caching perspective.

Object caching is different. It stores the results of database queries in server memory (RAM). When WordPress needs the same data again, it retrieves it from RAM instead of querying the database again. Every admin page load benefits because the admin makes many repeated database queries.

Redis is the industry-standard object cache for WordPress. Memcached is an older alternative still offered by some hosts. The setup process depends on your hosting environment. On Kinsta, enable Redis in the Kinsta dashboard under your site’s tools. On Cloudways, toggle Redis in your application settings. On SiteGround, enable Memcached or Redis in Site Tools.

On WP Engine, contact support for Redis add-on options. Once enabled at the hosting level, follow your host’s instructions to connect it to WordPress- typically done through your host’s own plugin or a dedicated Redis plugin.

Do not attempt to configure Redis manually on shared hosting without confirmed host support. A misconfigured object cache causes more problems than it solves. Most quality managed hosts offer it with one-click enablement.

Fix 5: Regulate the WordPress Heartbeat API

The WordPress Heartbeat API runs in the background of wp-admin and sends regular AJAX requests to your server. It powers autosave functionality in the post editor, post locking when multiple editors are active, and some plugin notification systems. By default it fires a request every 15 seconds while you have an admin page open.

On most sites, that default is more frequent than necessary. On shared hosting with limited server resources, multiple admin tabs open simultaneously can produce what effectively becomes a sustained stream of server requests from your own browser. This consumes CPU and can cause the admin to feel sluggish under what should be very light load.

The Heartbeat Control plugin (free on WordPress.org) lets you set the Heartbeat interval separately for the dashboard, the post editor, and the frontend, without editing any code. The recommended approach: set the dashboard to 60 seconds (the maximum), keep the post editor at 30 seconds to retain reliable autosave, and disable the frontend heartbeat entirely unless a specific plugin requires it. This configuration reduces Heartbeat-related admin-ajax.php calls by roughly 60 to 75% compared to defaults.

Do not disable Heartbeat completely in the post editor. Doing so removes autosave protection while you are writing. The risk of losing content is not worth the marginal performance improvement.

Fix 6: Clean Dashboard Widgets and Admin Notices

The WordPress dashboard loads several default widgets that make outbound HTTP requests to external servers: the WordPress news widget fetches data from WordPress.org, some plugin widgets fetch remote data from their own servers, and marketing notifications from various plugins load content from external APIs. Each of these is a blocking HTTP request that your server makes before the dashboard finishes rendering.

Remove or disable any dashboard widgets you do not actively use. From the WordPress dashboard, click Screen Options at the top right and uncheck any widget section you do not need. For more aggressive cleanup, Admin Notices Manager (free on WordPress.org) consolidates admin notices into a dedicated panel so they do not fire their loading overhead on every admin page view.

Additionally: if you have WooCommerce installed, the WooCommerce admin dashboard loads remote inbox notifications from WooCommerce’s servers by default. Disable WooCommerce Bloat (free on WordPress.org) removes these with checkboxes, eliminating the outbound HTTP request they generate on every WooCommerce admin page load.

Fix 7: Optimise Your Database

WordPress databases accumulate overhead over time. Post revisions from years of content editing. Expired transients that cron jobs failed to clean up. Orphaned metadata from deleted posts and users. Tables left behind by plugins you removed months ago. Autoloaded data in the wp_options table growing beyond a healthy size.

None of this causes dramatic slowness individually. Accumulated over a year or more on a busy site, it meaningfully increases the time it takes to execute common database queries. The wp_options table is particularly important:

WordPress loads all autoloaded options on every single page request. A bloated wp_options table with megabytes of autoloaded data from old plugins slows every page load proportionally.

WP-Optimize handles database cleanup through a safe, previewed interface. Before removing anything it shows exactly what will be deleted.

Start with expired transients, post revisions, orphaned metadata, and spam comments. Also use the built-in WordPress tools: go to Tools → Delete Revisions if available, and WooCommerce → Tools → Clear transients and clear customer sessions if you run WooCommerce.

After cleanup, run the WP-Optimize table optimisation to rebuild indexes and reclaim space. On a site that has been running for two or more years without a database cleanup, this step alone often produces a noticeable admin speed improvement.

Fix 8: Disable WP-Cron and Replace with a Real Cron Job

WordPress’s built-in WP-Cron system runs scheduled tasks — plugin updates checks, scheduled post publishing, email notifications, cache rebuild triggers — by piggybacking on page views. Every time any visitor or admin loads any page, WordPress checks whether any scheduled tasks are pending and runs them if so.

On a busy site, this creates a consistent overhead on every page load. On a quiet site, it means scheduled tasks only run when pages are loaded, which can delay them unpredictably. Neither behaviour is ideal.

The fix is to disable WP-Cron and replace it with a true server cron job that runs independently on a schedule you control. Add define('DISABLE_WP_CRON', true); to your wp-config.php file to disable the default system.

Then create a server cron job in your hosting control panel (cPanel, Cloudways, Kinsta, or via SSH) that calls your site’s cron URL every 10-15 minutes: wget -q -O /dev/null "https://yourdomain.com/wp-cron.php?doing_wp_cron".

Your hosting provider’s documentation will have specific instructions for creating cron jobs in their environment.

This change removes the WP-Cron overhead from every single page load and replaces it with clean scheduled execution at the server level. On sites with many scheduled tasks running through plugins, the admin speed improvement is noticeable.

Fix 9: Limit Admin Screen Items Per Page

WordPress admin list tables — the posts list, pages list, users list, WooCommerce orders list, products list — default to displaying 20 items per page. Many users increase this through Screen Options to reduce pagination clicks, setting it to 50, 100, or more items per page.

This seems efficient but has a cost. Loading 100 items on a WooCommerce orders list means 100 database queries for order data, 100 queries for order metadata, and potentially additional queries for custom columns added by plugins. On a store with thousands of orders, a list set to 100 items per page can add several seconds to the orders list load compared to the default 20 items.

Check your Screen Options setting on your most-used list screens. Set them back to 20 unless you have a specific reason to see more at once.

If your main need is finding specific records quickly rather than scanning through lists, a command palette like Commandify is a better tool for that purpose: it finds specific records in under two seconds without loading a large paginated list at all.

What Does Not Speed Up Your WordPress Admin

These recommendations appear regularly in WordPress speed guides and are simply not relevant to the admin environment.

Page caching plugins. WP Rocket, LiteSpeed Cache, W3 Total Cache, and every other page caching plugin explicitly skips wp-admin for authenticated users. They are designed this way by intent. Installing or optimising a page cache has zero effect on admin page load times.

CDN for the admin. Content delivery networks route frontend static asset delivery through geographically distributed servers. Admin pages are dynamic, authenticated PHP responses that do not go through CDN layers. A CDN setup change will not improve admin speed.

Image optimisation. Compressing and converting images improves frontend page load speed for visitors. The admin does not serve your product images or post images to visitors. Image file size has no relationship to admin page load time.

Increasing PHP memory limits. Unless your admin pages are crashing with out-of-memory errors, increasing the memory limit does not speed anything up. Memory limit affects stability under peak load, not baseline performance. If your admin is slow but not crashing, the memory limit is not the constraint.

Prioritised Action Plan

FAQs on How to Speed Up WordPress Admin Dashboard

Why is my WordPress admin slow but my frontend is fast?

This is the most common pattern and it has a specific explanation. Your frontend is fast because it is being served from a page cache that pre-rendered pages serve to visitors without hitting PHP or the database. Your admin bypasses all caching.

Every admin page load is a live PHP and database operation. When the admin is slow but the frontend is fast, the problem is either application-level: a slow plugin, database bloat, no object caching, or a PHP version that is well behind current. The Query Monitor diagnostic step is the right starting point.

Does switching hosts actually improve admin speed?

Sometimes, but not always. If you are on shared Apache hosting with no object caching, switching to LiteSpeed-based hosting with Redis can produce a very significant admin speed improvement because the server architecture handles PHP and database workloads much more efficiently.

However, if the cause of your slowness is a badly coded plugin, a bloated database, or PHP 7.4, none of those problems are fixed by switching hosts. Always diagnose with Query Monitor before spending money on a hosting migration.

How much does fixing the WordPress admin speed actually matter for SEO?

Admin speed has no direct relationship with your search rankings. Google’s Core Web Vitals measure frontend performance for visitors, not authenticated admin sessions. The value of a fast admin is entirely about your own productivity and operational efficiency.

A slow admin does not hurt your rankings, but it does slow down the work you do to improve your site, which has an indirect compounding effect on every other aspect of your workflow.

Is it safe to disable WP-Cron?

Yes, provided you replace it with a server-level cron job. WP-Cron is not a service that runs independently- it is a hook that fires on page loads.

Disabling it and configuring a real cron job is strictly better: your scheduled tasks run at consistent, predictable intervals rather than being dependent on page traffic, and every page load is freed from the cron-check overhead.

The only risk is if you disable WP-Cron without setting up a replacement cron job, in which case no scheduled tasks will run. Follow the setup process in Fix 8 completely before deactivating WP-Cron.

Most WordPress users spend more time clicking than they should. You reach for the mouse to bold a word, click through three menus to add a block, drag to rearrange sections that keep slipping. It’s not a skill problem. It’s a habit problem.

WordPress keyboard shortcuts fix the habit. The ones in this guide are not a complete list of every shortcut that exists; that list is 85+ entries long and most of it you’ll never use. These are the 15 that actually change how fast you work, whether you’re a blogger, a store owner, or a developer managing client sites.

Each one includes the correct key combination for both Mac and Windows, because they’re different in WordPress and most guides get this wrong.

Keyboard shortcuts speed up editing. But they don’t touch plugin management, WooCommerce orders, user lookups, or template access. Commandify adds a command palette to WordPress (Cmd/Ctrl + K) that handles all of that. Free on WordPress.org.

Before You Start: Mac vs Windows in WordPress

WordPress uses two different shortcut systems and most guides only show one. Here’s the rule:

• For formatting shortcuts (bold, italic, undo, save): Windows uses Ctrl, Mac uses Cmd (⌘)
• For WordPress-specific shortcuts (publish, preview, add media): Windows uses Alt + Shift, Mac uses Ctrl + Option

This is important. If you’re on a Mac and you try Alt + Shift + P to publish, it won’t work. The correct Mac shortcut is Ctrl + Option + P. Every shortcut below shows both.

The 15 WordPress Keyboard Shortcuts Worth Learning

1. Open the Keyboard Shortcut Reference Anytime

Windows: Alt + Shift + H    Mac: Ctrl + Option + H

Start here. This shortcut opens a popup showing every available keyboard shortcut for whichever editor you’re currently in, block editor or Classic. You don’t need to memorize this entire article. Learn this one shortcut and use it as your reference whenever you need a reminder.

In Gutenberg, you can also access it from the three-dot menu in the top toolbar → Keyboard Shortcuts.

2. Save Your Draft Without Clicking

Windows: Ctrl + S    Mac: Cmd + S

Works in both the block editor and the Classic Editor. Saves the current state as a draft without publishing. Make this automatic- press it every few minutes while writing and you’ll never lose content to an accidental tab close or browser crash again.

3. Undo and Redo

Undo — Windows: Ctrl + Z    Mac: Cmd + Z
Redo — Windows: Ctrl + Y    Mac: Cmd + Shift + Z

Gutenberg maintains a deep undo history, far deeper than the Classic Editor ever did. You can step back through dozens of block changes. This makes experimentation safe- try a layout, don’t like it, undo your way back. Note that redo uses different keys on Mac vs Windows, which catches people out.

4. Publish or Update a Post

Windows: Alt + Shift + P    Mac: Ctrl + Option + P

Triggers the publish or update action depending on the post status. On an unpublished draft, it opens the publish panel. On an already-published post, it updates it immediately. Useful when you’re doing a round of quick content updates across multiple posts.

5. Insert a New Block Instantly

Shortcut: Type / on any empty block (Mac and Windows)

This is the highest-value Gutenberg shortcut for anyone who builds pages or writes long-form content. Type a forward slash on an empty line and the inline block inserter opens. Start typing the block name (“image”, “table”, “quote”, “heading”) and it appears. No toolbar clicking, no drag from the sidebar.

Once you build muscle memory for this, reaching for the + button will feel slow.

6. Duplicate Any Block

Windows: Ctrl + Shift + D    Mac: Cmd + Shift + D

Copies the selected block and places the duplicate directly below it. Useful when building repeating content structures- a set of feature cards, a series of FAQ blocks, or multiple variations of a CTA section. Much faster than copy-paste when you need the exact block type and settings preserved.

7. Move Blocks Up and Down

Move up — Windows: Ctrl + Shift + Alt + T    Mac: Cmd + Shift + Option + T
Move down — Windows: Ctrl + Shift + Alt + Y    Mac: Cmd + Shift + Option + Y

Drag-and-drop in Gutenberg works fine on short pages. On long pages with 20+ blocks, it’s imprecise and frustrating. These shortcuts move the selected block one position up or down with precision. Select the block, press the shortcut, repeat as needed.

8. Remove a Block

Windows: Ctrl + Shift + Alt + Z    Mac: Cmd + Shift + Option + Z

Deletes the currently selected block. Faster than right-clicking and choosing Remove Block from the context menu, especially when you’re cleaning up a page with blocks you no longer need. If you delete by mistake, Ctrl/Cmd + Z brings it back.

9. Open the Block List View

Windows: Ctrl + Alt + O    Mac: Ctrl + Option + O

Opens the List View panel, which shows every block on the page in a hierarchical tree. Invaluable on complex pages with nested blocks- columns inside groups, buttons inside columns, and so on. You can click any block in the list view to select it instantly rather than hunting for it on the canvas.

10. Toggle Distraction-Free Writing Mode

Windows: Ctrl + Shift + Alt + F    Mac: Cmd + Shift + Option + F

Hides the sidebar, the top toolbar, and all admin chrome. Only your content remains on screen. If you write long-form posts inside WordPress, this is the shortcut that transforms the block editor into something resembling a proper writing environment. Press the same combination to exit.

11. Switch Between Visual and Code Editor

Windows: Ctrl + Shift + Alt + M    Mac: Cmd + Shift + Option + M

Toggles between the visual block editor and the raw block markup (code editor). Useful when you need to inspect or manually fix block HTML- a common need when pasting content from external sources that imports with broken markup. Switch back with the same shortcut.

12. Bold, Italic, and Underline Selected Text

Bold — Windows: Ctrl + B    Mac: Cmd + B
Italic — Windows: Ctrl + I    Mac: Cmd + I
Underline — Windows: Ctrl + U    Mac: Cmd + U

Works in both editors. Select the text first, then apply the shortcut. These are the same combinations used in Word, Google Docs, and most text editors; so if you already use them elsewhere, they’re zero learning curve in WordPress.

13. Insert or Edit a Link

Windows: Ctrl + K    Mac: Cmd + K

Select any text in the block editor, press Ctrl/Cmd + K, and the inline link popover opens. Start typing a URL or a post title, WordPress searches your existing content in real time. Press Enter to apply. To remove a link, select the linked text and press Ctrl/Cmd + K, then choose Remove Link.

Note: in the Classic Editor, this same shortcut opens the Insert Link dialog, which works slightly differently.

14. Enable Comment Moderation Shortcuts

Setup: Users → Profile → check “Enable keyboard shortcuts for comment moderation”

Once enabled, you can moderate your entire comments queue without touching the mouse. J/K moves between comments. A approves, S marks as spam, D deletes, U sends back to pending, R opens the reply field. For high-volume sites, this turns comment moderation from a tedious clicking exercise into something you can process in under a minute.

These shortcuts must be enabled per user, they’re off by default.

15. Use Markdown-Style Formatting Shortcuts

Works in: Gutenberg block editor (type and press Space or Enter to apply)

Most people don’t know Gutenberg supports Markdown-style shortcuts directly in the editor. Type these at the start of an empty block and press Space or Enter:

• ## → H2 heading   ### → H3   #### → H4
• * or – → unordered list
• 1. → ordered list
• > → blockquote
• — → horizontal divider
• `code` → inline code

These are faster than clicking toolbar buttons for common formatting tasks and work entirely within your natural typing flow.

Quick Reference: All 15 Shortcuts

One Thing These Shortcuts Can’t Do and You Choose Commandify Plugin

Everything above makes editing faster. But editing is only part of what you do in WordPress.

Finding a WooCommerce order. Deactivating a plugin. Looking up a user by email. Clearing cache. Switching between staging and live. Opening an Elementor template without loading the full builder first. These are the tasks that actually eat admin time and no keyboard shortcut covers them.

That’s the problem Commandify solves. It adds a true command palette to WordPress- press Cmd/Ctrl + K from anywhere in wp-admin and type what you want to do.

• Type order 4152 → jumps directly to that WooCommerce order
• Type deactivate jetpack → deactivates Jetpack without visiting the Plugins screen
• Type @sarah → opens Sarah’s user profile with actions ready
• Type clear cache → clears cache with one confirmation
• Type maintenance → toggles maintenance mode on or off

The fuzzy search handles typos and partial input, so you don’t need to type exact command names. Commandify Pro extends this to the full WooCommerce command suite (orders, products, variations, customers, coupons) and adds Elementor, Bricks Builder, and Contact Form 7 integrations.

If you’ve found yourself switching between WordPress users repeatedly for testing or client support, there’s a command for that too.

Install Commandify free from WordPress.org– no setup required. Press Cmd/Ctrl + K and start using it immediately. See Pro pricing for WooCommerce and page builder integrations.

Two Common Issues to Know About

Browser shortcuts can conflict with WordPress shortcuts

Some browser extensions (particularly tab managers, password managers, and accessibility tools) use the same key combinations as WordPress. If a shortcut doesn’t work, check whether an extension is intercepting it.

In Chrome, you can audit extension keyboard shortcuts at chrome://extensions/shortcuts. Firefox extensions like Keyconfig can create similar conflicts.

Cmd + K opens the command palette, not a link dialog, in Gutenberg

Since WordPress 6.3, pressing Cmd/Ctrl + K without text selected opens the WordPress command palette. With text selected, it opens the inline link popover. This is intentional but confuses users who muscle-memory the old “press Cmd+K anywhere to insert a link” behavior from the Classic Editor. Select your text first, then press Cmd/Ctrl + K.

FAQs on WordPress Keyboard Shortcuts

Why are my WordPress keyboard shortcuts not working?

The most common reasons: you’re using the wrong key combination for your OS (Alt + Shift on Windows, Ctrl + Option on Mac for WordPress-specific shortcuts), a browser extension is intercepting the shortcut, or you’re on the wrong editor- some shortcuts are Gutenberg-only and won’t work in the Classic Editor.

Try pressing Alt + Shift + H (Windows) or Ctrl + Option + H (Mac) first to confirm shortcuts are working at all.

What is the shortcut to publish a post in WordPress?

Alt + Shift + P on Windows, Ctrl + Option + P on Mac. On a draft post, this opens the publish confirmation panel. On an already-published post, it updates the post immediately. There’s no single-key “publish without confirmation” shortcut- WordPress always shows the publish panel on first publish to prevent accidental publishing.

Do WordPress keyboard shortcuts work in WooCommerce?

Standard WordPress keyboard shortcuts work in the post and page editor, which includes WooCommerce product pages. They don’t work in the WooCommerce Orders, Customers, or Reports screens- those are custom admin pages with their own interface.

For keyboard-driven navigation across WooCommerce, Commandify Pro’s WooCommerce command suite is the practical solution.

What is the difference between Gutenberg and Classic Editor shortcuts?

Formatting shortcuts (bold, italic, undo, save, links) work in both. Block-specific shortcuts (inserting blocks with /, duplicating, moving, List View, distraction-free mode, code editor toggle) only work in Gutenberg.

The Classic Editor has its own set of Alt + Shift shortcuts for formatting and navigation that Gutenberg replaced with the block-centric shortcuts. If you’re still on the Classic Editor, pressing Alt + Shift + H shows you the full Classic shortcut list.

Can I add custom keyboard shortcuts to WordPress?

WordPress doesn’t have a native interface for creating custom shortcuts. You can use browser-level tools like AutoHotkey (Windows) or Keyboard Maestro (Mac) to create system-wide shortcuts that trigger wp-admin actions.

For admin-level actions like running commands, clearing cache, or managing plugins, Commandify Pro lets you configure the trigger key and customize command visibility per user- which is the closest native WordPress gets to custom shortcut management.