Is WordPress dying? What the W3Techs market-share data actually says

The short answer before anyone panics

WordPress is not dying. It has been shedding fractions of a percentage point month after month since late 2025, but it still powers 41.2 percent of all websites on the internet and 59.1 percent of the sites that use any recognized CMS at all. The nearest rival, Shopify, sits at 5.3 percent. That means WordPress is still almost eight times larger than whatever is next in line. The headline about a sustained decline is true. The conclusion that the platform is winding down is not.

I run a WordPress agency and I have helped organize the European side of this ecosystem for years. I am not writing this to defend my own stack. I am writing it because clients have started forwarding these charts asking whether they should flee to a no-code builder. The short answer is: look at who is actually gaining in this data, because it is not a competing CMS.

#What the W3Techs data actually shows

Start with the numbers, not the feelings. W3Techs measures technology usage across the top ten million domains, and it is their data that drives the industry headlines. As of 30 July 2026, WordPress sits at 41.2 percent. In May 2025 it was 43.5 percent, and in December 2025 it was still 43.2 percent. Search Engine Journal described the earlier run as six consecutive months of decline, the first such run in years.

Three things stand out once you set aside the WordPress row itself. First, the decline is slow rather than a cliff. Second, the classic CMS competitors moved much less. Third, the largest change is None, W3Techs’ label for sites where it detects no monitored CMS.

#The trend line over a decade, not a quarter

Zoom out and the panic loses its shape. W3Techs has tracked WordPress since 2011, when it sat around 13 percent of all websites. It climbed almost without interruption through the 2010s, crossed 30 percent around 2018, and reached the low forties by the early 2020s. Since roughly 2022 the line has been flat, parked between 43 and 43.5 percent for the better part of three years. What we are looking at now is not a plunge from a peak, it is the first sustained dip after a long plateau. A platform that spends three years flat and then gives back a point and a half has stopped growing. It has not started dying. Those are different diagnoses, and the ten-year chart makes the difference obvious in a way a six-month window never will.

It also helps to see WordPress next to the rest of the field rather than in isolation. W3Techs publishes two numbers for every CMS: its share of all websites, and its share of the market of sites that run a recognized CMS at all. The second column is the one that describes competitive position, and it is where WordPress’s lead is almost comically wide.

Read the right-hand column slowly. Among sites that chose a CMS, nearly six in ten chose WordPress, and the entire chasing pack of Shopify, Wix, Squarespace, Joomla and Drupal combined does not add up to half of WordPress’s slice. BuiltWith, which counts live sites rather than sampling top domains, tells the same story by a different method: WordPress is the most widely deployed CMS on the web by a margin measured in tens of millions of live installations. Two independent measurement approaches, one conclusion. A category leader does not lose its lead by shedding the cheapest tail of its own userbase.

#It is not a competitor winning, it is the no-CMS category

None in the W3Techs vocabulary does not mean nothing. It means sites where no known content management system could be detected. That can include hand-coded HTML, output from frontend frameworks like Next.js or Astro, static-site generators, headless delivery, and sites assembled by AI tools that produce finished output with no detectable CMS. The category grew from 28.6 percent in December 2025 to 30.4 percent on 30 July 2026.

This is the whole point the headlines miss. The named competitors did not grow fast enough to mirror the WordPress decline, while the no-detectable-CMS category grew more strongly. That is correlation, not migration evidence: W3Techs cannot tell us which WordPress sites moved where, or why. It does show that the market change is broader than one CMS replacing another.

Break it down by intent and the picture sharpens further. The bottom of the market, the simplest sites that historically landed on a free WordPress theme, are now just as easily produced in a browser by an AI website builder in fifteen minutes. Those sites were never high-margin projects. Their departure lowers the share bar but barely touches the value the WordPress ecosystem actually creates.

#Why WordPress is shedding fractions of a point

Four plausible forces are worth testing rather than presenting as settled causes. AI-built sites can ship static output with no detectable CMS. SaaS builders continue to grow slowly. Headless architecture can keep WordPress underneath while hiding its fingerprint from a frontend scan. Ordinary churn can also remove abandoned WordPress domains from the sample. W3Techs alone cannot rank those explanations.

Notice that three of those four forces are not a story about WordPress being weak. They are a story about the simplest site no longer requiring any CMS, and about a measurement method that structurally undercounts headless. WordPress still wins where a site is meant to live: to be edited, extended, integrated with payments and logistics, and maintained for years. It loses where a site is meant to be built once and never change, which was never its strongest or most profitable territory.

#The counter-evidence the headline ignores

There is a number the “dying” story needs but these market-share charts do not provide: a comparable time series of active WordPress installations. Share and absolute count are different measures. WordPress can lose share while gaining sites, or lose both at once. W3Techs’ percentage alone cannot decide between those scenarios, and BuiltWith’s deployment totals should not be substituted without comparing the same population over time.

Then there is where the project is spending its energy. Gutenberg and block themes have turned the editor from a liability into full site editing, so the design flexibility that once pushed people toward page builders now ships in core. The commercial ecosystem underneath WooCommerce still moves a large share of independent online retail, the catalogue-and-checkout work no prompt-to-site tool will carry. And the platform is not sitting out the AI wave that supposedly threatens it: WordPress has stood up its own AI effort to bring assisted authoring and site building inside the CMS rather than cede that ground to external generators. Enterprise adoption has if anything hardened, with major publishers and brands running on managed WordPress precisely because the open licence and the deep talent pool remove the vendor lock-in a closed builder quietly reintroduces.

None of that erases the decline. It reframes it. A dying platform stops investing, loses its enterprise base, and watches its absolute numbers fall. WordPress is doing the opposite on all three counts while giving up the one segment, the disposable single-page site, that it was never especially good at monetizing in the first place.

#What it means for a business choosing a platform in 2026

The useful question is not “WordPress or not”, it is “what kind of project is this”. If you need a one-off brochure page with no plans to grow, then yes, a static generator or an AI builder will close the case and there is no shame in that. But if your site is meant to be alive, regularly updated, extended with new sections, wired into a store, a CRM or a booking system, and maintained for several years, then WordPress’s advantage has not changed by a hair over this fraction of a point. The scale of the ecosystem, plugin availability, depth of talent, and absence of vendor lock-in are exactly where they were.

Here is the practical test I give clients. Write down how many times a year someone on your team will want to change content, add a page, or wire in a new integration themselves. If the answer is near zero, a builder is fine. If it is a two-digit number, every hour saved today on a cheaper tool comes back as a cost the moment you want to do something the tool did not anticipate. That is why our WordPress project pricing stays individual: it depends on whether we are building a living site or a tombstone.

#What it means for WordPress developers

For people who make a living on this platform, the decline headline sounds scarier than it is. Demand is not shrinking, it is shifting. The simplest, cheapest sites are leaving, and those are precisely the low-margin jobs that were first to lose the price war with freelancers anyway. What remains, and relatively grows, is the work an AI builder will not touch: architecture decisions, performance budgets, security posture, payment and logistics integrations, migrations, maintenance, and fixing what AI generated and then collapsed under its first real traffic.

In other words, losing the bottom of the market raises the relative value of senior work. This is exactly the piece I wrote about in the article on who a WordPress developer is and what they really do: value shifts toward judgment, and judgment has no “generate” button. The most exposed person is not the WordPress developer, it is the seller of the cheapest templates who competed on price alone.

#A view from the workbench

It shows up most concretely in a real question I got recently. A client running a WooCommerce store had just read one of these charts and wrote that, “since WordPress is dying”, maybe he should move to something more modern. We sat down with the numbers. His store had tens of thousands of SKUs, an integration with a warehouse system, and monthly campaigns that needed on-site changes. Migrating to a closed builder meant rewriting every integration from scratch, losing control of his data, and a monthly fee that scaled with revenue. WordPress “dying” had no operational meaning here at all. What mattered was that no no-CMS tool would carry his catalogue and his process.

The second observation is timely as of May 2026. In a few days WordCamp Europe opens in Kraków, the largest European conference for this ecosystem, and the room will be full of agencies and companies building real businesses on WordPress. An ecosystem that is losing relevance does not draw several thousand people to its own conference. That, too, is data, it just does not fit in a W3Techs table.

#Dying or maturing? The honest verdict

Put the two readings side by side. The bear case is a sustained decline after a long plateau. The bull case is a still-dominant CMS-market share near 59 percent and active investment in editing and AI. Both descriptions fit the measured data. “Maturing” is a more useful working diagnosis than “dying”, but it remains an interpretation that should be tested against active-site counts, project investment, and demand rather than claimed from one percentage alone.

#The point: share is not the same as usefulness

The drop from 43.5 to 41.2 percent in fifteen months is real and worth watching, but it measures one thing that nobody should confuse with another. It measures what fraction of W3Techs’ surveyed websites can be attributed to WordPress. It does not establish the cause, the absolute active-site trend, or whether WordPress is a good choice for the project in front of you. Those are separate questions.

The most honest summary is this: WordPress is handing the bottom, cheapest segment of the market to no-CMS tools, while keeping the projects that have to be edited, integrated and maintained. For a business with that kind of project, and for a developer who can run one, this data is good news rather than a warning. If you are wondering which side of that line your idea falls on, get in touch and let’s scope it before you decide on the strength of a headline alone.

Last updated: 30 July 2026.