WordPress Has a Branding Problem, Not a Code Problem
Ask a casual user to explain the difference between WordPress.org and WordPress.com, and you will likely get a blank stare. It is a question I pose to students in my WordPress development course every semester, and it never fails to highlight a fundamental confusion. A platform that powers 43% of the internet can go largely unrecognized for what it actually is—and that is precisely the issue.
For developers and power users, the discrepancy between the open-source community project (WordPress.org) and the commercial hosted platform from Automattic (WordPress.com) is obvious. Yet, the line between these two entities remains both sacred and blurry. It is sacred because crossing it threatens the decentralized, community-maintained ethos of the open-source project. It is blurry because the shared branding makes it nearly impossible to tell where the community ends and the corporation begins.
A Recent Flashpoint: The Plugin Directory Clone
A perfect illustration of this tension surfaced recently when WordPress.com published a clone of the WordPress.org Plugin Directory on its own site. Within days, plugin pages hosted on WordPress.com began outranking their WordPress.org counterparts in Google search results, sparking familiar accusations. Developers argued that Automattic was leveraging the unpaid labor of the open-source community to advance its own commercial interests. Automattic's response was equally predictable: they were simply distributing developers' work to a larger audience, to mutual benefit.
Both arguments have merit, and neither is entirely wrong. It would be disingenuous for plugin authors to claim zero benefit from the added exposure, just as it is misleading for Automattic to suggest developers gain as much from that exposure as they invest in writing and maintaining code. But when the debate devolves into grievances over labor and hurt feelings, it misses the central point. WordPress does not have a plugin problem. It has a positioning problem.
The Case for Splitting the Brand
Imagine if the ongoing conflict were framed as a battle between WordPress and Automattic, rather than WordPress versus WordPress. The conversation would shift dramatically. Instead of arguing about search rankings and blocked accounts, we would have a clear discussion about distribution and labor within an open-source ecosystem. Sharper lines between business and community interests would allow for more productive conversations, unclouded by blended identities.
The timing is ideal for such a repositioning. It has been five years since Matt Mullenweg advised developers to "Learn JavaScript deeply," and the platform has undergone radical transformation. The Gutenberg project and full-site editing have created an entirely visual editing experience, changing the relationship both users and developers have with the software. The product has evolved so significantly that its current perception lags behind its reality.
Companies often outgrow their own names. Facebook became Meta, Google became Alphabet, and Twitter is now something else entirely. Products evolve like people, and WordPress is no exception. WordPress.org and WordPress.com are now vying for their own identities, often battling each other instead of buttressing one another. The cloned plugin directory on WordPress.com only worsens this conflict. We have reached the point of diminishing returns with the shared "WordPress" brand equity.
Questioning Co-Branding as a Strategy
Mullenweg has argued that the shared branding has historically made it difficult for competitors like Typepad to gain traction in the CMS space. That may have been true in the past, but with a 43.1% market share, is there truly an existential threat to WordPress that necessitates co-branding two different flavors of the same platform? The real threat to WordPress's dominance today comes not from legacy competitors, but from the rise of low-code and no-code platforms. Co-branding cannot solve what is fundamentally a user interface and experience challenge.
The argument that WordPress would have failed like Joomla without co-branding relies on a false premise. Past success does not guarantee future efficacy of the same strategy. Marketing myopia—the assumption that what worked before will always work—often sows the seeds of failure. It is time to question whether co-branding remains the optimal path.
One viable alternative is a clearer separation of concerns. Today, there is remarkably little practical difference between running a site on WordPress.com's Business Plan and self-hosting the same software with a managed host like WP Engine. Users get identical access to identical files running identical code. Without the shared branding, the commercial platform could pursue its own identity, allowing the open-source project to retain its community-driven character.
The solution may also lie in going further with differentiation rather than less. Explicit descriptors such as "WordPress Platform" versus "WordPress CMS" are not elegant, but they illustrate the need for clarity. The current setup, where both properties share a top-level domain name, only muddies perceived similarities and differences further.
Where Do We Go From Here?
The WordPress community has hidden behind past successes for too long, allowing tension between commercial and community interests to simmer beneath a shared brand name. The alternatives are clear: either rename WordPress.com so that WordPress.org can fully own the WordPress identity, or deepen the co-branding strategy to properly differentiate the two entities while still leveraging the name's equity. As it stands, the "WordPress" label serves neither party well. Clarity is the only path forward to a healthier ecosystem.
