The Domain Written Into the Contract: One Workspace for an Inherited Estate

A booking arrives quoting a company that stopped existing eighteen months ago. The name is copied from a framework agreement signed in 2022, and the shipper's system will keep producing it until that agreement is renegotiated. Somewhere in your estate a website carries that name, and nobody in the room can say whether it is safe to switch off.

Advice about running several websites assumes somebody decided to have several websites. In forwarding it rarely happens that way. The estate is sediment — what settles after a group buys a customs broker one year and a warehousing operator the next, each arriving with a domain, a decade of standing among a particular set of shippers, and a page of authorisations someone's audit department has bookmarked.

Nobody chose this portfolio; it accumulated

A consolidating industry produces domain lists the way it produces legal entities: faster than anyone tidies them. Three transactions in, marketing is minding properties built by people who left long ago, on platforms chosen for reasons nobody recorded.

The instinct is to fold everything into the parent brand and be done. That is usually right for a retailer and usually expensive here, because a freight relationship is documented. The counterparty's procurement system holds a supplier record. The record carries a name. The name may be the one you retired.

These four behave nothing alike, and a plan treating them as one job will either strand a customer or waste a subscription. The first useful act is not technical: it is deciding what each domain is for.

Brand, credential, dead weight

Every domain in an acquired estate falls into one of three categories, and the category decides what follows: what you spend, whether it gets written for, whether it may be redirected, and who sees its figures.

A brand is a name you still sell under; it earns budget, content and rank tracking. A credential must stay reachable because it appears in a document somebody else controls — a framework agreement, a submitted tender, an insurer's schedule. It needs no marketing; it needs to resolve, to state the truth, and to be indexed enough that a search for the old name finds it. Dead weight is neither, and deserves retirement on a stated date.

The credential category catches groups out. From the marketing side it looks like dead weight — flat traffic, nothing worth logging — yet its disappearance produces the call from a shipper whose system can no longer match your supplier record.

A workspace organised the way the estate actually is

Once the categories exist, the working environment has to hold them: one account, a project per domain, each with its own campaign settings, verified Google connection and reporting, and an account above that shows the whole set without four logins. That is the shape the unified panel is built around.

A portfolio-level figure sits alongside the per-project ones: a ranking score over every domain you hold, with a trend line. It answers one question — is the estate gaining or losing ground — and should be asked no other.

A triage that lives only in a spreadsheet is out of date by spring. Site tags are the mechanism that fixes that: arbitrary labels attached to sites and applied as a filter across the whole workspace, so the classification you argued about in a meeting becomes the thing that shapes what you see. Keep two axes and no more — what a domain is for, and who owns it.

• Purpose tags. Brand, credential, retiring. Mutually exclusive, reviewed yearly against the contract register rather than against traffic.
• Ownership tags. Wholly owned, joint venture, partner-controlled. Decides whether anyone on your side may edit a page at all.
• Transaction tags, if the group is still integrating. Which acquisition a domain arrived with. Useful while finance still reports by legal entity, and worth deleting afterwards.
• Nothing else. Tags for service lines or countries duplicate the projects and become a second taxonomy nobody maintains.

One indexing budget, unevenly deserved

The submission allowance is the one resource in the workspace that genuinely is shared. It belongs to the account, not to any single project, so everything you push through it competes with everything else. In a single-site business that is invisible. Across an inherited estate it decides what actually gets crawled this quarter.

Allocation then follows the triage almost mechanically. A brand rebuilt after a rename can absorb the whole day's allowance for a fortnight. A credential site needs a handful of addresses submitted once and confirmed: the entity page, the authorisations page, the contact page procurement was pointed at. A retiring domain gets none — indexing a page you will redirect in March is work done twice.

The half of the estate that is somebody else's too

Terminal partnerships and joint ventures produce a category of website most portfolio advice ignores: one you must report on and may not touch. Your group holds a stake, another group the rest — sometimes a competitor in a different lane — and nothing is published without two approvals.

The workable arrangement is narrow access rather than shared logins. One property is shared to a named address at the partner company; they see that project and nothing adjacent. No password circulates, and it ends cleanly when the venture does.

Two rules make this survivable. The account belongs to a company, never an individual — people leave, and acquired-company logins leave with them. And every grant of access carries a review date, because access nobody revisits outlives its reason.

Three audiences, and none of them wants the same page

An estate assembled by acquisition has an unusual number of people entitled to a report, and entitled to different ones. A steering group wants the estate in aggregate. The managing director of an acquired firm, often still on an earn-out, wants their domain in isolation and reads any blending into a group figure as a slight. A venture partner wants their venture alone. An auditor wants proof a page was live and correct on a given date.

The export formats shape each. Machine-readable output runs to ten thousand rows, where analyst work belongs; the rendered document caps at two hundred and fifty, a discipline rather than a limitation.

The report builder takes a logo and a colour set, which sounds cosmetic and is not mid-integration. A report on an acquired firm's domain in that firm's own marks reads as information. The same figures under the parent's branding, months after a transaction people remain unhappy about, read as a case for closure.

Background workers keep all of it current without a refresh button, which matters when a partner's finance team asks at a day's notice. The published feature overview sets out what each view holds; the value here comes from the projects and tags underneath, not from any single view.

Spending in proportion to what a domain is for

Campaign subscriptions are priced per domain at two levels: 149 USD a month automated, 500 USD managed, the latter adding manual keyword selection with an automatic fallback, manual placement against a donor-authority target, and human review before on-site changes go live. The difference between the two tiers is control rather than capability — the axis an acquired estate cares about.

Per-domain pricing is what makes the triage pay. A brand carries a campaign. A credential carries none: it needs indexing and accuracy, both available without one. Dead weight carries a diary entry. The arithmetic of a multi-year commitment is worked through elsewhere in the English article index; the point here is that category, not traffic, decides whether a domain is subscribed at all.

• Half-owned properties need a funding answer first. If a campaign benefits a venture both partners own, settle who pays before anyone configures anything. It is a shareholders' question in marketing dress.
• Placement add-ons are per unit and bought in fixed quantities. They attach to a campaign, therefore to a brand domain. A credential site has no use for them.
• Expect the first movement in weeks, not days. Four to eight weeks before anything measurable shifts, and an acquired domain with a confused history sits at the slow end.
• Retirement has a cost too. Redirect mapping, amending documents that name the old address, telling counterparties. Budget it once rather than as an emergency.

An estate of this shape generates many small questions, which is where the per-project assistant earns its place. It reads that project's own data, holds a thread of roughly twenty exchanges, and files what it produces — reports, new placements with donor figures, tasks — into a single chronological feed filterable to links, files or open items. Our services pages set out how we sequence that work for a group mid-integration.

Questions this raises

What to do with the domain list this month

Export every domain the group renews. Beside each, write the category and the document that proves it. Where no document exists and no enquiry has arrived in four quarters, propose a retirement date and circulate it — the objections are themselves the audit, and they usually surface one credential nobody had remembered.

Then build the workspace to match: a project per surviving domain, tags for purpose and ownership, access granted property by property with a review date, and the indexing allowance pointed at the domains actually being worked on. Open the panel and set up the first two projects — the brand you are investing in and the credential you nearly switched off — and the rest of the estate will be easier to argue about, because the two hardest cases will already be in front of you.