Digital Agency for West Malling Businesses

How Organisations End Up With Four Websites

Rarely by decision. A corporate site exists. A product launch needed something and there was no time to add it to the main site, so a separate one was built. An acquired business kept its own. A campaign got a microsite that nobody retired.

Each was reasonable at the time. Collectively they become an estate: several platforms, several hosting arrangements, several sets of credentials, and a growing uncertainty about who is responsible for any of it.

The problems are rarely dramatic. They are a domain nobody renewed, a site running software two years out of date, and nobody quite able to say what would break if it were switched off.

Which Properties Deserve to Be Separate

Separation is sometimes right and frequently inherited rather than chosen.

Genuine reasons include a distinct brand with its own audience that would be diluted by association; a business operating under different regulation or in a different market; something with functional requirements the main site cannot accommodate; and occasionally a commercial reason — a property intended for sale, or a joint venture.

Weaker reasons: it was quicker at the time, a department wanted its own, or nobody could agree how it would fit into the main site. Those produce an estate reflecting internal history rather than what serves visitors.

It is worth asking of each property whether you would create it today. Where the answer is no, consolidation may be simpler than continuing to maintain it.

What Can Be Shared Without Merging

Properties that stay separate need not be built from scratch each time.

A good deal can be common: visual conventions and components, the underlying platform, hosting arrangements, tracking configuration, form handling, and the approach to how content is structured.

The visible identities can differ considerably while the machinery beneath them is shared. That reduces the effort of building each one, makes maintenance predictable, and means anyone working on one property recognises how the next is put together.

Where sites were built by different suppliers on different platforms, none of that applies — which is why estates assembled opportunistically cost more to run than their size suggests.

Platform Decisions Across an Estate

Running several properties on several platforms multiplies effort in ways that are easy to underestimate.

Each has its own update cycle, its own quirks, its own way of doing routine things. Anyone maintaining them needs to know all of them, and a change applied across the estate must be implemented several times differently.

Consolidating onto one platform where it genuinely suits every property is usually worthwhile. Where a property has requirements that platform cannot meet, keeping it separate is legitimate — but that should be a stated reason rather than an accident of who built what.

Where Webflow suits the estate, having several sites on one platform makes maintenance considerably more predictable than the alternative.

Knowing What You Actually Have

The most common gap is documentation, and its absence surfaces at the worst moments.

Worth recording, once, in one place: every domain, when each renews and who holds the account; where each site is hosted and under whose login; which platform each uses; who built it and whether they are still involved; what tracking is installed; and who internally is responsible.

This is an afternoon of work that prevents the situation where a domain lapses because the renewal notice went to somebody who left, or a site cannot be updated because nobody can access it.

Tracking That Can Be Compared

Where properties are set up independently, their analytics usually are too.

Different configurations, different definitions of what counts as an enquiry, different tag arrangements. The result is that performance cannot be compared across properties, and combining the picture means manual reconciliation nobody has time for.

Agreeing conventions — how actions are named, what gets recorded, how sources are categorised — makes the estate legible. It is far easier to establish once than to standardise retrospectively across four differently configured properties.

Avoiding the Same Work Four Times

Duplication across properties is the quiet running cost.

The same policy pages written separately. Similar service descriptions maintained in parallel. Four cookie banners configured differently. The same photograph resized four times because each site expects different dimensions.

Where information genuinely needs to appear on several properties, deciding where it lives authoritatively — and how it gets to the others — prevents versions drifting apart. Where it does not, removing it from the properties that do not need it is simpler.

Who Is Responsible for Each One

Estates accumulate orphans: a site nobody has looked at in eighteen months, still live, still indexed, still representing the organisation.

Assigning a named owner to each property — someone responsible for noticing it exists — addresses most of that. It does not need to be a large commitment. It needs to be somebody rather than nobody.

It also makes retirement possible. Properties that have served their purpose should be closed down deliberately, with their addresses pointing somewhere sensible, rather than left running indefinitely because no one has authority to switch them off.

Working With a Kent-Based Digital Agency

Maidstone Digital is based in Maidstone and works with businesses in West Malling, elsewhere in Kent and further afield. We do not have premises in West Malling. Most work is carried out remotely and reviewed through shared documents and regular calls, though we are happy to meet where useful.

West Malling Digital Agency FAQs

Should we consolidate our websites into one?

It depends why they are separate. Where separation reflects a genuine distinction — a different brand, market or regulatory position — keeping them apart is sensible. Where it reflects how they happened to be built, consolidation usually reduces cost and effort. The question worth asking of each is whether you would create it today.

Can several sites share a design without looking identical?

Yes. The underlying components, spacing and structure can be common while colours, typography and imagery differ. That keeps each property distinct to visitors while making them all quicker to build and more predictable to maintain.

What should we document about our digital properties?

Domains and renewal dates, hosting and platform details, who holds each account, who built each site, what tracking is installed, and who is internally responsible. One document, one location. Most estate problems are access and ownership problems rather than technical ones.

What do we do with a microsite nobody maintains?

Decide deliberately rather than leaving it running. If it still serves a purpose, give it an owner and bring it up to date. If it does not, close it down properly with its address pointing somewhere sensible. What is worth avoiding is an unattended site still representing the organisation.