New

The WPforOps Manifesto. Why WordPress can run more of your organisation than you think.

Read it
Expertise

Multisite & Multi-brand

One governed WordPress platform running several sites or brands. Shared components, central updates, and clear roles, with each site free to serve its own audience.

What it is

Many sites. One platform to govern.

Organisations with several brands, regions, programmes, or subsidiaries often end up with a separate website for each, built at different times by different teams. Every one needs its own updates, security, and hosting, and the brand drifts a little further with each new site.

WordPress Multisite brings them onto one platform. Sites share a design system, components, and plugins. Updates are applied once across the network. Roles decide who manages the network, who manages a site, and who edits content.

Not every group of sites belongs on one network. We assess whether Multisite or separate, coordinated installs suit your structure before anything is built.

When it fits

  • Groups with several brands or subsidiaries
  • Organisations operating across territories
  • Programmes that each need their own site
  • Networks of offices, chapters, or schools
What we do

One network, built to be governed.

  • 01

    Network architecture

    Multisite or separate installs, domains, and structure decided before the build.

  • 02

    Shared design system

    Components and templates every site uses, with room for each brand.

  • 03

    Roles and governance

    Network, site, and editor roles set up so the right people manage the right things.

  • 04

    Central updates

    Core, theme, and plugin updates tested once on staging and rolled out across the network.

  • 05

    Consolidation

    Existing sites migrated into the network with content, users, and redirects intact.

  • 06

    Network maintenance

    Monitoring, backups, and security handled for the whole network.

How we work

How a network comes together.

Planned as a whole, rolled out in order.

  1. 01

    Map

    We map every site, brand, and team the network needs to serve.

  2. 02

    Design

    A shared design system, with brand variations agreed up front.

  3. 03

    Build

    The network built on staging, with roles and governance in place.

  4. 04

    Roll out

    Sites launched or migrated in a planned order.

Multisite projects follow the same six phases as every other WPFlat project.

See our full process
Questions

Frequently asked questions

Can each site have its own domain?

Yes. Each site in a network can run on its own domain, or as a subdomain or subdirectory of the main one.

Can each brand look different?

Yes. Sites share components and code, but colour, type, imagery, and content can be set for each brand.

Can you bring our existing sites into one network?

Yes. We migrate existing sites into the network with a pre-migration audit, redirect mapping, and post-migration testing. See Migrations.

Is Multisite always the right choice?

No. If sites need very different plugins or must be hosted separately, coordinated single installs can serve you better. We advise on this during discovery.

Start a project

Tell us what you need WordPress to do.

A new website, a redesign, a client portal, a booking system, or a move from another platform. Tell us what you need and we will tell you how WordPress can carry it.

What happens next

  1. 01
    Introductory callUnderstanding the project, the organisation, and the brief.
  2. 02
    Discovery questionnaireThe detail we need before designing anything.
  3. 03
    Scope agreementDeliverables, timeline, and investment confirmed in writing.
See how a project runs