How AI Is Replacing WordPress Developers

I didn’t want to form a fixed opinion or scaremonger – but AI replacing WordPress developers is already happening, and it is happening from the bottom up.

And the reason is not just WordPress specific. It is universal.

From the bottom up I mean that the first work to go is the work that was always repeatable, for example:

• a 5-page brochure site for a local business
• a theme tweak or a CSS fix
• a snippet copied from a forum thread and adjusted to fit

If that work and these small gigs paid most of your bills, the pressure you have felt this year is real and it won’t ease off.

The work that stays is the part a model can’t be held responsible for. Somebody still has to decide what a site should do and keep it safe once real customers and real money pass through it. Somebody also has to answer when an update breaks checkout at 2 a.m.

My position is simple.

AI has made WordPress code cheap, and it has made responsibility for a live WordPress site more valuable.

I run my own sites through Claude Code (and sometimes ChatGPT Codex) with a plain .env file that carries REST and WP-CLI access. I do manual code reviews, write word by word, handle WordPress problems waking up at 2 a.m., so I want to ensure you see both sides clearly: what AI already does well, and where it leaves a mess for someone else to clean up.

What AI Can Already Do in WordPress

In 2026, AI can build anything, to be honest – from a simple WordPress site to a full-fledged WooCommerce store. It can also operate a live site through the site’s own API, which is the bigger change.

The WordPress itself is being rebuilt so AI agents can work inside it:

• The Abilities API arrived in WordPress 6.9 in December 2025. It gives plugins a standard way to register actions with typed inputs and permission checks.
• WordPress 7.0 Armstrong shipped on May 20, 2026 with an AI Client in core and a Connectors screen where a site owner adds AI providers in one place. WordPress 7.1 followed on August 19, 2026.
• The official AI plugin writes alt text, titles, excerpts and meta descriptions, translates content and generates images. It has 60,000+ active installs.
• The MCP Adapter exposes those abilities to agents such as Claude Code. It is still prerelease, at version 0.7.1, and already has 50,000+ active installs.
• And then there are tools like Site Agent, Novamira, WPVibe – which can do these and a bit more.

I covered how these pieces fit together in AI in WordPress. The short version is that WordPress now expects AI agents to log in and do work alongside people.

Matt Mullenweg, the cofounder of WordPress, showed how far the coding side has come. In his WP AI post, he described a Claude Code session that “completed a cleanroom implementation of the ACF plugin* in about 45 minutes.“

(*ACF is Advanced Custom Fields, one of the most used developer plugins, and he stopped the run before it rebuilt the Pro features.)

The builders and hosts moved just as fast:

• Elementor released Angie as a beta plugin in September 2025 and formally introduced it on March 23, 2026. It is an agent that builds widgets, snippets and custom post types, and it has 100,000+ active installs.
• Bricks 2.4 added experimental AI abilities in September 2026. It is as good as it gets (but still under beta).
• WordPress.com launched an AI website builder in April 2025. I haven’t tried it but I don’t think it can build complex websites. Their Telex was an attempt to do a bit more, but it has been retired – so let’s not talk about that.
• Hostinger says more than 1 million people tried its AI Builder in its first year. That builder makes sites and apps outside WordPress.

Developers have moved too.

In the Stack Overflow 2026 Developer Survey, 73% of developers who use AI coding assistants use them every day, and Claude Code was the most used coding agent.

The WordPress Work AI Is Replacing

As far as I can tell, the pressure is uneven. It lands hardest on work with a known answer and barely touches work where someone has to take responsibility for a live site.

WordPress work	What AI does now	What still needs a developer
Brochure sites for small businesses	Drafts the pages, layout and copy from a prompt	The offer, the positioning and the path to a sale
Theme and CSS changes	Handles many layout fixes in one attempt	Testing on real devices and browsers
Snippets and small plugins	Writes valid PHP that usually runs on the first try	Capability checks, escaping and hook timing
Custom blocks	Scaffolds a working block from a description	Editor experience and markup changes over time
SEO and content chores	Writes alt text, excerpts and meta descriptions	Deciding what deserves to be published
WooCommerce, migrations and hacked-site cleanup	Speeds up diagnosis and log reading	Production access, judgment and accountability

If most of your invoices come from the first 3 rows, expect your rates to keep falling. A client can now see a draft site in minutes, so a quote for 2 weeks of work looks expensive even when the 2 weeks are justified.

Matt Schwartz, who runs a WordPress agency, said as much on the WP Tavern Jukebox podcast: “Brochure sites I think are going to continue to drop.” He was talking about price, because clients now know AI makes simple sites cheap.

Plugin businesses feel it too. Collins Agbonghama, lead developer of ProfilePress, told the Blocksy blog that some agencies “churned because they’ve been able to replace our plugin with an AI-assisted coded one.” Those agencies had bought the plugin for a single small feature.

The early freelance data points the same way. Demirci, Hannane and Zhu studied a large freelance platform after ChatGPT’s launch, in research later published in Management Science. Within 8 months, posts for software, app and web development jobs fell about 21% compared with jobs that need manual work.

That study covers the first months after ChatGPT. The tools in the lists above are now far more capable than what those freelancers were up against. So, the challenge is even more acute.

WordPress Market Share

The quieter change is that AI is also replacing WordPress itself on some small sites.

On October 18, 2026, W3Techs shows WordPress running 39.6% of all websites. That is down from 43.6% on January 1, 2025 – a big drop of 4 percentage points, and the share has fallen every month this year. Over the same period, sites using no CMS at all rose from 29.6% to 32.1%.

My reading is that a growing number of small sites never touch a CMS now. Vibe coding tools such as Wix’s Base44, Replit’s AI, etc., generate and edit a site or an app as code.

WordPress developer Brian Coords expects the same, mainly for small sites and landing pages. In a post, he wrote that “we’re absolutely going to see more vibe-coding taking market share from WordPress.”

And now Cloudflare’s EmDash CMS is here to compete with WordPress. It is built with Astro and runs on Cloudflare Workers (and compatible servers) and has easy import from WordPress. More than that, it is more AI-friendly than WordPress to begin with. But the EmDash plugins and themes are still very few and don’t cover the needs of most sites – and the eCommerce capabilities are minuscule.

Whatever the matter, WordPress is still the default for sites that do use a CMS, at 58.4%. But the client who skips WordPress also skips the WordPress developer, and that is a loss no AI plugin inside WordPress can win back.

Who Owns the Small-Business Client

The bigger shift is who a small-business owner talks to first.

For years the path was simple. An owner searched for help and found a WordPress developer, and the developer picked the host.

Now the host gets there first, before the developer. The hosting checkout offers an AI builder, and the site exists before any developer is called. So, it is not one thing that is challenging the devs – the whole ecosystem is.

I think while this is too harsh on developers, the hosts have every reason to push this. A site built inside their builder keeps the customer on their platform, and that customer renews with them instead of following a developer to another host.

The developer used to own the relationship and recommend the host. Now the host owns it, and the developer gets the call only when the AI-built site needs something the builder can’t do.

So your first contact with a client has to come from somewhere a hosting checkout can’t reach, such as referrals and your own published work.

What WordPress Developers Are Saying

The mood among WordPress developers depends on which clients they serve. These posts from the last few months read like reports from 2 different markets:

• I have seen a freelancer with nearly 20 years in business telling that new leads and their businesses dried up – as everyone is now going to AI builders.
• Some say, “If you’re using WordPress, Drupal, etc, then AI is devastating.”
• In a Hacker News thread, a developer who runs WordPress for clients wrote that “most of the ‘AI WordPress killers’ are just glorified chatbots.” They added that 99% of their clients are still on WordPress.
• Clients have tried to vibe-code their sites but the AI slop and security issues are completely visible. These vibe-coded sites are not tailored to scale.

Both sides are right about their own clients. The developers losing leads mostly sold small sites to owners who shop on price, which is the same work AI builders now handle. The ones holding steady serve clients who run their business on the site, and those clients still want WordPress and someone to call.

The Junior Developer Problem

This is the part I think the WordPress community is underrating.

The Stanford Digital Economy Lab’s “Canaries in the Coal Mine” paper, revised in August 2026 with payroll data through June 2026, found this:

• Employment of workers aged 22 to 25 in AI-exposed jobs is 19% below where it would be if it had kept pace with less-exposed peers.
• Older workers in the same jobs show no comparable gap.
• The drop comes mainly from fewer new hires. The authors describe the pattern and don’t claim AI caused it.

Job postings tell a similar story. Indeed’s index of software development postings stood at 78.1 on October 9, 2026, about 22% below February 2020. Indeed also found that 71% of the increase in software development postings between May 2025 and May 2026 came from senior roles.

Many junior WordPress developers learned on brochure sites and small plugins, which is exactly the work AI now does. That work taught them how WordPress breaks before anyone trusted them with something that mattered. Take it away and you have to ask where the next senior WordPress developers will come from.

A developer on Hacker News went further in August 2026, writing that “most entry level friendly engineering opportunities are likely about to be decimated.” I think that is too strong for WordPress, where millions of small sites still need affordable upkeep, but the direction is right.

If you run an agency, it is wise to keep hiring juniors and give them review work. Reading AI output against the WordPress security model teaches more than writing the tenth settings page by hand.

If you are the junior, learn by fixing. Broken production sites teach faster than new builds, and AI-built sites will supply plenty of them.

What AI Still Gets Wrong in WordPress

At the moment, if the vibe-coder knows what they are doing – AI doesn’t fail. But this is subject to the fact that they are proficient in PHP and the WordPress API.

But for someone who is not a WordPress developer, AI writes WordPress code that works in a demo and fails in production, and the failure is usually silent. They have no idea what is happening.

Every plugin runs in the same PHP process as core and every other plugin, with full access to the database. Many mistakes there don’t crash anything. They just leave a door open.

These are the places AI-written WordPress code breaks most often:

• a REST route registered without a real permission callback
• output echoed to the page without escaping
• options saved with autoload on, so they load on every request
• SQL built by joining strings instead of using $wpdb->prepare()

I walked through each of these with fixed code in Vibe Coding WordPress: Where AI-Written Code Breaks.

The WordPress.org plugin review team sees AI-written code more calmly than I do. In its 2025 review, it wrote that AI “has lowered the barriers to entry without compromising plugin quality.” Its reviewers also cleared a queue that peaked near 1,050 plugins in mid-April, with AI-assisted checks helping and people making the final call.

I take them at their word for the plugins they review. The bigger risk, as I see it, is the far larger pile of AI-written code that goes straight onto client sites and never sees a review queue at all.

Building with AI is easy but handling bugs – not.

Will AI Replace WordPress Developers?

AI will replace WordPress developers who sell code by the hour for problems with known answers. The developers clients trust with a live business will stay in demand as long as a model can’t be held responsible for a breach or a lost sale.

The official outlook is steady. The US Bureau of Labor Statistics projects 5% growth for web developers and digital designers from 2025 to 2035. Median pay for web developers was $92,650 in May 2025, and the bureau notes that AI “may soften the employment growth.”

These are the WordPress developers I expect to do fine:

• Developers who own outcomes. A care plan with monitoring and a promised response time sells a promise that someone answers, and clients keep paying for it.
• WooCommerce and membership specialists. A bug in a store costs money every hour it stays live, so clients pay for experience.
• Performance specialists who measure first. AI will suggest changes all day. Someone has to test them on the real site and explain the tradeoff.
• Developers who build for agents. Registering abilities, scoping permissions and deciding what an AI agent may touch on a site is WordPress work, and it is new.
• Developers who review and repair AI-built sites. This share of the work grows with every AI-built site that goes live.

The job title stays the same. More of the job becomes reviewing and approving code rather than typing it.

What to Do If You Build WordPress Sites

Remkus de Vries, a long-time WordPress developer, put the hard part well in a post: “the difficulty you endured doesn’t entitle you to a profession that stays the same.” I agree with him, and I’d rather adjust early than late.

You don’t need to pick between ignoring AI and handing it your whole business. These are the moves I’d make now:

1. Use AI for the repeatable parts today. Settings pages, block scaffolds, WP-CLI commands and tests are where it saves hours. If you’re choosing a tool, I compared the two I know best in Claude Code vs Cursor. Be honest about AI – and embrace it.
2. Stop billing hours for work AI finishes in minutes. Price the result and the responsibility, such as a working checkout or a migration with a tested rollback plan.
3. Learn the WordPress security model well enough to review AI code. You should spot a missing capability check, an unescaped output and an unprepared query on sight.
4. Learn the Abilities API and the MCP Adapter. This is where the future of WordPress development is easiest to see. Sites that agents operate need someone who decides what each agent may do, and that person should understand WordPress permissions.
5. Sell ongoing care alongside builds. A care plan with monitoring and a promised response time is something an AI builder can’t sell.
6. Own your client channel. Referrals and your own content reach clients before a hosting checkout does.

FAQs on AI and WordPress Developers

Will AI completely replace WordPress developers?

I don’t expect it to for production work in the next few years. AI handles tasks with known answers well, but a live site needs someone accountable when it breaks or gets hacked. Simple brochure sites are the exception, and AI builders already handle many of them.

Is WordPress development still a good career in 2026?

Yes, if you move toward work with responsibility attached, such as store builds and ongoing maintenance. Entry-level WordPress developer jobs are likely harder to land now, because junior hiring across software has slowed while senior postings have grown. WordPress still runs 58.4% of sites that use a CMS, so the installed base needing care is huge.

Can AI build a WordPress site on its own?

It can build a simple site from a prompt, and WordPress.com and Hostinger both offer AI builders that do this. It can build a store too, but stores and custom features still need a developer to review the code and own the result.

Should I still hire a WordPress developer?

Hire one when money or customer data is at stake. For a 5-page site with no custom features, an AI builder is a reasonable place to start, and you can bring in a developer when the site starts earning.

Final Remarks

AI has made WordPress code cheap, and that won’t reverse. Being the person who answers for a live site is still expensive, and every AI-built site adds to the demand for that person.

If you build WordPress sites, price your work by the responsibility you carry and let the AI do the typing.