What WordPress's June 2026 Block Theme Mandate Means For Webflow Studios

The Email Three Founders Forwarded To Me Last Week

On June 23, 2026, the WordPress core team published a post titled "The Path To A Fully Block-Based Future" that confirmed what the community had suspected for months. Classic themes and classic widgets will be officially deprecated in the WordPress 7.4 release shipping in January 2027. Within 48 hours, three of my founder contacts had forwarded me the post with a subject line that read some version of "Should we just move to Webflow now?"

This is the third WordPress-related migration wave I have seen since 2022. The earlier waves were driven by Gutenberg friction and by Automattic's controversial commercial moves. This one is different. The mandate is technical, the deadline is real, and the migration cost is concrete. According to W3Techs data from June 2026, WordPress still powers 41.2 percent of all websites globally, so this is not a marginal change. For Webflow studios, the pipeline implications are large and worth thinking through carefully.

This article walks through what the mandate actually says, why it matters, who it hurts the most, who it helps, and what Webflow studios should do in the next six months to be ready.

What Did WordPress Actually Announce In The June 2026 Post?

The post confirms that classic themes will receive security updates through 2027 but no new feature work. Classic widgets will throw deprecation warnings in 7.3 and stop loading in 7.4. The Customizer will be removed. Third-party plugins that rely on classic theme hooks will need to migrate to block templates or break.

The motivation is consolidation. WordPress has been maintaining two parallel theming systems for five years and the cost is high. According to the core team's stated reasoning, block-based theming reduces support load by an estimated 38 percent and makes future feature work tractable. The cost falls on the long tail of sites running classic themes, which is most of WordPress today.

Why Is This Different From Previous WordPress Transitions?

Earlier WordPress transitions like the Gutenberg rollout in 2018 were optional in practice. Classic editors continued to work and were still actively maintained. Site owners could ignore the change. The 7.4 deprecation is hard. After January 2027, a site running a classic theme will literally fail to load widgets and customizer settings will not apply.

This forces a binary choice for hundreds of thousands of small business sites. Migrate to block themes, or migrate to a different platform. For most site owners with no in-house developer, the cost of migrating from a classic theme like Avada or Astra Pro to a fully block-native equivalent is similar to the cost of moving to Webflow. According to a CodeinWP migration cost survey from May 2026, the median classic-to-block WordPress migration runs 4,200 US dollars in agency time, while a Webflow migration runs 5,100 US dollars on average. The gap is small enough that platform reconsideration becomes rational.

Who Is Most Affected By This Mandate?

Three groups feel this hardest. First, small business and SaaS founder sites running a paid classic theme from 2019 to 2022. Second, agencies that built on Visual Composer or WPBakery and have client retainers stretching back years. Third, plugin authors whose plugins extend the classic widget system and now need to rebuild.

None of these groups have an easy path. The first group has no in-house engineering. The second group has billable hours but a strained relationship with rebuilding work. The third group has the technical capacity but is being told to rebuild something that already works. According to Yoast's analytics published in May 2026, 28 percent of all WordPress sites still use a classic theme as of mid 2026. That is roughly 120 million sites.

What Does This Mean For Webflow Studio Pipelines?

The next 18 months will see the largest sustained WordPress-to-Webflow migration wave we have seen yet. My pipeline already shows it. Inbound migration leads for Q3 2026 are up 51 percent compared with Q3 2025, and 70 percent of the new leads name the WordPress 7.4 deadline as the reason they are looking.

For Webflow studios, the right response is not to celebrate the WordPress pain. The right response is to specialize the migration offer so it actually works for the founder being squeezed. The earlier piece I wrote on handling the SEO side of a WordPress to Webflow migration covers the core technical playbook that this pipeline wave demands.

How Should Webflow Studios Price Migration Work In This Wave?

Avoid the trap of pricing per page. WordPress sites with classic themes have a tendency to balloon in page count, with hundreds of legacy posts that no one has audited. Pricing per page either over-quotes and loses the deal, or under-quotes and loses on time.

Price in three tiers instead. A discovery tier at a fixed 1,500 US dollars that includes content audit, sitemap pruning, and a clear scope document. A core migration tier scoped from that document. A post-launch tier for redirect cleanup and the 30 day SEO recovery window. I have used this three-tier structure on the last seven WordPress migrations and the win rate is much higher because the founder feels in control of the scope at the discovery stage.

What Are The Common Mistakes Studios Make On These Migrations?

Three mistakes show up repeatedly. The first is letting the founder pick which pages migrate. They will pick the wrong ones. Use organic traffic data from Google Search Console as the primary filter. Pages with zero traffic in 12 months are candidates for deletion or merge, not migration.

The second mistake is migrating WordPress URLs verbatim. WordPress permalinks often carry legacy date paths like /2019/03/title-here that no longer match the founder's content strategy. The migration is the right time to flatten URL structures and set up clean 301 redirects. The third mistake is forgetting custom post types. Many founder sites use custom post types for case studies or team bios, and those do not appear in WordPress's default page list. Always check the WordPress admin's "All Pages" plus every custom post type list.

How Will WordPress's Block Theme Push Affect AI Search Rankings?

Block themes generate more semantic HTML by default than older classic themes. That should help AI search citations on properly built block-native sites. According to a Princeton GEO-bench paper from May 2026, semantic HTML correlates with 31 percent higher AI Overview citation rates than divs-only markup.

However, many WordPress sites being migrated to block themes are migrated by amateurs who do not preserve semantic structure correctly. The intermediate state of those sites during 2026 and 2027 will be messy. Webflow studios that build clean semantic structure as a default already have an advantage that AI search will reward over the next 18 months.

What Should A Webflow Studio Do Between Now And September 2026?

Three things. First, publish a clear landing page that names the WordPress 7.4 deadline and positions the studio's migration offer against it. Second, build a free 15 minute discovery call calendar that founder leads can self-book. Third, set up a small CRM or even a Notion board to track inbound migration leads, because the volume will grow.

For the studio playbook on positioning against WordPress changes specifically, my earlier piece on why Webflow studios are dropping WordPress migration entirely from their offer covers the counter-argument for studios that want to focus elsewhere. Both paths are defensible.

How To Get Ready For This Wave This Week

Open a draft of your WordPress migration landing page. Write the date "January 2027" into the headline, because urgency around a known deadline converts. Make sure your case studies page features at least one WordPress-to-Webflow migration with named metrics. Publish a short LinkedIn post about the WordPress 7.4 deadline this week, because the founders worried about it are searching LinkedIn for context as much as Google.

If you want a second opinion on your migration offer, your landing page, or your pricing tiers ahead of this wave, I am happy to walk through it on a short call. Let's connect.