I spend 8+ hours a day building with AI. Claude, Cursor, Telex — I’m in it. I love these tools. I also love WordPress. And I’m tired of people telling me I have to pick one.
Here’s what nobody in the “AI will kill WordPress” crowd seems to understand: I have never once considered replacing the WordPress layer with something AI generated. Not once. And I build with AI every single day.
Think about it like remodeling a house.
When you renovate, you rip out the ugly kitchen. You tear down a wall to open up the living room. You add a deck. You repaint everything. Maybe you go full HGTV and add an addition.
You know what you don’t do? Rip out the plumbing. You don’t tear out the electrical. You don’t dig up the foundation and pour a new one because you saw a cool new concrete mix on TikTok.
Why? Because the guts work. They’ve worked for years. Every fixture in the house connects to them. Every outlet, every switch, every faucet — all of it runs through infrastructure that was installed once and has quietly done its job ever since.
WordPress is the plumbing.
This isn’t the first time we’ve heard this
WordPress has been “dying” for as long as I can remember. The threats change but the headlines don’t.
Mobile was going to kill it. Remember? Fixed-width PHP themes couldn’t possibly survive the iPhone era. WordPress went responsive and grew from 13% to 21% of the web during the exact years everyone said mobile would finish it off.
Wix and Squarespace were going to kill it. They spent millions on Super Bowl ads with movie stars. They ran attack campaigns. WordPress barely acknowledged them. Today WordPress powers 43% of the web. Wix has 3.7%. That’s not a competition. That’s a rounding error.
Gutenberg was going to kill it. This one came from inside the house. People were furious. Two thousand one-star reviews. A literal fork of the project. And WordPress grew faster in the three years after Gutenberg than almost any period before it.
JAMstack was going to kill it. Developers on Twitter declared WordPress’s architecture “impossible to scale.” WordPress added a REST API, absorbed the headless CMS concept, and grew from 29% to 43% during peak JAMstack hype.
Every single time, the pattern is the same: someone declares WordPress dead, WordPress absorbs the thing that was supposed to kill it, and WordPress gets bigger.
AI is next in line to not kill WordPress.
AI needs somewhere to land
Here’s what the “just vibe code everything” crowd doesn’t talk about: where does the thing you built go?
You can prompt an AI to generate a beautiful website in 90 seconds. Genuinely impressive. But then what? Where’s the content management? Where are the user accounts? Where’s the media library? Who handles the SEO? What about the contact form submissions — where do those go? What happens when your client wants to update a page without calling you?
All of that invisible, boring, essential stuff? That’s what WordPress does. That’s the plumbing.
AI is incredible at generating the visible layer — the themes, the blocks, the custom components, the interactive frontends. The curb appeal. But curb appeal needs a house behind it, and that house needs working pipes.
I use AI to build WordPress blocks. I use AI to write plugin code. I use AI to generate custom CSS and prototype ideas in minutes that used to take days. AI hasn’t replaced WordPress in my workflow. It’s made WordPress better in my workflow. The two aren’t competing. They’re collaborating.
The people who built WordPress get this
WordPress 6.9 shipped with an Abilities API that makes every WordPress function discoverable by AI agents. It shipped with an MCP Adapter so tools like Claude can talk to WordPress directly. There’s now a PHP AI Client SDK baked into core. Telex turns plain-English prompts into working Gutenberg blocks.
The WordPress project isn’t pretending AI doesn’t exist. It’s not circling the wagons. It’s opening the front door and saying “come on in, here’s how everything works, build whatever you want.”
That’s the move. That’s always been the move. WordPress survived every previous threat by absorbing it, and it’s absorbing AI faster than anything that came before.
The real question isn’t whether AI replaces WordPress
It’s whether the WordPress community welcomes AI or fights it.
Because the technology isn’t the risk. The risk is us. It’s WordPress people getting defensive, treating AI as the enemy, gatekeeping who counts as a “real” developer, and making the same mistake every threatened community makes: turning inward when they should be opening up.
WordPress has always been at its best when it’s welcoming. When it says “you don’t need permission to build here.” When it treats a blogger with no technical skills the same as an agency shipping enterprise sites.
AI tools are the next wave of people showing up and saying “I want to build something.” The question is whether we hand them the keys or tell them they’re not welcome because they didn’t learn PHP first.
I know which side I’m on.
Nobody rips out the plumbing. But the smartest homeowners upgrade their fixtures every chance they get.