Most firms do not decide to run five domains. They merge, they rebrand, they keep an old name alive because it still ranks — and one day a single person inherits the whole collection. This article is about the workspace that makes such a portfolio legible, and about the fact that the report it produces will be read by a partner or a board, not by a marketing lead.
One moment changes how a Calgary firm thinks about search, and it is not the moment traffic drops. It is a partner, halfway through a quarterly review, pointing at a slide and asking where the number came from.
The question is not hostile. It is the reflex of someone who signs off on figures that have to hold up later. But it exposes a weakness in most SEO reporting: the number is real, the chart is accurate, and nobody in the room can reconstruct the path from raw data to slide. In a marketing department that is survivable. In front of a partnership it ends the conversation.
The portfolio nobody planned
Calgary is a head-office city, and firms here consolidate. An engineering consultancy absorbs a two-partner geotechnical practice; a professional-services group merges with a rival and keeps both names alive while clients adjust. Each event leaves a domain behind, and nobody switches the old one off, because it still ranks for something — a service page that took eight years to earn its position, a founder's name clients still search.
Five years on the estate is the current corporate domain, two legacy brands still resolving, a separately built careers site, and a microsite from a campaign that ended. All of them carry the firm's reputation. None of them appears in the same report.
The person who inherited them is rarely a specialist — more often a coordinator hired to run proposals. They are not short of tools. They are short of one place where all of it is visible, and a way to explain any part of it to somebody senior.
A feed that answers "when did we decide that", and the filters that keep it readable
Inside the My SEO area each project has a feed called Stream: chronological and mixed. Model answers, automatically generated reports, newly placed backlinks with the donor's domain rating and traffic, system-raised to-dos and campaign news all land in one column in the order they happened.
The value is not novelty — it is that the feed doubles as a record. Six weeks after a decision the question is never "what is the current position" but "when did we start pushing that page, and what were we looking at". A chronological feed answers that in a scroll. A dashboard, which only shows the present, cannot.
One column, five kinds of entry
What actually accumulates in a project feed over a quarter.
- Assistant answers. Kept in place rather than lost to a closed chat window.
- Automatic reports. Generated summaries, timestamped where they belong.
- New backlinks. Each placement recorded with the donor's domain rating and traffic, so quality can be judged later.
- To-dos. Work items raised against the project, each carrying a state.
- Campaign news. What the automation started and stopped doing.
One detail matters more than the rest: the feed is per project. The legacy brand's history stays attached to the legacy brand, so when somebody asks why that domain still exists, the answer is in its own feed rather than in someone's memory.
A feed that records everything becomes unreadable at the moment it becomes useful. Four filters cut it down: All, Links, Files and To-do — placements, exported or uploaded files, and the work itself, each on its own.
To-dos carry three states, and the middle one matters most. Active means somebody is meant to do it; dismissed means it was judged not worth doing; deferred means it was worth doing and the moment was wrong. Most task systems lack that middle state, which is why work in them becomes either urgent or forgotten.
| State | What it means | Where it belongs in a review |
|---|---|---|
| Active | Accepted work, not yet done | The current list — what the quarter is spending effort on |
| Deferred | Accepted in principle, wrong moment | The backlog you can defend: known, judged, timed |
| Dismissed | Judged not worth doing | The record that a decision was made, not an oversight |
In a firm where people rotate, "it was dismissed in March, here is the entry" is a different conversation from a shrug.
Over all of it runs full-text search across every message. That is what turns a year of noise into an archive: search a domain or a phrase somebody used, and the thread comes back with its date attached.
Zero to three data blocks, and why that is the interesting part
The assistant in Stream is not a general chatbot pointed at your account; it is bound to the project's own data. When you ask a question, a router model first decides which data blocks are relevant — Search Console, SERP, campaign, custom — and loads between zero and three of them before the answer is composed.
Read that with the partner's question in mind. "Where did the number come from" has a structural answer: the reply was composed from a named set of blocks. An assistant that always sees everything cannot say which part it leaned on. One that selects a small set can.
Answers stream token by token, so you can tell within a second whether the question was understood and stop rather than wait. Up to twenty messages of history are retained, so "and the other two domains" needs no restatement. Beyond twenty, context falls away — a limit worth knowing before building a long interrogation on it.
The Semalt panel keeps its Search Console, SERP and AI-analytics views as separate, inspectable pages precisely so a claim made in conversation can be checked against a chart. The conversation is the fast path; the chart is the evidence.
Access follows people, and people leave
The panel is multi-tenant. Google accounts link into groups through one OAuth2 consent flow covering Gmail, Search Console and Analytics, and individual sites can be shared to other email addresses instead of handing over an account. Sharing is per site, and so is revocation.
In most organisations that is an administrative convenience. In a partnership it is governance, because partners leave and frequently leave for a competitor. When a principal joins the firm across the street, what they can still see is not an IT ticket; it is something the managing partner wants answered the same week, in a form that can be shown to somebody.
Sharing one site, not the estate
Access is issued per domain to a named address, so a contractor on the careers site never sees the corporate domain's figures.
- Named recipient, not a shared login
- Scoped to the domain in question
- Reversible without touching anything else
Ending access on the day it ends
Withdrawing a site removes that person's view of it, and because the grant was per site, nothing else is disturbed.
- Departure, contract end, change of role
- No password rotation ritual
- The remaining team keeps working
Two practices make this hold up. Never share a Google account where you can share a site; a shared login cannot be revoked from one person. And keep a short list, outside the panel, of who holds access to what. The panel enforces grants; it does not tell you when one has outlived its reason.
Tagging a portfolio you did not choose
Site tags act as a global filter: set one and every list, dashboard and export narrows to the domains carrying it. That is what turns an accidental estate into a portfolio you can reason about.
The temptation is a taxonomy mirroring the org chart: division, practice area, brand, status. Resist it. Deep hierarchies fail predictably — a domain belonging in two branches is filed in one and vanishes from the other, and nobody but the author remembers the third level. Flat tags survive because they combine at the moment of asking rather than the moment of filing.
A flat scheme for a merged firm
Six to ten tags, each answering one question about a domain.
- Origin. Founding brand, first acquisition, second acquisition — why the domain exists at all.
- Status. Active, retained-for-rankings, being retired. The middle value fits most legacy domains.
- Audience. Clients, recruitment, investors — Calgary firms are read by all three.
- Ownership. Who answers for it internally. With one inheritor, mark that as temporary.
With tags in place the awkward question takes one filter: what is the second acquisition's old domain still doing for us? Ranking score, keyword count, clicks, the pages drawing them. In a partners' meeting that is usually the first time the legacy brand's contribution appears as a figure rather than a feeling.
The report goes to a partner, not a marketing lead
Here Calgary's requirements diverge from the standard advice. A marketing lead reads a dashboard, wants frequency and detail, and will click through. A partner or a board reads a document once, in a meeting, alongside eleven other agenda items. They will not click through — but they will ask where a number came from.
The export limits track those two audiences. CSV and JSON run to 10,000 rows — the analyst's format, opened in a spreadsheet to check a claim. PDF is capped at 250 rows and rendered server-side; the cap is a feature, since 250 rows is the outer edge of what anyone reads in a meeting. The builder is configurable and carries your logo and colours, which matters for provenance rather than vanity: a branded document goes into a board pack without explanation.
| Format | Ceiling | Who it is for | What it is good at |
|---|---|---|---|
| CSV | 10,000 rows | Whoever checks the figure | Recomputing a claim independently |
| JSON | 10,000 rows | Anyone joining this to other data | Feeding a finance or CRM model |
| 250 rows | Partners, boards, clients | Standing on its own without the panel | |
| Live view | 50–200 rows a page | The person doing the work | Sorting and filtering while thinking |
The visualisations split the same way. Time series and metric cards carry the narrative; sortable, filterable tables carry the evidence; sparklines show direction inside a row; heatmaps make country and device distribution readable at a glance. A board pack wants two or three of these, not all. Put the chart in the document and the export in the appendix, so "where did that come from" is a file you can send within the hour.
Background workers keep syncing, so the figures are current without anyone pressing refresh — except for Search Console's two-day lag, which is built into the date presets and worth stating in any document dated near a month end. Our analytics articles cover those underlying views in detail.
A week on an engineering consultancy's five domains
Take an engineering firm of about ninety people, two mergers behind it, five domains: the corporate site, two legacy brands, a careers site and a project-showcase microsite. One coordinator, hired to run proposals, now owns all of it. An ordinary week looks like this.
Read the feed, not the dashboard
Fifteen minutes in Stream across five projects: placements recorded, to-dos raised, reports generated.
- Filter to Links, check donor ratings
- Filter to To-do, triage into three states
- Defer anything that needs a partner's view
One question, asked properly
A partner asks whether the older legacy brand is worth keeping. Filter to that tag, then ask the assistant in that project.
- Router loads the relevant blocks
- Cross-check the reply against the SERP view
- Note the conclusion into the feed
Access review
A principal left last month. Their per-site grants are withdrawn; the careers-site contractor keeps theirs.
- Withdraw by site, not by account
- Record the date in the feed
- Note that an April export still exists
Build the quarterly pack
A branded PDF for the partners' meeting: one time series per domain group, one metric row, one table under 250 rows.
- CSV of the same data held in reserve
- Two-day lag stated on the cover
- Deferred to-dos listed as the plan
Total hands-on time: perhaps three hours, most of it on Friday. The automation is not what makes that possible — the record is. Nothing required reconstructing a decision from memory, and the one partner question had a chart behind its answer.
Hold the timing expectation steady: first measurable movement typically appears four to eight weeks in, slower still on a legacy domain with an established position. That suits a quarterly rhythm, which is what a partnership runs on anyway. The campaign automation tiers are documented in full if you need the comparison first.
Frequently asked questions
How many domains does this stop being worth it at — one? Two?
Roughly at three. With one or two domains you can hold the state in your head and a spreadsheet. From three upward — where most merged firms land — the cost is not the analysis but remembering which domain you were looking at and what you concluded last time.
Can I give a partner read-only access instead of sending PDFs?
You can share individual sites to their email address, which gives them the live views. Whether you should is another matter: partners want the conclusion and its provenance, not an interface, and a branded PDF with a CSV on request usually serves better than a login they will use twice.
Someone left for a competitor last week. What exactly do I do?
Withdraw access site by site and note the date in the feed. Then check whether any of their linked Google accounts were the connection point for a property, and re-link it under someone still there. Finally, say out loud that exports taken while access was valid are outside your control, rather than implying a completeness revocation does not have.
Why does the assistant sometimes not use my data at all?
Because the router judged none of the blocks relevant. It loads between zero and three, and zero is legitimate for a general question. Know which kind of answer you received before quoting it, and verify any figure against the view it came from.
Our old brand still ranks. Should we keep the domain?
A commercial decision, but an informed one now. Tag the domain, filter to it, and look at what it earns: clicks, the queries producing them, and whether those are the old brand's name or a service term. A domain ranking only for its former name is worth less than one holding service positions.
What still has to be done by a person
Be precise about the limits; this audience is sceptical by profession and will find them anyway.
- Prioritisation stays human. The panel ranks opportunities by volume and difficulty. It cannot know the geotechnical practice is being wound down and its pages no longer matter.
- Cause-finding stays human. A drop in impressions is visible. Whether it was an update, a competitor's new page or your own migration is a conclusion someone reaches.
- Goal-setting stays human. No model can say whether this year's objective is more enquiries, a better result for a named partner's search, or simply not losing ground during a reorganisation.
- Client and partner communication stays human. Explaining a bad quarter to a board is judgement and relationship. A generated summary is an input, never a substitute.
What the workspace changes is the ratio. It removes the assembly work — collation, chasing, reconstructing what was decided when — and leaves the judgement, which is the part worth a professional's time. On five domains with one inheritor that shift shows up first in how long it takes to answer a partner's question.
For a portfolio that arrived by merger rather than by plan the sequence is: link the Google accounts, tag the domains flat, put the feed in front of whoever inherited them, and build one branded report a partner could read without you in the room. You can open the workspace and connect your first domain in the time it takes to find the legacy site's login. If you would rather have the estate audited first, that is what our consulting engagements are for — and the panel's reporting and export tools are where the conversation with your partnership has to land.