A grip and lighting outfit off San Fernando Road trades under four names, files one tax return and employs twelve people. The owner calls it one business. The search data has never once agreed with him, and settling that argument is what a shared workspace is really for.
Nothing about the four names is a trick. Each exists because a different buyer looks for a different supplier, and nobody wanting a transport quote reads three paragraphs about welding first. They are also four reporting problems pretending to be one.
Four trade names, one payroll
Walk the yard and the arrangement is obvious. A fabrication side builds sets and rigging hardware. Owning forklifts and a yard, it began renting equipment under its own name, renters and fabricators not being the same customer. Rentals had to reach Santa Clarita by six in the morning, so a transport arm appeared under a third name. The lighting and grip divisions then each grew a site of their own.
Four domains, four verified properties, four query sets that barely intersect. One payroll, one accountant, and an owner who thinks of Tuesday as Tuesday rather than as four businesses having four different weeks.
The buyer decides the brand
A production manager sourcing a five-ton truck and a designer sourcing a welded frame are two procurement decisions with different vocabularies.
- Each name matches how one buyer phrases the search
Consolidation costs more than it saves
One domain administers more easily and loses the exact terms that bring work in. Nobody gives up a name a repeat client already types.
- Rebuilding four link profiles into one is a year of work
The person who maintains your site also maintains theirs
Here is the part that surprises people from other industries. The freelancer keeping those four sites alive keeps two competing rental houses alive as well, and everybody knows it. The copywriter who rewrites the equipment pages also writes for an apparel manufacturer in Vernon and, last spring, for a firm the fabrication side lost a bid to.
This is not a lapse in judgment; it is how a project economy staffs itself. The same freelancers rotate through the same twenty companies for a decade, work is seasonal, nobody carries a full-time marketer through a slow February, and the pool who understand both search and this trade would fit in one restaurant.
It does mean access must be granted narrowly and withdrawn without drama. The platform is multi-tenant by design: Google accounts link into a group, and a single site can be shared to another email address and taken back later, one property at a time. Here that is a courtesy as much as a control — handing a freelancer the transport site and nothing else spares her figures she would rather not be responsible for knowing.
Tags by trade name and tags by buyer
Site tags are a global filter, and the temptation is to build them like an org chart — parent business, division, sub-division, site. Resist it. A deep tree encodes one relationship and forbids every other, and a site belonging in two branches makes the structure lie. Flat tags do the opposite: any site carries any number, and a filter is only a selection.
| Tag axis | Example tags | Question it answers |
|---|---|---|
| Trade name | fabrication, rental, transport, lighting-grip | How is each name doing as a business the owner recognizes? |
| Buyer type | production-coordinator, designer, logistics-manager | Which customer finds us at all, across every name? |
| Commitment | retainer, project, dormant | Is the retained budget where the traffic is? |
| Who tends it | in-house, freelance-web, freelance-copy | Which sites have nobody looking after them? |
The buyer-type axis pays for itself. Cross it against trade name and the argument resolves in ten minutes: production coordinators reach three of the four names, designers reach exactly one, and the transport site — which the owner rates his weakest — is the only one a logistics manager ever finds. That is not a ranking problem. It is a discovery about who the customers are.
- Tag on the way in. A tag added when a site is connected costs five seconds. Tagging a portfolio that has already reached nine domains costs an afternoon and never quite finishes.
- Keep the vocabulary short. Twelve tags everyone uses beat forty invented separately by three people. Write the list where freelancers can see it.
- Let sites carry several. The rental site is rental, production-coordinator, facilities and retainer at once. One bucket per site is how filters start producing answers nobody trusts.
- Mark the dormant ones. A name kept alive for one client who still types it should say so, or every review flags it as an underperformer.
One chronological record per project
Stream changes daily habits: one feed per project, in time order, holding what the campaign produces — assistant answers, automatic reports, each backlink as it goes live with its donor authority and traffic, to-dos and campaign news. Nothing needs forwarding, because everyone looks at the same record.
The assistant that is wired to your own figures
For teams whose members are part-time, rotating, and rarely in the same room.
- A router decides what to read. Every question goes first to a routing model that picks the relevant data blocks — Search Console, rank tracking, the campaign, custom sources — and loads zero to three of them. Last week's positions pull figures; how something works pulls none.
- Answers arrive token by token. Text streams as it is produced rather than after a wait, which matters when you needed only the first sentence.
- The conversation remembers. Up to twenty messages of history are kept, so follow-ups behave like follow-ups: ask about the rental site, then "and the transport one?"
- Lists go in by the batch. Keyword and URL lists are taken wholesale — the difference between pasting a spreadsheet column and typing four hundred addresses.
That zero-to-three behavior separates a useful assistant from a decorative one. Without your data a model gives generic advice; loading everything is slow and buries the relevant figures. Selecting a few blocks per question lets an assistant bound to the project's own numbers answer "which of our names lost ground in July" with a figure.
Filters, to-do states and the search box
A year of history is a swamp unless it can be narrowed, so four filters sit above the feed: everything, links only, files only, to-dos only. Links only is the review view — every placement in order with its donor authority and traffic. Files only finds the export sent in March.
To-dos carry three states rather than a checkbox. Active means somebody is expected to act. Deferred means considered and postponed, which is not the same as ignored. Dismissed means examined and rejected — the underused state that saves the most time, because a dismissed item stops resurfacing in every review as a suggestion nobody has explained away.
Work that is expected
An open item with an owner. Where freelancers rotate, the value is that it outlives whoever created it.
- Visible to anyone with access to that site
Decisions that were made
Postponed for a reason, or rejected for one. Both record that the question was asked, preventing the same debate every quarter.
- Dismissed items stop cluttering the review
Full-text search across every message matters most to the freelance model. A copywriter returns in October to a rental site she last touched in February, searches the equipment category, reads the eight exchanges about it, sees which two terms were dropped and why, and starts work in twenty minutes instead of sending an email answered on Thursday.
Exports, PDFs and the argument they settle
Reporting reconciles the owner's mental model with the search record, and the workspace manages it by refusing to take a side. A tag filter produces a per-name report; clearing it produces the portfolio; a buyer-type filter cuts across both.
Know the mechanics before building a template. CSV and JSON exports run to 10,000 rows, comfortably a quarter of query data at this size. PDF renders server-side and stops at 250 rows, less a limit than a description of what a PDF is for. Nobody reads row 900 of a printed table.
| Who is reading | Format | What goes in it |
|---|---|---|
| The owner, monthly | Branded PDF, under 250 rows | A page per trade name, a portfolio total, the two lines that changed |
| The freelance copywriter | CSV of queries | Everything, sorted ascending by impressions |
| A client of the transport arm | Branded PDF, single site | Only the property they pay for, in their colors |
| The office manager, weekly | Screen only | Filtered tables and sparklines, no export at all |
Branding — logo and colors on the report builder — sounds cosmetic and is not. The transport arm sends reports to clients who receive reports from three other suppliers too. A document that looks like yours gets filed under your name; a generic export gets skimmed and lost. A configurable report builder with your own branding is the difference between correspondence and paperwork.
The visualizations favor reading over presentation. Time series show direction, metric cards hold the headline figures, tables filter and sort at fifty to two hundred rows per page. Sparklines put a shape beside a number so a row reads without a second click, and heatmaps take the country and device splits, where the outlier is the point and hides easily in a column.
Five days across four names
As a feature list none of this is worth much. As a routine it is, and the routine for twelve people and four domains is smaller than expected.
- Monday, the office manager, twenty minutes. Open the portfolio with no tag filter, read clicks and health flags across all four properties. Anything that moved gets a note in that site's feed, and nothing else happens.
- Tuesday, the web freelancer, an hour. Rental and transport only. She reads her filtered feed, clears failed URLs from the log, closes two to-dos and defers a third with a line saying the catalog rebuild lands in November.
- Wednesday, the copywriter, two hours. Fabrication only. She exports the query list, reads the bottom two hundred rows, and asks the assistant which new pages collected queries they were not written for. Two answers become a page each.
- Thursday, the owner, fifteen minutes. He filters by buyer type rather than by name — the one view genuinely his — and checks whether logistics managers found the company this month.
- Friday, nobody. Background workers keep the dashboards current with no manual refresh, so an unattended Friday costs nothing. That matters when the team is on a job in Valencia.
Four hours a week across four people, none of them a marketer — the realistic ceiling at this size. The argument for holding several domains inside one workspace is that the same four hours split across four logins would produce almost nothing.
What the workspace will not do for you
All of it removes labor: tab-switching, forwarding, credential sharing, refreshing, the recurring conversation beginning "did anyone find out why the transport site dropped?" It does not remove judgment, and four decisions stay human permanently.
Prioritization first: the panel shows fabrication has more upside than lighting this quarter, not that the crew is booked through November and more work would burn a relationship. Cause-finding second: the record shows the drop, never the reason, and the reason usually sits outside the data. Goal-setting third, because a target is a decision about capacity and margin, not a number extrapolated from a curve. Client communication fourth: a report explains what happened, a person explains what it means for the job starting on the eighteenth.
AutoSEO — one campaign per name
For a portfolio where every domain needs attention and none of them justifies a full-time person.
- Charged per domain, which forces a decision. Four names at $149 is a real number, and it ends the pretense that a dormant site is maintained. Run campaigns on the names that trade.
- Candidates found and ranked automatically. The pool draws on Search Console history, the live results page and your seed terms; each candidate is approved, rejected or deferred one at a time.
- Placement runs on the partner network. Link building draws on more than 230,000 sites — the part no rotating freelancer performs by hand.
FullSEO — for the name that carries the revenue
For the one domain in a portfolio where the vocabulary is contractual and edits need a signature.
- You choose the terms; automation fills gaps. Manual keyword selection with automatic fallback, so trade vocabulary survives contact with more popular and less accurate phrasing.
- Links placed against an authority target. Manual placement with a Domain Authority goal rather than whatever the queue offers.
- Human review before publication. Specialists, developers and writers check on-site changes first — the mode to switch on when a freelancer with competitor clients has edit rights.
The sensible arrangement is not four identical subscriptions: one tier on the name that produces quotes, a lighter tier on the two that trade steadily, nothing on the fourth until somebody says what it is for. Working notes sit on our blog, engagement formats under services.
Five questions from owners running several names
Should we just merge the four sites into one?
Rarely, and never for reporting convenience. Where each name attracts a different buyer with different vocabulary, merging buries all four specialties under a general page and costs the terms repeat clients already type. Merge only where two names serve the same buyer and neither has history. Tags settle the reporting problem far more cheaply.
Our freelancer also works for a competitor. Is it safe to give her access?
Give her the properties she works on and no others, and take them back when the engagement ends. Sharing is per site rather than per account, so she sees one client's figures and not the rest. Say so in advance and revocation never becomes awkward.
How many tags is too many?
Too many is when two people would tag the same new site differently. Keep the list flat and short — a trade-name axis and a buyer-type axis carry most portfolios under ten domains — and write the vocabulary where everyone sees it. Nested structures look organized for a month, then produce filters nobody believes.
Can the assistant tell us why a site dropped?
It can tell you what dropped, when, on which queries and pages, in one sentence instead of four screens. Not why: the cause usually sits outside the account — a canceled project, a competitor opening nearby, a season turning. Treat the answer as a brief for a conversation, not its conclusion.
Do we need a separate report for every client of every name?
Only for clients paying you to work on their site. Filter to that property, apply your branding, keep it under 250 rows so the PDF is worth reading. For your own use export the CSV — no client has ever read ten thousand rows.
The situation does not change. Four names, twelve people, two freelancers who work for the neighbors, an owner who rightly calls it one company while the data rightly insists on four markets. A workspace does not resolve that contradiction; it makes it legible, which is all anybody needed.
What changes is that the record survives the people. The freelancer who leaves in March leaves her reasoning in the feed, and the consultant arriving in October searches it instead of asking. Releasing a single property to an outside address stops being a favor requiring trust and becomes an ordinary administrative step.
Start with the portfolio you have rather than the one you mean to build. Link the Google account and put all four names in one view, tag them by trade name and by buyer on the way in, and give it a month. The first useful discovery is almost never a ranking. It is that one of the names has been doing a job nobody noticed.
