June 4-6, 2026 | ICE Kraków Congress Centre, Kraków, Poland
WordCamp Europe 2026 will bring the WordPress community together in Kraków, Poland, from June 4–6 for Contributor Day, two conference days, and a program shaped by the ideas, tools, and people moving WordPress forward. This year’s schedule includes two official keynotes, hands-on workshops, panels, and sessions across development, accessibility, artificial intelligence, content, search, business, education, security, and community.
The program offers a broad view of how WordPress is used today: as publishing software, a framework for building at scale, a tool for business growth, and a global open source project shaped by contributors around the world. Whether you build with WordPress, write for the web, support clients, teach new learners, or contribute to the project, WordCamp Europe offers a chance to learn from practical examples and connect them to the platform’s future.
The keynote sessions at WordCamp Europe 2026 will give attendees two ways to look at WordPress today: through a large-scale institutional adoption story and through a broader closing reflection on where the project is headed. These sessions anchor the program while connecting many of the themes that appear throughout the conference, from infrastructure and governance to contribution, innovation, and the future of the web.
Joachim Valdemar Yde and Francisco Borges Aurindo Barros will share how CERN is adopting WordPress as its future content management system. Their keynote will explore the governance, infrastructure, and migration work behind moving more than 800 websites onto a customized WordPress Service, offering a look at WordPress on an institutional scale.
Ma.tt Mullenweg will close WordCamp Europe 2026 with a broader look at WordPress, the open web, and the ideas shaping what comes next. As the event’s final keynote, this session will bring together many of the conversations happening across Contributor Day, sessions, workshops, and community gatherings throughout the week.
Program Themes to Watch at WCEU 2026
The rest of the WCEU themes are organized around topics that reflect the breadth of the WordPress ecosystem. These themes give attendees a way to follow the sessions most relevant to their work, from building better sites and improving content discovery to growing sustainable businesses, strengthening security, expanding access, and supporting the people and communities behind the project.
Search, Visibility, and Discovery
Search continues to change, but helping people find the right information remains central to the web. WCEU’s search and SEO sessions look at how AI-generated answers, generative engine optimization, shifting user habits, and new discovery platforms are changing visibility for publishers, businesses, and builders. Sessions include Panel: The Future of SEO, with Kacper Bartoszak, Pam Aungst Cronin, Alex Moss, David Cuesta, and Jovana Smoljanovic Tucakov, as well as Emma Young’s AI Search: Why Your Whole Company Should Care, which looks at why AI-native discovery now affects content, development, partnerships, and business strategy.
AI and the Future of Building
Artificial intelligence has a dedicated presence at WordCamp Europe 2026, with sessions that move beyond general discussion and into practical use cases for marketing, product work, development, and site management. Vito Peleg’s Agentic AI & WordPress: From Prompts to Tools & Systems will explore how teams can move from simple prompts to AI workflows that execute tasks, while Monika Dimitrova’s AI Won’t Save Your Marketing (but it might save your time and money) focuses on how small businesses can use AI without losing the strategy and identity that make their work effective.
Accessibility is part of building a better web for everyone, and WCEU’s accessibility sessions give attendees practical ways to make digital experiences more usable, inclusive, and sustainable. This theme connects directly to WordPress’s project values, from how content is structured to how themes, plugins, and interfaces are designed. For designers, developers, content creators, and project leads, these sessions offer a chance to make accessibility part of everyday decisions rather than a final step at the end of a project.
Content, Writing, and Communication
Content and writing sessions at WCEU will focus on how clearer communication helps users find what they need, teams share what they know, and communities make information easier to understand. Pooja Sanwal’s Why Writing Still Matters in a Video-First Internet looks at the role of written content as video continues to dominate online traffic, Fernando Tellado’s Do You Really Need an SEO/GEO Pugin for WordPress? explores what WordPress can already do for visibility, and Birgit Olzem’s Documentation as a Love Language for the Future You looks at how simple documentation practices can help teams and communities preserve knowledge.
Security and Trust
Security remains central to maintaining websites people can rely on. WCEU’s security-focused sessions look beyond basic reminders and into the risks, systems, and decisions that shape safer WordPress experiences. The broader program includes talks on AI-assisted spam and bot detection, plugin permissions, and secure headless WordPress architectures, giving attendees practical ways to think about resilience, trust, and responsible site management.
WordCamp Europe 2026 will bring together many parts of the WordPress ecosystem in one place: software, publishing, business, design, education, and community. The keynotes and theme-based sessions offer a broad look at how WordPress is being used today and how contributors, builders, and users are preparing for what comes next.
Explore the full WordCamp Europe 2026 schedule and choose the sessions that match how you use, build, teach, support, or contribute to WordPress. Tickets are available now for attendees joining the community in Kraków. All sessions will be live streamed. Keep checking back for updates.
Kraków is calling. See you at WordCamp Europe 2026!
Ever logged into WordPress to publish a post, only to end up spending hours on admin tasks?
It happens more often than we probably want to admit. You meant to write, but then you noticed yesterday’s orders needed checking. A landing page needed updating before tomorrow’s promo. And your form needs to be integrated with your email list. An hour disappears before you’ve written a single sentence.
What if you could have an AI agent built right into WordPress… one that can handle all of that admin work for you?
Imagine opening your dashboard and just asking: “How many orders came in yesterday?” Answered. “Update my About page to mention our new location.” Done. “When someone fills out my contact form, send me a Slack message and add them to my newsletter.” Set up… all it takes is a single line request in plain English.
That kind of help has never existed inside WordPress… Until now!
Today, I’m excited to introduce Uncanny Agent, the first true AI assistant built natively for WordPress.
As you may know, Uncanny Automator is a no-code automation plugin, used by over 50,000 websites, that connects your WordPress plugins, sites and apps. With Uncanny Agent, the AI assistant built within the plugin, you can ask any questions about your site or tell it what you need done…and it takes care of it for you.
Why Uncanny Agent?
Over the last two years, the #1 question I’ve received from WPBeginner readers is: “How can I use AI to save time on my WordPress site?”
Most of the answers floating around are weak. You can type in a prompt in ChatGPT and follow its instructions manually. Or you can spend hours building an automation setup, only to replace manual work with automation management.
The problem is that most AI chatbots can only talk about WordPress in general terms. They recommend generic tutorials and broad advice because they don’t actually have access to your WordPress site or your plugins. That means you can’t ask questions like:
Which products sold best last week?
Can you edit a blog post and make certain changes?
Which WooCommerce orders are still pending?
Why isn’t the WooCommerce checkout redirect firing?
That’s a real problem for small business owners. You don’t typically have a developer to call or an operation team to work for you. When you need an answer about your site, you need it instantly, not after an hour of clicking through dashboards.
So, I asked myself: what if every WordPress user could have an AI assistant right inside WordPress?
That means you can get instant answers for all the questions you have about your site. Or give it instructions in plain English, and it acts on your site directly.
In other words, having an AI assistant inside WordPress is like having a senior WordPress operator on call 24/7 for your site.
That’s exactly what Uncanny Agent delivers.
What is Uncanny Agent?
Uncanny Agent is an AI assistant for WordPress built into the Uncanny Automator plugin. It helps you get real work done on your WordPress site just by describing what you want in plain English.
There are three core things Agent does:
Answers questions about your site: “How many users completed Course B this month?” or “What’s my best-selling product this quarter?”
Completes tasks for you: Drafting posts with featured images, updating settings, generating reports, formatting content
Builds automations from a conversation: describe a workflow in one sentence, and Agent builds it for you
Ask Your Site Anything, Get a Real Answer
If you’ve purchased an AI + Automation plan, Uncanny Agent lives inside your WordPress dashboard. You don’t need to install a separate plugin or sign up for another account.
Click the Uncanny Agent widget to open it, type your question, and get instant answers. No more digging through three different plugin dashboards or exporting CSVs into a spreadsheet.
Since Agent has direct access to your WordPress data, answers are accurate to the second… no real-time snapshots needed from an external analytics tool.
Draft Content and Handle Admin Work in Seconds
Uncanny Agent can complete tasks on your behalf, all through natural conversation. What used to take 10+ clicks to complete a task will now get done in just one request in plain English.
The best part is that you can have back and forth conversation with Agent to get the best results.
For example, you can simply ask “Review our current blog posts and propose 3 complementary article topics”. Once you get a response, you can ask to “Draft a post that covers the second topic”.
The same goes for updating product descriptions, formatting content, or even writing a code snippet that you can add to your theme file to enhance a WordPress feature.
The result: routine WordPress busywork disappears from your calendar.
Build Automations Without Touching a Recipe Builder
Most automation tools require you to map every step manually. Triggers, actions, fields, conditions… it adds up.
With Uncanny Agent, you describe what you want in one sentence: “When someone submits my contact form, send me a Slack notification and add their info to Google Sheets.”
Agent builds the automation for you. You review it, save it, and move on.
Built on a Mature Automation Engine
Uncanny Automator has been the standard for WordPress automation since 2020, with 50,000+ active sites. It already does the heavy lifting of connecting WooCommerce, Slack, Zoom, Mailchimp, Google Sheets, OpenAI, and the rest of your stack.
Uncanny Agent, the new feature, is the AI layer sitting on top of that proven engine that runs billions of recipe combinations to connect your WordPress plugins, sites, and apps together. It is by far the most capable AI assistant available for WordPress.
AI-Powered Automation: How Much Does It Cost?
Here’s what it costs to get AI-powered automation on your WordPress site without Uncanny Agent.
You will need an automation tool like Zapier or Make along with a general AI assistant like ChatGPT, Claude, or Gemini. Both these tools, automation + AI, cost around $40 to $70 per month. Yet they don’t talk to each other and don’t truly know your site.
That’s because AI is guessing from generic documentation, sits outside WordPress, is connected by API, and is unable to reach most of what actually lives in your database.
Uncanny Agent, on the other hand, is one platform on one subscription, starting at $25/month on the AI + Automation Pro plan.
Because Agent is built right into Automator, it reads your actual WooCommerce orders, users, and content. You can ask it to build an automation, and it build the recipe inside the same tool that will run it.
What’s Coming Next!
We’re just getting started with Uncanny Agent, and I’m genuinely excited about what’s ahead. The Uncanny team is actively expanding Agent’s capabilities across more plugins, more use cases, and deeper automation logic. My goal is to make Uncanny Agent the most useful AI assistant in WordPress.
And the best way to get there is by listening to your feedback and building the features you actually need.
If there’s a specific workflow you’d love Agent to handle, drop it in the comments. Your suggestions shape the roadmap.
And if you’ve been putting off using AI on your WordPress site because the tools felt disconnected from your data or too generic to be useful, then I hope you’ll give Uncanny Agent a try. Start with the free Uncanny Automator plugin from WordPress.org, upgrade when you’re ready, and have your first AI assistant running inside WordPress in under ten minutes.
Thank you for your continued support of WPBeginner and the products I’ve been part of over the years.
A standard contact form tells you almost nothing about the person who just filled it out. You get a name and an email address, but no idea whether that person is ready to buy, still exploring options, or not a real fit at all.
At WPBeginner, we run a hosting quiz that works differently. Before we ask anyone for their email, the quiz asks a few short questions about their goals and current situation. Those answers sort each visitor into a group, so our follow-up emails match where they are in their decision.
This guide shows you how to build the same kind of qualification filter using WPForms. This post focuses on the qualification logic: how to define your lead criteria, score answers, and route each lead automatically.
TL;DR: I’ll show you how to build a quiz that automatically filters your leads into hot, warm, and cold groups using WPForms and the Quiz Addon. You’ll define your qualification criteria, write readiness-focused questions, score the answers on a 0–100 scale, and connect the results to your email marketing tool so each lead gets the right follow-up automatically.
Before diving in, there are a few quick things to note.
First, this guide assumes you already have an email marketing tool. If you don’t, check out our roundup of the best email marketing services to get started.
Second, you’ll be building your lead filter using WPForms. Because WPForms is built by Awesome Motive, the same company behind WPBeginner, we trust the plugin and use it on our own site every day.
Finally, this post focuses specifically on the logic of scoring and routing your leads. If you need a more general walkthrough of the form builder itself, see our guide on how to create a quiz in WordPress.
Why a Quiz Beats a Contact Form for Finding Real Buyers
Most people think lead generation is a numbers game: the more sign-ups, the better. But a smaller list of people who are genuinely interested in what you offer will almost always outperform a huge list of strangers who barely remember signing up.
Consider two scenarios. You could collect 1,000 email addresses with a free wallpaper download, or 200 emails from people who completed a quiz called ‘Is your website ready to grow?’
The wallpaper group signed up for a freebie and told you nothing. The quiz group revealed their goals, readiness, and mindset just by showing up and answering.
That’s the difference between a wide net and a filter. A net catches everything, including people who will never buy from you. A filter catches fewer people, but the ones it catches are far more likely to become real customers.
Here’s how this plays out across different business types:
Business Type
Quiz Example
What You Learn
Web hosting / SaaS
‘Which plan is right for you?’
Match visitors to the right tier
Coaching / consulting
‘What is your biggest challenge?’
Identify client fit before a sales call
Blogger building a course
‘What is your experience level?’
Route learners to the right content
Local service business
‘What do you need help with?’
Qualify inquiries before a callback
eCommerce store
‘Find your perfect product’
Recommend items based on preferences
A quiz does more than collect emails. It gives visitors a personalized result that feels immediately useful, which builds trust before you ever send a single follow-up message.
Define What Hot, Warm, and Cold Leads Look Like for Your Business
Before you open the form builder, you need to decide what a ‘hot’ lead actually means for your specific business. This is the step most people skip, and it’s why their quiz ends up sorting leads in ways that don’t match reality.
Which Signals Actually Matter
Not all signals are equally useful. Four types of information tend to reveal the most about lead quality: timeline urgency, budget range, problem complexity, and decision-making authority.
Of these, readiness signals matter most. Someone who says ‘I need this launched in two weeks’ is a completely different lead than someone who says ‘I’m just exploring options.’ Timeline and urgency tell you whether a person is ready to act, not just interested in the topic.
Budget matters, but weight it lower. A lead with a clear, urgent problem and no stated budget is often closer to a sale than a lead with a large budget and no urgency at all.
Before building anything, complete this template for your own business:
A hot lead for my business is someone who ___.
A warm lead is someone who ___.
A cold lead is someone who ___.
Write your criteria down before you design a single question. Your answers will directly shape which quiz responses get the highest point values.
How the WPBeginner Hosting Quiz Defines Leads
Here’s how we apply this at WPBeginner. Our hosting quiz asks visitors about their experience level, monthly traffic, and hosting priorities. Those three signals tell us whether someone is ready to switch hosts or is still figuring out the basics.
A hot lead for our quiz is someone with an existing WordPress site, over 10,000 monthly visitors, and ‘performance and uptime’ as their top hosting priority. That person is shopping seriously.
A warm lead is someone building their first site who wants affordable, reliable hosting. A cold lead is someone who is not yet sure they need WordPress at all.
Notice that budget doesn’t appear in that definition. We found that readiness signals like existing site and current traffic predict sales-ready conversations far better than budget answers alone.
Three Reader Scenarios
Your criteria will look different depending on what you’re selling. Here are three examples to help you think through your own:
Blogger building a course audience. Hot lead: someone who already has a blog with an engaged audience and wants to monetize it in the next 30 days. Warm lead: someone building content but without an email list yet. Cold lead: someone who is curious about online courses but doesn’t have a site or audience.
Local service business. Hot lead: a visitor with a specific problem, a clear timeline, and readiness to book. Warm lead: someone researching options across multiple providers. Cold lead: someone browsing for general pricing with no specific need or date in mind.
eCommerce store recommending product tiers. Hot lead: a returning customer who knows what they want and is ready to upgrade. Warm lead: a first-time buyer with a specific use case. Cold lead: a window shopper with no clear purchase intent.
Once you have your own version of these three definitions written out, you’re ready to build the quiz that enforces them.
What You Need Before Starting
Before building your quiz, make sure you have these four things in place:
WPForms Pro. The Quiz Addon and the conditional lead routing features used in this guide both require the Pro license. You can get it from the WPForms website.
An email marketing tool already configured. This guide assumes you have one set up. If you don’t, start with our best email marketing services comparison first.
Your hot, warm, and cold criteria. The definitions you wrote out in the previous section. These drive every decision you’ll make in the build.
Once those four things are in place, you’re ready to install WPForms and start building.
Step 1: Install WPForms and Activate the Quiz Addon
WPForms is a drag-and-drop WordPress form builder used by over 6 million websites. Its Quiz Addon extends the plugin with everything you need to create scored quizzes, display personalized results, and route leads to your email tool automatically. This setup only needs to be done once.
I use WPForms for this specifically because its Quiz Addon is built for scoring-based lead qualification, and the conditional logic runs entirely inside the form builder, with no separate automation tool required.
First, install and activate WPForms Pro on your WordPress site. If you need help, see our guide on how to install a WordPress plugin. Once active, go to WPForms » Settings and paste your license key from the purchase confirmation email, then click ‘Verify Key’.
Next, you need to go to WPForms » Addons and use the search bar to find the ‘Quiz’ addon.
Once you find it, simply click the ‘Install Addon’ button.
Once installed, the addon status updates to ‘Active’ in green. You’re now ready to build your qualification filter.
Step 2: Build Your Qualification Filter
With WPForms installed and your lead criteria defined, you’re ready to build the quiz that enforces them.
This section walks through every decision in order, from choosing your quiz type to routing each lead to the right list.
Pick Your Quiz Type
Go to WPForms » Add New Form in your WordPress dashboard. Give your form a descriptive name, like ‘Lead Qualification Quiz’ or ‘Find the Right Plan for You’.
You can start with the AI generator, a blank form, or a pre-built template. The AI option is the fastest way to get a working draft. See my guide on how to create a quiz in WordPress for a full walkthrough of each starting method.
Once you’re inside the builder, select your quiz type. WPForms offers three options:
For most lead-qualification use cases, choose Weighted. It assigns numeric point values to each answer, making it straightforward to score readiness and urgency on a consistent scale.
Choose Personality instead when you want to route visitors to distinct product tiers like ‘Beginner’, ‘Growing Business’, or ‘Enterprise’ rather than a numeric score.
Write 4 to 6 Readiness Questions
Under the ‘Questions’ tab, drag and drop fields onto your form.
Multiple Choice, Dropdown, and Checkbox fields work best for lead generation because they support scoring and conditional logic.
Keep your quiz to 4–6 questions total. That’s enough to learn something meaningful about each visitor without causing drop-off before the optin step.
Remember the rule from earlier: focus on readiness rather than just budget. Try to frame your questions around the user’s current struggles or how quickly they want to solve their problem. This is the secret to separating serious buyers from casual window shoppers.
Here are some example questions for a hosting quiz:
‘What best describes your WordPress experience?’ This tells you how much support a visitor is likely to need. Someone who has run WordPress sites for years has very different needs than someone setting up their first one.
‘How many visitors does your site get each month?’ Traffic level is a strong readiness signal for hosting. Someone with 50,000 monthly visitors is actively feeling the pain of a resource-limited plan. Someone with 500 visitors is not.
‘What is your top priority in a hosting plan?’ This reveals purchase intent. ‘Performance and uptime’ signals someone shopping seriously. ‘Lowest possible price’ signals someone still early in the decision.
Notice that none of these questions ask for a budget range. The answers still tell you exactly how to follow up with each person.
Assign Point Values to Your Quiz Answers
Now assign point values to each answer. Use a 0–100 total scale so the conditional logic you’ll set up in the routing step is unambiguous.
Click on any question field in the builder, then toggle on ‘Include in Quiz Scoring’ in the left-hand ‘Field Options’ panel. A numeric input box appears next to each answer choice where you can enter a point value between 0 and 99.
Assign higher point values to answers that signal readiness. For example, you might use this:
‘Experienced WordPress user’ = 25 points; ‘Brand new to WordPress’ = 5 points
‘Performance and uptime’ = 25 points; ‘Lowest possible price’ = 8 points
With three questions like these, a perfect score adds up to 75 points.
Adding a fourth readiness question lets you reach 100. Set your hot-lead threshold at 75 and your warm-lead threshold at 40. You’ll have a clean scale to reference when setting up the conditional connections in the next step.
Build Outcome Screens by Lead Temperature
Now you need to click the ‘Outcomes’ tab at the top of the builder. This is where you write the result screen each visitor sees after submitting.
Click ‘Add New Outcome’ to create separate screens for each lead temperature. Open each outcome and toggle on ‘Enable conditional logic‘ so the right screen shows for the right score range.
The key principle: give visitors something genuinely useful before you make any ask.
A personalized result they can act on immediately builds the trust that makes a follow-up email feel helpful rather than intrusive.
Here are some examples from our own quiz:
Hot lead (score 75–100): Lead with the personalized result, then make a specific ask. Our screen says something like: ‘Based on your answers, you’re ready for a managed WordPress host. Here’s our top pick for your traffic level and goals.’ The CTA links directly to our hosting comparison page.
Warm lead (score 40–74): Offer something useful but lower-commitment. A relevant guide, a comparison article, or a free trial option works well here. No direct sales ask. The CTA might say ‘Compare your top options’ and link to a review roundup.
Cold lead (score below 40): Point them to an educational starting point with no product pitch. A ‘beginner’s guide to WordPress hosting’ is a far better fit than a ‘Book a call’ button for someone who scored this low.
To turn the quiz into a lead generator, add an optin step between the last question and the result screen. Because visitors have already invested time in answering your questions, they are far more likely to share their email to see their personalized outcome.
First, you should drag the ‘Page Break’ field to the very end of your question section. Then, place ‘Name’ and ‘Email’ fields on this final page, right before the submit button.
Make the email field required so visitors must enter it before seeing their result.
After that you need to click on your Page Break field and change the ‘Next’ button text to something benefit-driven, like ‘See My Results’.
Then, go to Settings » General in the builder to update the final ‘Submit Button Text’ field the same way.
If your quiz audience is in the EU, add WPForms’ built-in ‘GDPR Agreement’ field to this page. It gives visitors a consent checkbox and links to your privacy policy before they submit. See our guide on how to create GDPR compliant forms in WordPress for full details.
Note: Test your completed quiz on a smartphone before publishing. The page-break layout behaves slightly differently on small screens, and a button that’s easy to click on desktop can be hard to tap on mobile.
Once your optin gate is configured, you’re ready to connect the quiz to your email marketing tool.
Route Leads to Your Email Tool With Conditional Connections
This is where the qualification work pays off. After someone submits the quiz, WPForms fires a connection to your email marketing tool and applies the tag that matches their score. This happens automatically, every time, with no manual review required.
Click the ‘Marketing’ tab in the left-hand menu of the builder. Select your email provider. WPForms connects natively to popular email tools including Brevo, Constant Contact, Mailchimp, AWeber, and ActiveCampaign. If your platform is not listed, see the FAQ section below for how to connect through Zapier or Make.
Once your account is linked, you can click the ‘Add New Connection’ button to create different routing rules. You will need to create a separate connection for each of your lead tiers.
Here’s how to set up all three:
Connection 1: Hot leads. Map the email field to your list. Scroll down and enable ‘Conditional Logic’ for this connection. Set the rule: ‘Quiz Score’ is ‘greater than or equal to’ 75. Apply the tag quiz-hot to the contact record. This connection fires only when someone scores 75 or above.
Connection 2: Warm leads. Create a second connection. Set two rules: ‘Quiz Score’ is ‘less than’ 75 AND ‘Quiz Score’ is ‘greater than or equal to’ 40. Apply the tag quiz-warm. This fires for scores between 40 and 74.
Connection 3: Cold leads. Create a third connection. Set the rule: ‘Quiz Score’ is ‘less than’ 40. Apply the tag quiz-cold. This fires for any score below 40.
Note: Use ‘greater than or equal to 75’ for the hot-lead threshold, not ‘greater than 75’. Using ‘greater than 75’ means a score of exactly 75 falls into a gap and gets assigned no tag at all.
Inside your email tool, each new subscriber now arrives already sorted into one of three tagged groups. Here’s what to do with each:
quiz-hot. Route to a personal follow-up sequence. A direct email from you, a booking link, or a special offer works well here.
quiz-warm. Route to a nurture sequence. A helpful guide series or a regular email newsletter builds trust over time without pushing for a sale.
quiz-cold. Route to an educational sequence. Low-pressure content helps these leads get to a point where they’re ready to move forward later.
The quiz is just the entry point to your funnel. Each tagged group flows into a different email sequence that continues the conversation over time. Hot leads get a shorter, high-intent track. Warm leads get a longer nurture series. Cold leads get educational content that builds toward readiness at their own pace.
When you’re done, click the orange ‘Save’ button at the top of the builder.
Your quiz is also a shareable asset. Once it is live, embed it on a dedicated landing page and promote it through social media or your newsletter. People share personalized results, and a quiz that produces a clear outcome gives visitors something worth passing along.
Every share brings in new visitors who have already seen what the result looks like, a warm audience before they’ve answered a single question.
Step 3: Analyze Your Results and Tune the Filter
You did the hard part and your lead filter is built. Now, don’t worry if your scoring system isn’t 100% perfect on day one. Once you get your first 50 to 100 entries, you’ll start to see clear patterns in how people are answering.
Here is how to easily read those early numbers and make simple tweaks to improve your quiz over time.
Reading Score Distributions
Start by opening your quiz in WPForms and then click the ‘Results’ tab at the top of the screen.
This opens your reporting dashboard, where each question gets its own chart showing how visitors answered.
Unlike standard form entries, the quiz dashboard turns your completion data into interactive charts and graphs.
You can hover over any bar or slice to see the exact percentage of visitors who chose each answer.
Now, look at how your completions are distributed across the three tiers. A reasonable starting target is roughly 20–30% hot, 40–50% warm, and 20–30% cold.
If your distribution looks very different from that, here’s what it usually means:
Everyone scores hot: Your hot-lead threshold is too low, or your questions tend to produce high answers regardless of actual readiness. Raise the threshold by 10 points and recheck after another 50 submissions.
No one scores hot: Your threshold is too high, the traffic source is sending a cold audience, or your questions don’t discriminate well enough between ready and not-ready visitors. Check where the traffic is coming from before assuming the questions are the problem.
Almost everyone scores cold: This often means the quiz is being completed by people who found it through a very top-of-funnel entry point, like a broad social post or an unrelated article. Try placing the quiz on a more targeted page first.
You can also use the answer data to improve your follow-up emails. When you see that a specific answer is chosen by 70% of visitors, use that exact phrasing in your email subject lines and sales pages.
Spotting ‘Leaky’ Questions
A ‘leaky’ question is one where visitors stop completing the quiz.
Because standard reporting only shows completed entries, I recommend adding the WPForms Form Abandonment Addon to capture partial submissions as well.
Next, you should go to WPForms » Entries in your dashboard. Incomplete submissions are marked with an ‘Abandoned’ status.
You can click any abandoned entry to see exactly which question the visitor answered last.
If many visitors stop at the same question, that question is causing friction. It’s often too personal, too confusing, or asking for information visitors aren’t ready to share at that stage of the quiz.
In my experience, questions about phone numbers or exact revenue figures cause the most drop-off.
If you want to improve completion rates quickly, start by testing your first question. It’s the highest drop-off point in any quiz, and a single change here can lift the number of people who reach the optin step.
Try running two versions: one that opens with a readiness question (‘How urgent is your need right now?’) and one that opens with a goal question (‘What are you trying to accomplish?’). After 100 submissions per variant, you can compare completion rates and score distributions.
The version with the higher completion rate and a more spread-out score distribution is the stronger opener.
A great first question hooks visitors immediately and sets the tone for what follows.
When to Update Your Quiz Scores
As your business grows and your audience changes, your definition of a perfect lead will probably change, too. The point values you set today don’t have to be the same forever.
In fact, checking in on your point system occasionally is the best way to make sure your email list stays filled with high-quality contacts.
I recommend revisiting your scoring rules whenever you notice one of these three things happening:
Your business model changes. New product tiers, a pricing restructure, or a new service line may mean your old definition of ‘hot’ no longer fits.
Your hot, warm, and cold numbers change a lot.Check where your traffic is coming from first. A new campaign or busy season can change who’s taking your quiz, even if nothing about your scoring has changed. If your traffic looks the same as before, your point values probably need adjusting.
Your sales results don’t match your tags. If the people tagged quiz-hot aren’t converting at the rate you’d expect, your threshold may be set too low. If sales conversations are rare, it may be set too high.
Re-scoring takes less time than the initial setup. Treat it like a quarterly review rather than a one-time configuration.
Frequently Asked Questions
Here are answers to some common questions about using quizzes to qualify leads in WordPress.
Can I build a lead qualification quiz without paying for WPForms Pro?
No, building a scored lead qualification quiz requires WPForms Pro. The free version of WPForms doesn’t include the Quiz Addon or the conditional logic needed to route leads to your email tool based on their score.
However, WPForms offers a 14-day money-back guarantee, which gives you enough time to set everything up and test the results before committing.
What if my email marketing tool isn’t on the WPForms integration list?
WPForms connects natively to popular tools like Brevo, Constant Contact, Mailchimp, AWeber, and ActiveCampaign. If your specific email provider isn’t listed, you can route your quiz leads through Zapier or Make instead.
The conditional scoring logic still runs inside WPForms, and you simply pass the tagged contacts through an automation layer to your email platform.
How do I handle people who retake my lead generation quiz?
WPForms doesn’t block retakes by default. If someone retakes your quiz and qualifies for a different lead tier, most email tools will simply update their contact record when the connection re-runs.
To prevent a contact from collecting conflicting tags (like quiz-hot and quiz-warm at the same time), you should set your email marketing tool to replace existing tags on each new submission rather than adding to them.
Can I show my WordPress quiz in a popup instead of a standalone page?
Yes. WPForms can be embedded inside any popup builder that supports WordPress shortcodes, including OptinMonster. You simply paste your quiz shortcode into the popup content exactly the same way you would on a regular post or page.
The lead scoring and conditional email routing will work perfectly regardless of where the form is embedded.
Do quiz leads actually convert better than gated-PDF leads in real data?
In our experience at WPBeginner, yes. Lead qualification quizzes produce a much more engaged audience than standard content downloads. While gated-PDFs typically generate more raw sign-ups, the audience is far less filtered.
With quizzes, your open rates and click rates tend to be higher because the scoring system ensures every follow-up email matches exactly where the reader is in their buying journey.
Additional Resources for WordPress Lead Generation
I hope this article helped you learn how to qualify your leads with a WordPress quiz.
You may also want to check out some other guides about growing your email list and converting more visitors:
How to Easily Create a Quiz in WordPress. A complete walkthrough of building quizzes with WPForms, including templates, AI generation, and result configuration.
Content management systems are constantly evolving to meet the growing needs of organizations with vast amounts of information to share. One topic that’s often overlooked until it becomes a problem is how structured data impacts editorial efficiency and long-term website success. When a site has hundreds, or even thousands of individual pages, keeping everything organized […]
It’s good to be home again. It was an unusually long break, but I appreciate the series of official bank holidays that morph into long weekends away from the computer.
And of course, the catch-up is overwhelming. The creativity inside the WordPress community around content creation, development and design is highly energizing.
And it’s WordPress 7.0 release week! It’s finally here!
So don’t let me keep you any longer. Enjoy!
If you want to stop long enough to send me a note, I’d be delighted to hear from you.
Yours, Birgit
WordCamp Europe is coming up fast. It’ll take place Jun 4 to 6, 2026. The schedule just was posted. If you still are on the fence about getting your ticket. Here are another 49 reasons to head to Krakow. The schedule lists 34 Talks, 3 Panels, 10 Workshops and 2 Keynotes.
For armchair WordCampers, like myself, there will be a livestream. After the WordCamp recordings will be uploaded to YouTube and WordPressTV.
Closing Keynote with Matt Mullenweg on Saturday June 6, 2026.
if you rather stay in North America, WordCamp US just opened up the online ticket booth. It’ll take place from August 16 to August 19, 2026, in Phoenix, AZ. The calls for sponsors and speakers are also available now. The deadline for speaker submissions is next week Friday May 29, 2026.
Developing Gutenberg and WordPress
WordPress 7.0 “Armstrong”
After the decision to remove Real-time Collaboration from the release because it needs more time in the oven, so to speak, the release squad was really busy to produced RC 3 – 5 before the final release on Wednesday May 20, 2026.
Abha Thakor and I talked through a few features for the OpenChannels.fm episode to come out on Tuesday, May 26, 2026.
Justin Nealey product manager at GoDaddy breaks down why WordPress 7.0’s three new APIs matter far more than the headline features for plugin developers. The Connectors API means site owners manage their own AI provider keys centrally; WP AI Client gives you a single provider-agnostic call to invoke any model; and the Abilities API turns your plugin into something the site’s AI agent can reach for autonomously. Together, Nealey argues, your plugin stops being a destination users visit and becomes a verb the agent performs.
Ronak Vanpariya, web developer on Gujarat, India digs into why Real-Time Collaboration was pulled from WordPress 7.0 with a five-point technical post-mortem. You’ll learn how RTC had to work across every corner of the Site Editor, how simultaneous edits triggered race conditions corrupting block data, and how the feature’s reliance on persistent server connections would have overwhelmed shared hosting environments. Memory bloat on older devices and recurring block-tree breakage uncovered by fuzz testing sealed the decision. The feature lives on in the Gutenberg plugin.
Mike McAlister, creator of Ollie, released a video walkthrough of WordPress 7.0covering the features he sees as most impactful for site builders. He walks through the new AI infrastructure — WP AI Client and the Connectors API — content-only pattern editing, customizable mobile menu overlays, block visibility controls for responsive design, per-block custom CSS, visual revisions, the new Icon and Breadcrumbs blocks, an upgraded Font Library screen, and a command palette shortcut.
In other WordPress Core news:
Immediately after the release of WordPress 7.0, Jeff Paul published the WordPress 7.1 Call for Volunteers. Work has already started since the firsty 7.0 Beta in February. The first beta for WordPress 7.1 is roughly eight weeks out and scheduled for July 15, 2026, and the final release for August 19, 2026 aimed at the last day of WordCamp US.
In addition to the punted Real-time collaboration feature, I discovered a few tracking issue for WordPress 7.1 already:
#76525: Block Supports and Design Tools in WordPress 7.1 Opened by Aaron Robertshaw, this tracks new and enhanced block supports for 7.1, carrying over items descoped from 7.0. A living issue is updated as supports are added or dropped from the release scope.
#75707: Block Visibility: Configurable Breakpoints and theme.json Integration The follow-up to 7.0’s block visibility work. The goal is to let themes define custom breakpoints via theme.json and make visibility extensible for future responsive features — laying a solid foundation before more viewport-aware tools arrive.
#76045: DataViews, DataForm, et al. in WordPress 7.1 Tracks continued iteration on DataViews, DataViewsPicker, DataForm, and the Field API. Key work includes migrating @wordpress/dataviews to the new Design System primitives and extending DataForm to PHP-only blocks.
#77199: Block Bindings in WordPress 7.1 Narrowed in scope to match contributor availability. The headline goal is integrating the Block Bindings UI into Block Fields and removing the previous Block Bindings UI, plus adding Block Bindings support for the Cover block.
First-time release lead Paulo Trentin brought us the latest version for the Gutenberg plugin, 23.2. In his release post What’s new in Gutenberg 23.2? (21 May he highlighted: You can now style blocks differently for tablets and phones right from Global Styles, so your designs adapt to each screen. Pop-up dialogs slide up from the bottom on mobile, making them easier to tap one-handed, and animations across the editor now share a consistent feel. You’ll also see smoother Content Types management, friendlier Shortcode handling, clearer Revisions diff markers for better accessibility, and steadier real-time collaboration when teammates edit together.
Justin Tadlock rounds up what’s new for WordPress developers in May 2026, with WordPress 7.0 landing on May 20. You’ll find early details on the Content Types experiment for managing custom post types and taxonomies in Core, a new @wordpress/grid package for building grid-based editor UIs, revisions support extended to templates and patterns, and a wave of block fixes covering the Tabs block, Image alignment, Search block styling, and Global Styles rendering.
If you are interested in learning more about this, the Content Types tracking issue outlines the experiment to bring custom taxonomy and post type management into the WordPress editor. The initial focus is on simple use cases — complex ones stay in plugin territory — with open tasks including a dedicated creation page, richer fields, a quick-edit versus full-edit distinction, and deeper DataViews integration. It’s a living issue and community input is welcome.
John Blackbournclarified WordPress’s PHP support stance in a post that’s worth flagging for developers and hosts. The “beta” label for PHP 8.x support has been retired and removed retroactively from all WordPress versions. It was discouraging hosts and developers from upgrading. In short:
The minimum recommended version remains PHP 8.3;
the minimum supported version is PHP 7.4.
Versions 6.9 and 7.0 now officially fully support PHP 8.5,
Request Logging gives administrators visibility into every AI request fired across Core, plugins, and themes;
Connector Approvals lets admins control which plugins can access configured AI providers.
Beyond governance, you’ll find comment moderation upgrades with sentiment and toxicity sorting right in the dashboard, AI alt text generation baked into the media editor workflow, and editorial workflow terminology tidied up. Looking ahead to 1.1.0, the team is exploring type-ahead suggestions, focus-aware crop suggestions, an AI Playground, and C2PA content provenance tracking for both text and images.
Plugins, Themes, and Tools for #nocode site builders and owners
Jay Walsh, Director of Communications at Woo, announced that WooCommerce stores can now sell directly on YouTube via the Google for WooCommerce extension. You connect your store, tag products from your catalog in videos and Shorts, and they surface as shoppable cards while viewers watch — and also appear in your Channel Shopping tab. The same Merchant Center product feed that powers Google Shopping and Performance Max campaigns keeps everything in sync automatically, with AI-generated ad creative variations across formats included in version 3.6.
OpenRouter for routing across hundreds of models with cost optimization,
LM Studio for fully local inference suited to GDPR-sensitive workflows, and a
Universal OpenAI connector for any OpenAI-compatible endpoint including Ollama, Groq, and Mistral.
All three are built on the same PHP AI Client SDK heading into WordPress Core 7.0, so your setup today carries forward without code changes after the upgrade.
Artur Piszek explains how he uses WordPress as a sync backend for Obsidian with PushMD. This plugin was created with Adam Zielinski, the maker of Playground. It allows you to treat your WordPress site as a git remote using the REST API. You can git clone your blog as plain .md files. Write in Obsidian and push updates to sync. This setup turns your site into a repository without needing an external service. It is also compatible with the upcoming Guidelines/Artifacts system in WordPress Core, which lets you store private notes and configurations there too.
Seth Rubenstein at Pew Research Center shared a preview of PRC Block Bits, now open-sourced on GitHub. Block Bits solves a specific gap between block bindings and RichText: where bindings replace an entire block’s content with dynamic data, a “bit” lets you embed small dynamic pieces — an inline icon, a copyright year, live text — right in the middle of a paragraph or heading. You register bits via a PHP and JS API, choose between a pure-PHP callback or Interactivity API strategy, and an editor toolbar dropdown handles insertion. Built-in bits for icons and copyright ship out of the box.
Theme Development for Full Site Editing and Blocks
Damir Tahiri of Rareview has open-sourced the WordPress starter theme that underpins every one of the agency’s builds. It’s Gutenberg-ready, ships with global style variables, includes a one-command Figma sync, and runs an interactive setup that renames and configures everything automatically. You can grab it on GitHub and use it as the foundation for your own projects.
“Keeping up with Gutenberg – Index 2025” A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test, and Meta team from Jan. 2024 on. Updated by yours truly.
On the WordPress Developer blog, Róbert Mészáros shows you how to get started writing WordPress E2E tests with Playwright, using a book review site built on Block Bindings as the test subject. You’ll set up wp-env and Playwright, write your first test against the admin dashboard, then progress to inserting block variations, verifying patterns with aria snapshots, and testing front-end output by creating posts via the REST API.
Also on the WordPress Developer Blog, Felix Arntz, Senior Software Engineer at Vercel, walks you through building a provider-agnostic image generation plugin using WordPress 7.0’s built-in AI Client. You’ll see how a single wp_ai_client_prompt() call handles provider routing, how support checks gate your UI gracefully when no image-capable provider is configured, and how the REST API and Media Library integration come together. The full source code is on GitHub at wptrainingteam/ai-client-imagegen.
Sérgio Santos, Lead Engineer at 10up/Fueled, diagnoses three specific bugs you hit when using RichText outside a block — in InspectorControls or a Modal. The format toolbar fills route to the wrong slot, the inline toolbar is opt-in via inlineToolbar, and isSelected never turns true outside a block context. Each problem gets a targeted fix, and the pattern has since been packaged as a reusable component in 10up Block Components.
Eric Karkovack walks you through using my.WordPress.net as a safe AI sandbox — no production site at risk. You install WordPress in your browser in two steps, add the AI Assistant app from the apps menu, connect it to Anthropic, OpenAI, or a local Ollama model, and start prompting. It’s a low-stakes way to explore what AI can do inside WordPress before committing it to a live environment, though API costs from OpenAI or Anthropic still apply.
Fresh from last week’s WordCamp Portugal:
Imran Sayed presented The Fastest Way to Build Gutenberg Blocks: Modern Tools, Scripts, and AI at WordCamp Portugal 2026. The talk cuts through the complexity of custom block development by focusing on practical, immediately usable workflows built around modern WordPress tools and scripts.
Milana Cap presented WordPress Gems for Devs: Accessibility with Interactivity API and makes the case that it’s one of the most exciting APIs to land in WordPress in recent releases, with positive implications not just for developer experience but for performance and user experience too.
Jorge Costa presented AI is in WordPress Core. Here’s How to Use It. The talk digs into the AI building blocks already shipped in WordPress Core — the WP AI Client, the Abilities API, and the MCP adapter, and shows you exactly how to bring AI-powered features into your own plugins, themes, and sites.
JuanMa Garrido presented WordPress Development and Management with Claude Code. The talk treats Claude Code as a command center for WordPress work, generating block themes from HTML designs, querying a production site in natural language, installing plugins, and reading error logs, all from the terminal. Three concepts are at the core: Skills, MCP, and the Abilities API.
Now also available via WordPress Playground. There is no need for a test site locally or on a server. Have you been using it? Email me with your experience.
Questions? Suggestions? Ideas? Don’t hesitate to send them via email or send me a message on WordPress Slack or Twitter @bph.
You know what… free LMS plugins for WordPress are surprisingly good this year! You really don’t need to spend a cent to build a fully working online course, and this post proves it.
AI: super-smart guesser or just a robot with a flair for the dramatic? Join our hosts as they grill gadgets, predict the future, and ponder if their devices need bedtime stories.
WordPress 7.0 is finally here 🥳, and we’ve been testing it since the early beta.
It’s the first major release of 2026, and it’s a big one, with a brand-new AI Connectors screen, responsive block controls, and a refreshed admin experience that makes the dashboard feel like a modern web app.
Whether you run a small blog or a large multi-author site, WordPress 7.0 brings changes that will affect the way you create and manage content.
📌 Note: Real-time collaboration (RTC) was originally planned for WordPress 7.0, and we covered it in our What’s Coming in WordPress 7.0 post. It was pulled before release because the core team wasn’t confident the current approach was robust enough, citing concerns around race conditions, server load, and memory efficiency.
The feature is still in active development and can be tested via the Gutenberg plugin. We’ll cover it properly when it ships.
Connect WordPress to AI with the New Connectors Screen 🤖
WordPress 7.0 now gives you a central place to connect your site to AI services with no third-party plugin required.
A new Settings » Connectors screen lets you install and configure AI provider packages directly from your WordPress dashboard.
Think of it like a plugin directory, but specifically for AI. You choose your provider, enter your credentials once, and every plugin or theme that supports the AI API can tap into that connection automatically.
At launch, three providers are available: OpenAI (ChatGPT), Google (Gemini), and Anthropic (Claude). Once a connector is installed and authenticated, any plugin that uses the WordPress AI API will work with your chosen provider, without you needing to configure API keys in multiple places.
There are a ton of WordPress AI plugins that can now use your selected AI platform to provide AI features. Until now many companies were either asking you to enter your API keys or purchase credits from them.
The connectors store credentials securely and handle communication between WordPress and the AI provider in a standardized way.
Pro Tip: If you’d prefer to disable all AI features entirely — for privacy reasons or to keep things simple — you can add define( 'WP_AI_SUPPORT', false ); to your wp-config.php file. This turns off all LLM-related features across the site.
A Refreshed Admin Experience ✨
The WordPress admin area has a new look in 7.0, including updated color schemes, cleaner typography, and smoother transitions between screens.
It’s not a complete redesign, but in practice this means less waiting as you move between screens. For example, clicking from Posts to Settings to the editor no longer triggers a full page reload each time.
The cleaner layout and higher-contrast typography also make it easier to find what you’re looking for, which adds up when you’re publishing frequently or jumping between settings.
One of the most useful additions is that the Command Palette, which was previously only available inside the block editor, is now accessible from anywhere in the admin.
Just press ⌘K on Mac or Ctrl+K on Windows/Linux to open it from any screen.
From there, you can quickly navigate to any page, open settings, search posts, or run common actions without touching the mouse. If you’ve ever used the command palette in VS Code or Figma, then this will feel immediately familiar.
Note: This is entirely optional. If keyboard shortcuts aren’t your thing, you don’t need to learn this because all the same actions are still available through the normal menus. It’s a power-user shortcut for people who want to move faster.
Responsive Block Visibility by Device 📱
WordPress 7.0 introduces a feature that page builder plugins have offered for years, now built right into the core block editor: the ability to show or hide any block depending on whether a visitor is on a phone, tablet, or desktop.
Whether you want to display a larger image on desktop and swap it for a compact version on mobile, or hide a sidebar element entirely on smaller screens, you can now do all of this without touching a line of CSS.
To use it, select any block and look for the new visibility options in the block toolbar or the block inspector sidebar.
A visibility modal lets you choose which device types — desktop, tablet, or mobile — to hide the block on. Any changes you make only affect the viewports you choose, and other screen sizes are untouched.
Here are some more details:
Blocks with active visibility rules show a small device icon in List View, so you can see at a glance which blocks have restrictions applied.
Visibility controls are also available from the Command Palette.
You can apply different styles per breakpoint. For example, different font sizes or spacing on mobile, and even customize where breakpoints are defined.
WordPress has had a revisions system for years, but 7.0 makes it much easier to see what actually changed between versions.
You can now compare two revisions side by side in the editor, with color-coded overlays highlighting every difference.
Here’s a summary of the color-coding system:
Green outlines = blocks that were added
Red outlines = blocks that were removed
Yellow outlines = blocks with modified settings
For text, green with underline = added text, red with strikethrough = removed text
The sidebar now also shows changed block attributes alongside the visual diff, so you can see exactly what settings were changed, not just where.
This is a major improvement for anyone who manages a multi-author site or wants to review content changes before publishing.
But it’s just as useful if you’re the only person editing. It makes it much easier to spot what you accidentally deleted or changed when you want to roll back to an earlier version.
Custom CSS for Individual Blocks ✏️
Before WordPress 7.0, making a small one-off style tweak to a single block required a workaround, usually involving the Additional CSS panel, Global Styles, or manually adding a custom CSS class.
WordPress 7.0 changes that with a new Custom CSS field built directly into the block inspector.
Just select any block, open the Advanced panel in the inspector sidebar, and you’ll find a new Custom CSS field.
Whatever you type there applies only to that specific block instance, so nothing else on the page or site is affected. Changes also render live in the editor so you can see exactly what you’re doing before saving.
A few things worth knowing:
Only user roles with the edit_css capability — typically Administrators and Editors — will see this field.
The CSS is stored inside the block itself, so it travels with the block if you duplicate or move it.
Block developers can opt out of this feature in their block.json if needed.
If you’ve ever wanted to make one button a different color, or add a bit of extra spacing around a single image without affecting anything else on the page, this is now the easiest way to do it.
WordPress 7.0 adds three new native blocks that previously required a plugin. All are available immediately from the block inserter.
Icons Block
You can now insert SVG icons directly into your content without needing a separate plugin.
The Icons block comes pre-loaded with the full WordPress icon library, and you can search for icons by name.
You can also resize, recolor, and adjust spacing on each icon.
This makes it easy to add visual cues next to feature lists, service cards, or pricing tables without uploading image files or installing a separate plugin.
Pro Tip: Third-party icon libraries (like Font Awesome or Heroicons) aren’t included in 7.0, but official support for registering custom icon sets is coming in WordPress 7.1.
Breadcrumbs Block
The Breadcrumbs block adds a fully functional breadcrumb trail to any post, page, or custom post type template, with no plugin required. It automatically generates the trail based on your site structure.
Breadcrumbs help visitors navigate back up through your site hierarchy — for example, jumping from a blog post to its category page — and they’re a well-known SEO signal. Google uses them in search result snippets, which can improve how your pages appear in search results.
Developers can also customize the breadcrumb items and taxonomy preferences using two new PHP filters that ship with the block.
Headings Block
WordPress 7.0 adds a dedicated Headings block that consolidates all six heading levels (H1–H6) into a single block with built-in level variations.
You can switch between heading levels directly from the sidebar inspector without needing to transform the block, and all levels are searchable and accessible from the slash inserter.
This replaces the previous approach of inserting a Heading block and then adjusting the level separately, making heading hierarchy more intentional and easier to manage.
Proper heading structure also matters beyond just looks because screen readers use it to help visually impaired users navigate your content. Plus, search engines use it to understand what a page is about, which can influence your SEO rankings.
Customizable Navigation Overlays
Mobile menu overlays in the Navigation block are no longer experimental. You now have full control over how your mobile menu appears and behaves without needing a page builder plugin or custom code.
A new “Create overlay” button in the Navigation block walks you through the setup with a guided flow and pre-built design pattern options to choose from.
Theme developers can also register a new navigation-overlay template part area to give users even more control from the site editor.
Pattern Editing Gets Smarter
In WordPress 7.0, block patterns now default to content-only editing mode. When you click into a pattern, you’ll see a simplified view with block icons and grouped controls in flyout menus, rather than the full block toolbar and settings for every element.
This makes editing patterns much less overwhelming, especially for content creators who don’t need to adjust design settings, just swap out text and images.
Pro Tip: If you’re a developer or advanced user who prefers full access to pattern internals, you can disable content-only mode by adding a filter to your theme or plugin:
If you use the Gallery block with the lightbox feature enabled, WordPress 7.0 adds back/next navigation buttons.
This allows visitors to browse through your images without closing the lightbox.
Arrow key navigation also works, so visitors can press the left and right arrow keys to move between images. Any images with the lightbox individually disabled are automatically skipped in the sequence.
Under the Hood Changes in WordPress 7.0 🔧
If you build WordPress themes or plugins, 7.0 includes several developer-focused additions worth knowing about.
Pseudo-Element Support in theme.json
Theme developers can now style :hover, :focus, :focus-visible, and :active states directly in theme.json , with no custom CSS file needed. This works for blocks and style variations, giving you cleaner, more maintainable theme code.
You can now register a fully functional block using only PHP, with no JavaScript required for basic functionality. This is useful for server-side blocks and reduces the overhead for simple use cases.
Blocks can now declare a selectors.css entry in block.json to tell WordPress exactly which CSS selector to use when applying Global Styles. This gives theme and plugin developers precise control over how styles are scoped, which is useful when a block’s default CSS selector doesn’t match the element you need to target.
Font Library Gets a Dedicated Page
The Font Library has two significant upgrades in 7.0.
It now has a dedicated font management page in the dashboard. This is a single place where you and your team can manage, upload, and install fonts regardless of which theme type you’re using.
And it now works across all theme types: block themes, hybrid themes, and classic themes alike. Previously it was limited to block themes with Full Site Editor support (#73971, #73876).
WP-CLI 3.0
WP-CLI 3.0 is releasing alongside WordPress 7.0, adding two new command sets: wp block for read-only block entity access, and the new wp ability commands for working with the AI Abilities API.
The wp-env local development tool now supports phpMyAdmin on the Playground runtime, reaching feature parity with the Docker runtime. Enable it by adding "phpmyadmin": true to your .wp-env.json file.
Site Health now includes OPCache information under Tools » Site Health » Info » Server (#63697), making it easier to diagnose performance issues related to PHP opcode caching.
Iframed Editor
The post editor now automatically switches to an iframed layout when all blocks in a post are using Block API version 3 or higher. This improves editor stability and performance.
If a post contains older blocks that use an earlier API version, the iframe is skipped to preserve backward compatibility. Plugin and theme developers should verify their blocks’ API version declarations if they notice unexpected editor behavior after updating.
The Administrator and Editor roles have been removed from the new user default role selector under Settings » General. This prevents sites from accidentally assigning high-privilege roles to new accounts by default.
Site Health will display an alert if your site had one of those roles set as the default before updating. Developers can also use the new default_role_dropdown_excluded_roles filter to customize which roles are excluded.
PHP Requirements
WordPress 7.0 sets the minimum PHP version at 7.4, though the core team strongly recommends PHP 8.3 or 8.4 for performance and security.
Miscellaneous Enhancements in WordPress 7.0
Here are a few smaller improvements also included in this release:
Cover blocks now support video embeds via URL, so you no longer need to upload the video file to use it as a cover background.
Text alignment has been standardized across 8 additional blocks: Post Author Biography, Post Author Name, Post Comments Count, Post Comments Form, Post Comments Link, Post Terms, Post Time to Read, and Term Description.
Interactivity API adds a new watch() function for cleaner side-effect patterns in interactive blocks.
DataViews and DataForm packages received significant updates including new layouts, validation rules, and grouping improvements. Plugin developers using @wordpress/dataviews should review the breaking changes.
Note: Client-Side Media Processing, which was previewed during the beta cycle, was moved to a standalone plugin before the 7.0 release and is not included in core. It will continue to be developed and may return in a future release.
Final Thoughts on WordPress 7.0
We’ve been following WordPress 7.0 development from planning to release, and it’s genuinely exciting to see so many long-awaited features finally ship.
The new AI Connectors screen sets a strong foundation for how WordPress will integrate with AI going forward, and the editor improvements, including responsive block visibility and per-block custom CSS, give site builders and content creators the tools they’ve been wanting for a long time.
And if you’re on a busy or mission-critical site, consider testing on a staging environment before pushing to production. Once you’re in, set aside a few minutes to explore the new features, especially the Connectors screen and the revisions improvements. They’re easy to miss but genuinely useful.
If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.
The latest episode is 
