An organisation that grows through acquisition can inherit several websites, content systems, hosting arrangements, analytics properties and editorial calendars. Their direct costs appear in budgets. The work required to coordinate them is distributed across teams and is easier to miss.
Multiple sites are not inherently wasteful. Separate brands may serve distinct audiences, propositions, jurisdictions or regulatory contexts. Consolidation is valuable only when the reduction in complexity outweighs migration risk and the commercial value of separation.
The business case therefore needs three things: a complete current-state cost, a strategic brand and audience decision, and a credible account of the transition. Licence savings alone rarely settle it.
This article focuses on the financial and operational case. Our companion piece covers the people, politics and sequencing of post-acquisition consolidation.
Establish why each site exists
Before counting costs, create an estate register. For each website, record:
- brand, proposition and priority audiences;
- countries, languages and applicable obligations;
- owner and decision authority;
- CMS, hosting, domains, certificates and support suppliers;
- integrations, data collection and consent arrangements;
- content volume, quality and update frequency;
- traffic sources, important journeys and search visibility;
- accessibility, security and performance status; and
- contractual, technical or regulatory constraints on change.
Ask the owner to state the continuing purpose of the site. “It came with the acquisition” explains the history, not the strategy. Equally, low traffic does not make a site disposable if it serves a small, commercially important or legally distinct audience.
This register also identifies risks that consolidation may have little to do with, such as unclear ownership, unsupported components or duplicated tracking without a valid data purpose.
Count the direct estate cost
Collect actual invoices and internal allocations for:
- CMS licences and extensions;
- hosting, content delivery and domains;
- maintenance and support;
- security, certificates, monitoring and testing;
- analytics, consent, experimentation and search tools;
- design and development suppliers; and
- accessibility, privacy, legal and compliance work.
Separate costs that would genuinely disappear from costs that would transfer to a shared platform. One CMS licence may replace four, while usage, localisation or enterprise requirements make the remaining licence more expensive. Central hosting still needs capacity, resilience and support.
Account for contract dates and termination terms. A saving that begins two years after migration should not be shown as an immediate benefit.
Measure the coordination cost
The less visible burden often appears in work rather than invoices.
Repeated publishing and governance
Track how often teams adapt or duplicate announcements, people changes, service material, policies and campaign content. Include approval, checking and correction, not simply time in the CMS.
Some apparent duplication is legitimate. Different audiences may need genuinely different language, evidence or calls to action. The avoidable cost is repeated work that adds no audience value, plus the effort required to decide where content belongs.
Use a time sample across several normal weeks and a busier period. Convert effort to cost using a method agreed with finance, while keeping released capacity separate from cash savings.
Fragmented measurement
Several websites can be measured in a combined reporting model. The challenge is inconsistent configuration, identity, consent, definitions and ownership.
Record time spent collecting and reconciling data, then assess the decision consequence. Are leaders unable to compare service demand? Do acquisition journeys cross domains without reliable attribution? Are different teams using different definitions of an enquiry or engaged visit?
Consolidating domains will not fix weak measurement governance. A shared data model, documented metrics and lawful configuration may deliver value before a site migration.
Brand and message divergence
Inconsistency can confuse buyers and employees, especially when two sites appear to represent the same firm with different propositions. The effect is difficult to convert into a percentage of marketing spend.
Use evidence from buyer interviews, search behaviour, referrals, sales conversations and internal content decisions. Describe the consequence before estimating a financial value. A rough percentage inserted because brand dilution “must” cost something weakens the wider case.
Search overlap and content competition
Several domains may target similar queries or publish substantially similar content. That can divide links, editorial investment and reporting attention. It can also be entirely appropriate where brands, regions or user intent differ.
Run a page and query-level analysis. Identify overlapping topics, duplicate or near-duplicate pages, backlinks, branded demand and the destination that best satisfies each audience. Avoid promising that combining domains will automatically increase traffic. Search results can fluctuate during a move, and content quality, intent and technical execution all affect the outcome.
Security and operational surface
Each additional platform, supplier and integration adds components to inventory, patch, monitor and recover. The risk depends on architecture and controls, not a simple multiplication by the number of sites.
Assess unsupported software, access, backups, incident history, data flows, supplier dependence and recovery. Security and privacy specialists should evaluate current and target states. Do not probability-weight a generic breach cost without evidence suited to the organisation.
Compare three strategic options
Full brand and domain consolidation
This may fit when audiences and propositions substantially overlap, the organisation intends to trade under one brand and separate sites create measurable confusion or duplication.
The benefit can include clearer navigation, concentrated editorial investment and simpler governance. The risk includes loss of valuable brand demand, unsuitable compromises between audiences, search disruption and an overloaded central site.
Separate sites on shared infrastructure
A common platform, component library, support model and measurement framework can reduce operational duplication while retaining distinct brands and domains.
This option still requires governance. Teams need rules for shared components, local variation, content reuse, access and release. A single multi-site platform can also create concentration risk: one failure or poor architectural decision affects every brand.
Deliberate separation with improved governance
Keep sites separate when the business case for distinction is stronger than the operational saving. The organisation can still align contracts, security standards, analytics definitions, accessibility assurance and content governance.
This is an active strategy rather than an indefinite postponement. Set ownership and review triggers, such as a brand change, contract renewal, major platform end-of-support date or another acquisition.
The right answer can vary across the estate. Two sites may merge, three may share a platform and one may remain independent because its audience or obligations are materially different.
Build a finance case that survives challenge
Present four categories separately:
- Cash savings: contracts and supplier expenditure that will end, with dates.
- Capacity released: internal effort that could move to higher-value work.
- Risk change: current and transition scenarios assessed by specialists.
- Commercial opportunity: evidence-supported effects on audience reach, conversion, brand or service.
For the change side, include discovery, brand decisions, content audit and rewriting, design, platform work, integrations, data and consent, accessibility, security, migration, redirects, testing, training, dual running, decommissioning and contingency.
Show ranges, assumptions and confidence. Remove double counting. If one content-management saving is already included as staff capacity, do not add the same hours as a marketing-efficiency benefit.
Model each option across the relevant horizon. A shared-platform route may produce earlier operational benefit while deferring brand decisions. A full consolidation may cost more and create greater commercial value. The board needs those differences rather than a yes-or-no case built to favour a predetermined answer.
Protect users and search during a move
Domain consolidation is a service migration as well as a technical one. Every useful old URL needs a destination that serves the same intent, or an appropriate removal response where no replacement exists. Redirecting everything to the new homepage creates a poor user journey.
Google’s current site move guidance recommends planning URL mappings, using permanent server-side redirects where possible, updating internal links and sitemaps, monitoring old and new properties, and expecting temporary ranking fluctuation while pages are recrawled and reindexed. It also explains that sequencing depends on the site: smaller sites may move together, while large estates can be moved in sections.
Use that guidance alongside specialist search, analytics and infrastructure planning. Preserve high-value content and improve weak material deliberately rather than copying every historical page into a new structure. Test redirects, canonicals, metadata, structured data, consent, forms and measurement before and after release.
Keep redirects for the period supported by current guidance and user needs. Monitor search visibility, important journeys, errors and enquiries against a seasonal baseline. Avoid declaring success or failure from a few days of volatile data.
Consolidate for a reason you can name
The cost of several sites is more than several invoices. It can include duplicated publishing, inconsistent decisions, fragmented measurement and a larger control surface. Those costs are real only to the extent that the organisation can observe and support them.
Distinction offers a digital estate cost analysis and may benefit commercially from a consolidation programme. A useful assessment must be capable of recommending continued separation or shared infrastructure instead. If you want facilitated analysis, book that service with us. If you run it internally, use the same discipline: establish why each site exists, count the full current state, compare genuine options and price the transition before deciding that one domain is inherently better than four.
