WordPress Is Dying. Pivot Or Die With It.

Let us begin with the number you have used to comfort yourself at every conference, every client pitch, every awkward dinner-party question about what you do for a living. Forty-three percent of the web runs on WordPress. You repeat it like a prayer. You put it in slide decks. You use it to justify another year of not learning anything new. It is the market-share equivalent of a security blanket, and it is lying to you.

Forty-three percent of the web also includes every abandoned blog from 2011, every parked domain a plumber bought and never touched, every dentist's five-page brochure that has not been updated since his receptionist left in 2018, and every hollow shell of a site that still resolves only because nobody remembered to cancel the hosting. It is a census of the living and the dead, and the dead are winning. Market share is not a heartbeat. It is a headcount at a graveyard.

“You are not defending a platform. You are defending a habit that pays your mortgage.”

The receipts are in. Read them.

W3Techs still lists WordPress at the top, but the trend line has been sliding for three years running. The share peaked, plateaued, and started leaking to Shopify, Wix, Squarespace, Framer, Webflow, and — increasingly — to sites that were built with an AI prompt and deployed to an edge network the developer could not name if you paid him. Automattic has laid off staff. Matt Mullenweg has spent the last two years in a public brawl with WP Engine that made the entire ecosystem look like a divorce court, not a technology community. The core contributor count is down. The plugin economy is being strip-mined by private equity. The block editor is still, six years on, the thing every serious agency turns off first.

You know all of this. You have lived it. You have quietly, over drinks, admitted to another developer that the last three WordPress projects you shipped felt like assembling IKEA furniture in a house that was already on fire. And then you went back to work on Monday and quoted another WordPress build, because that is what your pipeline is, and pipelines have inertia, and inertia feels like a strategy right up until it isn't.

The stack is a Jenga tower and someone is shaking the table.

Count the moving parts of a typical WordPress site in 2026. A managed host you overpay for because raw LAMP terrifies your junior developers. A page builder — Elementor, Divi, Bricks, take your pick of hospice — that ships more JavaScript than a small React app and renders half the speed. A form plugin. A backup plugin. A security plugin whose entire business model is convincing you the platform is not secure by default, which is a confession dressed up as a feature. A caching plugin to un-break the performance the page builder broke. An SEO plugin whose upsell email arrives with the reliability of a debt collector. A membership plugin. A GDPR plugin. A cookie plugin. A plugin to manage your plugins.

• →Every plugin is a private-equity acquisition target. When it flips, the pricing flips, the roadmap flips, and your client's site flips with it — and you are the one on the phone at 9pm explaining why the invoice went up.
• →Every plugin update is a coin toss. Update in sequence and half a day disappears. Skip updates and the security plugin sends daily emails written in the tone of a hostage negotiator.
• →Every plugin author is one burnout, one buyout, or one abandoned repo away from becoming your problem forever. You do not own the stack. You rent it from forty strangers.

This is not a platform. It is a supply chain with no supplier of last resort. And you have been calling it 'flexibility' for so long that you have forgotten flexibility was supposed to reduce risk, not manufacture it.

Your clients never cared. They still don't.

Here is the sentence that will get me the most email, so let me be precise: the client does not know what WordPress is, does not want to know what WordPress is, and has never once made a purchasing decision based on the CMS underneath their brochure site. They care about the phone ringing. They care about the form filling. They care about the Google result their brother-in-law saw last week. The CMS is invisible to them and always was. You invented its importance so you could sell hours against it.

For twenty years that trade was fair. You knew a stack, they didn't, and you got paid to bridge the gap. That trade is now over. AI-native builders, Framer, Webflow, and a class of hosted platforms nobody had heard of in 2022 will produce a brochure site in a working morning that is faster, more accessible, cheaper to host, and will not need a security plugin at 11pm on a Sunday. Your client will never know. Your client will never ask. Your competitor is already doing it.

“The moat wasn't the CMS. The moat was the client's ignorance. AI just drained it.”

The identity trap — the reason you keep quoting WordPress anyway.

Every developer I have watched refuse to pivot has done so for the same reason, and the reason is never technical. It is identity. You did not just learn WordPress. You joined it. You went to WordCamps. You wrote a plugin. You have a favourite hook and an opinion about the difference between actions and filters. You know which theme framework you would defend at knifepoint. You have a WordPress-shaped hole in your résumé and a WordPress-shaped hole in your self-image, and switching stacks feels like betraying a tribe that fed you.

I understand this. I was there for the tribes before this one. I watched Flash developers refuse to see the iPhone announcement for what it was. I watched jQuery specialists insist React was a fad. I watched Perl guys sneer at PHP, then PHP guys sneer at Node, then Node guys sneer at serverless, and every single one of them was on the wrong side of the sentence 'the industry moved on without me.' The tribe is not going to save you. The tribe is going to a farewell dinner and you are not on the invite list because you keep insisting the restaurant is still open.

What the pivot actually looks like.

Pivoting does not mean deleting your WordPress installs on Monday. It means stopping the bleeding. It means the next project you quote is not a WordPress project unless the client has a genuine, articulated reason it must be one — and 'because we already have it' is not a reason, it is a symptom. It means every retainer conversation for the next twelve months is a migration conversation in disguise. It means the training budget you were going to spend on another Advanced Custom Fields course goes to whichever AI-native or hosted stack you would rather bet the next decade on.

• →Audit your book of business. Sort by revenue and by pain. The top-right quadrant — highest revenue, highest pain — is where the migration playbook starts. Not the small clients. The ones that are actually keeping the lights on.
• →Reprice everything as outcomes, not hours. The moment your invoice stops itemising 'WordPress theme customisation' you have started the pivot. The client did not want the theme customisation. They wanted the phone to ring.
• →Kill the maintenance retainer as a line item. Roll it into a hosted, opinionated stack you actually control. Every hour you spend babysitting somebody else's plugin is an hour your competitor spent shipping.
• →Retrain one developer this quarter, not next year. One. Give them a real project, not a course. The course industry is the last plugin ecosystem — a marketplace of people selling you the illusion of preparation.

The uncomfortable arithmetic.

Take the last twelve months of your agency's revenue. Split it into three buckets: net new WordPress builds, WordPress maintenance and rescue work, and everything else. If the first two buckets are more than sixty percent of your revenue, you are not running an agency. You are running a hospice ward with an invoice book. Hospices are noble. They are also, by design, terminal. The residents do not leave through the front door.

The agencies that will still be here in 2029 are the ones that looked at that arithmetic in 2026 and moved. Not the ones that wrote a blog post about how 'WordPress is still relevant' — that post is being written, right now, by somebody whose entire pipeline is WordPress and whose entire retirement plan is WordPress not dying before he does. That post is not analysis. It is a hostage note.

“You do not have to hate WordPress to leave it. You just have to be honest about who it is still working for.”

The eulogy, and the exit.

WordPress fed a generation of developers, myself included. It democratised publishing when publishing needed democratising. It made a lot of very ordinary people into small business owners, and a smaller number of extraordinary people into wealthy ones. None of that is being taken away. History does not require you to keep shipping into a dying stack in order to honour it. Nobody thanks the Blockbuster manager who kept renting videotapes in 2012 out of loyalty to the format.

You have a choice this year, and it is a simple one. Either you write the pivot memo, retrain the team, reprice the offer, and start moving the book of business off the corpse — or you keep quoting WordPress builds, keep collecting the maintenance retainer, keep telling yourself that forty-three percent is a heartbeat, and keep pretending you didn't read this. Both are legitimate choices. Only one of them still has a market in five years.

Pivot, or die with it. The corpse is not going to argue either way.