Ask a county IT director how many websites they manage and the honest answer is often "more than we would like." Parks, the library, the sheriff, health services, the clerk, economic development and tourism may all have their own sites, built at different times by different vendors on different platforms. Each one needs updates, security and hosting. Each one looks a little different.
WordPress Multisite combined with a managed hosting agreement is one of the most effective ways to bring order to that sprawl. AlphaWeb hosts all of Mercer County, New Jersey's WordPress sites, and this post describes the model we recommend.
Why one platform beats many sites
When each department has its own installation, every security patch must be applied many times, every design change is duplicated and every vendor relationship is separate. A single Multisite network changes that:
- One codebase to update and secure
- One design system so every department looks like part of the same government
- Shared features such as alerts, events, staff directories and forms
- Department editors manage their own content without touching others
- One hosting contract, one support channel, one set of documentation
How the network is organized
We usually structure county networks with a main site and department sites in subdirectories or on their own domains with domain mapping. Shared content, like a countywide emergency banner or the main navigation, comes from the main site and appears everywhere automatically. Departments get templates and patterns tailored to their needs, such as facility hours for parks or meeting agendas for boards, but always within the shared brand.
Roles are scoped per site. A parks editor can publish on the parks site and nowhere else. A small group of super administrators controls plugins, themes and network settings. Connecting the network to single sign on means accounts are turned off when staff leave.
Not every site belongs in the network
Some sites have genuinely different needs, such as a tourism portal with heavy custom search or an application with its own data. Those can live on the same managed hosting platform as separate installs, sharing monitoring, backups and security policies without sharing a database. The Visit Mercer County tourism site is a good example of a specialized build that still benefits from centralized hosting.
Scoping hosting for procurement
Public procurement rewards clear, comparable scopes. When we help a government client prepare a hosting quote or respond to an RFP, we spell out:
- Which sites and environments are included, including staging
- Uptime monitoring, response times and escalation paths
- Backup frequency, retention and restore testing
- Security controls such as WAF, two factor authentication and patching cadence
- Update and change management process
- Support hours, emergency contacts and what counts as an emergency
- Exit terms, including full data export in standard formats
Fixed annual pricing per network or per site is usually easiest for budgets and purchasing departments. We avoid vague "unlimited" promises and list the actual services, so finance, IT and legal can all see what they are buying.
Documentation that helps your team
Procurement and audits go smoother with documentation. We provide an architecture overview, a list of plugins and their purpose, account and role policies, backup and recovery procedures and an incident response plan. We are careful to describe the controls we actually operate rather than claim certifications we do not hold.
Migration without disruption
Consolidating existing sites into a network is a project in itself. We inventory each site, map content into shared templates, migrate users and media, and set redirects so bookmarks and search results still work. Our platform migrations page and our legacy CMS consolidation guide cover the details.
Shared features that pay off for every department
Once a county is on one platform, a feature built for one department can be offered to all of them. A staff directory, a public notices archive, an events calendar with filters, a document library, an emergency alert banner or a contact form routed to the right inbox only needs to be built and maintained once. Each department turns it on and fills it with its own content. That is where the long term savings of a shared platform really show up, because every improvement multiplies across every site instead of being paid for again and again by separate departments with separate vendors.
County platform checklist
- Inventory every department site, owner and platform
- Decide which sites join the network and which stay separate
- Shared design system, alerts and navigation
- Per site roles and single sign on
- Clear hosting scope with response times and exit terms
- Documentation for IT, procurement and audit
- Redirect plan for every migrated URL
Frequently asked questions
Can departments still have their own look?
Yes, within limits. Style variations and department specific patterns give each site character while keeping the county brand consistent.
What happens if we change vendors later?
You own everything. WordPress is open source, and we provide a full export of code, content and media.
Is Multisite secure for government?
Yes, with strict super admin control, tested updates and the hosting protections described above.
See our WordPress Multisite services and security and hosting services.
