WordPress 7.0 shipped on May 20, 2026, and if you have not updated yet, you are running the most outdated major version of WordPress since the block editor landed in 2018. That is not a scare tactic. It is just math. Two months is enough time for the early bugs to get patched and for the community to surface the real gotchas. The update is stable, and the features are worth your attention.

This is the release that carries over a year of accumulated development. The WP Engine lawsuit and Automattic's pause on contributions meant 2025 only delivered WordPress 6.8 and 6.9. WordPress 7.0 absorbed all the pent-up feature work from that gap, and it shows. There are five changes that actually matter for anyone running a WordPress site, and none of them require you to be a developer.

The AI layer is real, and it is not what you think

The headline feature is a full AI infrastructure built into WordPress core. Before you roll your eyes — no, WordPress is not trying to be ChatGPT. The team took the smarter route: they built the plumbing, not the faucet.

The Abilities API lets any plugin register what it can do in a standard format. The MCP Adapter exposes those abilities to AI tools like Claude, Cursor, and VS Code. The WP AI Client gives plugin developers a single integration point that works with OpenAI, Anthropic, Google, or whoever comes next. No vendor lock-in.

What does this mean for you? Your SEO plugin can now tap into AI for content analysis through a native WordPress interface instead of bolting on a third-party API. Your WooCommerce store can generate sales summaries through an AI assistant that actually understands your site structure. Your form plugin can summarize submissions without you building a custom integration.

None of this happens automatically. You still need plugins that use these new APIs. But the foundation is there now, and the plugin ecosystem is already moving. If you run WordPress for any kind of business, this is the infrastructure that will make AI features feel native instead of duct-taped on.

PHP-only blocks: finally, sanity for developers

If you have ever built a custom WordPress block, you know the pain. You need Node, wp-scripts, a build pipeline, React knowledge, and a bunch of boilerplate just to render some HTML on the server. WordPress 7.0 introduces PHP-only blocks, and it changes the math completely.

You can now register and render blocks entirely in PHP. No JavaScript, no React, no build step. For blocks that just display data from a WP_Query or render some structured content, this is dramatically simpler. Developers can ship custom blocks in minutes instead of hours, and the code is cleaner because there is less of it.

This does not replace JavaScript blocks for interactive use cases. If your block needs drag-and-drop or real-time editing, you still need the full Gutenberg stack. But for the majority of custom blocks that just display content in a specific layout, PHP-only is the way forward.

The admin dashboard got a facelift

The WordPress admin area has looked roughly the same since 2015. WordPress 7.0 changes that with a gradual modernization that brings the backend closer to the Site Editor's design language. New dropdowns, tooltips, and panels create a more consistent interface. Page transitions are smoother. Loading times are better.

The most practical change is client-side image processing. Uploaded images now get processed in your browser instead of on the server. This means faster uploads, less server load, and better support for modern image formats. If you manage a site with lots of media, you will feel this immediately.

The Site Editor keeps getting better

Full Site Editing continues to mature. You can now edit nested blocks, synchronized patterns, and templates without leaving the editor. New core blocks include icons and breadcrumbs. Paragraphs support native indentation and multi-column layouts. Image blocks respect aspect ratios at wide and full alignment.

These are not flashy features. They are the steady accumulation of small improvements that make the block editor genuinely usable for building complete pages instead of just writing posts. If you tried Full Site Editing a year ago and gave up, it is worth another look.

What to do right now

Update to WordPress 7.0. But do it smart. Back up your site first. Test on a staging environment if your hosting provider offers one. Check your theme and plugin compatibility — most popular plugins have already released 7.0-compatible versions, but older or unmaintained plugins may not have.

The update is available directly from your WordPress dashboard. If your site runs on managed hosting, your provider may have already tested and validated it. Check their documentation before you start.

WordPress 7.0 is not just another version number. It is the release that puts AI infrastructure, modern developer tools, and a refreshed interface into every WordPress site. The question is not whether to update. It is how long you want to stay behind.

Sources: Raidboxes WordPress 7.0 guide, ThemeRex WordPress 7.0 breakdown, WordPress 7.0 RC4 announcement