Managing Multiple Public Sector Websites: Governance, Standards and Maintenance

Running a single public sector website is difficult enough. Running several at once, each with its own audience, content requirements and compliance obligations, is a different problem entirely. County councils, combined authorities, NHS trusts with multiple hospital sites and arms-length bodies all face this challenge. The websites need to be consistent enough that users recognise them as part of the same organisation, yet distinct enough to serve their specific audiences properly. Getting this balance right demands clear governance, shared standards and a maintenance regime that scales across every site in the portfolio. For organisations managing this kind of multi-site estate, working with a team that provides digital services for the public sector brings the structural thinking needed to keep everything aligned.

The problem is not just technical. It is organisational. Multiple websites usually mean multiple teams, multiple content owners, multiple CMS instances and multiple sets of stakeholders with competing priorities. Without a deliberate approach to governance, each site drifts in its own direction. Design patterns diverge. Content standards slip. Accessibility compliance becomes inconsistent. What started as a coherent web presence becomes a collection of loosely connected sites that happen to share a logo.

Why Public Sector Organisations End Up with Multiple Websites

The reasons are rarely strategic. Most multi-site portfolios grow organically over years, driven by a mixture of political decisions, departmental independence and legacy technology choices. A council launches a separate site for its leisure centres because the main CMS couldn’t handle online bookings. An NHS trust runs distinct sites for each of its hospitals because they merged from separate organisations and nobody consolidated the web estate afterwards. A combined authority inherits websites from constituent councils that were never migrated onto a shared platform.

Campaign microsites add to the sprawl. A public health campaign gets its own domain. A regeneration project launches a standalone site. A consultation runs on a separate platform. Each one seemed reasonable at the time, but collectively they create a maintenance burden that stretches already thin digital teams. Each additional site needs hosting, security updates, content reviews, accessibility checks and somebody to take responsibility when something goes wrong.

There are legitimate cases for running separate websites. A council’s trading company might need a distinct online presence for legitimate commercial reasons. A tourism promotion site may have a different audience and tone from the main council website. The problem comes when the decision to run a separate site is made without considering the long-term cost of maintaining it. Every new domain is a commitment. If the organisation cannot resource that commitment, the site will decay. And a decaying public sector website is not just embarrassing. It can actively harm service delivery by providing outdated or incorrect information to people who depend on it.

Establishing a Governance Framework That Works Across Sites

Governance is the foundation that everything else rests on. Without it, multi-site management degenerates into reactive firefighting where each site is maintained in isolation and consistency is accidental rather than deliberate. A governance framework for multiple public sector websites needs to address three things: who makes decisions, what standards apply and how compliance is monitored.

Decision-making authority should be explicit. There needs to be a clear answer to questions like “Who approves new content on Site B?” and “Who decides whether a proposed microsite gets its own domain or sits as a subdirectory on the main site?” In many organisations, these decisions are made ad hoc by whoever shouts loudest. A governance framework assigns these responsibilities to named roles, whether that is a central digital team, a web governance board or a designated lead for each site within the portfolio.

The framework doesn’t need to be complicated. A short, well-written governance document that everyone understands is far more effective than a 60-page policy that sits in a shared drive unread. The key is making it practical. If a content owner doesn’t know what their responsibilities are. If the approval process takes so long that people bypass it, the framework has failed regardless of how thorough it looks on paper.

Maintaining Design Consistency Without Rigidity

When an organisation runs multiple websites, design consistency is one of the first things to erode. Different sites get redesigned at different times, by different teams, using different approaches. Fonts change. Button styles diverge. Navigation patterns vary. The user experience becomes fragmented. People who move between sites within the same organisation feel like they’ve arrived at a completely different place.

A shared design system is the most effective way to address this. A design system is a documented collection of reusable components, patterns and guidelines that any site in the portfolio can draw from. It includes things like typography scales, colour palettes, button styles, form patterns, navigation components and page templates. When every site in the portfolio uses the same design system, visual consistency follows naturally without requiring each site to look identical.

The GOV.UK Design System is the most well-known example of this approach in the UK public sector. It provides a set of tested, accessible components that government services can use. Local authorities are not required to adopt it, but many have built their own design systems drawing on the same principles. The important thing is not which design system you use, but that you have one and that all sites in your portfolio use it. Priority Pixels’ approach to web design for organisations with complex digital estates typically includes establishing these kinds of shared standards early in the project.

Consistency does not mean uniformity. A council’s leisure booking site might need a different layout from the main corporate site. A tourism website will have a different visual identity. The design system should accommodate these differences through flexible tokens and components that can be themed without breaking the underlying patterns. Colour schemes and imagery can vary while typography, spacing, interactive patterns and accessibility standards remain constant across the portfolio.

Content Standards That Scale Across Multiple Sites

Design consistency is visible. Content inconsistency is often invisible until a user encounters it. One site refers to the organisation as “the Council” while another uses “Borough Council” and a third uses the full legal name. Service descriptions use different terminology for the same thing. Tone shifts from formal and institutional on one site to casual and colloquial on another. These inconsistencies erode trust because they make the organisation look disorganised.

A shared content style guide addresses this. The guide should cover naming conventions, capitalisation, date formats, how to write about specific services and the overall tone the organisation wants to maintain across its web estate. The GOV.UK style guide is a strong starting point for public sector organisations. Many councils adopt it wholesale or use it as the foundation for their own guide, adapting specific entries to reflect local terminology and service names.

Content standards also need to address the practical challenge of who writes what and to what standard. When content is produced by subject matter experts across departments rather than by a central content team, quality varies enormously. Some contributors write clearly. Others produce dense, jargon-heavy text that serves internal stakeholders rather than the public. Training helps, but the biggest lever is having a central review step where someone with content design skills checks material before it goes live.

The most effective multi-site content operations share three characteristics: a style guide that people use in practice, a review process that catches problems before publication and a named content owner for every page who is accountable for keeping it accurate.

Where organisations operate in bilingual contexts, such as Welsh language requirements for councils in Wales, the content standards need to account for translation workflows, publication timelines and the specific standards set out in Welsh Language Standards. This adds another layer of complexity to multi-site management, but the same governance principles apply. Clear ownership, documented processes and shared standards keep things manageable.

Accessibility Compliance Across a Multi-Site Estate

The Public Sector Bodies (Accessible Websites and Mobile Applications) Accessibility Regulations 2018 apply to every public sector website individually. Running five websites means meeting WCAG 2.2 AA on all five. Each needs its own accessibility statement. Each needs regular auditing. Each needs a process for fixing issues when they are found. For organisations already struggling to maintain accessibility on a single site, this multiplied obligation can feel overwhelming.

A shared design system helps significantly here. If the components themselves are built to be accessible, with proper ARIA attributes, keyboard navigation, sufficient colour contrast and screen reader compatibility, then every site using those components inherits that accessibility. The investment in building accessible components once pays off across the entire portfolio rather than being repeated site by site.

Automated testing tools like Deque’s axe can run against multiple sites as part of a regular monitoring schedule. They catch a significant proportion of detectable issues, from missing alt text to insufficient contrast ratios to form inputs without labels. But automated tools only identify a portion of accessibility problems. Manual testing with assistive technologies remains necessary. For a multi-site estate, this needs to be built into the maintenance schedule rather than treated as a one-off exercise.

Accessibility statements need attention too. The regulations require each public sector website to publish a statement that describes its current level of compliance, lists known issues and explains how users can report problems. These statements must be kept up to date. After every audit, after every major content change, after every redesign. For organisations running multiple sites, maintaining accurate statements on each one requires a tracking system and clear accountability for updates. Priority Pixels works with organisations on website accessibility to build these monitoring and maintenance processes into the ongoing management of multi-site estates.

Technical Infrastructure for Multi-Site Management

The technical decisions behind a multi-site portfolio have long-term consequences for maintenance effort and cost. Running each site on a separate CMS instance, with its own hosting environment and its own set of plugins, creates a multiplication of maintenance tasks. Every security patch needs applying across every instance. Every CMS update needs testing on every site. Every plugin vulnerability needs checking across the entire estate.

WordPress Multisite is one approach to consolidating this. It allows multiple sites to run from a single WordPress installation, sharing a codebase and plugin set while maintaining separate content databases and admin interfaces for each site. This reduces the maintenance overhead significantly because a core update or plugin update applies across all sites at once. The trade-off is complexity. Multisite installations require more careful management. Issues with one site can potentially affect others if the shared infrastructure is misconfigured.

An alternative approach is running separate WordPress installations but standardising the technology stack. Every site uses the same theme framework, the same core plugins and the same hosting environment. Updates are applied in sequence rather than simultaneously, but the process is consistent. This gives each site more independence while still keeping the maintenance process predictable.

• Centralise hosting so that all sites benefit from the same security, performance and backup arrangements
• Standardise the CMS version and plugin set across all sites to reduce the testing burden for updates
• Automate monitoring so that downtime, security issues and performance problems are caught across every site without manual checking
• Use a shared deployment process so that changes are applied consistently rather than differently on each site
• Document the technical architecture so that it does not depend on the knowledge of a single person

Whichever approach an organisation takes, the principle is the same. Reduce the number of things that vary between sites so that maintenance effort scales as efficiently as possible. Every piece of bespoke code, every site-specific plugin and every custom integration adds to the long-term cost.

Content Review Schedules and Lifecycle Management

Public sector content has a lifecycle. Information about a service is accurate when it is published. Over time, opening hours change, eligibility criteria are revised, legislation is updated, staff names change and links to external resources break. Without a structured review process, pages drift out of accuracy quietly and nobody notices until a resident complains or a freedom of information request reveals that the website has been providing incorrect guidance.

A content review schedule assigns every page a review date based on how frequently the information is likely to change. Pages about services with annual budget cycles might be reviewed yearly. Emergency contact information should be checked quarterly. Statutory content that changes with new legislation needs reviewing whenever relevant regulations are updated. The schedule should be tracked centrally, ideally in a spreadsheet or content management tool that flags pages approaching their review date.

The GDS blog has written about using data to prioritise content improvements. The same principles apply to multi-site estates. Pages with high traffic and high user impact should be reviewed more frequently than obscure pages that receive a handful of visits per month. Analytics data, search queries and user feedback all feed into decisions about where to focus review effort.

Lifecycle management also means being willing to retire content. Public sector organisations are often reluctant to remove pages because someone, somewhere, might need that information. Outdated content actively harms users. A page describing a service that no longer exists does more damage than having no page at all. The same is true of eligibility criteria that changed two years ago. A clear retirement process with proper redirects in place for removed pages protects both users and search engine rankings. Good SEO practice means that retired URLs are redirected to the most relevant current page rather than left to return 404 errors.

Measuring Performance Across Multiple Sites

Performance measurement for a multi-site estate needs to work at two levels. Each site needs its own metrics to track how well it is serving its audience. At the portfolio level, there need to be aggregate metrics that give leadership a view of the overall health of the web estate. Without both levels, it is impossible to identify which sites are performing well, which are struggling and where investment is most needed.

At the site level, the metrics that matter most for public sector websites are task completion rates, user satisfaction scores, accessibility compliance levels and content accuracy. Traffic volume matters less than whether people who visit can complete the task they came to do. A site with modest traffic but high task completion is serving its users well. A site with heavy traffic and poor task completion has a problem that needs addressing.

At the portfolio level, useful metrics include the percentage of sites meeting WCAG 2.2 AA, the proportion of pages reviewed within their scheduled cycle, the average age of content across the estate and the number of outstanding accessibility issues per site. These aggregate measures help digital leaders make the case for investment and identify where governance processes are breaking down. The W3C guidance on evaluating web accessibility provides a solid framework for building accessibility measurement into regular reporting cycles.

Dashboard reporting that pulls these metrics together across all sites saves significant time compared to checking each site individually. Whether this is built into the CMS, provided by an analytics platform or assembled manually in a spreadsheet, the principle is the same. The digital team and senior leadership need a clear, current picture of how the web estate is performing against its obligations and objectives.

Building a Sustainable Approach to Multi-Site Operations

The organisations that manage multiple public sector websites well share some common characteristics. They have clear governance with named responsibilities. They use shared standards for design, content and accessibility rather than allowing each site to develop its own. They invest in technical infrastructure that reduces the per-site maintenance burden. They treat content as something that needs ongoing management rather than a one-off publishing exercise.

None of this is glamorous. It is steady, disciplined operational work that rarely makes headlines. But it is the difference between a web estate that serves its users reliably and one that gradually deteriorates until the next expensive redesign cycle. Public sector organisations have a particular obligation to get this right because their websites are not optional. They are how millions of people access services they depend on. Managing that responsibility well across multiple sites requires the same rigour that the organisation applies to any other part of its service delivery.

Priority Pixels works with public sector organisations to build these kinds of sustainable digital operations. From establishing governance frameworks and design systems to ongoing accessibility monitoring and technical maintenance, the goal is always the same: public sector websites that work properly for the people who need them, maintained in a way that the organisation can sustain over the long term.