WordPress vs WordPress  ## Metadata - Author: [[Jono Alderson]] - Full Title: WordPress vs WordPress - Category: #articles - Document Note: - #wordpress - #seo - #plugin_directory - #wordpressorg - #wordpresscom - #canonical_urls - #noindex - #google - #ethics - #user_confusion Author: Jono Alderson Source: Article Reference: https://www.jonoalderson.com/wordpress/wordpress-vs-wordpress/ date created: 2025-08-22 00:00 # Title: WordPress vs WordPress — SEO, ethics, and user impact of .com replicating .org’s plugin directory ## Table of Contents: - 🧭 Overview & Context (#overview--context) - 🔍 The Story So Far (#the-story-so-far) - 🤔 User Confusion & Incentives (#user-confusion--incentives) - 📈 The SEO Consideration (#the-seo-consideration) - 🛠️ Proposed Solutions (#proposed-solutions) - 🧠 Ethical & Ecosystem Implications (#ethical--ecosystem-implications) - 🗒️ Notes (#-notes) - 🗣️ Paraphrase (#-paraphrase) - 📰 Newsletter Blurb (#-newsletter) - ✅ Action Items (Career Alignment) (#-action-items) - 🧪 Hypotheses (#-hypotheses) - 📊 Methodology (#-methodology) - ❓ Questions (#-questions) - 🔮 Future Research (#-future-research) - 💡 Implications (#-implications) - 🧠 Learning Styles Assessment (#-learning-styles-assessment) - 📊 Accessibility Assessment (#-accessibility-assessment) - 🌍 DEIB Assessment (#-deib-assessment) - ✅ Logical Validity (#-logical-validity) - 🔍 DARVO Analysis (#-darvo-analysis) - 🔎 SEO Evaluation (#-seo-evaluation) - 🎯 Conclusion (#-conclusion) ### References: - Jono Alderson, “WordPress vs WordPress” (2023-09-16): https://www.jonoalderson.com/wordpress/wordpress-vs-wordpress/ ## 📝 Summary: The article examines the confusion and SEO consequences arising from WordPress.com replicating the WordPress.org plugin directory. While Matt Mullenweg argues that competition increases discovery and aligns with GPL freedoms, the author warns this creates misaligned incentives: Google may rank .com higher for plugin and generic searches, confusing users into paid .com plans to access plugins that are otherwise free on self-hosted .org. The author recommends either canonicalizing .com pages to .org (with caveats) or, more reliably, noindexing .com’s plugin pages to safeguard user clarity and the project’s integrity. ## 📖 Main Content: The piece lays out a clear chain: - Background: Many users already conflate .org and .com. Replicating .org’s plugin directory on .com intensifies overlap in search. - Matt’s perspective: Competition equals more surface area in Google, yielding more downloads and usage; GPL allows marketplaces. - Counterpoint: Because Google sees logged-out pages, .com’s stronger domain might outrank .org, unintentionally steering users toward paid .com tiers for plugin access. This risks confusion, reputational harm, and diversion of ecosystem value. - SEO specifics: .org’s technical and content SEO is “below par,” making it likely to lose to .com’s cleaner implementation, absent active search management. - Solutions: Canonical tags from .com to .org could help but are only hints, increasingly weak for syndicated content. The author favors noindexing .com plugin pages as a simple, low-opportunity-cost fix if those pages are truly for logged-in users. ### 🗒️ Notes - Problem framing: - Long-standing confusion between WordPress.org (software + free plugin repo) and WordPress.com (hosted service with plugin access gated behind Business plan). - Replication of .org’s plugin directory on .com escalates SEO competition. - SEO dynamics: - Google crawls logged-out .com pages on a stronger domain; lacking disambiguation signals, .com may “accidentally” win SERPs for plugin and general queries (“wordpress security,” etc.). - .org’s SEO weaknesses: technical setup, content quality/strategy, performance, accessibility, resourcing. - Incentive misalignment: - .com profits when it wins plugin searches; risk users feel “tricked” into paying for plugins they could otherwise use free on self-hosted .org. - Potential long-term damage to WordPress perception and adoption; users may churn to non-WordPress solutions after negative experiences. - Matt’s position: - Competition boosts discovery and distribution; GPL permits third-party marketplaces. - Author concedes GPL point but stresses unique ecosystem and ethical stakes due to brand overlap and user confusion. - Mitigations: - Canonicalizing .com plugin pages to .org equivalents: weak/unenforceable hint, less viable given Google’s stance on syndicated content. - Noindex .com plugin pages: trivial to implement, minimal cost if audience is logged-in users, reduces confusion and preserves .org’s role. - Strategic takeaway: - How Google interprets the two brands can shift power and money in the ecosystem. Without active management, users and the project may be harmed. ## 📖 References: - Primary: Jono Alderson, “WordPress vs WordPress,” 2023-09-16. https://www.jonoalderson.com/wordpress/wordpress-vs-wordpress/ - Related background (external context): - GPL overview: The GNU General Public License on the FSF site - Google canonical guidance: Google Search Central on rel=canonical - Google guidance on duplicate/syndicated content: Google Search Central documentation ## 🗣️ Paraphrase: 1) Original idea: “Matt’s stance is that most users hitting wordpress.com plugin pages are logged in, and understand what they’re looking at.” - Paraphrase: Matt argues that the typical visitor to .com’s plugin pages is already authenticated and context-aware, so their experience isn’t confusing. 2) Original idea: “There’s no guarantee that canonical URLs would reliably solve the problem.” - Paraphrase: Relying on canonical tags is unreliable; search engines may ignore them, especially when other signals point elsewhere. ## 📰 Newsletter: WordPress Watch: Discovery vs. Clarity in the Plugin Ecosystem Learning web dev this week? Here’s a teachable moment in SEO ethics. WordPress.com mirrored WordPress.org’s plugin directory. On paper, more surface area in Google means more discovery. In practice, Google sees logged-out .com pages on a stronger domain, which could outrank .org for plugin and generic searches (“wordpress security,” etc.). That risks nudging users into paid .com plans for plugins that are otherwise free on self-hosted .org—fueling confusion and ecosystem friction. Community highlights: - Healthy debate on competition vs. clarity and GPL freedoms vs. brand stewardship. - Calls to protect users with either canonical tags (weak hint) or the simpler fix: noindex the .com plugin pages if they’re truly for logged-in users. New plugins and dev tip: - Before shipping your next plugin landing page, audit how your content appears logged out. Search engines judge what they crawl, not your authenticated UX. Further reading: Jono Alderson’s analysis in “WordPress vs WordPress” (https://www.jonoalderson.com/wordpress/wordpress-vs-wordpress/). For canonical best practices, see Google’s guidance on rel=canonical. ## ✅ Action Items: Prompt for aligning articles with your Developer Advocate/OSPO trajectory: “Analyze how this article advances open-source advocacy, contributor onboarding, and educational clarity in the WordPress ecosystem. Identify: - Governance and ethical considerations (e.g., brand overlap, user trust, GPL freedoms). - Contributor impact (plugin authors’ discovery, support load, and revenue paths). - Education opportunities (explain .org vs .com; teach search literacy, canonical vs. noindex; create onboarding materials). - Community sustainability (minimizing user confusion; equitable distribution of SEO value; funding models). - OSPO lenses (policy proposals, documentation standards, technical SEO guardrails, and transparency practices). - Concrete interventions I could champion at GoDaddy: developer docs, contributor workshops, SEO guidelines, plugin repo health metrics, and cross-org coordination. - Measurable outcomes tied to inclusivity and transparency (reduced support tickets, improved SERP alignment, clearer product-market fit messaging).” How this article aligns with your goals: - Open-source advocacy: Balances GPL freedoms with responsible stewardship of shared brands. - Contributor engagement: Protects plugin authors’ discoverability and reduces misdirected support. - Education: Clear explana - Summary: There has been a recent controversy in the WordPress community regarding the relationship between wordpress.org and wordpress.com in Google's search results. The issue stems from wordpress.com replicating the plugin directory from wordpress.org, potentially leading to SEO implications and competition between the two sites. There are concerns about user confusion and misaligned incentives, as wordpress.com requires payment for plugin usage while wordpress.org allows free downloads and installations. The author suggests implementing a quick fix by noindexing the dot com pages to prevent them from being indexed by search engines, which would prioritize the integrity and health of the project over potential revenue. - URL: https://www.jonoalderson.com/wordpress/wordpress-vs-wordpress/  There’s been a lot of drama in the WordPress community this week, as people are questioning the relationship of *wordpress.org* and *wordpress.com* in Google’s search results. Its a long-standing issue that people don’t really understand the difference between the two sites and their propositions, but one that we’ve broadly learned to tolerate as immutable. But now the spotlight is being shone on some potentially harmful implications of that relationship. #### The story so far WordPress.com (which sells hosted solutions for WordPress) recently replicated the plugin directory from wordpress.org (which facilitates self-hosted WordPress). That has some interesting SEO implications, as dot com may outrank dot org when people search for plugins. That may also happen for more general searches for the kinds of phrases that might return plugins; eg, “wordpress security” or similar. It may also affect the indexing and ranking of both sites in unpredictable ways, as they ‘compete’ with each other. When people have raised questions to Matt Mullenweg (the co-founder of WordPress, and CEO of Automatic – the company which runs wordpress.com) about this, his response has been that it’s not a problem – that more real estate drives more discovery, more downloads, more distribution, and more usage; all of which are good things. He also argues that because WordPress plugins are released under GPL licensing, it’s perfectly fine for anyone to create their own marketplace of them (and that this is generally a good thing). That might be *generally* true, except that the existence of *this particular* marketplace comes with significant commercial implications, and may also represent an existential risk to WordPress. #### Confusing users? WordPress.org lets you freely download and install plugins (on your self-hosted site), whereas wordpress.com only lets you use plugins (on your dot com hosted site) if you pay for their ‘business’ hosting tier. There’s potential user confusion and misaligned incentives here; wordpress.com makes money from winning in these kinds of searches, in a way that might negatively affect the perception, positioning, adoption, and preference of WordPress as a solution. Most people don’t understand the difference between wordpress.org and wordpress.com, and it’s easy to imagine how folks might end up feeling like they’ve ‘been tricked’ into spending money on a solution when they might not otherwise have had to (or perhaps worse, that this happens without their awareness, and they perceive it as the norm). It’s also easy to imagine that folks might seek non-wordpress solutions if/when they discover that they ‘have to’ (or rather, didn’t have to) pay for plugins, or feel like they’ve been conned. #### The SEO consideration A lot of the arguments around whether this is good or bad hinge on the user experience for logged-in, solution-aware searchers on wordpress.com. Matt’s stance is that most users hitting wordpress.com plugin pages are logged in, and understand what they’re looking at. But that’s not the case for Google. Google sees a logged-out version of a plugin page, on a strong(er) domain, with no signals or strategy to help them to understand the desired outcome (ie, which site should ‘win’). Google judges sites based on what it sees, and uses that to determine if and when it presents it to it’s audience of searchers. The experience of logged in users doesn’t matter (and isn’t accessible) to search engines. The dot com repository is a (more or less) direct, competing plugin directory. That means that without that active management, we create a scenario where dot com ‘accidentally’ ends up winning more often than not. If that’s a deliberate strategy, it’s smart (though questionable ethically). If it’s an accidental oversight, it’s problematic. WordPress.org’s SEO leaves a lot to be desired; despite it’s size and ‘clout’, it’s technical setup, content, strategy, performance, accessibility, resourcing and other factors are woefully below par. There’ll be no shortage of cases where it loses to it’s cleaner, sleeker sibling. #### So, what should we do? WordPress.com plugin pages could use canonical urls to referencing their wordpress.org equivalents. This would send a clear signal that the duplication is intentional, and that the wordpress.org pages should win out. But if we consider Google’s recent updates to how they prefer “syndicated” content to be handled, then this isn’t a viable solution. Not to mention that canonical URLs are a ‘hint’ rather than a directive, and might be ignored when other signals (such as the poor state of wordpress.org pages) hint that the user might benefit from a different interpretation. There’s no guarantee that canonical URLs would reliably solve the problem. Instead, the best option might be for dot com pages to be noindex’d. If the target audience for these pages is indeed mostly logged-in users, then the small opportunity cost of preventing them from being indexed by search engines should be inconsequential. That’s a quick, trivially simple fix to implement, and should be uncontentious – unless the potential revenue from misrepresenting what WordPress is/isn’t to unknowing searches is more important than the integrity and health of the project. Ultimately, we need to understand that how Google perceives and interacts with these two distinct websites and brands has the potential to radically alter the balance of power and money in the ecosystem. If we’re trying not actively managing that, we’ll end up harming ourselves, and our users., WordPress vs WordPress, Jono Alderson, 01haesrktv95phnm6ahrf0k4wc.