18 min read

One Platform for Every Brand Site: Consolidating a Corporate Blog Network

Varun Dubey
Founder, Wbcom Designs · Published Nov 13, 2026 · Updated Nov 13, 2026
Hub diagram: WordPress, HubSpot CMS, Webflow, Substack, Medium and a custom CMS joining one network, for a corporate blog network

The best way to consolidate a corporate blog network depends on one question: do your brand sites need to share things, or only look related? If they share users, editors, a design system and one admin team, WordPress Multisite fits. If each brand needs its own team, release schedule and plugins, separate WordPress installs with shared standards fit better, and a headless front end can put one design on top of either. If your sites are mostly articles and pages and you want the lightest possible stack, EmDash is a fourth option we run ourselves. What does not work is leaving seven brands on seven platforms and hoping a style guide will hold them together.

This article is written for the marketing director, head of digital or CTO of a company group whose blogs live in too many places. Maybe one brand is on a WordPress install an agency built in 2019, another is on HubSpot CMS, a third is on Webflow, an executive writes on Medium or Substack, and one regional site runs on a custom system nobody wants to touch. You asked for one place to manage them all. Below we compare the real options, say what each one costs you in control, and cover the parts that decide success: governance, a shared design system, single sign-on, editorial roles and analytics.

What problems does a mixed corporate blog network cause?

Most groups do not decide to run six platforms. It happens one brand, one acquisition and one campaign at a time. After a few years the pain shows up in the same places.

  • No shared view of content. Nobody can answer “what did the group publish this month?” without opening seven logins.
  • Seven sets of accounts. People leave the company and keep access on three platforms nobody remembered.
  • Brand drift. Each site has a slightly different logo size, header, legal footer and cookie banner.
  • Security and upkeep spread thin. Each platform has its own updates, its own vendor and its own bill.
  • Analytics that do not add up. Each site counts visits differently, so group totals are guesses.
  • Slow changes. A group-wide change, such as a new legal line, is seven separate projects.
  • Search signals split. Strong authors and topics are scattered across domains with no clear structure.

Before choosing a platform, write down which of these hurts most. The answer shapes the choice more than any feature list.

Step one: take inventory before you pick a platform

Make one sheet with a row per site. Our enterprise page describes the same habit: model roles and approvals before building anything. For each site, record:

  • The domain, the platform and the version.
  • Who owns it, who edits it, and who has admin access.
  • How many posts, pages and authors it has.
  • Which integrations it uses: forms, CRM, newsletter, consent tool, analytics, search, ads.
  • Whether it handles logins or payments.
  • How much traffic it gets, and from where.
  • What it costs to run each year, if you can find out.
  • Whether it has a reason to stay separate: a different legal entity, a different country, a regulated product, a separate brand people must not link to the group.

That last item matters. Consolidation is not always the right call for every site. A joint venture with a partner, or a brand that must stay at arm’s length for legal reasons, can keep its own home while following the group’s standards.

Which platforms are in the mix, and what can you take out of them?

Moving content out is the first technical question, and each platform answers it differently. We read the vendors’ own help pages where they allowed it, and say below where they did not.

WordPress installs. These are the easiest sources. WordPress exports posts, pages and media in its own format, and the WordPress documentation lists the importers and the WP-CLI wp import command. Two installs can also be merged into a network, which our Multisite page lists as a service: import sites with users, content and media, or export one out to its own install with redirects.

HubSpot CMS. HubSpot’s knowledge base says a Super Admin or a user with Publish permission can export pages and blog posts as HTML from the blog index, with the download link sent by email. It also says blog post data can be exported as CSV, XLS or XLSX (HubSpot: export web content and data). We read that page through a search summary, and its menu labels may have changed, so check it live. The practical result is that HTML and a spreadsheet of metadata can both come out, and your importer joins them. Forms, workflows and HubSpot-specific modules do not come with an export, and each needs a decision.

Webflow. Webflow’s help center says code export does not include CMS content, and that CMS collections can be exported separately as CSV (Webflow: export your Webflow site code). The same help material says rich text exports as HTML, multi-reference fields export as comma-separated text, and images and files export as Webflow-hosted URLs. That last detail matters. If the old Webflow site is deleted before the images are copied, those image links break, including images inside rich text. So copy the media first and delete the old site last.

Medium and Substack. We could not read either company’s export documentation for this article, because their help pages did not load for us. We will not guess what the export contains. Ask the person who runs the account to run the platform’s own export and send us the file, and we will tell you exactly what it holds before any plan is made. Two things are worth asking for regardless: the subscriber list for a newsletter, and the full image set.

Custom or in-house systems. These need a database and file review. We cover that kind of move in a separate piece on replacing an in-house CMS.

A common result of this inventory is that the content is the easy part. The hard part is the surrounding behaviour: forms that feed a CRM, scripts that set cookies, and redirects.

What are your four real options?

Here are the options side by side, and then each in turn.

OptionWhat it isBest whenMain cost
WordPress MultisiteOne WordPress install running many sites, one network adminBrands share editors, users, plugins and a design systemOne failure or bad update can touch every site
Separate installs, shared standardsOne WordPress install per brand, same theme, same plugins, same rulesBrands need their own teams, releases and pluginsMore upkeep, so you need automation
Headless front endsWordPress holds content, an Astro front end shows itYou want one fast design layer on top of one or many content sourcesTwo systems to run, and editors lose some live previews
EmDashCloudflare’s open source CMS on AstroArticle and page sites with little plugin needYounger ecosystem, fewer plugins

Option one: WordPress Multisite

WordPress’s own documentation describes the model plainly: each site’s content lives in its own database tables, and “only the user table is shared between the instances.” Sites can share the theme and plugins while publishing different content. The network can be path-based, such as example.com/brand, or domain-based, using subdomains or mapped domains (WordPress: Multisite).

The same documentation set has a “Before You Create A Network” page with limits worth knowing. It says the sites in a network are separate, not interconnected like items in other kinds of networks, so if sites must share data beyond users, a network may not be the best fit. It says you cannot choose the subdirectory type if your existing WordPress install has been set up for more than a month, because of permalink issues. Subdomain networks need wildcard subdomains for on-demand site creation, and domain-based networks need DNS and server configuration (WordPress: before you create a network).

Our Multisite service page describes the shape we build for networks of 10 to 100 or more sites: subdomain, subdirectory or mapped domains chosen during discovery, wildcard DNS and automated certificates, network-aware plugins, Redis or Memcached with per-site cache keys, and network-wide backups with per-site restores. It describes updates tested on a canary site before a staged rollout. It also says plainly that central control is simpler than local autonomy, and that giving sites local autonomy with guardrails is a permissions design that takes longer than people expect.

Multisite fits when the brands share an editorial team or a central marketing team, you want one design system, one set of plugins, and one place for updates, and you are happy for the group to decide what each brand may install.

Multisite fits badly when one brand needs a plugin that conflicts with another, when brands have different release calendars, or when one site is so large that its database and traffic should not share a server with the rest.

Option two: separate installs with shared standards

Here each brand keeps its own WordPress install and its own hosting space, and the group enforces sameness through code and process rather than through a network. In practice this means:

  • One starter theme or parent theme, with the group design tokens in it, and a child theme per brand.
  • One must-use plugin that carries the group’s rules: legal footer, consent banner, analytics snippet, security headers, editor roles.
  • A fixed list of approved plugins, with versions, kept in code and installed the same way on every site.
  • One deployment pipeline, so a change to the shared parts rolls out to all sites in a controlled order.
  • One monitoring and backup setup watching all of them.

This costs more in upkeep than Multisite, and it needs discipline. In return, a problem on one brand stays on that brand. A regional site can run a different release schedule, and a joint venture can sit on its own hosting account and still look like family. Our enterprise page lists a guided decision between multisite and separate installs as part of how we start, because the right answer depends on how your teams work.

Option three: headless front ends on Astro

In a headless setup, WordPress holds and edits content, and a separate front end shows it. Our earlier pieces on headless WordPress with Astro and on headless CMS platforms cover the basics, and we do not repeat them here.

What matters for a blog network is this: one Astro design layer can show content from several sources. Brand A’s content can come from a WordPress install, brand B’s from a Multisite network, and a legacy archive from static files. The design system lives once, in code, and every site gets a change on the next release.

We run this pattern ourselves. In our write-up of request-time rendering, a Worker on Cloudflare fills page shells from the WordPress REST API at request time, with Workers KV as the cache, and the publishing tool clears the post’s cache entry and a list-version key, so a new post is live in about a minute with no build step. That write-up covers sites with roughly 586 to 2,500 posts, and says wbcomdesigns.com itself, on the same model, holds about 8,000.

The trade-offs are real. You now run two systems. Some editor conveniences, such as live preview of the exact front-end page, need extra work. Plugins that print front-end output, such as forms and popups, need a headless-friendly replacement. For a group that wants speed, security and one design layer, it is often worth it. For a group with a small team and simple needs, it is more machinery than the job requires.

Option four: EmDash

EmDash is an open source CMS from Cloudflare, built on Astro and released under the MIT license. Version 1.0 shipped on 28 September 2026, and from 1.0 breaking changes only arrive in a new major version. On Cloudflare it runs as a Worker, stores content in D1 and keeps media in R2.

We run five content sites on it in production, described in our EmDash write-up: attowp (230 posts), wppioneer (234 posts), woocustomdev, bpcustomdev and tweakswp. Our report on those sites also lists what went wrong, and a buyer should know it. Before D1 read replication was switched on, uncached home pages took 10 seconds or more on some sites. Migrations at runtime on one version took 44 to 93 seconds on the first request. A preview deployment on Cloudflare uses the production database. The standard D1 export refused databases with full-text search tables.

The same report says where EmDash does not fit today: communities, stores, course platforms and membership sites, mainly because WordPress’s plugin ecosystem is not yet matched. So for a corporate blog network, EmDash suits brand sites that are articles, documentation and marketing pages, and it does not suit a brand site that sells things or runs member logins. Our comparison of Astro CMSes pitched as WordPress’s successor goes deeper on that choice.

How do you decide? Five questions

  1. Do the brands share people? If the same editors and marketers work across brands, lean toward Multisite or a shared design layer.
  2. Do they share plugins and features? If one brand needs a feature the others must never get, lean toward separate installs.
  3. How different are the release calendars? If one brand freezes for a product launch while another publishes daily, separate installs hurt less.
  4. How much logged-in activity is there? Stores and communities push you toward WordPress, not toward EmDash.
  5. Who runs it after launch? A small central team can run Multisite. Brand teams with their own developers can run separate installs. Whoever runs it needs the skills for the option you choose.

Our piece on whether WordPress is still the right base works through the same kind of question for a single site, and you may want it open as a companion.

Governance: who is allowed to do what?

A consolidated network without governance becomes the same mess in a new place. Write the rules before the build.

Roles. Define a short list of editorial roles that mean the same thing on every site: contributor, editor, brand lead, legal reviewer, network admin. Our enterprise page says roles and approvals are modelled before building, and it lists multi-stage approval, legal holds, embargoes and coordinated regional releases as workflow needs. Map each role to what it can do, then give people the smallest role they need.

Ownership. Every site has a named owner on the business side and a named technical owner. The sheet from your inventory becomes the register.

Change rules. Decide what a brand team may change alone, what needs group approval and what is never allowed. Typical examples: a brand may add a page on its own, but may not install a plugin or edit the shared footer.

Offboarding. When a person leaves, one action removes their access everywhere. That brings us to sign-on.

Single sign-on: what to ask for and what to expect

Single sign-on, or SSO, lets people use the company’s identity provider, such as Microsoft Entra ID or Okta, to log in to every site. It is the cleanest way to solve offboarding, and for a corporate group it is often the feature that matters most.

We want to be careful here. Our own enterprise and Multisite pages do not list SSO as a packaged product. The enterprise page lists it only among systems a build may need to integrate with. So when we say SSO is part of a project, we mean integration work that we scope with you, and not a ready-made switch. Here is how to approach it.

  • Name the identity provider early. The choice of provider and protocol, such as SAML or OpenID Connect, affects the design.
  • Decide how roles map. Does a group in the identity provider become an editor on one site and nothing on another?
  • Keep one break-glass admin. If the identity provider is down, someone must still be able to get in.
  • Test offboarding. Disable a test user in the identity provider and confirm access disappears on every site.
  • Think about readers separately. SSO here is for staff. Public readers, newsletter subscribers and customers are a different login system.

On Multisite, the WordPress documentation says the user table is shared, which is why one set of staff accounts across a network is natural. On separate installs, each site has its own users, so SSO must do the unification. Either way, plan it as a project of its own.

A shared design system

A design system for a group is a set of tokens (colours, type sizes, spacing), components (header, article card, author box, newsletter form, footer) and rules (accessibility, tone, image sizes). It sits in one code repository, and every site consumes it.

  • On Multisite, it lives in the parent theme and shared blocks, and each site picks a brand variation.
  • On separate installs, it lives in a package that each theme pulls in, so a fix reaches every site on the next release.
  • On headless, it lives in the Astro component library, once.

Two things make it work. First, brand-specific differences are tokens, not copies of the code. A brand changes its colour value and logo, not the header component. Second, accessibility is built into the components. Our enterprise page says we design and build to WCAG 2.1 AA with automated checks, manual keyboard and screen-reader passes, and a written conformance statement. A group of ten sites that fix a contrast problem once, in the shared component, saves far more than ten separate audits.

Analytics: one view of the whole group

Pick one analytics setup and apply it everywhere, through the shared must-use plugin or the shared front end. Then decide:

  • One property for the group with a data stream per site, or one property per site with a roll-up. Both work. The decision is a reporting one, so involve whoever reads the reports.
  • A fixed naming scheme for events, so “newsletter signup” is the same event on every brand.
  • One consent setup, with the same behaviour on every site.
  • A shared list of content groupings, such as topic and author, so the group can compare brands.

If you move sites between platforms, keep the old analytics running in parallel for a month, so the before and after compare cleanly.

How do you move, and in what order?

Do not move everything at once. A sensible order:

  1. Inventory and decisions. One to two weeks of audit. Our Multisite page describes the network-shape phase as one to two weeks, ending in a fixed-price quote.
  2. Stand up the platform and the design system. A staging network or staging sites available early. The page says a staging network is available within 7 days.
  3. Move the simplest, lowest-risk site first. Prove the importer, the redirects and the editorial workflow on something that will not hurt if it needs a fix.
  4. Move the biggest brand next, with a delta sync and a rehearsed cutover.
  5. Move the awkward ones last: the custom system, the site with logins, the joint venture.
  6. Retire old platforms last of all, after the media is copied, the redirects are live and the exports are archived.

Our Multisite page puts the build or migration phase at 4 to 12 weeks depending on whether the network is new or built from separate installs, followed by a domain switch of 1 to 2 weeks and 30 days of close monitoring. For a group with many brands, we would run the phases in waves and monitor each wave before starting the next.

Each site’s move follows the rules in our WordPress migration service: map every old URL, test redirects on staging, keep the old site’s search signals, and watch Search Console afterwards.

What does it cost to run afterwards?

We will not print a figure, because a figure without your site count, traffic and integrations is a guess. What you can do is compare the running-cost items for each option:

  • Hosting. One larger environment for Multisite, several smaller ones for separate installs, edge hosting for headless and EmDash.
  • Updates and security. Once for the network, once per site, or once for the shared front end plus the content system.
  • Licences. The plugins that carry licences, counted once or counted per site.
  • People. The hours the central team spends on the shared parts, and the hours each brand spends on its own.
  • Retired platform fees. Each SaaS subscription you cancel is a line you stop paying, and you should list them in your business case from your own invoices.

Ask for the quote to show these side by side, so the comparison covers more than the build.

A checklist for the steering group

  1. Every site is in the inventory, with owner, platform, traffic and integrations.
  2. Sites that must stay separate are marked, with the reason.
  3. The platform choice names the one question that decided it.
  4. Roles and approvals are written down and mapped to the tool.
  5. SSO scope names the identity provider, role mapping and a break-glass account.
  6. The design system has an owner and a place to live.
  7. Analytics naming and consent are agreed once.
  8. Exports for every source are tested before anyone deletes anything.
  9. The move order starts with the safest site.
  10. Old platforms are cancelled only after the redirects and media are checked.

Questions people ask

Is WordPress Multisite good for a corporate blog network?

It is a strong fit when the brands share editors, users and a design system and the group wants one place to run updates. WordPress documents that each site keeps its own content tables and that only the user table is shared. It is a weaker fit when brands need different plugins or release schedules.

Can we merge existing WordPress sites into one network?

Yes. Our Multisite page lists moving existing sites into a network, with their users, content and media, and exporting a site out to its own install with redirects. WordPress’s own notes say the subdirectory type cannot be chosen on an install that has been set up for more than a month, so the network type needs checking early.

Can we move off Webflow or HubSpot without losing content?

Both let you export. Webflow’s help center says code export leaves out CMS content, which exports separately as CSV, with images as Webflow-hosted URLs. HubSpot’s knowledge base describes HTML export and spreadsheet export of blog data. In both cases, forms and platform-specific features need their own plan.

What about Medium and Substack?

We could not read their export documentation for this article, so we make no claim about what the export contains. Run the platform’s export and send us the file, and we will check it before planning.

Is EmDash ready for enterprise use?

Version 1.0 shipped on 28 September 2026, and we run five content sites on it. Our own report says it does not yet fit stores, communities, course platforms or membership sites, and lists problems we hit. For article and page sites it is worth a serious look. For anything with logins or payments, WordPress is still the safer base today.

Do you provide single sign-on?

We scope SSO as integration work inside a project. Our pages do not describe a packaged SSO product, so we do not promise one. Tell us your identity provider and we will say what the integration involves.

The next step

If your group runs blogs on several platforms and you want one place to manage them, start with the inventory sheet above and send it to us. We will tell you which option fits, which sites should stay separate and what order to move them in. Read how we build networks on our WordPress Multisite service page, and see how we handle approvals, security review and procurement on our enterprise page. Then book a free discovery call, and we will reply with a fixed-price quote within 48 hours of it.

Varun Dubey
Founder, Wbcom Designs

Varun Dubey is a full-stack WordPress developer with a passion for diverse web development projects. As a Core developer, he continuously seeks to enhance his skills and stay current with the latest technologies in the modern tech world. Connect with him on X @vapvarun.

Related reading