
As of November 2026, WordPress still runs more websites than any other content management system, but its share of the known CMS market has fallen to 57.9%, the lowest reading since 2013 and 7.3 percentage points below the 65.2% peak it recorded in 2022, according to W3Techs data reported by Search Engine Journal on 17 November 2026. The number a marketing lead should act on is not the ranking, though. It is whether your site can still be measured and moved when the platform underneath it changes. That question belongs in ai automation for business planning rather than in a dashboard subscription.
Key takeaways
The data comes from W3Techs, which surveys websites and reports two different measures. Usage is a platform's share of all websites surveyed; market share is its share of the sites where a CMS was detected at all. Search Engine Journal's report of 17 November 2026 uses both, and mixing them up is the easiest way to misread the charts.
| CMS (13 November 2026) | Market share | Type |
|---|---|---|
| WordPress | 57.9% | Open source |
| Shopify | 7.9% | SaaS |
| Wix | 6.2% | SaaS |
| Squarespace | 3.6% | SaaS |
| Joomla | 1.6% | Open source |
On the usage measure, 67.7% of websites run a CMS. Set against Netcraft's September survey count of 323 million domains, that puts the market at roughly 218.8 million sites. W3Techs published a slightly lower WordPress reading of 57.5% on 16 November 2026. Read that as a daily tick in a survey that rounds its percentages, not as a disagreement with the 57.9% headline.
Both things are happening, and the second is easier to miss. Inside the known-CMS group, WordPress has given up 7.3 percentage points since 2022 while Shopify, Wix and Squarespace grew. Joomla and Drupal went the other way, which is why the headline "WordPress is declining" tells you less than it seems: some of the movement is between the older open-source systems and the newer hosted ones, not a straight exit from WordPress.
W3Techs found 32.3% of websites running none of the systems it monitors. The label means "not detected", not "built by hand". A bespoke stack, a headless setup and a detection gap all land in that bucket, and Search Engine Journal is careful to say the category is no proof that those sites abandoned a CMS. The honest reading is that part of the web is drifting outside the measurement frame at the same time as hosted platforms grow inside it.
WooCommerce is installed on 11.4% of sites with a known CMS, and because it is a plugin rather than a standalone platform, its numbers sit inside the WordPress ecosystem. Studio Wombat's 2026 study of stores that once ran WooCommerce found 14% had moved off the platform, and 4.6% of the tracked moves went to Shopify. That is a direction of travel, not a verdict. A store's catalogue, checkout and payment stack weigh more in the decision than a shift of one or two points.

This is the question the headline leaves open, and the answer is less dramatic than the coverage suggests: a falling share changes your negotiating position, not the test you should apply. Three questions decide more than the ranking does.
| Test | Stay on WordPress if… | Move to a hosted platform if… |
|---|---|---|
| Technical control | you need custom post types, bespoke schema or plugin-level changes | you want hosting, updates and security handled for you |
| Portability | content and events export cleanly into your own analytics | you are content with the platform's own reporting and export limits |
| Maintenance capacity | someone owns updates, backups and security patches | nobody can own them, and the site is a brochure or a simple store |
A content-heavy publisher or a multi-market brand site usually keeps more room on an open-source base, because that is where template and plugin depth is deepest. A small professional-services firm or a single-market online store often gets more from a managed platform, since the hours saved on maintenance are worth more than the flexibility it gives up. A company with an in-house developer and a strict data-residency rule is the case where neither default fits, and the stack should be drawn around the constraint instead.
There is also a plain commercial argument for staying put longer than the headlines suggest. A platform change moves the cost from a monthly line item to a project budget: rebuild, retest, recrawl, retrain. Share numbers do not appear in that budget, and they do not pay for the quarter the team spends on it.
Portability is decided long before anyone fills in a migration form. It is decided by where your events are defined and who holds the raw data. That is the part of marketing report automation a platform change tests hardest.
Write down every page, template, redirect, structured-data block, form, tracking tag and hard-coded campaign parameter. Anything that exists only in the theme will be rebuilt by hand on the other side, and anything you cannot list is a cost you have not budgeted. The audit takes an afternoon and saves a quarter.
Events should reach your own data layer first and the platform second. When event definitions, identifiers and report logic sit in marketing report automation you control, the CMS becomes a publishing surface rather than the system of record. The same principle runs through our work on AI automation for hotel and retail marketing.

For capability, yes; for strategy, not much. Search Engine Journal's own reading of the shift is that fluency in a second ecosystem is now useful rather than exotic, because clients arrive with different development and maintenance arrangements. Shopify's gain of 1.1 percentage points over twelve months is small in absolute terms and large in a client mix: a handful of store clients can move a small agency's whole workload.
Two groups can skip most of it. A business whose site is a single landing page behind a paid campaign has no platform decision to make; the media plan, the offer and the page itself decide the result. A business already inside a proprietary enterprise platform should fix its data-export rights before it considers re-platforming, because the migration is the cheaper half of that problem.
You can buy evidence cheaply. Build a pilot with a handful of real pages on the candidate platform: a product category, a landing page and one article. Put the same content and tracking on it as the live site. Then compare what a visitor sees, what your event layer receives and how long the build took your team, not how the demo looked in a sales call.
The pilot answers the questions a market-share chart cannot. Does the candidate let you control headings, canonical tags and structured data? Can it send the events your reports need, under your own identifiers? And who fixes the template when a layout breaks in a browser update? If the answers are no, unclear or "the platform team will handle it", the share number was never the deciding factor, and the ai automation for business scope should start with those three questions rather than with a tool shortlist.
Topkee answers the platform question in a different order from most vendor pages: keep the measurement layer independent, and the CMS stays a choice rather than a commitment. Its TTO customer data platform already connects WordPress, Wix and Weber websites, plus Shopify and Weber stores, so a change of CMS does not cut the reporting line. For brands that want the platform itself replaced, Weber is Topkee's in-house no-code website builder: a single back office, one-click publishing, an automatically generated robots.txt, a dynamic XML sitemap kept up to date by the system, free SSL on every site, and layouts built for three device screens. Portability is part of the delivery model: landing pages, event tracking and lead data sit on the client's own Weber, TTO CDP and Leadbox accounts, and the raw event data, schema and pixel ownership can leave with the client.

For most content-led sites, yes. WordPress remains the largest ecosystem in the survey at 57.9% of the known CMS market, so plugins, themes and people who know the platform are still easiest to find there. It is the weaker choice for a team with no one to own updates, backups and security patches.
Shopify, at 7.9% of the known CMS market, ahead of Wix at 6.2% and Squarespace at 3.6%. Note the denominator: that is Shopify's share of sites where a CMS was detected, not its share of all online stores.
Only indirectly. Share tells you where plugin and theme support will concentrate; rankings depend on crawlability, structure, content and speed. A smaller share does not make WordPress worse at SEO, but it does mean more of the ecosystem's new work will happen elsewhere.
Map every URL and redirect, keep the title and structured-data patterns, and avoid changing URL structure and content on the same day. Watch Search Console for coverage and performance changes for a few weeks after the switch, because the first signals arrive late.
If your events are defined outside the theme and land in your own data layer, yes, because you reconnect the source. If everything sits in the platform's dashboard, expect to rebuild it, which is the single strongest argument for defining events properly before the move and the first item any marketing report automation brief should settle.