What’s New in WordPress 6.9

Getting WordPress updates wrong breaks revenue, support queues, and trust.

You feel that pressure every time a new release drops.

WordPress 6.9 raises the stakes with big user features and deeper developer APIs in one release.

If you skipped the beta chatter, you’ll want the highlights and the how-to.

I’ll show you exactly what’s new in wordpress 6.9 and how to switch it on, test it, and verify if it works.

We’ll cover the user-facing features first. Then the new blocks, editor upgrades, developer APIs, performance wins, changelog scope, and a safe upgrade plan.

You’ll get step-by-step UI paths, quick code where it’s unavoidable, and verification steps for every change.

Here’s the payoff. You’ll leave with a complete 6.9 rollout plan that you can run on your staging site today.

Worth noting: Over 900 contributors shipped this release, with 70+ accessibility fixes along the way WordPress 6.9.

That’s not a patch release.

The takeaway? Upgrade right, and you’ll ship a faster, more accessible, and more capable site without surprises.

Core User Features: Notes, Command Palette, and Block Visibility

You get three quality-of-life features that change daily workflows. Notes, a remix of the Command Palette, and block-level visibility controls.

• Notes adds in-editor comments you can pin to blocks or text. Less Slack screenshots, more context where the work happens.
• Command Palette speeds up keyboard-first actions. Search for commands, not menus.
• Block Visibility lets you hide or show blocks based on conditions, like device size or user state.

1) Add Notes For Block-Level Collaboration

Notes are inline comments you attach to selected content blocks or ranges.

They live inside the editor.

With this feature, you get to keep feedback where the edit happens, so reviewers stop guessing context.

How to do it:

• Go to Pages or Posts, click Edit for any page.
• Select a block, open the toolbar, and click Add note. Type your comment and @mention a user if needed.
• Click Resolve when addressed, or Reopen from the note panel.

Verify it worked:

• In the editor, click the Notes icon in the top bar. You should see your note tied to the block.
• Switch to another user, refresh the editor, and confirm the note appears in their view.

One mistake to be weary of is perhaps leaving notes on draft revisions that never get merged.

Before publishing, open the Notes panel and resolve any stale threads.

A great usecase for notes is using them to document why you used a custom CSS class on a block.

Six months from now, future-you will thank you.

2) Move Faster With The Command Palette

The Command Palette is a quick search UI for actions and navigation. Think Spotlight, but for the editor.

Your hands stay on the keyboard, and repetitive tasks get quicker.

How to do it:

• In the editor, press Ctrl+K on Windows or Cmd+K on macOS.
• Start typing, for example “Insert Accordion” or “Switch to Code Editor.”
• Use arrow keys to choose a command, press Enter to execute.

Verify it worked:

• Run “Open Preferences” from the palette. The Preferences modal should open instantly.
• Run “Toggle List View.” The left List View panel should appear or hide as expected.

Common mistake: Searching for submenu commands that only appear when a block is selected.

You need to select the target block first, then open the palette.

The palette also surfaces settings and templates. It’s faster than drilling into the top-right kebab menu.

3) Control Block Visibility Without Custom Code

Block Visibility rules let you show or hide a block based on conditions like device size, login state, or template context.

This way you stop cloning pages for small variations and keep logic within the block tree.

How to do it:

• Select any block, open the right Block settings sidebar.
• Expand Visibility. Choose a rule like “Hide on mobile,” “Show to logged-in users,” or “Only on single posts.”
• Click Update. Preview the page in responsive mode to confirm.

Verify it worked:

• Click the Preview dropdown, choose Mobile. The hidden block should be gone.
• Open a private browser window and view the page to test logged-out visibility rules.

Common mistake: Stacking conflicting rules, like hiding on desktop and showing on large widths via custom CSS.

You want to keep visibility logic in one place to avoid confusion.

Speaking of which, visibility rules respect theme breakpoints, so mismatched custom CSS can override them. Test across devices.

New Blocks: Accordion, Math, Terms Query, and Time to Read

You get four practical blocks that used to require plugins or hacks. Now they’re core, consistent, and theme-friendly.

• Accordion handles FAQs and collapsible content.
• Math renders formulas with proper typesetting.
• Terms Query lists categories or custom taxonomy terms with tight control.
• Time to Read displays a calculated reading estimate.

4) Build FAQs Fast With The Accordion Block

Accordion creates collapsible sections with a header and hidden body content.

This means you can ship accessible FAQs and accordions without shortcode spaghetti.

What’s not clear, however, is whether this supports FAQ schema that can provide rich results in search engines result pages (Google, Bing, etc).

How to do it:

• In the editor, click the plus icon and search for Accordion. Insert it.
• Click Add Item to create Accordion Item blocks. Enter a title and content per item.
• In block settings, toggle Allow multiple open or set Initial state to closed.

Verify it worked:

• In the front-end, click an accordion header. It should expand and collapse smoothly.
• Run the URL in Lighthouse and check the Accessibility score for no interactive control issues.

What you don’t want to do, though, is nesting accordions 5 levels deep. no one enjoys endless expansion.

Keep everything simple for keyboard navigation and also screen readers.

5) Render Equations With The Math Block

For very long time now, adding mathematical expressions to wordpress was nothing short of a nightmare, plus plugins that you could barely get them to work.

Luckily for us, obsessed with data, WP has heard our cries. Introducing

Math block!

As the name suggests, Math block supports formatted equations, using LaTeX-style input for clean display.

Why it matters: Education, finance, and scientific content looks professional and stays readable.

How to do it:

• Insert a Math block from the block inserter.
• Type or paste your LaTeX-style expression, for example \int_{0}^{\infty} e^{-x} dx.
• Use block settings to adjust inline display or block-level formatting.

For the formula above, the results look like this:

Verify it worked:

• View the front-end and confirm the equation renders, not raw markup.
• Use your browser’s View Source to ensure no script errors near the math output.

Just be careful not to paste unsupported macros. Keep formulas to standard LaTeX where possible and test on mobile.

6) List Categories With The Terms Query Block

Terms Query pulls taxonomy terms like categories or tags and displays them in a layout.

With this new block, you can build directory-style lists, tag clouds with control, or category indexes inside the editor, the same way you build blog pages using Query Loop Block.

You will need to include other details / blocks inside the term template. By default, it only has Terms name, but you can add:

• Term Count
• Term Description (if your theme supports it)
• Terms custom fields, if any

How to do it:

• Insert Terms Query.
• Choose the Taxonomy in the block settings, for example Categories.
• Set Order by (name, count) and Order (ASC, DESC), then set Number of terms.
• Customize the inner Term template, adding name, link, and description as needed.

How to verify:

• Preview and ensure the number, order, and taxonomy match your settings.
• Click a term link to confirm it routes to the correct archive page.

Not working?

You likely forgot to include the inner template content. Open List View and add the Term Name block inside the template to display something.

7) Show Reading Length With Time To Read

Time to Read estimates how long a post takes to be read, based on word count and a default reading speed.

Setting expectations improves long-click rates, which are the times users stay on your page instead of bouncing back.

How to do it:

• Insert the Time to Read block at the top of your post template or inside a post.
• In settings, adjust Words per minute if your audience reads faster or slower.
• Style it with your theme’s typography settings to match headings or meta.

Verify it worked:

• Publish and view the post. You should see something like “5 min read.”
• Update the post to double the length and refresh. The time should increase accordingly.

Common mistake: Hiding it behind the fold. Keep it near the title or metadata where readers look first.

The ideal place to insert this should be near the title or metadata as this is whre readers tend to look first.

This doesn’t do much for your seo metrics though, but it’s nice to have.

Editor Enhancements: Drag-and-Drop, Fit Text, and Allowed Blocks

Beyond new features, and blocks, this rollout ships with new improvements to the already existing features and tools.

• The editor got smoother and safer.
• Drag-and-drop is less jittery
• Fit Text gives you hero-worthy typography, and
• Allowed Blocks prevents editors from going rogue.

I’ve rolled these out for some of my clients who want speed without losing editorial guardrails.

And honestly, these three changes cut editing time and cleanup emails by a lot.

8) Reorder Content Faster With Improved Drag-And-Drop

You can drag blocks in the canvas or in List View with better indicators and drop targets.

Reorganizing long content or complex layouts stops feeling like a game of chance.

How to do it:

• Open List View from the top toolbar to see your block tree.
• Click and drag a block handle up or down. Watch the live preview line for the drop location.
• For nested blocks, expand the parent, then drag the child to the new position.

Verify it worked:

• Switch between List View and the canvas to confirm the block moved where you expected.
• Undo with Ctrl+Z or Cmd+Z, then redo, to check stability.

9) Make Headlines Pop With Fit Text

Fit Text is a typography control that auto-scales text to fit a container, keeping multi-line headings balanced.

You get consistent hero headings across screen sizes without custom CSS hacks.

How to do it:

• Select a Heading block or a group containing text.
• In the right sidebar, open Typography and enable Fit text.
• Set a Minimum font size and Maximum font size to control scaling.
• Looks like we have a dedicated block for this stretchy paragraph.

Verify it worked:

• Resize your browser window and confirm the heading scales smoothly within the container.
• In PageSpeed Insights, run a test and ensure no CLS (Cumulative Layout Shift) warnings are introduced.

10) Lock Down Creativity With Allowed Blocks

Allowed Blocks lets you restrict which blocks can be used in a pattern, template part, or entire post type.

This is important as you can now prevent off-brand layouts and keep editors focused on approved components.

How to do it:

• Go to Appearance → Editor → Templates and open a template or template part.
• Select the container block, open the sidebar, and find Allowed blocks.
• Choose the block types you allow. Save the template.

Verify it worked:

• Back in a post, try inserting a disallowed block inside that container. It should be unavailable or show a restriction notice.
• In List View, confirm existing disallowed blocks are flagged or removed.

Common mistake: Over-restricting too early. Start with templates and patterns, not site-wide, so you do not block legitimate use cases.

If you use custom roles, make sure edit_theme_options or custom capabilities align with your restrictions. Conflicts can make blocks appear allowed but fail on save.

Developer APIs: Abilities API, Block Bindings, and Interactivity Updates

Developers get deeper control over who can do what, how blocks connect to data, and richer client-side interactions.

• The Abilities API centralizes capability and feature gating for editor features.
• Block Bindings expands how block attributes connect to meta or external sources.
• Interactivity updates make small front-end behaviors easier without full frameworks.

11) Gate Features With The Abilities API

Abilities API exposes granular “abilities” for editor actions and features, mapped to roles or context.

You can hide or disable features for certain users without forking the editor.

How to do it:

1. In a custom plugin, add a filter for abilities. Example skeleton:

<?php
// plugin.php
add_filter( 'wp_abilities', function( $abilities, $context ) {
  // Disable pattern creation for Contributors.
  if ( current_user_can( 'contributor' ) ) {
    $abilities['patterns']['canCreate'] = false;
  }
  return $abilities;
}, 10, 2 );

2. Activate your plugin in Plugins → Installed Plugins.
3. Log in as a Contributor and open the editor to test pattern creation.

Verify it worked:

• As a Contributor, open Patterns in the editor. The “Create pattern” option should be missing or disabled.
• As an Administrator, the option should be present.

Common mistake: Checking roles with current_user_can( 'contributor' ), which is not a capability. Map to capabilities like edit_posts and check context.

The 6.9 dev notes outline editor-facing abilities and how they map to capabilities.

12) Connect Content With Expanded Block Bindings

Block Bindings link a block attribute, like a heading’s text or an image’s alt, to a data source such as post meta or global options.

You reuse the same block template across posts and let data flow without manual duplication.

How to do it:

• In the editor, select a block that supports bindings, like Paragraph or Image.
• In the block toolbar or sidebar, click Connect to data.
• Choose Post Meta and select a key, for example _hero_subheading. Save.

To verify:

• Change the post meta value in Post → Custom Fields or via your custom meta UI.
  
  Refresh the editor and confirm the block updates.
• On the front-end, view source and ensure the bound value is rendered without escaping issues.

A common mistake that you’re likely to encounter is binding to meta that is not registered with show_in_rest.

To solve this, just register it with register_post_meta to make it available to the editor.

13) Add Small Behaviors With Interactivity API Updates

The Interactivity API provides lightweight directives for client-side state and events, like toggles or filters, without a full JS framework.

With this you can build rich interactions, keep hydration minimal, and avoid performance debt.

How to do it:

1. Enqueue a script with interactivity support in your theme’s functions.php:

wp_register_script( 'site-interactivity', get_template_directory_uri() . '/interactivity.js', array( 'wp-interactivity' ), null, true );
wp_enqueue_script( 'site-interactivity' );

2. In HTML or a block template, add interactive attributes:

<button data-wp-interactive
        data-wp-on--click="state.isOpen = !state.isOpen">
  Toggle
</button>
<div data-wp-bind--hidden="!state.isOpen">Panel content</div>

3. In interactivity.js, optionally set initial state:

wp.interactivity.store( 'site', {
  state: { isOpen: false }
});

Verify it worked:

• Click the button on the front-end. The panel’s visibility should toggle without a page reload.
• In DevTools, confirm no JS errors and minimal network calls.

When enqueuing your script, you want to depend on wp-interactivity . Without this dependency, directives won’t work.

Start with one interactive component per template. Keep the state local and avoid global stores until you need them.

Performance and Accessibility Improvements with Benchmarks

Core also rolled in performance improvements like on-demand CSS and better fetchpriority handling for key images.

You can expect wins in LCP, the Largest Contentful Paint metric.

Research backs this up: independent testing shows 2.8 to 5.8 percent gains tied to on-demand CSS and fetchpriority improvements.

14) Ship Leaner CSS With On-Demand Loading

---

With on-demand CSS, WordPress only loads styles for the blocks used on a page.

Styles for unused blocks are not loaded.

When a page loads, the browser must process all CSS before it can show anything on screen. It does this by building the CSSOM (CSS Object Model).

In simple terms, the CSSOM is the browser’s internal map of all your CSS.

The process looks like this:

• The browser downloads your CSS
• Reads and understands it
• Turns it into a structured model called the CSSOM

The CSSOM is then combined with the HTML structure (the DOM) so the browser can decide:

• which styles apply to which elements
• how the page should look
• when the page can be painted on screen

Less CSS thus means the browser builds the CSSOM faster, so visible content appears sooner.

How to do it:

• Update to WordPress 6.9 via Dashboard → Updates → Update Now.
• Do not remove core block styles globally. Delete any wp_dequeue_style( 'wp-block-library' ) overrides.
• In theme.json, keep styles modular. Avoid large global CSS files that duplicate block styles.

Verify it worked:

• Run Lighthouse and check Unused CSS and total CSS size.
• Use WebPageTest filmstrips. The first visual render should appear earlier.

---

Why Hosting Is the Silent Decider in WordPress 6.9

WordPress 6.9 leans into:

• REST driven editor features
• Dynamic block rendering
• Smarter asset loading
• More JavaScript in core flows

That combination exposes weak hosting instantly.

Slow disks, underpowered PHP workers, and aggressive limits no longer hide behind caching.

If your hosting struggles:

• Editor saves feel random
• Previews time out
• “Publishing failed” errors appear
• Updates get postponed out of fear

At that point, WordPress becomes the scapegoat. You need a better host, and one that doesn’t cost an arm and a leg;

---

Best WordPress Hosting You Can Trust

Here’s the simple truth.

You don’t need expensive hosting.
You need reliable WordPress hosting.

That’s where Olitt fits cleanly into this story.

Here at Olitt, we now offer WordPress hosting for $9.99 per year.

Not a monthly teaser.
Not a bait and switch.
One payment. One year.

What this unlocks for WordPress 6.9:

• Affordable staging environments
• Stress free testing
• No hesitation to upgrade
• No pressure to delay core releases

This is especially useful if you:

• Run multiple content sites
• Maintain client demos
• Build MVPs
• Manage blogs where margins matter
• Want WordPress stability without recurring anxiety

Instead of asking “Can we afford to test this update?”
You just test it. Perid. Did I mention money back guarantee? We got that too.