One domain per market sounded sensible in 2016. Nine years later there are eleven of them, three people hold the passwords, two were inherited with an acquisition, and nobody can say which of the eleven produced an enquiry last quarter.
Portfolios rarely grow by design. A country site here, a product brand there, a domain someone registered defensively and then built on. Every individual decision was defensible. The result is a set of properties nobody has looked at together, which means the most important question about them has never been asked.
That question is not "how is each one performing". It is "are any of them working against each other" — and it cannot be answered one report at a time.
The cost of looking at them separately
While each domain lives in its own tool, a specific cost accrues that appears on no invoice: the time spent assembling. Several logins, several exports, a spreadsheet in which somebody aligns the columns by hand, and a final figure that cannot be verified because it was made by hand.
In organisations with three to five domains, the person responsible typically spends half a working day a month on this. Across a year that is six working days producing no outcome, only data in a comparable shape. The figure never appears in a budget because it is treated as unavoidable — but it is real and it can be counted.
The second effect is more serious and entirely invisible in separate reports. Domains that compete with each other for the same terms split the attention between them, and the number on each individual report looks acceptable. Only side by side does it become clear that one property is holding another down.
What a shared workspace changes
The approach in the Semalt workspace is not one tool per website but one workspace in which several domains, several Google accounts and several people coexist, with filters that apply across all of them.
Three mechanisms that produce the order
None of them is remarkable on its own. Together they resolve the distributed-access problem.
- Linked groups of Google accounts. Several Google logins are combined into one group, so Search Console properties stop living in separate silos and appear in a single overview.
- Issuing an individual site to an external address. One domain can be handed to a different email address — an external specialist, the manager of a regional business — without exposing the rest of the portfolio.
- Site tags as a filter across everything. A tag such as "DACH", "Benelux" or "legacy" applies in every view simultaneously, separating reporting without fragmenting the underlying data.
The third mechanism does the most day-to-day work. Tags allow the same underlying data to be cut several ways without maintaining several reports. The board report filters to everything, the regional report to one tag — same numbers, different frames.
What this arrangement deliberately does not do is worth stating. It does not merge domains, it does not merge campaigns and it does not decide which property should own which role. It creates the conditions for making that decision on comparable figures. Expecting a shared workspace to solve a portfolio problem leads to disappointment; expecting it to make the problem visible delivers exactly that.
What only appears in the comparison
Once the domains sit in one view, patterns emerge that no individual report can show. Five recur so consistently that at least three of them are present at almost every first review.
Two of your own domains, one term
Both rank moderately. Consolidated, one would stand considerably higher than either does now.
- Visible immediately in global ranking
- Decision: one leads, one redirects
The domain nobody maintains
Acquired years ago, untouched since, still consuming attention and holding inbound links.
- Compare clicks per domain first
- Redirect beats leaving it running
Eighty per cent on one property
One site carries almost everything while the others return residual figures nobody has quantified.
- Budget frequently follows the wrong domain
- Tags make the split explicit
Different rules per property
One uses trailing slashes, another does not; one has a sitemap, another does not.
- Align before comparing anything
- Otherwise a year is spent on measurement artefacts
The fourth card causes the most wasted effort. If two properties are technically inconsistent, the first joint review compares things that are not comparable, and the discussion that follows is about the measurement rather than the market. Aligning that is a one-off task and belongs at the start; it forms part of the groundwork described under technical SEO.
A fifth pattern shows up only in international portfolios and is the most expensive to find late: two country sites whose content is the same text in two languages, both targeting buyers who search in English. This happens constantly with Benelux and Nordic markets, where a large share of commercial searching is done in English regardless of the local language. Two properties then compete for the same English queries, each holding a middling position, and both are reported as "performing adequately" in their own market review. Only the shared-keyword column reveals that you are paying twice to publish one page. Consolidation is seldom the answer here. What settles it is naming the property that keeps the English vocabulary and giving the second one a reason to exist that belongs to its own market. Somebody has to say that out loud, because no single report will ever force it. The campaign side of My SEO makes it visible early, since the term pool for both domains is assembled in the same place.
The global ranking view
Position tracking maintains a ranked list across every tracked domain, with a consolidated ranking score per site, average position, keyword count and a twenty-eight-day trend line. It sounds like one more metric; in practice it is the view that settles priorities.
| View | Question it answers | Typical consequence |
|---|---|---|
| Ranking score per domain | Which property stands best overall? | Budget follows the leverage |
| Keyword count per domain | How broadly is each positioned? | Breadth weighed against depth |
| Best pages per domain | Which single page carries the result? | Protect and extend that page first |
| Competitors in the keyword field | Who shares our terms? | Your own domains appear here too |
| Twenty-eight-day trend | Where is the portfolio heading now? | Short-term response rather than annual review |
The fourth row carries the uncomfortable finding. The competitor view lists any domain appearing for the same terms, including your own. For many organisations that is the moment the secondary domain is recognised for what it has become: an in-house rival.
Who should see what
As soon as more than one person is involved, access becomes practical rather than theoretical. The usual state in mid-sized companies is one shared Google login whose password circulates. It works until somebody leaves.
- External specialist. Receives exactly the domain they work on, at their own address. When the engagement ends, access ends — with no password change and no side effects for other properties.
- Regional manager. Sees the reporting for their tag. The colleague running Benelux does not need the German figures in order to understand their own.
- Executive team. Needs no working-level access at all, only a short report covering everything. A PDF of up to 250 rows, carrying your logo and colours, does that job completely.
- Finance or board. Needs comparability across periods rather than currency. A fixed quarterly export serves better than a live login nobody opens.
The gain is less about security than about quiet. When each role sees precisely what it needs, the follow-up questions that arise when somebody encounters a number not meant for them simply stop occurring.
One login for everybody
A single Google account whose password several people know. Changes cannot be attributed to anyone.
- Every departure forces a password change for all
- No record of who altered what
One address per person
Everyone works under their own address and sees only the sites they are responsible for.
- Access ends precisely and without side effects
- Decisions stay attributable
One detail that saves recurring irritation in multi-country teams: the connection to Google is made through a single consent covering mail, Search Console and Analytics together. That replaces three separate setup steps with one, and it removes the most common reason a portfolio quietly loses one of its data connections — an authorisation that expired months ago and that nobody noticed because the other two kept working.
Reports that get read
The report builder allows custom compositions with your own logo and colours. More decisive than the styling are the format limits, because they determine what belongs where.
That produces a simple division. Anything somebody reads goes into the PDF and stays under 250 rows. Anything somebody works with goes into the export and may run to ten thousand. Time series, metric cards, sortable tables, sparklines and country and device heat maps are available through both routes; the only question is whether they will be looked at or processed.
Styling deserves one sentence, because it is underrated rather than overrated. A report carrying the company's own logo and colours gets forwarded noticeably more often than a neutral tool export. This is not vanity: a document that looks like a company document is read as a statement by the company, rather than as a printout from an external system whose provenance has to be explained first.
For the working level a different point matters more. Reporting refreshes continuously in the background, so opening the Semalt workspace in the morning shows yesterday's state — minus the two days of lag with which Search Console data always arrives. Across eleven properties, that removes the ritual of refreshing each one in turn and waiting.
The timeline is the memory
Each project carries a chronological record: assistant answers, automated reports, newly created links with the referring domain's rating and traffic, open and completed tasks, and campaign notices. Filters cover everything, links, files or tasks; tasks can be active, deferred or cancelled.
With one site you remember. With eleven you do not.
At portfolio scale, the record stops being a convenience and becomes the working basis.
- Answers grounded in project data. A routing step decides per question which data blocks to load — Search Console, SERP, campaign or user-supplied — anywhere from none to three by relevance.
- Streamed output, twenty messages of history. Enough to continue a line of questioning without restating it, short enough not to become an archive.
- Links with donor metrics. Every new link arrives with Domain Rating and referring traffic rather than as a bare line in a list.
- Full-text search across all messages. The decisive function at portfolio scale: what was decided about this domain seven months ago, and on what grounds?
Deferred tasks deserve a mention of their own. Across a portfolio, a great deal of work is not wrong, merely not now. A deferred item stays findable without cluttering the active list. Leaving everything open produces a list nobody reviews after a year; cancelling everything loses the reasoning. The assistant also accepts batches of terms and addresses directly, which removes the intermediate spreadsheet.
At eleven domains and four people involved, the timeline stops being a comfort feature and becomes the working basis. It answers the three questions actually asked in a portfolio review: what happened, who decided it, and why is it still open. Where local presence signals were changed for a particular market — service area, address, contact details — those decisions are worth recording alongside, since they are the ones most likely to be reversed accidentally by whoever inherits the site; the practical checks behind them are covered under local SEO.
Bringing a grown portfolio under control
A portfolio assembled over years can be sorted out in manageable steps, provided the sequence starts with an inventory rather than with tidying.
| Step | Action | Result |
|---|---|---|
| 1 | List every domain, including the forgotten ones | a complete list rather than a remembered one |
| 2 | Link the Google accounts into one group | a single overview of all properties |
| 3 | Assign tags along commercial lines | a filter that applies in every view |
| 4 | Read the global ranking and competitor views | your own domains obstructing each other |
| 5 | Define one report per role | an end to the all-recipients monthly email |
| 6 | Record decisions in the timeline | a history that survives staff changes |
Step three rewards care. Tags that have to be reworked later cost more than they save. What works is a small number of clearly separated categories following commercial reality rather than technology. "Benelux" is a usable tag. "WordPress" is not. Which domain should own which terms is decided beforehand during keyword research, and without that assignment even a perfect overview changes nothing.
The portfolio overview, global ranking, tags and reports can be run against your own domains in the Semalt dashboard rather than reconstructed from exports, and background workers keep the figures current without a manual refresh.
Open the portfolio overview in the dashboard
Frequently asked questions
Is a shared workspace worthwhile with only two domains?
Yes, though for a different reason than with ten. At two domains it is not about administrative effort but about whether the two properties obstruct each other. That question can only be answered by looking at them together, and it is as relevant at two as it is at twenty.
What should happen to a domain inherited through an acquisition?
Measure first, decide second. Check how many clicks it still produces and whether external sites link to it. If either figure is meaningful, a carefully mapped redirect to the corresponding pages is better than switching it off. If both are close to zero, it is costing a renewal fee and some attention. Either way, document the decision — a year later nobody will remember why the redirect exists, and it will be removed by accident.
Can an external specialist see only one site?
Yes. Individual sites can be issued to an outside email address without exposing the rest of the estate. That is the practical replacement for a shared password, with the useful side effect that access can be withdrawn precisely when an engagement ends.
How many tags make sense?
As few as possible. Three to five following the commercial split are enough for most organisations: by region, by business line, or core versus legacy. Twenty tags recreate exactly the confusion they were introduced to remove.
Does every domain need its own campaign?
Campaigns are purchased per domain; the analytics remain shared. In practice that means one domain can be actively worked while two others are only observed, without losing the overview. For portfolios where a single site carries eighty per cent of the result, that split is usually the more economical arrangement.
What is the most common mistake when consolidating?
Switching things off too early. A domain with no clicks may still hold valuable inbound links that disappear with it. The order is always inventory, measure, decide, redirect — and only then retire, if at all. The second most common mistake is not recording those decisions anywhere, which converts a deliberate redirect into an unexplained artefact within twelve months.
