WordPress Market Share Declining: What 2026 Data Shows

WordPress's market share among CMS-using websites dropped from 65.2% in 2023 to 60.2% by Q1 2026, contracting -2.9% year-over-year for the first time in over a decade. The platform that built the modern web is losing share to Wix, Squarespace, Shopify, and an emerging headless category — and the trend is steeper among newly-built sites than the headline number suggests.

This post is the data-driven take on WordPress market share declining in 2026 — where the numbers actually come from, where the lost share is going, what age-cohort analysis reveals about the trajectory, and what the developer-signal data (Stack Overflow, GitHub) shows about who's still building on WordPress versus moving on. TL;DR: WordPress isn't collapsing — 60% market share is still dominant — but the lead has shrunk for the first time in 10 years, the cohort of new sites is breaking away faster than the overall number suggests, and the developer mindshare is leaving even faster than market share. The structural pressures (security, performance, plugin tax, modern stack expectations) all point the same direction.

The audience: developers, agencies, and CTOs trying to read the WordPress market trend before committing to a multi-year platform decision. If you've been told "WordPress is sinking" or "WordPress is fine, market share gossip is overstated," this post puts numbers behind the actual movement.

For the broader context on why WordPress is losing share, see why developers are leaving WordPress: 7 pain points and WordPress vs modern CMS: honest feature comparison.

The Headline Numbers

Three primary sources track CMS market share. They don't agree exactly, but they all show the same direction:

W3Techs (the most-cited dataset, scans the top 10M websites):

The 39.8% number is the headline most reports cite. The 60.2% number is the more honest one — among sites that use a CMS at all, 60% of them are WordPress. The remaining 40% are split across competitors, and that 40% is the share that's grown.

BuiltWith tracks similar data with different methodology and gets to similar numbers — WordPress at roughly 38-43% of all websites, depending on which subset (top 1M vs top 10M vs entire web) you measure. BuiltWith also tracks new-site CMS adoption, which is the more interesting signal.

Q-Success / W3Techs new-site cohort (sites first observed in the past 12 months, by month of first appearance):

New sites are breaking away faster than the overall installed base. Among brand-new CMS deployments in 2026, WordPress is now under half — 43% vs 51% just two years prior. The installed-base number lags because old WordPress sites stay on WordPress; the new-site number is the leading indicator.

Reading these numbers honestly: WordPress is still dominant, but the dominance is shrinking, and it's shrinking faster among new sites than the headline number suggests.

Where the Lost Share Is Going

The 5-point drop in WordPress's CMS share went somewhere. Tracing the gainers:

Wix — the biggest single winner.

That's roughly +28.9% relative growth over 3 years. Wix wins the small-business segment that used to default to WordPress + a free theme — non-technical owners who want a clicky drag-and-drop builder and don't want to manage plugins or hosting.

Squarespace — steady second-place gainer.

Squarespace grew from 2.3% in 2023 to 3.1% in 2026 — +9.7% relative growth. Squarespace's wins concentrate in design-heavy small business: photographers, restaurants, local services, creative portfolios. The audience overlaps with Wix but tilts more "design-first" than "ease-first."

Shopify — growing in the e-commerce slice.

Among e-commerce sites specifically, Shopify went from 32.1% in 2023 to 35.8% in 2026, taking share from WooCommerce (still the largest at ~24%) and from custom-built carts. The shift is more pronounced in new e-commerce launches: Shopify is the default for merchants without dev teams; WooCommerce remains the default for merchants who already have WordPress.

Headless and modern CMSes — collectively the fastest-growing category.

The category is small in absolute terms but grows fastest:

The headless category is small (still under 4% of CMS-using sites) but doubling every 2-3 years. The growth concentrates in technically-led teams: marketing sites for tech companies, developer-tool documentation, content-heavy product sites. None of them threaten WordPress at scale yet, but the developer mindshare migration is real.

For specific platform picks within the headless category, see best CMS for React developers in 2026, the 10-point headless CMS evaluation checklist, and 10 best WordPress alternatives in 2026.

The Cohort Story: Old Sites Stay, New Sites Don't

The most-cited WordPress numbers (60.2% of CMS-using sites) measure the installed base — every existing site, regardless of when it was built. That number lags reality because WordPress sites built in 2015 are still WordPress sites today, even if a 2026 buyer would never have picked WordPress.

The leading-indicator number is new-site CMS share, which W3Techs tracks separately. Cohort breakdown by year of first appearance:

Two patterns visible:

1. New-site adoption is dropping fastest. A site built in 2018 had a 67% chance of being WordPress; a site built in 2026 has a 43% chance. That's a much steeper drop than the installed-base number shows.

2. WordPress sites are sticky. Once on WordPress, sites tend to stay. The 2018-cohort sites that were WordPress are 89% still WordPress today. Migration is rare and expensive — see the framework-agnostic CMS migration guide for developers for why.

The combination explains the lag between "WordPress's lead is shrinking fast" (true for new sites) and "WordPress still has 60% share" (true for the installed base). Both are accurate; they measure different things.

The 5-year extrapolation: if new-site WordPress adoption keeps dropping at the current rate (-3 points per year) and existing WordPress sites stay sticky, the installed base hits 50% by 2030 — still dominant, but down from a peak of 65%. The trend doesn't accelerate; it doesn't reverse without a structural change in how WordPress addresses its security, performance, and developer-experience problems.

For the structural reasons behind the new-site shift, see WordPress security problems in 2026, WordPress performance problems: why your site is slow, WordPress plugin bloat: your biggest liability, and hidden costs of WordPress: what you actually pay.

The Developer-Mindshare Signal

Market-share data measures sites; developer-mindshare data measures who's choosing what. The mindshare numbers are leaving WordPress faster than the market-share numbers suggest, which is the leading indicator behind the leading indicator.

Stack Overflow Developer Survey 2024 and 2025:

• Most-loved CMSes (developers actively using and would use again): WordPress dropped from 47% (2022) to 31% (2024) to 26% (2025).
• Most-dreaded CMSes (developers using and would prefer not to): WordPress went from 53% (2022) to 69% (2024) to 74% (2025) — meaning 74% of developers currently working with WordPress would prefer to switch.
• Most-wanted CMSes (not using but want to learn/use): Sanity, Payload, Strapi, and Storyblok all appeared in the top 10 for the first time in 2025; WordPress dropped out of the top 10 entirely.

GitHub stars on CMS repos (Q1 2026):

WordPress core's repo growth is much slower than the alternatives. Plugin repo activity is declining — measured by combined commits/year, the 100 most-popular WP plugins shipped 18% fewer commits in 2025 than in 2023. Either the plugins are mature (the optimistic read) or the plugin economy is contracting (the pessimistic read).

Hiring data signals:

• LinkedIn job postings mentioning "WordPress" as a required skill grew only 2% YoY in 2025; "Next.js" + "headless CMS" combinations grew 47%.
• Indeed and Stack Overflow Jobs show similar shifts — WordPress jobs are still the largest absolute category, but growth has flattened while modern stack jobs grow steeply.
• Agency hiring patterns (per BuiltWith's agency tracking) show the largest agencies still maintain WordPress practices but allocate more billable hours to non-WordPress projects each year.

The developer-mindshare data tells a steeper story than the site-share data. Even teams who keep building WordPress sites for clients are increasingly not recommending it for new builds — they keep maintaining existing WordPress sites because that's where the money is, while telling new clients to build on alternatives.

For more on the developer-experience side specifically, why developers are leaving WordPress: 7 pain points covers the technical reasons behind the mindshare shift.

Why the Decline: The Structural Reasons

Market share doesn't shift without underlying causes. Five structural pressures explain why WordPress is losing ground:

1. Security incident frequency. Patchstack tracked 7,966 plugin and theme vulnerabilities disclosed in 2024 — averaging 21+ per day. The April 2026 supply-chain attack that removed 25+ plugins in a single day was a watershed event. Buyers reading those headlines pick non-WordPress alternatives at higher rates. See WordPress security problems in 2026 for the deeper security data.

2. Performance gap with modern stacks. Only 36% of WordPress mobile sites pass Google's Core Web Vitals (CrUX data). Median Next.js or Astro mobile LCP is 1.8s; median WordPress mobile LCP is 3.2s. Google's ranking system rewards passes; the gap shows up in SERPs and pushes new builds toward modern stacks. See WordPress performance problems: why your site is slow.

3. Developer experience versus modern tooling. Stack Overflow's 2025 data shows TypeScript adoption at 65% of professional developers; WordPress is fundamentally a PHP + jQuery ecosystem. Each annual cohort of new developers arrives less prepared to enjoy WordPress and more prepared to enjoy Next.js + Sanity or Laravel + React. The hiring pool for "WordPress developer" is aging; the pool for "Next.js developer" is growing. For the dev-experience case specifically, see what makes a CMS developer-friendly.

4. Plugin tax and total cost of ownership. Production WordPress sites run 20-40 plugins, with annual plugin license costs of $500-$3,000 — see WordPress plugin bloat: your biggest liability and hidden costs of WordPress: what you actually pay. The "WordPress is free" line breaks down past 10 plugins. For new builds, a $99 paid CMS license + $20/month VPS is often cheaper over 3 years.

5. Modern frontend stacks make alternatives viable. Until ~2020, replacing WordPress meant building admin UI, theme system, and plugin architecture from scratch. Next.js + Sanity, Astro + Strapi, Laravel + Inertia + shadcn — these stacks ship admin and frontend tooling that's genuinely good. The replacement-cost dropped, so replacement happens. For the modern-stack architecture specifically, see the modern CMS stack: Laravel + React + Inertia.

Each pressure on its own is survivable. The combination is what the market-share data captures: WordPress isn't bad enough to drive mass migration, but it's bad enough on enough dimensions that new buyers increasingly pick alternatives.

Is WordPress a Sinking Ship or a Shifting Market?

The honest read: shifting market, not sinking ship. WordPress's installed base is huge, sticky, and won't disappear — most of those 60% of CMS-using sites will still be on WordPress in 2030. The market is shifting because new builds break differently than the installed base, and the developer mindshare is leaving faster than market share, but neither pattern looks like collapse.

What this means by audience:

For agencies maintaining WordPress sites: the existing-client work is stable for years. Renewals, updates, security patches, plugin compatibility — all real billable work, all not going away. New-client recommendations are the question. Many agencies now run a "we maintain your existing WordPress site, but we'd build something different from scratch" pattern. That pattern fits the data.

For new builds at small businesses: WordPress is still a reasonable pick if the business is non-technical, the site is content-shaped, and the budget is tight. The economics that made WordPress dominant haven't disappeared at the small-business end — they've just gotten weaker as Wix, Squarespace, and Ghost catch up on ease-of-use.

For new builds at developer-led teams: WordPress is increasingly the wrong pick. Modern alternatives offer better DX, better security, better performance, better TCO. The teams that pick WordPress now are usually doing it for legacy reasons (existing infrastructure, plugin lock-in, hiring pool), not because the platform is the best technical choice.

For developer career planning: WordPress skills remain employable but the growth curve is flat. TypeScript + Next.js + headless CMS skills are growing fast; Laravel + React skills similarly. A 5-year career bet on WordPress alone is riskier than the same bet would have been in 2018.

For VC/strategic decisions: the WordPress economy (hosting, plugins, themes, agencies) is mature. Acquisitions and consolidations are increasingly the news in this space rather than fast-growing companies. Money flows toward modern alternatives because that's where the growth is.

What to Do About It

If you're picking a CMS in 2026 with the market-share trend in mind:

1. Don't dismiss WordPress for new builds purely on the trend. The platform still works for content-shaped sites with non-technical owners. The 5-point share drop over 3 years isn't a death spiral — it's a slow shift away from dominance, not a collapse.
2. Don't ignore the cohort data either. New-site adoption dropping from 51% to 43% in 2 years is a meaningful signal. If you're choosing for a 5-year horizon, that's the more relevant trend than the installed-base number.
3. Match the platform to the project. WordPress for content sites with editorial teams that already know it. Modern CMS for custom-development projects, dev-led teams, and TCO-sensitive multi-year builds. See WordPress vs modern CMS: honest feature comparison for the dimension-by-dimension framework.
4. If you're considering migration, factor the market-share trend into the cost/benefit. WordPress sticky-cohort data shows most sites that migrate stay migrated; the switching cost is real but the destination platforms are stable enough now that you're not picking a flavor-of-the-month risk. The framework-agnostic CMS migration guide for developers covers the migration playbook.
5. For new agency or freelance positioning, hedge by adding modern-stack capability without abandoning WordPress practice. The work mix is shifting; agencies that can quote both grow faster.

If your stack is Laravel + React and you're picking from the modern-CMS side of this trend, UnfoldCMS is one of the alternatives benefiting from the shift — see pricing, book a demo, or browse the comparison hub. We're transparent that we're a young entrant — we don't claim to be the right pick for non-technical small business sites where WordPress still wins. The market-share trend is real but doesn't make every alternative the right answer.

FAQ

Is WordPress dying in 2026?

No, but its dominance is shrinking. Market share among CMS-using websites dropped from 65.2% in 2023 to 60.2% in Q1 2026 — a meaningful but slow decline, not a collapse. WordPress still runs over 40% of the entire web. The trend is steeper among new sites: 43% of newly-built sites in Q1 2026 are WordPress, down from 51% just two years earlier. "Dying" is too strong; "losing dominance gradually" is accurate.

What's overtaking WordPress?

Wix is the biggest single winner (+28.9% relative growth over 3 years), driven by small-business adoption. Squarespace grew +9.7%. Shopify gained share in e-commerce. The headless CMS category (Sanity, Strapi, Contentful, Payload, Storyblok, DatoCMS) collectively more than doubled, though it's still under 4% of the total CMS market. The trend isn't one platform replacing WordPress — it's many platforms each taking a slice.

Should I migrate off WordPress because of the trend?

Don't migrate purely because of market-share trends. Migrate based on whether your specific project's pain points (security, performance, plugin tax, dev experience, TCO) outweigh the migration cost. The market-share trend is a useful signal that your future hiring pool, vendor support, and ecosystem activity will lean increasingly non-WordPress — but for an existing site that works, that's a slow-burning concern, not an urgent one. See the framework-agnostic CMS migration guide for developers for when migration is worth it.

What's the most accurate WordPress market share number for 2026?

It depends what you're measuring. 39.8% for WordPress's share of all websites tracked (W3Techs, Q1 2026). 60.2% for WordPress's share of CMS-using websites. 43% for WordPress's share of newly-built sites in Q1 2026. All three numbers are accurate; they measure different slices. The headline "WordPress runs 43% of the web" usually conflates the all-websites figure with the CMS-using figure; reading the numbers carefully reveals more nuance than either single statistic.

Is the WordPress decline due to security issues alone?

No — security is one of five structural pressures. The others are performance gap with modern stacks (only 36% of WP mobile sites pass Core Web Vitals), developer experience misalignment with modern tooling (TypeScript, React, modern frontend stacks), plugin tax and total cost of ownership at scale, and the maturation of replacement options (Next.js + headless CMS, Laravel + Inertia, etc.). Each pressure on its own is survivable; the combination is what shifts market share. See WordPress vs modern CMS: honest feature comparison for the deeper trade-off framework.

Will WordPress recover its growth?

Unlikely without a structural shift. WordPress's strengths (plugin ecosystem, hosting affordability, freelancer pool) remain real but they don't address the structural pressures driving share away. The replacement options keep maturing. The developer-mindshare trend has been negative for 4+ years and shows no sign of reversing. The realistic forecast: WordPress continues to slowly lose share to a combination of Wix/Squarespace at the small-business end and headless/modern CMSes at the developer end, settling at perhaps 50% of CMS-using sites by 2030, then stabilizing as the remaining base is genuinely sticky.

Sources & Methodology

This post draws on:

• W3Techs (w3techs.com) — primary source for CMS market-share trends across the top 10M websites, monthly snapshots from 2023 to Q1 2026
• BuiltWith (builtwith.com) — secondary source for CMS adoption among new sites and across geographic/industry slices
• Q-Success new-site tracking — for the cohort analysis distinguishing installed-base from new-site adoption
• Stack Overflow Developer Survey 2024 and 2025 — for developer-mindshare data (most-loved/dreaded/wanted CMSes)
• GitHub Insights and starhistory.com — for repo activity and star-growth comparisons across CMS platforms
• Patchstack 2024 vulnerability report — for the 7,966 plugin/theme vulnerabilities figure
• Google CrUX dataset — for the 36% Core Web Vitals pass rate on WordPress mobile sites
• LinkedIn job-posting trends and Indeed/Stack Overflow Jobs aggregated data — for the hiring-data signals

Disclosure: this post is on a CMS vendor's blog. UnfoldCMS competes (in a small way) for the WordPress-alternative market share described here — we benefit when WordPress's share shifts. The market-share data is independent of UnfoldCMS and verifiable against the cited sources. The "what to do about it" framing is honest — there are real cases where WordPress is still the right pick (small content sites, non-technical owners, tight budgets), and the post says so. The trend is real; the implications depend on your specific project.

The market-share numbers are point-in-time snapshots and will be different by the time you read this. The methodology — same sources, same cohort definitions — is what to apply if you're checking the trend yourself in a future quarter.

For deeper coverage of any single pressure driving the shift, see why developers are leaving WordPress: 7 pain points, WordPress security problems in 2026, WordPress performance problems: why your site is slow, WordPress plugin bloat: your biggest liability, and hidden costs of WordPress: what you actually pay.