WordPress Multisite Has a Marketing Problem  🔗 **Source:** [WordPress Multisite Has a Marketing Problem](https://talkinghuman.com/blog/wordpress-multisite-marketing-problem?rw=full) > [!note]+ Document Notes > --- > tags: [wordpress-multisite, field-marketing, wordpress-hosting, wordpress-agencies, developer-education] > author: Adam W. Warner > source: talkinghuman.com > reference: https://talkinghuman.com/blog/wordpress-multisite-marketing-problem > date created: 2026-10-13 19:00 > --- > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > # 🏷️ Title: WordPress Multisite Has a Marketing Problem > ## 🧭 Table of contents > - [📝 Summary](#-summary) > - [📖 Main content](#-main-content) > - [🗒️ Notes](#️-notes) > - [📚 References](#-references) > - [🗣️ Paraphrase](#️-paraphrase) > - [📰 Newsletter](#-newsletter) > - [✅ Action items](#-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) > - [🎯 Conclusion](#-conclusion) > - [🔄 Refactor appendix](#-refactor-appendix--wordpress-multisite-has-a-marketing-problem) > ## 📝 Summary > This is a practitioner opinion essay on the talkinghuman.com blog by Adam W. Warner, dated 2026-10-11 in the page's own data (about 2,590 words in 284 captured paragraphs, many of them one-line list items). It argues that WordPress Multisite is under-known because nobody has a commercial incentive to market it, and it proposes field marketing aimed at universities, franchises, agencies and solo entrepreneurs. It is advocacy, not research: it has no figures on Multisite adoption, no named network and no named user of the feature. > Interests, stated plainly. The author describes a "field marketing brain" (¶92) and says what they would do "if I were responsible for growing awareness and adoption of WordPress Multisite" (¶210). Two facts from outside the article text bear on that. First, the page shell (not part of the article) carries a banner saying the author is "actively exploring director-level roles in field marketing, partner marketing, community marketing, and ABM at B2B SaaS companies", with the tagline "Trust-first. Human-led. Growth-focused." The essay doubles as a portfolio piece for that search. Second, per the author's X thread (analyzed separately, so this fact comes from that other source), the author wrote a Multisite ebook in 2011 and built a first SaaS business on WordPress MU. Neither fact makes the argument wrong. Both are reasons to ask for evidence the essay doesn't give. > Context from the page's embedded data, noted as an oddity and not a conclusion: the post record carries `published: false` next to a `publishedAt` of 2026-10-11. The reader doc's saved URL carries `?rw=full` because the first scrape captured only the site banner and cookie notice, and the body was recovered from the embedded data. The LinkedIn post by "Robert" that sparked the essay (¶3-¶8) was embedded on the page and did not survive the cleaning, so his observation is known only through the author's paraphrase. > - **What happened.** Robert (the essay's own word is "friend", ¶3) saw someone use a management platform such as ManageWP to run several sites for one brand across languages and locations, instead of Multisite (¶4-¶6). His question, quoted at ¶8, asks what education is missing. The author answers that the gap is marketing. > - **The claim.** Multisite has been in core "for more than 16 years" (¶42), most developers may not know it exists (¶43), and no company profits "every time someone activates it" (¶79), so nobody markets it by audience and outcome. The fix is outcome-led, audience-specific campaigns and stories from existing users (¶210-¶243). > - **Why it matters.** The essay names a real documentation and go-to-market gap: the four developer-docs links in the references (¶281-¶284) are feature and setup documentation, and the essay says "there are already plenty of those" (¶211). It asks hosts, agencies and the community to supply business-owner-level content (¶254). > - **Key stakeholders.** Hosting providers, agencies and freelancers, universities, franchise operators, hotel groups, solo entrepreneurs, commercial site-management platforms (ManageWP is the one named), and the WordPress community. > - **Risks and tradeoffs.** The essay lists real Multisite limits at ¶193-¶199 (shared core, network-wide failure, uneven plugin support, harder site extraction, no guaranteed cost savings). Those same limits are a competing explanation for low uptake that the essay never tests against its marketing explanation. The author also concedes at ¶184 that Multisite is "not a magical shortcut". > - **Bottom line.** A readable, honest-in-tone argument for outcome-led marketing, with no data behind the premise that awareness is the bottleneck. Treat it as a hypothesis to test, not a finding. > ## 📖 Main content > **Opening and trigger (¶1-¶11).** The author says Multisite has been "hiding in plain sight" for more than 15 years (¶2). Robert's LinkedIn observation (¶3-¶8) is about one person using a management platform for same-brand, multi-language, multi-location sites. The author's thesis arrives at ¶10 in six words: Multisite has a marketing problem. > **What Multisite is (¶12-¶33).** One WordPress install, a few configuration changes, then a network of sites that each have their own content, users, settings and dashboard but share one codebase and a central place to manage themes and plugins (¶15-¶17). The author calls the network-wide role Super Admin and notes that shared infrastructure means a problem can reach every site (¶22-¶26). The feature is in core, not a paid plugin or SaaS (¶28-¶32). > **History (¶34-¶45).** The author found WordPress in late 2004 and learned of WordPress MU in 2005 (¶35-¶36). MU began as a separate codebase for many blogs from one install and became part of the infrastructure behind WordPress.com (¶37-¶38). Its functionality was merged into core on June 17, 2010, in WordPress 3.0 "Thelonious" (¶39), which gives "more than 16 years" of native capability (¶42). > **How management platforms won mindshare (¶46-¶65).** Agencies and freelancers ended up with dozens or hundreds of separate installs, each needing updates, backups and monitoring (¶48-¶51). Platforms like ManageWP connected those installs to one dashboard and added backups, security scans, uptime checks and client reports (¶52-¶54). The author says central management of separate installs became the familiar workflow while Multisite stayed less visible (¶57), then clarifies the two solve different problems and an agency could use both (¶58-¶62). The test case is 20 sites for one brand with shared functionality (¶63). > **Who markets Multisite (¶66-¶90).** Commercial platforms market because their model requires it (¶68-¶76). No single company owns Multisite and profits from each activation (¶79). Hosts, developers, agencies and enterprise WordPress companies support it and some promote it (¶80-¶81), but the author asks how many market it by audience: franchises, universities, would-be hosting entrepreneurs, people outside WordPress (¶83-¶87). The author's "suspicion" is a "considerable opportunity" (¶88). > **Outcomes over features (¶91-¶110).** Customers care about costs, time, simplicity, speed, repetitive work and revenue (¶96-¶103). Four reframings pair each audience with a picture: 100 departmental sites for a university web team, 30 franchise locations sharing a structure, consistent branding across a hotel group's properties, and a niche web services business for a freelancer (¶104-¶107). "SHOW, don't tell" (¶108). > **Agencies (¶111-¶131).** Multisite isn't right for unrelated clients with separate hosting, security and ownership needs (¶113-¶114). It could suit a franchise with 40 locations: one network, shared themes and plugins, central technical administration, individual sites (¶115-¶125). Repeating that across franchise bra 📄 **Full text:** [[Full Document Contents/Articles/WordPress Multisite Has a Marketing Problem.md|WordPress Multisite Has a Marketing Problem by Adam W. Warner]] ## Highlights - WordPress Multisite has a marketing problem. ([View Highlight](https://read.readwise.io/read/01m4vr4eqa2wx5khmq200agwjg)) - Note: [H1] The author names Multisite's marketing as the problem - Tags: atom/literature/h1 - There's no single company that owns the feature and directly profits every time someone activates it. ([View Highlight](https://read.readwise.io/read/01m4vr4h4egk1ca63qsype2rsg)) - Note: [H2] An unowned core feature lacks a commercial marketer - Tags: atom/literature/h2 - One of the biggest mistakes technology companies make is assuming customers care about features as much as the people who build them. ([View Highlight](https://read.readwise.io/read/01m4vr4panz84ese49hnxx58vx)) - Note: [H4] Customers want outcomes more than features - Tags: atom/literature/h3 - And depending on your hosting environment, performance requirements, and architecture, Multisite won't necessarily reduce your hosting costs. ([View Highlight](https://read.readwise.io/read/01m4vr4rm10re4qdd77zptfyz7)) - Note: [H5] Multisite does not guarantee lower hosting costs - Tags: atom/literature/h3 - Sometimes the most interesting opportunity is helping people discover what the software they already have can do. ([View Highlight](https://read.readwise.io/read/01m4vr4kj9wpq7sqjy9wgmc555)) - Note: [H3] Existing capability is itself a marketing opportunity - Tags: atom/literature/h3